this post was submitted on 30 Jan 2026
138 points (92.6% liked)
Programming Circlejerk
278 readers
10 users here now
Community to talk about enlightened programming takes
Rules:
- read and follow the programming.dev code of conduct
- no flamewars
- mark your unjerks
- only programming related content allowed
- link to the original source
- do not mention this community in places like hackernews, lobste.rs, or the general programming communities on Lemmy where we source jerk material from.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
One of our devs came to me with an LLM rewrite of some parts of our automation. Even at first glance you could see a lot was missed, the refactor simply wasn't going to work in that state and critical migration logic just wasn't present.
I binned the branch and did the refactor myself, as it would have taken more time to figure out the damage caused than just starting over.
So glad we now pay premium prices for RAM and non-volatile storage, just so some LLM can vomit up a reheated turd.
and that's the fucking crux of it right there, the damage. Any code base without someone smart enough to throw this trash out is going to take forever to fix or might just be too far gone to save