Don't complain when it optimises some code for throughput when you haven't told it you're working in a low latency or realtime system
They are bad at architecture, even when given directives and tons of examples.
They will 1) fall into established patterns, which is fine if that's what you want, but extremely bad if that's not what you want or worse, when you're in territory where are not eestablished patterns and 2) the hardest/worst thing is leave all sorts of dangling state, impl. in the wrong places etc.
No human ever wrote a module and 'voila' - it's a constant process of iteration and refactoring - observing the situation, identifying paths to reduce complexity or state, grouping behaviours etc. etc. The best AI doesn't do this very well at all. It can do a tone of planning but it tends to very much be 'one waterfall iteration' and it's suggested improvements after that are generally poor.
It just does not work, we have to direct the iterations.
We still have stuff like godel's incompleteness and the halting problem that hint there's more to the universe than computation.
Food for philosophical thought.
There could be levels of emerging intelligence which will 'bitter pill' the brute force / mechanical AI we have today, for sure, yes.
It's reasonable that JEPA models might be a step in that direction.