Sorry, I'm British (I just happen to live in the Bay Area) and I don't get it either.
Maybe you should clearly explain your problem with 'USAmericans'.
What are they anyway? Is that as opposed to South Americans?
Thank you. I think this is one of the first/. posts I've seen where the person doing all the talking actually has some experience of the situation.
I've spent some time in Redmond for meetings (WSI), and it looks like a cool place to work. I've also spent some time (and money!) in the company store, salivated over the nice plasma tv / media pc and felt a little geeky in the musuem.
From what I see and hear from my MS friends its a great environment.
Yep we do an incremental build every night, and a system build (clean build) once a week.
Of course, we build a compiler and then use that to compile our own code each week, which used to add an interesting wrinkle when some one broke the checker or linker the night of a system build.
these days we have a delivery system that does a build, and only if that works (and passed automated tests) does the delivery system pass the component into the nightly, and then weekly build.
we've been doing that since I wrote the delivery system 5 or 6 years ago. we compile 2 compiler/ide products (think visual studio like) a code analayse tool and an integration server 5 days a week.
takes about 3 hours to build each compiler/ide suite and 1-2 each for the analasis/IS tools.
Of course MS also used to have a tester per developer (not sure they still do) so unit testing gets done each day by someone other than the developer. I still have to do my own:-(
I like a good ranter as much as the next person, but please, couldn't you keep it a bit shorter next time? In fact most of the time the anti MS posts are pretty funny, if only becuase they're so full of crap.
I suspect that NT BSD'd on you, right in the middle of a 6 hour coding session - with no save right? Something must have put that bug up your butt..
Can I tell my fiance that her assumption that they are made of sugar and therefore I shouldn't eat them doesn't hold true, quantum'ly?
hmm, this theory could work you know..
"There is still some controversy about why this seemingly simple error could have such severe consequences, but a popular theory attributes it to the use of the Windows NT operating system"
So the divide by zero error causing everything to stop was because of Windows? Erm NO.
It was caused by bad software design, coding or piss poor testing. probably all 3.
I can give you a divide by zero peice of code that'll fail just as well on Linux, Unix, AIX or a couple of other playforms if you like.
Slashdot Mirror
Sorry, I'm British (I just happen to live in the Bay Area) and I don't get it either. Maybe you should clearly explain your problem with 'USAmericans'. What are they anyway? Is that as opposed to South Americans?
Thank you. I think this is one of the first /. posts I've seen where the person doing all the talking actually has some experience of the situation.
I've spent some time in Redmond for meetings (WSI), and it looks like a cool place to work. I've also spent some time (and money!) in the company store, salivated over the nice plasma tv / media pc and felt a little geeky in the musuem.
From what I see and hear from my MS friends its a great environment.
well to be fair only the kids from computer club who ALSO read /. will shun you. The others may be a little more , err.. balanced?
Yep we do an incremental build every night, and a system build (clean build) once a week. Of course, we build a compiler and then use that to compile our own code each week, which used to add an interesting wrinkle when some one broke the checker or linker the night of a system build. these days we have a delivery system that does a build, and only if that works (and passed automated tests) does the delivery system pass the component into the nightly, and then weekly build. we've been doing that since I wrote the delivery system 5 or 6 years ago. we compile 2 compiler/ide products (think visual studio like) a code analayse tool and an integration server 5 days a week. takes about 3 hours to build each compiler/ide suite and 1-2 each for the analasis /IS tools.
Of course MS also used to have a tester per developer (not sure they still do) so unit testing gets done each day by someone other than the developer. I still have to do my own :-(
I like a good ranter as much as the next person, but please, couldn't you keep it a bit shorter next time? In fact most of the time the anti MS posts are pretty funny, if only becuase they're so full of crap. I suspect that NT BSD'd on you, right in the middle of a 6 hour coding session - with no save right? Something must have put that bug up your butt..
Can I tell my fiance that her assumption that they are made of sugar and therefore I shouldn't eat them doesn't hold true, quantum'ly? hmm, this theory could work you know..
"There is still some controversy about why this seemingly simple error could have such severe consequences, but a popular theory attributes it to the use of the Windows NT operating system" So the divide by zero error causing everything to stop was because of Windows? Erm NO. It was caused by bad software design, coding or piss poor testing. probably all 3. I can give you a divide by zero peice of code that'll fail just as well on Linux, Unix, AIX or a couple of other playforms if you like.