Software Engineering at Microsoft
an_mo writes "A link to a google cached document is floating around some mailing lists containing some info about microsoft software engineering. In particular the document contains juicy bits about the development of a large project like NT/2K. Some examples: Team size went from 200 (NT3.1) to 1400 (Win2k). Complete build of win2k time is 8hrs on 4way PIII and requires 50GB of hard drive space. Written/email permission required for checkins by the build team." The HTML version on Usenix's site is much nicer than Google's auto-translated version.
So, the first day after checking out the source for the first time will be completely unproductive... Let me see, 1440 man days is about 7 man years which is about $210,000 in salary alone. Disk would be at least $144,000. Hmmmm.
And 1440 is a hell of a lot of people to be working on one project. I know there'll be a lot of smaller sub-projects, but trying to co-ordinate anything would be a managerial nightmare!
The UML is NOT a fad. I can only suggest that you never decide to become a software architect as opposed to just coding for non-profit.
As for the 'phenominal success' of OSS, please point me to the profits, ok? Linux is great, but Phenominally successful? In what universe? When you and your 80 year old grandma can run any CDRW or scanner that YOU want, and not have to re-complile every time you change your socks, then maybe.
As for Code Review, even the best coders can always learn something, and no one is mistake proof. Oh, let me guess; you finished your "Learn Java in 24 hours book, and now you are untouchable, right? One clue; good developers cost a LOT MORE than 20-40 an hour, partner. You better get another book, and buckle down.
For now, I suggest you re-evaluate your statements.
Not only is this old (read it months and months ago)... and what is so "juicy" about it? So it gives a brief detail of the lifetime of a big software project. What do you think Lightwave3D is like? Maya? Shake? This isn't anything leaked or top-secret. This is just a little short about the history of the engineering of a project. Big deal. Can't wait to see the next kernel patch level.
Why bother.