Earlier quoted context omitted.
It would write incorrect code and then you'd need to go debug it, and then you would have to come to the same conclusion that you would have come to had you written it in the first place, only the process would have been deeply frustrating and would feel more like stumbling around in the dark rather than thinking your way through a problem and truly understanding the domain. In the instance of getting claude to fix c…
I'm like 60% there with you: * When it gets the design wrong, trying to talk through straightening the design out is frustrating and often not productive. * I've learned to re-prompt rather than trying to salvage a prompt response that's complicatedly not what I want. * Exception: when it misses functional requirements, you can usually get a session to add the things it's missing.
What I have learned is that when it gets the design wrong, your approach is very likely wrong (especially if you are doing something not out of ordinary). The solution is to re-frame your approach and start again to find that path of least resistance where the LLM can flow unhindered.