And then Microsoft gets annoyed when people don’t immediately start using Win 10, then Win 11.
Seeing the results, it looks like earlier versions had more QA done before the release, whereas nowaday a bigger part of QA is done by customers after the release.
Sacking testers makes nothing but sense if your customers are as dumb as us. My employer continues to sign contracts before the functions we need have been proven. income independent of functionality.
TBF our procurement people don’t seem to think our requirements are any more complex than “big computer” and MS probably offered “really big really good computer, cheap computer, big , nice price, 25% less than oracle, high security, safe computer, cloud, ai, yes fully working with 12 month, you pay now, special discount, extra 10% off if you sign today, hurry rush best deal”.
I suspect negotiations like that drive a disappointingly large amounts of their revenue.
One is nearly inclined to think that in-house beta testers weren’t a waste of money.
And then Microsoft gets annoyed when people don’t immediately start using Win 10, then Win 11.
Seeing the results, it looks like earlier versions had more QA done before the release, whereas nowaday a bigger part of QA is done by customers after the release.
Only if revenue goes down.
Sacking testers makes nothing but sense if your customers are as dumb as us. My employer continues to sign contracts before the functions we need have been proven. income independent of functionality.
TBF our procurement people don’t seem to think our requirements are any more complex than “big computer” and MS probably offered “really big really good computer, cheap computer, big , nice price, 25% less than oracle, high security, safe computer, cloud, ai, yes fully working with 12 month, you pay now, special discount, extra 10% off if you sign today, hurry rush best deal”.
I suspect negotiations like that drive a disappointingly large amounts of their revenue.