Comment by g947o
8 hours ago
1. "isn't felt right away" then what's the correct timescale? Is it 2 years? Is it 5 years? We are looking at 10 years now. Do you have any studies on this that you can quote to prove that at Microsoft scale and for the product they develop, 10 years is the time when things go bad?
2. "becoming more frequent and harder to solve" how much more frequent and harder? Things works pretty fine during Windows 10, but these days I run into a bug in Windows 11 every other day myself.
It would be a surprise if this has more to do with QA from 2014 than vibe coding.
Updates breaking stuff already started when they moved from the security/bugfix-only updates to the add-new-features-into-the-mix model with Windows 10. That was roughly 10 years ago.
For example: https://www.zdnet.com/article/microsoft-on-windows-10-annive...
These things have been keeping happening.
These are multipliers. First, the QA left, but nothing major happened for years, automated tests did suffice. Then, vibe code happened, that with the lack of QA, led to disaster.
I doubt "studies" exist and proving every little assumption takes too much effort as per Brandolini's law.