When AI writes the software, who verifies it?
leodemoura.github.io
When AI writes the software, who verifies it?
1–10 of 309 posts
Re: When AI writes the software, who verifies it?
#2Re: When AI writes the software, who verifies it?
#3It’s such an intoxicating copyright-abuse slot machine that a buddy who is building an ocaml+htmx tree editor told me “I always get stuck and end up going to the llm to generate code. Usually when I get to the html part.” I asked if he used a debugger before that, he said “that’s a good idea”.
Re: When AI writes the software, who verifies it?
#4In fact it will probably need to happen a few times PER org for the dust to settle. It will take several years.
Re: When AI writes the software, who verifies it?
#5Re: When AI writes the software, who verifies it?
#6Re: When AI writes the software, who verifies it?
#7no one wants to believe this but there will be a point soon when an ai code review meets your compliance requirements to go to production. is that 2026? no. but it will come
Re: When AI writes the software, who verifies it?
#8You do. Even the latest models still frequently write really weird code. The problem is some developers now just submit code for review that they didn't bother to read. You can tell. Code review is more important than ever imho.
Then don’t even bother looking at C work or below.
Re: When AI writes the software, who verifies it?
#9You do. Even the latest models still frequently write really weird code. The problem is some developers now just submit code for review that they didn't bother to read. You can tell. Code review is more important than ever imho.
It is remarkably effective to have Claude Code do the code review and assign a quality score, call it a grade, to the contribution derived from your own expectations of quality. Then don’t even bother looking at C work or below.
Also works with planning before any coding sessions. Gemini + Opus + GPT-xhigh works to get a lot of questions answered before coding starts.
Re: When AI writes the software, who verifies it?
#10No one really. Code is for humans to read and for machines to compile and execute. Llms are enabling people to just write the code and not have anyone read it. It’s solving a problem that didn’t really exist (we already had code generators before llms). It’s such an intoxicating copyright-abuse slot machine that a buddy who is building an ocaml+htmx tree editor told me “I always get stuck and end up going to the llm…
If boilerplate was such a big issue, we should have worked on improving code generation. In fact, many tools and frameworks exist that did this already:
- rails has fantastic code generation for CRUD use cases
- intelliJ IDEs have been able to do many types of refactors and class generation that included some of the boilerplate
I haven't reached a conclusion on this train of thought yet, though.