this post was submitted on 10 Sep 2026
278 points (90.6% liked)
Technology
88303 readers
2936 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
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 am not talking about the Linux kernel or the Rust project - they have stabdards way above average commercial projects - but generally "using ai" in practice means to use it for code generation. Then, programmers are expected to review the output but are not given extra time for it. This creates an extremely slippery slope leading to mostly unsupervised code creation. Also because reading and understanding buggy third party code means more effort than writing new code.
Then there is the idea to get rid of the bugs by "debugging", but debugging is frankly not a software engineering strategy, because you can always just recognize a fraction of the bugs that your process created in the first place. Debugging is also more expensive tha writing good code.
Then, what makes the process between product managers and software developers very often a bit friction-loaded is that good developers always want to have clear specifications what they are supposed to build.
LLM code generation largely replaces clear specifications with plausible assumptions. That appears to make the process fast, but the result is often wrong. At times obviously wrong, and at times subtly and catastrophically wrong.
Excellent observation, which aligns with my observation that fans of "coding assistants" can't wrap their head around algorithms, not to mention a sound software architecture.
Eh, I now have witnessed two cases where I asked a software team lead of a project I was working for for a precise interface or API for a planned function and they looked at me as if I had talked about going on a giraffe ride with a bunch of alien Martian schoolkids.
(And subsystem interfaces is really a subject I was taught in 10th grade by a math professor who himself had been a student of Niklaus Wirth. Maybe if you stand on the shoulders of giants, you should not be pissing on them...)
It was already difficult to find people who know how to phrase good requirements and / or design an architecture before the slop machines got introduced. It will be so much worse for the next couple of decades, with idiots bullshitting their way past HR into a position.