Yeah. I was tasked with evaluating LLMs for software dev at my company last year. Tried a few solutions and tools, and various workflows from just using it as a crutch to basically instructing the LLM to make the application. The former was rarely necessary (but sometimes helpful) and the latter was ridiculously cumbersome.
You need to be specific, and leave no room for interpretation, because the moment you do the latter it'll start making stuff up that doesn't necessarily fit in with the spec, and while you can correct that, that's tedious in and of itself, and once it's already had the idea it'll often have a hard time letting go of it.
I also had several cases where it outright ignored provided context. That was even more frustrating because then it made assumptions that I'd already proven to be false.
The best use cases I got from it was
Explaining unclear code
Writing clear documentation (it was really good at this)
Rubberducking
Essentially, it was a great helper, but a horrendous developer. Felt more like I was tutoring it than anything else.