Microsoft has been making quality assurance mistakes lately
computerworld.com
Microsoft has been making quality assurance mistakes lately
1–10 of 62 posts
Re: Microsoft has been making quality assurance mistakes lately
#2Since the HN guidelines ask for linkbait titles to be changed, we changed the somewhat baity title to a representative sentence from the article.
Re: Microsoft has been making quality assurance mistakes lately
#3Since the HN guidelines ask for linkbait titles to be changed, we changed the somewhat baity title to a representative sentence from the article.
dang, have you considered aggregating these kinds of notifications onto a separate page, or maybe using a specific account for administrator action? It would be helpful for those of us who value transparency (and thank you for your continued transparency - it has been great).
Re: Microsoft has been making quality assurance mistakes lately
#4Since the HN guidelines ask for linkbait titles to be changed, we changed the somewhat baity title to a representative sentence from the article.
Thanks for letting me now. I appreciate it.
Re: Microsoft has been making quality assurance mistakes lately
#5The title seems to apply to Apple, too (see iOS and Yosemite WiFi bugs), and could probably be applied to Google, too (Hangouts bugs, Lollipop problems, etc). But mistakes happen and many bugs are less obvious to reproduce than others, so I wouldn't point fingers too hard, personally.
Re: Microsoft has been making quality assurance mistakes lately
#6This is exactly what I thought would happen when they gutted their QA staff and reassigned the surviving testers as developers. Your employees act in accordance with their incentives, and the incentives aren't there for QA. Microsoft made it clear that they only value feature development and shipping, and their employees now associate "doing QA" with "being fired en masse".
To corrupt a phrase, they've crapped their bed and now they have to lie in it.
Edited to add: I'm not some hardcore "M$FT SUXXXX" guy. I like and use their products, but I'm deeply concerned about the direction the company seems to be heading.
Re: Microsoft has been making quality assurance mistakes lately
#7Unless I'm missing something, this article really seems unreasonably harsh. He cites two bad updates within the past months (one for Windows 7, one for Exchange) that have had to be pulled due to issues, but it seems like well over half the article is devoted to complaints about patches for Windows 10 - an (officially) unreleased product.
Re: Microsoft has been making quality assurance mistakes lately
#8Unless I'm missing something, this article really seems unreasonably harsh. He cites two bad updates within the past months (one for Windows 7, one for Exchange) that have had to be pulled due to issues, but it seems like well over half the article is devoted to complaints about patches for Windows 10 - an (officially) unreleased product.
You can look through the author's blog history. One in three is an anti-Microsoft diatribe.
Re: Microsoft has been making quality assurance mistakes lately
#9One of the main points:
> how in the world can a patch to the Web browser lock up the operating system when you have an office suite installed?
In a perverse way, I enjoy stuff like this. Why? Because, someday, Raymond Chen will write about this and I will get to read about it on The Old New Thing, and while Chen will do a wonderful job of explaining the immediate causes, they will point to other technical oddities so bizarre that I will be reduced to a kind of mute incomprehension usually reserved for people who deal with the really interesting anal insertion cases in our fine nation's ERs.
I enjoy that feeling.
Re: Microsoft has been making quality assurance mistakes lately
#10Ordinarily I would brush off complaints about prerelease alpha software quality. But the same problems are affecting mature flagship products.
Last month a Microsoft Visual Studio update intercoursed all our Azure development machines. We never got any reply from Microsoft, and had to reimage all the machines. I see from https://connect.microsoft.com/VisualStudio/feedback/details/... this has nearly a dozen repos, and still no official reply or workaround.