I can easily believe it.
Back when I worked for a living as a test-designer and builder, I’d joke with the project code leads that their best hires would be the laziest coders they could find. The coders who automated/scripted/whatever any process they’d be required to do more than two or three times.
If I was still designing/coding I’d be using some form of AI to generate the ground code. That was always the best way to get a project started - steal some code either from my own vast snippet library or from some generous chap online. If you weren’t a good code thief, I didn’t want you on my project. Of course, all the code I’m talking about was ‘in-house’, and never marketed. Back then, there were dozens of websites where good-hearted blokes shared generous chunks of working code - copy/paste/modify and move to next leg.
I use it.
I’ve been writing software for 57 years. I don’t need AI. I have a monstrous “toolbox” and I’ve very fast.
It’s great for saving 10 minutes here and there. Anything deep or more obscure like thread pools and Windows sockets for example can easily cost hours of debugging time. Better to ask it questions and write the code yourself in those situations.
take the AI crutch away and those ‘senior developers’ will be crippled.
writing code on a blank slate takes experience.
experience these ‘senior developers’ would be lucky to possess as they’ve been using AI for the last 2+ years.
Anyone can code, few can debug.
AI does not come up with the same answer twice as far as I know.
Google AI mode: Create full length webpage using css and html that is responsive with a header and footer and two columns with the main column having 2 small images side by side
Now copy the code and compare after running the same query and you will get a different way of doing the same thing and not necessarily the correct answer.
Change the question slightly and again different results.
The layout is a simple one, I cannot fathom a more difficult question for critical software.
Plus AI looks on the internet and can come up with the wrong answer altogether. If looking in some code library in house then maybe you get a better result but how many partial pieces of code and old dated ones do you have? You would need to edit that library constantly.
Example not quite AI but human AI was a new supervisor who came up with what he thought was a better way of finding an answer in our knowledge base articles such as kb123 then the subject.
He decided to do away with the numbers and left the subject since he thought you could remember some exact long subject name among hundreds. The problem was many many articles had the title of the software we used followed by part of the subject so a search brought 101 articles that buried the correct one if one was found at all. He left the company but his legacy lived on. Before you could tell someone look for kb123 and that was the only article that would come up.
The internet is too big a database to rely on critical software answers. You need a human from the USA to comb thru the result.
I see new cars are being built with fly by wire steering wheels and brakes... <—YIKES!!
You just know the software will fail!
Example of failures already are car doors that cannot be opened if a battery dies. I guess AI and the software engineers did not think it thru.