jmileham

7 ms·

31.
by jmileham 14y ago
This is a great example of the complexity tradeoff when you choose performance over atomicity. Delayed::Job has lost favor lately, but the semantics of the job becoming visible to the queue runner atomically with the related new record are
32.
by jmileham 14y ago
Not defending the article's glossing over the subject, but the nutrition facts don't look completely different from one randomly selected meaty equivalent. Both have protein, fat, sodium, iron and carbs in similar proportions, plus or minus
33.
by jmileham 14y ago
I agree with you that this may not be revolutionary, but with some relatively realistic numbers (1300 kg lead car, a giant 1500 kg moose, 80kph road speed, 6m following distance, 7m/s^2 max decel of following vehicles), it looks like you'd
34.
by jmileham 15y ago
I'm not an ActionScript hero, so I can't really weigh in on its awesomeness, but the fact that they rewrote it three times and ultimately ended up with a solid language is to be applauded but not surprising. If you were to put the perfect l
35.
by jmileham 15y ago
I agree, your app looks dangerous in a good way. I think the most important thing is that the loading animation be anchored to the bottom of the loaded content so that it never obscures content that's already loaded. If the user manages to
36.
by jmileham 15y ago
I don't know about you folks, but I find that I can be effective in a lot of professional contexts on relatively little sleep (decision-making, brainstorming, demanding technical meetings, project management tasks), but I rarely get into th
37.
by jmileham 15y ago
I didn't know about the hireable flag either. Cool feature for the genuinely unemployed, but imagine the team morale repercussions of setting your hireable flag to true while in a job you're looking to move on from...
38.
by jmileham 15y ago
I'd guess that the mean request size is misleading though - it is presumably the average of a mix of lightweight CDN requests and gargantuan app requests loaded up with the egregious cookies jgrahamc mentions. It's not hard to imagine a he
39.
by jmileham 15y ago
Yeah, there's an initial hit, but only one DNS lookup per session-or-so if you've got your TTLs right. You're likely to hit hundreds (if not thousands) of assets in a typical Facebook session, though. Edit: Actually, in Facebook's case, Aka
40.
by jmileham 15y ago
Finding exceptional talent on GitHub certainly a solvable problem, but the real challenge for GitHire is the one you can see immediately when you pull up this page: http://githire.com/order In the first few reloads, I've seen John Resig,
41.
by jmileham 15y ago
"We're talking about the average speed of the whole internet" 5% fewer bytes in the request headers would seem to be well within the noise in terms of user experience when you consider latency and application runtime. This is probably a goo
42.
Storing private files in public with Paperclip(engineering.impulsesave.com)
2 points by jmileham 15y ago|0 comments