Is what I would be saying if I worked for Microsoft PR. Check this quote from some blog Mark follows.

Here is the thing with software development, you pay for your incompetence. The only choice is whether you pay for it up front with bad PR, or over the course of the product lifecycle through support, angry customers, lost future sales, renewals and so on.

So Microsoft took their flagship product, bumped the public availability release one week to work out the kinks. Is anyone REALLY going to be all that inconvenienced with this delay? And what is Microsoft being beaten up over, the fact they found a problem and tried to address it before they endangered a ton of systems on what is the most widely deployed operating system… ever?

There are plenty of good reasons to smack Microsoft around, production delays for QA is not one of them. I know SPFs that can fix everything because they work by themselves in a moldy basement can’t grasp the concept of software development with worldwide teams comprised of thousands of engineers and personnel all being all on the same page… It’s different than Bob the SPF being able to fix the decaying thermal compound on his eMachines server thats 3 feet to the left, just slightly more complex.

You can leave a response, or trackback from your own site.