If you don't specify the model you are talking about, you have written a sentence with near-zero information content. If that's your habit, well... that's likely part of the problem.
I promise you, Fable and Neon are better than you are at pretty much whatever. Sonnet 4.X and MechaHitler, well, maybe not.
In a similar vein public clouds contain the components to built any software you can think of. But that doesn't mean that all the solutions possible spring into existence just because AWS exists.
The tools are amazing, but I think they are most amazing when you can have deterministic verification loops. Async bugs aren't always encountered, so it's a little more difficult for the LLM to prove its work and iterate. At least, that's my current hypothesis for why it tends to degrade so much for this type of problem.
They'll shove out a pattern quickly, but no matter how new and magical the latest model is, they will just put out some tweaked variant of existing designs. I find myself treating it like a junior-mid engineer. "Add rdtsc-based timers around major parts of the code to whittle down what's taking too long." "Use that to figure out where the transfer amount is way too small to justify the time taken without copying the payload." etc.
But concurrency bugs from large LLM-developed codebases are a major issue. They constantly find bugs they wrote. I eventually told it to start writing formal models of the concurrent uses and to (a) validate the models; (b) verify the code implements the models; to make it work.
So yeah, I stand by my words. For simple commands and tiny codebases, it /can/ do those things, but even small projects (50 KLOC) are a mess of making it fix its own mistakes, reconcile basic logic in requirements analysis, and everything has to be taken over with a fine-tooth comb to make it any good.