These models making bad / tasteless decisions about what dependencies to pull in is one of the main reasons they work best in the hands of experienced developers. You've got to know what you want it to use and tell it, and anticipate what shortcuts it will want to take and tell it not to do those things. For these reasons we're not yet at the point where inexperienced non-programmers can get high quality software out of these tools. I do think this will improve with time though.
You need to tell the model what to do and what not to do:
The dependency thingy is an issue, yes, but you can tell the model not to do so - and you should always know which result the prompt should create: For sure you must be able to read/understand/judge the code - completely fire and forget is not possible (to my experience), though I see many people saying "I had one mega prompt and after 2 days the app was ready", I take those always with a grain of salt.
Absolutely. These models still need a lot of this sort of hand holding, so they work best in experienced hands. I'm also skeptical of those very long runs, letting it go so long without active oversight must surely produce at least some objectionable design or implementation details, right? So I guess the people claiming those sort of results have less care for these sort of qualities.
