Well "Sherlock Holmes Debugging" may be redundant, since this is really just "debugging" (though who would have clicked on that link?), I was most excited by this line:
> There is no sin in software engineering more serious than thinking some behavior of a computer system is magical or beyond our understanding.
I've been trying to find a good test case to get my junior engineers to step out of their code and see more of the layers. This is a pretty good mantra for improving your debugging skills.
Very neat! When I clicked around, it looks like a few of the places categories come back with all the places as "undefined". I got this for bakeries and food markets.
The golf part is that you can only get the most points by writing the shortest regex possible. However, I think the game avoids just giving a score based on the number of characters. To do that, you would be required to match all on the left and none on the right (the equivalent of actually getting the golf ball in the hole). This game lets you pick up your ball whenever you want and scores you based on distance to the hole. For the golfers, think of it more like a closest-to-the-hole competition than the more common stroke play.
I was thinking the same thing. First one I saw was for the Eiffel Tower, which took 300 people 2 years, so that should actually show as 600 years, not 2.
Not to mention the time required to design it, the time spent by workers to collect the raw materials used to build it, the time spent in factories to produce a finished metal product that could be used in construction, etc.
Attempting to calculate the man-hours that went into almost any project of scale is absurd. There are far too many factors to consider.
You have to pay for the one electron. Since it's the only electron, the cost is infinite. This results in a buffer overflow. Your utility bill is an overflowed unsigned short, divided by 100. This is why the maximum utility bill you will ever see is $655.35.
I find your streak particularly impressive, since it is all public contributions. The authors streak (as well as any, much shorter, streak that I have made) has always relied much more heavily on private repos for personal projects.
Hmmm... Well you may want to actually put that on your website. And you probably want to be careful, since you've posted comments on here like "all the rest documentation can be found at Amazon S3 documentation site, it is basically the same with small differences" and you have "Amazon" on the sign, which is above the "fold" on my screen and pretty much the first connection I made on S3. If your entire website doesn't scream "we are just like Amazon S3" then I must be missing something.
I was really thinking this was going to be a pretty lame list (which probably puts my in with the other people who have time suck issues). I was pleasantly surprised though. A few good recommendations. I especially appreciate the reminder to journal more.
Yeah, I also found it very well-written, reasonable and honest. I'm in a kind of impressionable phase, in a good way, where I look at things like this like "whoa, minimize time sinks, that is a great thing, let's do that."
One thing I've started to learn in my 20's is to really enjoy myself. Seems fairly important, don't know why I didn't think of it earlier...
> There is no sin in software engineering more serious than thinking some behavior of a computer system is magical or beyond our understanding.
I've been trying to find a good test case to get my junior engineers to step out of their code and see more of the layers. This is a pretty good mantra for improving your debugging skills.