@SnotFlickerman@lemmy.blahaj.zone
Post #2415088
2025-12-06 02:06 UTC
Replies (4)
-
@darkevilmac@lemmy.zip 2025-12-06 02:42
It's less the vibe coding and more: this is what happens when you have the developers do all the QA and fire the actual QA staff. They've been screwing up the Windows updates since Windows 10, vibe coding wasn't a thing at that point.
-
@tidderuuf@lemmy.world 2025-12-06 04:45
In a way they are. Their QA was sent overseas and at some point was cut down to basically skeleton crew. Every engineer at MSFT was recently ordered to use AI. The bulk of where MSFT makes money is not from its OS but from selling your data and being a cloud provider. They don't really care about the user experience anymore and that has very clearly shown to be their lowest priority for a few years on now.
-
@Aedis@lemmy.world 2025-12-06 06:43
A lot of what the other comments have said is right, but also add that to on top of all the layoffs theyve had and they keep telling their devs to double their efforts. Its been in so many meetings that at this point a single engineer should be able to do the work of the whole company... the shareholders keep demanding doubling pace from their engineers but they just wont listen smh They should just fire all the engineers already theyre clearly slacking off /s
-
@mlg@lemmy.world 2025-12-06 05:18
> Do these updates not go through any rigorous testing at all Lol no, MSFT infamously dropped their entire Hardware QA team after WIndows 7 and instead relied on the also infamous insider hub to get QA "feedback" from home users instead, leading to the also infamous Windows 8 disaster and slightly less infamous critical CVEs that went unaddressed because MSFT ddidn't even bother to read the insider hub posts. Oh and they didn't learn anything and kept running with the insider hub well into Windows 10 & 11.