1809, 1810, 1811, and still counting...

While it is fun to take a humorous look at the huge problem created by Microsoft, in real life it is actually very serious.  In any project management or development life cycle, there are three variables:  features, schedule, resources.  Microsoft paid no attention to these three variables, which will always dictate the outcome of a project.

And, it appears that the insiders, which are supposed to have Microsoft’s ear, had little or no impact on the reality of what was happening.  If Microsoft holds the insiders so dear, why was no action taken?    Are the insiders serving any real purpose?  Time for Microsoft to step back and re-evaluate this approach and make some serious changes.  When you start designing an operating system by a committee of unqualified insiders and a mismanaged group of unqualified developers, 1809 is what you get.

Why, during August and September, was there a Quality Improvement (aka fix) KB released, and re-released, every week?  The lack of quality control in this group has been apparent for a long time.  Remember, 1803 was not released on time because of problems.  And, we can go back further than that, but it would serve no purpose.

John Cable, and his statement about the number of systems affected, is unbelievable, and he should learn to keep his mouth shut on such matters.  He has no understanding of the impact of 1809 on the users and businesses that installed it.  For him to be so dismissive goes straight to the heart of the matter – a team of unqualified developers run by a team of unqualified and inexperienced leaders.  And, you can include Satya in that group.  If he claims he was unaware of the issues, then that is even worse.

There is no excuse for what Microsoft did.  They screwed up, big time.  And, the silence from Redmond speaks volumes.  Any statement or apology is worthless at this point.  Any defense or reason as to “why” does not really matter.

It will take them a long time to repair the damage to the software, and their reputation, if anyone still cares.  They seem to be more focused on not supporting government agencies.  Do not worry.  With releases like 1809, that problem will go away.

Doc

Captain's log - supplemental.  Many of our command and control files are missing.  As such, we have no way to repair the damage caused by the computer software update.  We are preparing for a complete shutdown and restore to an older version of the software.  Life support is now failing, and it is unlikely that we will have time to complete the restore before complete failure.  Oxygen levels are dropping, and the temperature is falling rapidly.

Captain’s Log – Star date 1811.02.  The ship’s computer still experiences widespread failures on all systems since the last software update.   Our only hope is to reach star base before life support is affected.  With engines affected, we have little hope of success.

Absolutely amazing isn't it? I'm sure they will be back to their total ineptitude shortly. They seem to be really committed to it.

Had tons of problems with Win 10 1803, as well as 1709, and never thought that migrating from Vista (the Windows version that worked, by far, the better on my DIY PC, truly loved it) to 8.1, then 10 1709 (unable to install my Asus ROG Strix GTX 1070 drivers) to 10 1803 with it's tons of random hangs and BSODs, to finally find system stability and (for now, since yesterday) with 10 Pro 1803, which seems to work as well as my old Vista 64... Now, I'm quite afraid of how 1809 (or what we should call 1811 now, just as you suggested) will do to the system...