News for hackers. Stuff that matters.
Re:Ask HN: Is anybody producing good code with coding agents? by runjake on Friday October 02, 2026 @02:08PM (#49936657)
Yes. The whole time. But, you still need to write good specs if you want well-designed software. Agents are not magic.

- Write good specs into files, usually Markdown.

- Go through the spec files with the agents, have it point out holes and problems, and then update the specs. Go through a few iterations of this and then start your agents on development.

Garbage in, garbage out.

Re:Ask HN: Is anybody producing good code with coding agents? by daringrain32781 on Friday October 02, 2026 @03:36PM (#49937626)
> Write good specs into files, usually Markdown.

When I'm building something new there's a good chance I don't know about a lot of problems (unknown unknowns). How do you overcome this with just spec files?

I keep coming back to this and the only way to develop properly without tons of hacks patching bugs afterwards is by working at a low level. I don't really write code but I work at the code level still and have Claude write each function and whatnot.

Re:Ask HN: Is anybody producing good code with coding agents? by sigbottle on Friday October 02, 2026 @10:45PM (#49940968)
For personal projects, I've rewritten bounded integration parts for things all the time, and so far it's been fine. Coding agents are RL'd to get the thing done, they'd rather get to 95%, not realize there's some fundamental architectural flaw, and hack the last 5%, rather than taking that lesson and redesigning. That's your job.

For business settings, yeah I dunno, a ton of rewriting all the time is not seen as a good look.

Re:Ask HN: Is anybody producing good code with coding agents? by runjake on Monday October 05, 2026 @11:46AM (#49966410)
I try to have a good overall idea of what I want to build from the start. Sometimes I don't know and that involves long walks and iterative conversations with the agents. It's okay to stub out functionality or modules and the agent will be comfortable with this. As the agent builds, I have it update an architecture document.

It's always good to have another agent (sans existing context) review the project for slop and hacks, best practices, security flaws, etc. I usually have Codex do one, and Claude do the other. Hope this makes sense.

Re:Ask HN: Is anybody producing good code with coding agents? by piscaries on Monday October 05, 2026 @12:23PM (#49966915)
Agree, you can't spec what you don't know yet. Two things could help: Let the agent grill you before writing the spec. Answering its questions surfaces a lot of the unknowns. Then have a different model grill the plan, with questions specific to your product. In one case of mine, that caught a design issue which the generic review missed.
Re:Ask HN: Is anybody producing good code with coding agents? by ruffrey on Friday October 02, 2026 @03:11PM (#49937320)
Are you still saving time or effort using coding agents this way? How much (estimated)?
Re:Ask HN: Is anybody producing good code with coding agents? by hollowturtle on Friday October 02, 2026 @05:58PM (#49939124)
> Write good specs into files, usually Markdown.

Specs that gets systematically ignored way too often XD