Yes. If you were hiring an engineer and you asked them a coding question, what would you think if the very first thing they did was start writing code without asking a single question? They’d fail the interview instantly, right?
These LLM’s seem to assume their job is to just write code instantly. No! Tell them to not do that! “No code yet, let’s make sure we are on the same page first. This is requirements and discussion, I’ll tell you when it’s time to write code” and go back and forth on requirements and stuff. If fact bake that into your “system prompt” or whatever your tool provides to set up the pre-prompt—I will straight up tell it what I just used as an example about failing an engineer who jumped right into writing code. That LLM had plenty of training data about why that is a bad idea! You just need to “remind it” by telling it.
These tool makers should honestly build that in by default but I bet a lot of people expect the magic genie to start writing magic code by just reading your mind or something. If they had it ask all those pesky requirements first, I bet they’d start failing some idiotic benchmarks or something.
In addition consider asking it if it has all the context it needs to help you. Sometimes it will say “no, can you let me see such and such class/file”.
Also I make sure to include the full path and file name at the top of all my files to help the LLm since I doubt that kind of metadata gets passed through otherwise. I’ll sometimes give it a “tree” of my own entire project so it knows where all the files are at.
Providing proper context is absolutely critical. This tool cannot read your mind! Tell it exactly what its role is and give it the context to do the job properly.
These things aren’t magic. Learn how they work a bit and then you’ll realize they are a really fancy command line interface or something… dunno how to describe it, but it’s just another way to interact with a computer. That’s all it is.