Microslop: When 30% AI-Written Code Becomes a Wall of Windows 11 Failures
Description
A dense satirical collage styled as a newspaper front page. The masthead reads 'Microslop' (mocking Microsoft) with overlay text forming the sentence: 'Microslop IS A SLOPORATION THAT TURNS [the headline] INTO...'. The central headline is 'Microsoft CEO claims 30% of its new code is written by AI', surrounded by dozens of real-sounding Windows 11 failure headlines: 'Windows 11 Update KB5063878 Reportedly Causing SSD Failures', 'KB5063878 triggers BitLocker recovery on PCs for businesses', 'Microsoft Rushes Emergency Fix After Latest Windows Update Leaves Bluetooth, Audio, and Webcams Useless', 'Microsoft WSUS Remote Code Execution (CVE-2025-59287) Actively Exploited in the Wild', 'A bizarre Windows 11 bug duplicates Task Manager instead of closing it', 'Play Call of Duty: Black Ops 6? Windows 11's latest patch reportedly has a game-breaking bug', 'Microsoft accidentally wipes out Copilot in latest Windows 11 update', 'Microsoft finally admits almost all major Windows 11 core features are broken', and many more update/breakage headlines (KB numbers, broken taskbars, File Explorer issues, VPN breakage, January patch problems). The meme draws a causal line between Satya Nadella's claim that ~30% of Microsoft's code is AI-generated and the perceived avalanche of Windows 11 quality regressions - 'slop' being the pejorative for low-quality AI output
Comments
29Comment deleted
30% AI-written code, 100% AI-written postmortems - at least the incident reports ship on schedule
Thirty percent generated, seventy percent spent bisecting the regression.
waiting for Liza lgbt plus's comments under every post about vibecoding Comment deleted
So basically windows is windowsing even more now Comment deleted
Each time it gets posted, a couple new vulnerabilities are added Comment deleted
On linux side of things we'll have similar soon with all those rust rewrites... Comment deleted
Yeah, but it's different. Issues in Linux space is user skill issue (and only it) Comment deleted
lmao what a take Comment deleted
true tho Comment deleted
no? Comment deleted
you'd say it applies to anything that is vibecoded Comment deleted
also that yes Comment deleted
yeaaaah you came Comment deleted
…? Comment deleted
Same rn Comment deleted
thats what ubuntu non-lts is for. test the rust rewrites Comment deleted
yay, test in prod Comment deleted
unit tests only get you so far, and only idiots use non-lts builds in prod Comment deleted
yeah, only idiots get graphics Comment deleted
that sounds more of a reason to shit on linux packaging Comment deleted
.... of the kernel itself? Comment deleted
kernel has no stable api for stuff linking via DKMS Comment deleted
and where exactly do I get dkms drivers for amd? Comment deleted
just vibecode them Comment deleted
why code Comment deleted
I'm not into the topic. But vibecoding drivers just sounded like the worst possible idea to me, so I suggested it. Comment deleted
It's for the better Comment deleted
Pls Comment deleted
Like we now use the scuse of vibecoding? Windows ,as a true lover of this OS, since ever and Forever Will suck Comment deleted