Earlier quoted context omitted.
The next time I am angrily typing to claude 3.7 in all caps because he overengineered a bunch of code I didn't even ask him to write in the first place, I'll be sure to let him know his continued failures are risking the entire world economy.
I think SWE's have a serious blind spot here. I use the (rough) analogy of bowling to help illustrate this. People need to knock over pins in the bowling lane. SWE's are the pro bowlers who can (usually) throw pretty cleans shots to knock over pins. Now bumpers have been invented (LLMs) and regular folks who only have the faintest idea of how to roll a ball are knocking over pins. To the pro's these bumpers are all m…
The problem isn't that a "pro bowler" could come in and do something irrelevant for more money. Professional programmers understand that you shouldn't prematurely optimize things like memory or performance in contexts where that doesn't matter. You're ignoring the most important metric which is correctness. When we write a program, we make it correct then we can optimize it if that's actually important.
What's going to happen when you have your non-expert write a program using these tools and it inevitably gets something wrong? Are you prepared to build business process on top of a program whose author can't tell you how it works which might contain bugs? Do you even realize that this is just a recipe for producing mountains and mountains of technical debt?
You seem to believe this is going to put programmers out of a job but you're just explaining why they'll need even more of us in the future when these piles of garbage inevitably cost the company money.