this post was submitted on 31 Mar 2026
143 points (99.3% liked)
Programming
26370 readers
164 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
And LLM slop coding will make it exponentially worse.
It's like purposefully introducing tech debt into the code.
My LLM slop personal projects have better test coverage than many many many professional projects I have had the “pleasure” of working with.
I've seen many an old crusty system with good test coverage. Doesn't mean it's good and high coverage doesn't mean a good test suite. Coverage doesn't measure quality of assertions being made.
Good coverage is still a lot better than no coverage when doing changes in a project you haven’t touched in ages
Yes and they’ll try to use more LLM slop coding to fix it, except it’ll cause the codebase to balloon way beyond any possible ability to contain it within a context window, so LLMs will hallucinate more slop and the whole edifice will come crashing down.
Yeah, but the LLM will eventually realize there's no fixing it and delete everything. /s
Under capitalism there's no lowest quality level at which workers can refuse to exchange their labor for pay.