A nice illustration of "Don't snort what you cook."
A nice illustration of "Don't snort what you cook."
@stevelieber wasn't there a single human involved in that 30%?
What does that even mean?
No one wrote a promt?
Nobody checked the code?
There was no correction or altering the code after generation?
@rhold @stevelieber ai "boom" isn't even real you tools, it's practically a fraud bubble to the tune of 610+ billion banking on bros like you 😂😂😂
@rhold @stevelieber I don't see any of those assumptions. Nor really a direct correlation between the use of the AI and the rate of rot in the Windows codebase.
However, the implication is that AI can generate subtle bugs faster than human engineers can track them down and correct them.
Even with purely human generated code, the majority of human reviewers do not do a deep dive looking to fully understand code. The best you get is a two minute read through of changes that took two days to make, and a "LGTM 👍".
Perhaps we're doing this wrong; keep humans for writing code, and use AI for doing the boring difficult bit - looking for bugs. Combine that with language constructs that indicate intent, and I think you'll have a winning combination.
Links to the article:
"I'll just put this here, and this here and expose the obvious stupidity of both to the Universe.
There."
Congratulations for the best catch, the best exposure, the best explanation, the greatest teaching social media has ever enjoyed.
Boom.
#ai #microsoft #techbro #vibe #code #crap #journalism #linux
@stevelieber They blame XAML code. Their OS is bloatware. All is being rewritten with XAML.
Mozilla had to drop XUL from Firefox.
But if it's true they generate so much code with word predictors, it'd be even worse. Bloatware and slop.
@fcalva @stevelieber They blame XAML: https://www.neowin.net/news/microsoft-finally-admits-almost-all-major-windows-11-core-features-are-broken/
The link above is in a reply to the same original post of this thread.
Neowin released an update on December 3rd: Microsoft admits major Windows 11 25H2 UI features broken too alongside 24H2 on some PCs https://www.neowin.net/news/microsoft-admits-major-windows-11-25h2-ui-features-broken-too-alongside-24h2-on-some-pcs/
It seems they call it now WinUI, but it's still XAML. https://github.com/microsoft/microsoft-ui-xaml
They added preloading to the file explorer and it still is sluggish and proprietary software spying on you.
Tested: Windows 11’s ‘faster’ File Explorer (preloaded) is still slower than Windows 10, and uses additional RAM https://www.windowslatest.com/2025/11/28/tested-windows-11s-faster-file-explorer-preloaded-is-still-slower-than-windows-10-and-uses-additional-ram/
How long before this:
I went to a restaurant and the food was truly horrible. So I complained to the chef and he said, "Talk to the owner." So I complained to the owner and he said, "30% of the food prep is done by an LLM cook. It saves us a fortune! And it washes the dishes, too! Would you like to see it in action?" I said yes, and the cookbot was frying eggs in soapy water. No wonder the food tasted like shit. I wanted to tell the owner that I'd never come back but he'd already been replaced by an LLM owner-bot. So I walked out but on the way I noticed that all the diners were bots, too. Probably they're designed to eat soapy food so problem solved. It's a closed ecosystem and humans are not needed.
I'm no fan of the various Alpha & Beta testing releases being pushed around as production ready code - called "A.I."...
---
Over about 15ish years, I wrote/maintained/ran code that generated my database classes (for couple DB systems) through many DB changes/upgrades - result was many files with clean code lines of 800k to 1 million lines.
So automation is not all bad.
What is bad is thinking that Alpha/Beta LLM software is ready to generate production releases.
What could possibly go wrong...
"written by software" isn't the same as "written by AI"
@stevelieber The worst thing about it is that they're proud of it.
I was never proud of any of my code when it didn't work properly.
AI: "Yes, i know it's wrong, here is the solution"
Prompter: "It still doesn't work because X"
AI: "Yes, thanks for pointing that out. Here is the solution"
Prompter: "Now it's broken here"
AI: "Haha, you're right. Here is the solution"
12 hours later it still doesn't work.
@Brokar @stevelieber I've worked with *people* like that. Classic symptom of not understanding the code.
My motto was "take pride in your work, but don't get emotionally attached to it".
That's very reassuring. I was starting to wonder, frankly. They call that the broken windows theory I believe, but I understand it's been discredited.
lol. lmao.
One for the FAFO file.
@stevelieber @eniko GitHub goes down almost daily now…
I wonder what the next big fiasco will be.
@stevelieber Somehow... I am not surprised with the privacy invasions and consent issues... I didn't expect Microsoft to make so many bad decisions on stability though.
This is a whole new level of fail
Microsoft itself admits almost all of windows 11 core features are broken.
I honestly never even noticed.
Why, because I only run antiX Linux full stable version and everything works as expected.