You’re fucked once you have to start getting AI to produce code for languages you’ve never actually worked in.
You will have to write code to understand deeply what goes on at the low level. Without a solid understanding of the low level, you won’t truly know what optimal solutions look like on a high level. You will be flying by the seat of your pants, churning out code that works but has bad low level quirks sprinkled through the code base. The AI will say it’s fine, but you’re just building up shitty software. Feels like shit, run likes shit.
Once someone new comes along who has worked with the language manually and can get AI to produce effective high quality code, you’ve lost competitive advantage. They can build way better versions of whatever you do. You’re finished. You’re a low quality engineer.
Your argument has many, many leaps but I infer your point.
The lack of attention does reduce the overall correctness of the system.
But, and unfortunately, in most situations the loss of correctness is more than made up for by the speed gains.
Unless you're building software that could kill someone, it's hard to reject the improved speed. The cost of delay is usually more damaging than the cost of incorrectness.