516
Microsoft executive vice president bemoans employees sending him "AI slop," saying "This is a doom loop."
(www.windowscentral.com)
this post was submitted on 03 Sep 2026
516 points (99.4% liked)
Not The Onion
22409 readers
1340 users here now
Welcome
We're not The Onion! Not affiliated with them in any way! Not operated by them in any way! All the news here is real!
The Rules
Posts must be:
- Links to news stories from...
- ...credible sources, with...
- ...their original headlines, that...
- ...would make people who see the headline think, “That has got to be a story from The Onion, America’s Finest News Source.”
Please also avoid duplicates.
Comments and post content must abide by the server rules for Lemmy.world and generally abstain from trollish, bigoted, ableist, or otherwise disruptive behavior that makes this community less fun for everyone.
And that’s basically it!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I find writing the code is the easy part. The difficult part is figuring out what the requirements are, fitting together all of the data relationships, figuring out the security so the correct people and systems have access to the data. To do these things I need very specific knowledge of the systems I'm working on, knowledge the AI doesn't have.
I could see it could give you a simple interface that's similar to something it's been trained on. But it's capabilities are very limited in terms of doing anything novel. It can't actually understand a problem, it can only give some code similar to problems that exist in it's training data. Sometimes that's useful, since at times I do have to solve problems that's been solved by others. But most of the time the AI can't understand what I'm trying to do and it's easier to write the code than it is to try to explain to an LLM how to write the code I want it to write.
Maybe you are doing some exotic stuff, but for me it’s more than capable of writing code, coding is mostly about applying existing patterns to solve known problems, very few programmers deal with novel problems.
Design Patterns book has been out for what? 2 decades, and it’s not outdated.
For good team interoperability you want to have code that’s standardized, that’s also where LLMs excel at.
It’s a nice productivity tool, just like an IDE is a nice productivity tool
In software engineering, sure there's patterns, but that's just guidelines. Eventually you run up against a problem where an something you don't have control over isn't 100% reliable so you have to think through how to handle that scenario. Maybe you retry an API call, maybe you notify some people about the issue, it's all context dependent what you need to do. The AI doesn't know what to do, because how would it? There are a massive (I won't say infinite, but in terms of a human lifespan it may as well be) number of combinations of technology X connecting to technology Y. So there is always going to be a great many problems that no one has ever encountered before. LLMs increasing the number of features in the software doesn't solve those kinds of problems it just increases the number of problem.
I think it's fine to think of it as a tool, like an IDE. But just like an IDE, it doesn't solve the problems, the person using the tool solves the problem.
For instance today, the LLM explained to me how to enable SSL certificate negotiation with TLS 1.3 some shitty IIS setup I have to maintain. I used the LLM because I figured that I'm probably not the only one that has seen that issue. Now the problem I have to deal with is whether the software that updates the certs might break the config, that's a little less likely the LLM will have a reliable solution to. I might just wait until the software updates the cert an manually test if it broke. The day before I had to launch some stuff in the middle of the night so I wouldn't interfere with business operations. The launch was to change something from single linked list to a doubly linked list which is important for reasons I can't explain now. I mean I would explain it, but honestly I can't remember why. I just have in my notes that it needs to be a doubly linked list for the recursion to work properly. Maybe next week when I fix the FE I'll remember why, but if I was correct many months ago (it's a low priority issue), the FE should now have the data it needs to solve whatever problem was there.
So yeah, I use LLMs sometimes for problems that I think other people have seen before but sure as hell can't be driving on what I do. Someone has to make the various pieces of software work together, know the business the software is being used in. More software means more problems that someone has to figure out. If you make n pieces of software with LLMs, you're make n! problems to solve.
Yes AI or LLM isn’t able to code solution itself, but it can fill in a lot of gaps based on what you tell it, it can copy existing patterns.
And you can direct it, it’s a tool like an IDE, just much better .