I still feel that for large project, and large changes within those projects - I should write the code myself.
The code outputted often runs, especially after a few attempts of fixes etc. However when I read the code later, I can see often it could have been done in a much simpler way.
In a recent talk by the author (I just posted a link), he says a best practice for large requests (e.g. implement an entire project/solution) is to ask Claude Code to think about it and present you with alternative approaches/designs (which you can then review). You could provide feedback and iterate if you wanted to.
Ah. I find that I don't have enough focus on my projects where I use Claude and so it helps keep me focused, plus I can outline a task, hit send, and deal with the next crisis, then come back to what got generated and evaluate it.
I still feel that for large project, and large changes within those projects - I should write the code myself.
The code outputted often runs, especially after a few attempts of fixes etc. However when I read the code later, I can see often it could have been done in a much simpler way.