Nope, I'm always there on day 1 also :D. They always do such a great job, I'm always around poking installing/trying out new enhancements and sub projects for at least a week.
There are ethical and economical reasons for low to zero-cost mp3s.
1. The artist actually gets even more of a shit deal with digital distribution than they did with physical media. You are supporting the machine, not the musician.
2. The cost of developing a quality recording has plummeted dramatically, the only substantive cost remaining is the advertising. The exception might be for faux artists like Rihanna that hire top notch songwriters to pen hits, but for lesser known musicians, mp3 distribution has been shown in studies to have a positive impact.
3. mp3s can function as the advertising medium itself. The money can be made elsewhere like endorsements, or touring. Live music can never be "stolen".
Get out of the company. Find yourself something laid back where you can see your family as much as you would like. Sounds like you have the resume to push telecommuting during hiring negotiations.
Compiler safety for the design. Implement a base class, and force implementation for sub classes. I know that CS philosophically is about keeping JS's openness, but I feel it would be a time saving convenience if the compiler told me I was missing a method.
Crunchpad anyone? I found him too infrequent to be a major reason to visit the site. I suspect that most of the traffic hit techcrunch thanks to the endless link baiting of MG or popularity contest blather like their Twitter "coverage". Twitter used to be every other feature.
Other big winners were Sarah Lacy saying that old media is dead and no one wants to be a journalist at WSJ (how did that turn out btw) or other random bouts of idiocy (RSS is dead!)
Frankly, Techcrunch has long been a source of tech trolling. For trolls, by trolls. Its no wonder it went under - the sugar high simply ran out.
After everyone saw how it easy it was to write your own blog in Rails, everyone ... used Wordpress anyway.
The Rails use case was always truly limited. I still don't know any application that achieved maturity and stayed coded in Rails. For a while that was Twitter, but then they started moving stuff over the jvm.
Node will probably end up in a similar way, because at the end of the day no one wants to manage thousands of lines of Javascript (or any other language that doesn't enjoy the benefits of a statically typed ide).