Slashdot Mirror
Inside The Development of Windows NT
mrpuffypants writes "Winsupersite has a 3 part series this month about the history and development of Windows NT all the way up through Windows Server 2003. The author goes fairly in-depth describing how Windows is developed, managed, and how all 50 million+ lines are compiled daily. Part One covers the history of NT from its early days at Microsoft and Part Two discusses how the deployment of the forthcoming server version of Windows is coordinated daily." *shiver*
The stuffed mascot in the background looks an awful lot like someone else we know ;)
#!/bin/bash
You are not the customer.
0) CVS checkout the latest net stuff from freebsd.org
1) Look at code and scratch head until "A-ha!"; enlightenment.
2) Merge code into Windows source
3) go to 0
Trolling is a art,
We thought, 'How hard could it be to build an OS?' and scheduled 18 months to build NT. But we had forgotten about some of the important stuff--user mode, networking, and so on."
Either this means that the NT team were actually fairly clueless...or incredibly cocky. Either way, that seems like a pretty stupid thing to say.
"You compile it today."
"No way--*you* compile it!"
"No way! Hey--let's get Mikey, he'll compile *anything*!"
"By late 1989, the NT group began growing. They added a formal networking team and expanded the security team beyond a single individual who, incidentally, had also been previously burdened by file system and localization development."
You mean they've got more than one guy working on security for Windows? Oh come on, who's gonna believe that?
I thought it was forged deep within Mt. Doom...
Engineers: "No problem, we'll release betas every year and you can sell them to the public for the price of a finished product."
Bill Gates: "Good idea. What do you think Steve?"
Steve Ballmer: "Developers, developers, developers, developers, developers, developers, developers, developers, developers, developers, developers, developers...*wheeze* *hack* *cough*...."
Bill Gates: "It's ideas like those that will make you CEO in 10 years."
"On the day I attended, one feature group had four of its bugs punted to Longhorn because they had failed to shown up for War Room. When someone argued that they should be given another day, Wanke simply said, "F#$% 'em. If it was that important, they would have been here. It's in Longhorn. Next bug."
Did one feature group have its *feature* postponed to longhorn or the *bug-fixes* postponed to longhorn ? hmmmmmm interesting.
"For Windows Server 2003, the War Room is run by Todd Wanke, who we eventually found to be an amazingly likeable guy. However, in the hour-long War Room sessions, Wanke rules with an iron fist" :)
"...compiling and linking it into the executable and other components that make up a Windows CD is a 12 to 13 hour process that is done every day of the week
So they rebuild Windows from scratch every day? Somebody send them a copy of make, please.
...the War Room is run by Todd Wanke...
Oh dear. Poor Todd.
"We thought, 'How hard could it be to build an OS?' and scheduled 18 months to build NT. But we had forgotten about some of the important stuff--user mode, networking, and so on."
I think that sums-up Microsoft perfectly.
A programmer is a machine for converting coffee into code.
To be honest, I don't see why they just don't hold these bug fixing meetings around the IIS guys desk :o)
Avantslash - View Slashdot cleanly on your mobile phone.
There are 5000 developers on the Windows team generating over 50 million lines of code for Windows Server 2003.
I think it's safe to say that they're most defniitely _NOT_ using VSS!
There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
I guess this statement neatly sums up the attitude behind much of their corporate culture.
Off topic but....
Give a man a fish, he owes you one fish.
Teach a man to fish, you give up your monopoly on fisheries.
My favorite...
Build a man a fire and he will be warm for the night. Set a man on fire and he will be warm for the rest of his life.
Be nice to people on the way up. You will meet them again on your way down!
"My god, it's full of crap!"
Malike Bamiyi wanted my assistance.
So in a couple of years we'll learn that:
...for not showing up to the goddamned meetings with his bugfixes.
-Looking for a job as a materials chemist or multivariat
50,000,000 lines of code / 5,000 developers= 10,000 lines of code for each developer/
Spread that over a 3 year development cycle. Thats only 9.13242 lines of code a day per developer! How much are they getting paid? Sign me up!
Looks like one of our guys is on the inside. Caught him on film. He's infiltrated the war team. Check him out, in the background by the TV...
See it here
When someone argued that they should be given another day, Wanke simply said, "F#$% 'em. If it was that important, they would have been here. It's in Longhorn. Next bug."
C#, J#, S#....now we have F#....shall we pronounce it "Fuck Sharp"?
[chanting] Developers, developers, developers, developers!
Not All Who Wander Are Lost
That "goto" in line 3 prevents lines 4 and 5 from working:
4) ???
5) Profit!
(Not that Micro$oft needs anymore of that.)
That mascot is probably reserved for voodoo rituals :-) Geek or not, it's still MS... :-)
The ENIAC Demo Competition
> "NT 3.51 was a very unrewarding release," Thompson said, contrasting it with
> Daytona. "After Daytona was completed, we basically sat around for 9 months
> fixing bugs while we waited for IBM to finish the Power PC hardware. But
> because of this, NT 3.51 was a solid release, and our customers loved it."
I wonder why I think so bad about Microsoft products?!
-fren
"Where are we going, and why am I in this handbasket?"
You've been living in a cave, perhaps? ;-)
Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
The Theorem Theorem: If If, Then Then.
Ahh, good ol' sed. I wonder if he used the Windows version, or if he booted up the Linux box? :-)
This just goes to show that even the biggest software developers have to deal with "simple" requests like name changes that are very inefficient uses of engineers time. I want to know what super-duper advanced bug system they use.
My beliefs do not require that you agree with them.
Microsoft's record of "innovation" has sunk to a new low -- now it looks like they are going to embrace-extend-exterminate Tux. These bozos can't even invent their own mascot...but then again, a furry, squishy bug (the animal most reminiscent of Windows, IMHO) isn't the most inspiring marketing tool.
Bet they claim they had a penguin for a mascot all along and it was those hippies, foreigners and un-American freaks that stole their idea and made Tux the mascot for that mean ole' Linux.
How typical.
"We should be able to reproduce that [build] three years in the future, using the various tools, compilers, and scripts we used at that time."
amazing... they figured out CVS, aren't they special.
all brought down routinely by 5 line scripts :(
Boy, its a good thing that no frame buffers are in the Linux kernel.
http://saveie6.com/
What are you people blind?? That is not a penguin--it's a puffin.
And when finally that CPU had come to the end of its working life and was finally retired, it's package was broken open and was found to be filled with some kind of organic matter. DNA analysis found its origins were from three men; Judas, Brutus, and Cassius
Rich
I guess it's true: What Intel giveth, Microsoft taketh away...