this post was submitted on 03 Dec 2025
863 points (98.9% liked)
Programmer Humor
27673 readers
939 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
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
I seriously doubt your quality is maintained when an LLM writes most of your code, unless a human audits every line and understands what and why it is doing it.
If you break the tasks small enough that you can do this each step, it is no longer writing a full application, it’s writing small snippets, and you’re code-pairing with it.
Great? Business is making money. I already explained we have human reviewed PRs on top of full test coverage and other validations.
We're compliant on security policies at our organization, and we have no trouble maintaining what the current code we're generating because it's based on years of well defined patterns and best practices that we score internally across the entirety of engineering at our organization.
As more examples in the real world:
Aider has written 7% of its own code (outdated, now 70%) | aider https://aider.chat/2024/05/24/self-assembly.html
https://aider.chat/HISTORY.html
LibreChat is largely contributed to by Claude Code, it's the current best open source ChatGPT client, and they've just been acquired by ClickHouse.
https://clickhouse.com/blog/clickhouse-acquires-librechat
https://github.com/danny-avila/LibreChat/commits/main/
Such suffering from the quality! So much worse than our legacy monolith!
Your product is an LLM tool written with LLM tools. That's is hilarious.
If the goal is to see how much middleware you can sell idiots, you're doing great!
Incorrect, but okay.
We have human code review and our backlog has been well curated prior to AI. Strongly definitely acceptance criteria, good application architecture, unit tests with 100% coverage, are just a few ways we keep things on the rails.
I don't see what the idea of paircoding has to do with this. Never did I claim I'm one shotting agents.