I've seen a lot of programmers go from writing no tests at all, to TDD (and pair programming, etc.). This extreme shift in behavior makes it seem more like a fad; I prefer a balanced approach. Use what works for you and your team, and if it stops working, do something else.
Good for them. But I think in this situation MS typically swoops in and makes a deal with the customer (and even if it's an unprofitable arrangement, why not keep the other guy from gaining revenue and headlines?).
Regarding the message in your edit, thanks for your post--this is (mostly) a helpful discussion. Just search for the dollar signs (norcalgrrl had a good response, as did a few others).
"every year he tops out at about 60% of his time being billable"
Another general guideline is to estimate 1,000 hours of billable work (which makes it easy to calculate an hourly rate for some amount of desired annual earnings).
"Also, don't forget taxes."
Definitely don't forget the taxes, especially estimated payments. Consider that 40% of that money, once deposited, isn't yours and is untouchable, and you'll be better off.
That gossip is best left unsaid, but my advice if you are looking to work at Apple - choose the team you join carefully. Apple's most secretive teams are also the most talented and brilliant folks I've ever met. But they work hard to be friends of Steve.
