765
Generative AI Is an Engineering Disaster. A shockingly inefficient trillion-dollar project.
(www.theatlantic.com)
this post was submitted on 15 Jul 2026
765 points (97.6% liked)
Technology
86413 readers
3169 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
The interesting bits are when it derives the likely hood of something being correct and does more passes, or splits the data apart in the first pass and opens up new context processes with specialized instructions to handle it. The code stuff goes full on ororborus on some models, writes out the code on one pass, checks for issues on another pass, runs the code looking for errors on a third pass and goes back to step 1 if it fails.
They're getting a lot out of it for it primarily just being a weighted token generator wrapped in an orchestrator.
Particularly software development with very good and very quick tests allow rerolling and that is very appealing in those scenarios. Problems being that very good tests are rarer than people like to think and sometimes it just gets stuck in a loop. At work the other week someone set it at the task of fixing a bunch of build warnings that had accumulated over the years. It succeeded after burning through tokens to take 30 tries at it. It's solution after all that hard thinking? It put // @ts-nocheck at the top of every file and called it a day.
But superficially, someone handed it a chore and didn't have to think about it, and if no one looked deeper, then it was able to get to the desired behavior simply by rerunning the given task over and over without human intervention until it worked. Which is also broadly relatable as there's a lot of humans in the industry acting broadly the same, but I've always been frustrated by those folks anyway.
Wide scoping like that rarely ends well. Give it the list, tell it to spin a new agent for every single issue and operate on them separately. If any of those agents run out of context memory, it will just shit the bed. Clarify that you need the test to actually work and not be commented out, and that the tests themselves still need to be viable and indicate a healthy working app, not just report that it's healthy. Trying to get tests happy in AI is like making wishes on a monkey's paw. Then assign someone to look after it because that bastard will chew through 10's of thousands of dollars to fix a laundry list of tests, which in my dev experience will be all broken and ignored in 2-3 minor releases.
You can generally get it to do things, even somewhat complicated things, but it's not easy, and the shit it gives you back while you're trying to convince it to do the job is the same stuff you'd fire an employee over.
My favorite thing is to make it make ansible tools, They're easy to read, easy to lock down, keys and passwords go in a vault that it's forbidden to read. Then I have it write runbooks on how to operate the playbooks. I then make an index of runbooks, and ask it to do them. It's an ansible job, so I can read it easily and make sure it's not able to delete my drive or my production database.
If I lose access to cheap tokens, everything I've making is still usable, and for now, I can spend my time working on stuff that's not simple enough that it can handle it well.