Anyone who's old enough will remember several waves of "eliminate the programmer". What was the first technology aimed to do that? COBOL? Anyone have a good gu

Anyone who's old enough will remember several waves of "eliminate the programmer". What was the first technology aimed to do that? COBOL? Anyone have a good guess? In any case, yawn to the eliminate the programmer stuff. Been there, done that, history repeating itself for the n+1 time. here's what's always happened and what will happen again: the framework being presented as a programmer antidote will come up short to business requirements. then there will be a scripting layer built on top (if not already). And boom, you will need a programmer to implement these scripts for customizations. So in reality you are just adding an abstraction layer to the mix. Those layers are why we don't program in assembly anymore, they are why we don't manage our own memory anymore (yeah lots of unmanaged tech out there, etc). That's also why we don't compile stuff anymore (see previous disclaimer). Etc. Just more of the same stuff, one more abstraction layer.