You still have to describe to the automaton what you want it to do -- and in doing that, you're programming.
Modern languages are all "automated programming" already -- you aren't writing machine code, you're describing to the automation system what you want, and then it generates the machine code for you.
Faster machines, but with each new language, you still have the baggage of design/code/compile/test/debug/refactor and the library/dependency hell that plagues things like oh, say Node.js with NPM, maven with Java, make with C/C++ etc. etc.
Then there is the flood of new "UI hotness libraries" in the JavaScript space alone. Pick one. wait 6 months and see what else is now the new hotness or if your current one has changed with a new major version release (Angular?).
There should be more folks like Bret Victor working with language teams in the FANG(+MS) companies to drive some further breakthroughs in reducing cognitive load and tool/library dependency complexities.
Where are this generation's Alan Kay and Jean-Marie Hullot types, pushing the envelope on software development environments?
All coding is itself the act of automating something. I don't think there is a risk to developers as there is always more to automate. We use products that automate our own programming tasks to create more code to automate yet more things.
I'm also thinking that how people code could change drastically, but even so, that's less of a problem. Because the rules and logic of any programming language boil down to fundamental computer science principles which should remain constant despite the interface you're using to code, whether it's a keyboard and monitor or some kind of visual drag and drop thing or whatever someone comes up with.