Slashdot Mirror
How Microsoft Develops Its Software
crem_d_genes writes "David Gristwood has a post on his blog that notes '21 Rules of Thumb - How Microsoft Develops Its Software', on which he will elaborate at TechEd in Amsterdam next week. It was derived from interviews with Jim Mccarthy, also of Microsoft. Gristwood: 'As someone who has been involved with software development for over two decades, the whole area of how you actually bring together a team and get them to successfully deliver a project on time, is one worthy of a lot of attention, if only because it is so hard to do. Even before I joined Microsoft, ten years ago, I was interested in this topic, having been involved myself in a couple of projects that, I shall politely say, were somewhat less than successful.' Tips include such features as 'Don't know what you don't know.'; 'Beware the guy in a room.'; 'Never trade a bad date for an equally bad date.'; and 'Enrapture the customers.'"
Naturally, we'll exclude non-profit and free-software vendors because they couldn't possibly have the financial resources necessary to produce quality software.
So you're saying that Linux and its graphical work environments, upon the development of which large companies spend billions of dollars each year, don't have much money? Or are you claiming that a Linux 2.6 box running Gnome or KDE is a piece of shit? Inquiring minds want to know...
*whoooooosh!!*
1. It is possible to program a bug-free program.
2. Security is not an inherent issue with computing.
3. A program that does not work is not finished
4. Computers are made of 0's and 1's.
5. CODECs are temporary in the computer timeline.
6. x = 2 * y means something different in programming than in math.
any old-schoolers care to add some more?