this post was submitted on 19 Dec 2025
184 points (99.5% liked)
Programming
26952 readers
658 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
Bad article, the number of issues aren't normalized to anything other than PRs. I expect AI authorized PRs to be somewhat bigger than a fully human authorized one.
Ideally they'd compare time to write + time to fix. My experience is that if you use test driven development, LLM isn't too bad. No worse than an intern.
I think it comes down to who is using the LLM. I had a junior dev once "presumably" AI gen a ton of code (broken trash). Then to fix it, they wrapped each function in a try catch block that dropped the error. Unit tests were mocked out to the extent they didn't test anything.
When I use an LLM, I have tests and hard constraints on the LLM. It isn't good enough to do everything, but it can generate about 80% of a simple app
While I can get speedups for rapid prototypes where the code doesn’t need to be good, just mostly working, to get actually good code it’s inevitably significantly faster for me to write everything than to fix what an LLM starts.