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.
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.
I was also impressed but concur that there seems to be significant loss when zoomed out. I'm not sure how they sample for the larger scales, but it seems very inaccurate.
I think that this is an obvious extension of what new businesses have been doing for decades. If you open a storefront, you would do a soft opening to test the idea and then a grand opening to generate traffic.
If I was having a grand opening, I would get every friend there, even if they would never shop at my business, to make the place seem full and busy during the "party".
Obviously this is not on the scale of a start up, but I think the idea of faking initial interest is actually common for any business.
The article hints at how sinister your faking is seems to affect how much backlash you get from it.
I would second a lot of what is said in here and add that I think being a part of a network of similar minded people (i.e. local programming/hacker club) can be just as beneficial as having one official mentor. It may not get you from point A to point B as quickly, but if you aren't really sure where you want to go at this moment, being part of a club can be just as useful as a mentor.
A lot of the anecdotes about incubators that I have heard (and I'm not familiar with StartupChile, so it may not apply at all there) is that a lot of time there is movement between ventures as ideas don't pan out and others need more help.
I feel like being a one-man team can lead to a hard situation where you need more help to have time to get funding and need more funding to get help.
An incubator could be a good middle ground to offer some help and help you prioritize.
> 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.