What happens when programming becomes routine? I expect there will be a very scary moment when we all realize that someone with the right resources has discovered the right learning algorithm, before all of us plebes die.
What happens when programming becomes routine? I expect there will be a very scary moment when we all realize that someone with the right resources has discovered the right learning algorithm, before all of us plebes die.
In programming languages, there has never been a push toward easy programming. Everyone thinks it's great to make people do useless work to become an expert before being able to achieve anything. Elegant, simple, obvious syntax like Python that is suitable for beginners makes programmers scowl: to the point that they would like to require users to learn a new non-obvious meaning for a semicolon, and put it at the end of each and every instruction they write. (Just one of many, many examples, other examples being library and package management, nature of error messages, interfaces, API's, etc etc etc. Everything is about making things harder, to the point that you would be mistaken for thinking that "require user to spend more than 15 seconds interacting with documentation before achieving what is obvious and easy using our solution" is a design requirement.)
I would say that a lot of programmers could program their job out of existence if they wanted to.
At this point it's basically "We welcome our computer overlords." and not only programming will be at risk.
In other words, as some programming tasks becomes routine, many more non-routine tasks become available to us.
Assuming the sheer level of interconnectedness and computational ubiquity where every conceivable piece of matter used by humans out there has a bus or exports a remote API for most of these far-fetched AGI apocalypse scenarios to work, it's probably wiser to worry about crippling cyberwar way before AGI is even a consideration.