In a code editor or the website? Coding using the website has distinct disadvantages, imo.

But yeah… Arguing with an LLM is never worthwhile. If it doesn’t (mostly) work the first time, roll back and start over with a better prompt. This is because there is a big element of randomness (seed) that causes every run to potentially be different, ranging from slight to drastic. Basically, you can get junior dev who should be fired one time, and a senior engineer the next. Start over, improve the prompt/context/plan, run it again. E.g. there is a reason the Copilot in-line editor has that little try again button right there; because you should use it, same with entire prompts—hence the reason the up arrow in VS Code Copilot gives you back your last prompt.

Also, lots of times it means it just doesn’t have the right context to pull from (or too much, or not useful, depending on the model). Small well-defined tasks are almost always better. Documentation in an LLM readable/searchable format can be highly beneficial, especially API references for libraries that are well organized, or things like Context7 MCP if the library is recent or can be parsed correctly by C7. Expecting a general knowledge LLM to be an expert in every language/library or to just intuit correctly from the library sources hasn’t ever worked out well in my experience (unless it is a small library).

At least that’s my 2 cents if you’re interested. Hope it is helpful (to someone).