Windows 10 News and info | Forum
November 12, 2018, Loading... *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: This is a clean Ad-free Forum and protected by StopForumSpam, Project Honeypot, Botscout and AbuseIPDB | This forum does not use audio ads, popups, or other annoyances.
 
  Website   Home   Windows 8 Website GDPR Help Login Register  
By continuing to use the site or forum, you agree to the use of cookies, find out more by reading our GDPR policy.
Pages: [1]
  Print  
Share this topic on Del.icio.usShare this topic on DiggShare this topic on FacebookShare this topic on GoogleShare this topic on MySpaceShare this topic on RedditShare this topic on StumbleUponShare this topic on TechnoratiShare this topic on TwitterShare this topic on YahooShare this topic on Google buzz
Author Topic: Microsoft accused of a fundamentally flawed Windows 10 development process  (Read 30 times)
javajolt
Administrator
Hero Member
*****
Offline Offline

Gender: Male
United States United States

Posts: 29153


I Do Windows


WWW Email
« on: October 21, 2018, 05:58:20 PM »
ReplyReply

By now we are all aware of the fiasco which has been the release of the Windows 10 October 2018 Update, but we probably already forgot that the April 2018 update was also delayed due to late-breaking bugs which caused blue screens on some PCs.

Ars Technica has taken a closer look at the development of Windows, and they believe Microsoft’s process of developing their operating system was flawed from the get-go,  all the way back to even Windows 7.

They note that Microsoft has a process of actually writing code for new features of only a few weeks, and then spending the rest of the time (of several months) integrating the software and then ironing out bugs before release. This meant poor quality, the unreliable software was introduced to the Windows 10 code base, and if issues are not found, delivered to the end user.

Coupled with an ineffective testing regime, in part due to Microsoft firing their SDTs in 2014 and placing more responsibility on developers to test their own code, and a Windows 10 Insider process by amateurs which was not comprehensive and which did not deliver professional bug reports, meant more than a fair share of bugs ended up being shipped.

Ars Technica also confirmed that Windows developers were allowed to integrate code without any testing at all, though hopefully, this was the exception.

They called for a change in Microsoft’s development process and asked that new software be well tested before integration using modern techniques such as automated testing, meaning that even Insider builds will have high quality, well-tested code with no “known issues”.

They note:

Quote
A new feature might be unstable during its development, but before that feature can be merged into the production code, it has to meet a very high-quality bar. Rather than Microsoft’s approach of “merge the bugs now, we’ll fix them later,” the approach is to ensure that code is as bug-free as possible before it gets merged.

They conclude:

Quote
Adopting the principle that the Windows code should always be shipping quality—not “after a few months of fixing” but “right now, at any moment”—would be an enormous change. But it’s a necessary one. Microsoft needs to be in a position where each new update is production quality from day one; a world where updating to the latest and greatest release is a no-brainer, a choice that can be confidently taken. Feature updates should be non-events, barely noticed by users.

Ars Technica holds Google’s Chrome team up as a company that is doing it right, and with ChromeOS becoming an increasingly viable option, Microsoft can certainly not afford to lose more trust from end users.

source
« Last Edit: October 21, 2018, 06:04:55 PM by javajolt » Logged



Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2017, Simple Machines

Google visited last this page November 08, 2018, 10:21:08 PM