Mate, I'm watching my director and architect slack each other epics of slop trying to get our harness to accept the specs for a feature. I could've built the whole thing by now, but they don't want that, they want reproducibility and predictability. If they could just be happy with 25% productivity gains, we'd make a killing with our services contracts.

Here's the thing: these morons are never going to get what they want describing it in vague, natural language terms. The reason you're having success with AI is because you know the fundamentals of coding and you know the practicalities. You can describe in specific terms exactly what you want and how to build it. People who can't do that are never going to replace those who can.

Coding may be solved in the sense that AI has instant access to things we haven't done before or haven't touched in years. Maybe I used to do something by hand but 9 months ago spring added some annotation or library and now it's solved without those side effects or quirks our homegrown solution has.

But you still have to know what to do. You have to add this hook so you can troubleshoot issues in the future. This needs to be an interface because you know it's going to have different case implementations. This can be an enum, but that needs to be freeform text. This database needs to be normalized for cross-referencing, but that one needs to be denormalized for performance.

People who understand code can't be replaced by those who can't. This is just another layer of abstraction.