- Joined
- Aug 20, 2006
- Messages
- 13,000
Microsoft’s recent fumbles with Windows 10 have prompted critical analyses of what is wrong at Redmond these days, and there appears to be a growing consensus that the root of the issue lies strictly in the OS’s development process: contrary to some complaints, Ars suggests the problem has nothing to do with frequency, but that proper planning and coding has been superseded by laziness, which includes identifying and patching problems only after release.
Microsoft's new development process has, proportionately, a greater amount of time spent writing new features, and a reduced amount of time stabilizing and fixing those features. That would be fine if the quality of the features were higher to start with, with the testing infrastructure to support it and higher standards before new code was integrated. But the experience with Windows 10 thus far is that Microsoft hasn't developed the processes and systems needed to sustain this new approach.
Microsoft's new development process has, proportionately, a greater amount of time spent writing new features, and a reduced amount of time stabilizing and fixing those features. That would be fine if the quality of the features were higher to start with, with the testing infrastructure to support it and higher standards before new code was integrated. But the experience with Windows 10 thus far is that Microsoft hasn't developed the processes and systems needed to sustain this new approach.