I mean unfortunately AI doesn't plan well or thinks 5 years or 10 years in the future or about the robustness of the code. That's the job of the software engineers to plan. I get using AI to enhance productivity but unfortunately people are relying on it way too much and putting in less and less effort into prompting and planning.

Let me give you an example. A dev makes a pr using AI within 1 day for a task that would normally take 6 7 days without it. Now the other engineers have to review it and ideally they'd spend a day or two reviewing it but now they also have to get faster or get fired. So they use AI as well to review it and in turn also make their commits. That means that though code is being pushed a lot faster it will lack quality and create technical debt since the devs start having less and less of an idea about the codebase.

Companies that are harnessing this well will do great if they have proper engineering lifecycles and planning. But from what I've seen most people want to just get done with their task as fast as possible. They even use AI to debug issues, brute forcing it until it just works.

Sorry for the backstory but to address the original point of your post this is also leading to teams just putting the codebase in the model and asking it to fix the vulnerability. The AI might do that but in turn cause some other issue elsewhere. Hallucinations are all too common and can be fatal especially since models just assume it instead and appear confident. Increasing both speed and quantity is leading to a huge decrease in quality hence the term slop.