I'm coming to the conclusion that the right way to use LLMs for code generation is asking it to solve specific problems, giving it existing code and asking it h

I'm coming to the conclusion that the right way to use LLMs for code generation is asking it to solve specific problems, giving it existing code and asking it how it would propose changing something or other, or if it has an alternative to an existing logic flow that's problematic and asking it what it thinks the problem is and how it would suggest it be written. I'm coming from the perspective of infra management so that's my bias, and a very complex code base may make my perspective off mark. But nowhere does it seem it to be a good idea for the whole thing to be LLM generated. It seems to view a big holistic problem in steps in isolation, causing it to add complexity on top of complexity as it's going through it's later stages. For example it'll create infrastructure designs that add layers of unnecessary and redundant tooling and business logic, when a human would have re evaluated step 1's path when it realized step 3 was doing the same thing again in a more complex way.