You know what makes good systems work, how to architect solutions, how to separate responsibilities and write code that’s easy to maintain and extend over time.

But that advantage fades away very quickly when you throw a prompt Claude Code’s way and then try to review the resulting code.

(sooner or later you’ll get fed up of trying to read the LLM’s code and just sign it off anyway… it’s human nature to take the easiest path).

I feel this. You try to do a good job looking over the code. You try to find everything, but the code keeps coming and coming...then...you just sigh and move on. All the willpower in the world can only get you so far.

So keep the reins on the LLM. Get involved and steer it before it writes the code (because catching up afterwards is a lot harder).