http://en.wikipedia.org/wiki/2009_Jupiter_impact_event + Missing Belt = Scary

If you want programming to be a lucrative career, you have to think of it as a rewarding career first. A lowish starting salary in a company where you can learn the trade is going to serve you better in the long than a high starting salary with an outfit with no ability or interest for assisting your technical development. To para-borrow, if you're smart and get things done you can get yourself a good salary.

I work in Visual Studio every day during the week, and use Eclipse to pursue non-MS interests when I can. Without having investigated many other open source IDE's, I will say that I think Eclipse is fantastic. (that being why I didn't really investigate further) VS might be more polished and focused in many ways, but Eclipse has amazing breadth and functionality. Sure some of the quirks are irritating, but that is true of any complicated tool.

Dear British,

Please forgive the (sic) my spell check is AE.

Best Regards,
cmsjr

"one of which (the '906) was successfully used in litigation against Microsoft Corp for a $565 million judgement." (sic)

This isn't clear from the article, but other sources indicate that the judgment in question was overturned on appeal, and the case then settled out of court, presumably, for a lesser, but still staggering amount of money.

I don't disagree with any of the arguments you have made, but I think you underestimate the importance of both "idiots" and sound-bites. Policy comes from politicians, not scientists. In a representative democracy, politicians are (loosely) accountable to the electorate, consisting largely of "idiots", who, particularly on complex issues, tend to base their views on sound-bites. If the scientific community, and those who support it, neglect to generate compelling sound-bites and to dispel un-scientific ones, then policies for a given issue will tend to be driven by the rhetorical value of the sound-bites surrounding the issue.

While coding style is certainly important, the most clearly written, nicely commented, richly documented source possible can't tell you if the code does what it's intended to. Formal coding standards may help mitigate the difficulty of debugging and modifying a program, but I think can you get a lot more bang for your buck by implementing a solid testing framework. If I had to pick between coding behind someone with great style, or someone with great unit tests, I'd take the latter.

I am so impressed with Google's approach on this that I am immediately adopting it. From now on, anything personally advantageous that I don't do, well obviously, that was for the good of the geecosystem.

Pardon me now, I have to go read some Ayn Rand.

You just had to add your own spin/2, didn't you.

Purpose is an abstraction of the need to survive. If you want something smart,

1. Start with something simple, mutable, and capable of self reproduction (like a virus or p2p software)
2. Threaten it constantly and ruthlessly
3. Lather, rinse, repeat (billions of times)
4. Hide

I can see your point on it being a labeling issue. When I read "High Multitasker" I envision someone working the help desk, playing an FPS and being active on chat. (and maybe posting some opinionated response on some website)

Stanford scientists have again proven, that anomalous results can, in fact, be generated by choosing unrepresentative models for a behavior or phenomena under study. A particular key for reaching such results in this study was to replace the simultaneous performance of multiple tasks with performing a single task involving multiple inputs and success criteria.