My feeling is that clean code, SOLID and a good project structure are even more important now than ever. Especially when you're building something long term, not just a prototype.
Ask HN: What is your take on the importance of code quality when coding with AI?
1–4 of 4 posts
Re: Ask HN: What is your take on the importance of code quality when coding with AI?
#2Agree. When I first started using AI to build projects I just let it do whatever it wanted. Turned out to be completely unmaintainable — everything was a black box.
The worst is when you find a bug, fix it, and then Claude Code starts spiraling — "this isn't right either", "actually let me change this part too", "wait no let me revert that" — just Clauding endlessly and making things worse.
Now I make it break everything into atomic changes. At least it's not a total black box anymore.
Re: Ask HN: What is your take on the importance of code quality when coding with AI?
#3[dead]
Re: Ask HN: What is your take on the importance of code quality when coding with AI?
#4Agree. When I first started using AI to build projects I just let it do whatever it wanted. Turned out to be completely unmaintainable — everything was a black box. The worst is when you find a bug, fix it, and then Claude Code starts spiraling — "this isn't right either", "actually let me change this part too", "wait no let me revert that" — just Clauding endlessly and making things worse. Now I make it break everyt…
Exactly, for me starting with spec works well. I even do multiple rounds with Claude: "review this from the clean code / SOLID perspective", "check if everything is consistent and follows project conventions". Only after that I allow him to proceed with implementation. And I have architecture and tech stack clearly described in CLAUDE.md