That’s always true in my experience, but that doesn’t necessarily mean you need to. The trick I’m working towards is refining the workflow such that i can reliably produce maybe 90% as “good” as what I’d personally produce but much, much faster.
All sorts of side work I was avoiding before also becomes much easier, less tedious refactors and large test coverage and etc.
It can type much faster than I can, the trick is if we can constrain the thinking enough to make it useful. Keeping it as an autocomplete is as productive as it is difficult imo.
Indeed, I hit the stop button quite a bit when Claude goes off course. Then make a note of the right choice so maybe it won't do that again, revert and proceed. I have the feeling there is an optimal size of project proportional to the context size, where you can fit the critical design points into the context and/or there are enough examples in the code of how things should be done.