If you check out the Microsoft Visual programming tools, the process is basically automated. You drag and drop icons for the resources and processes to apply, select the files, database links and constants you want to use, and the tool creates the program/module/code for you. The skill comes in when you start applying and combining libraries of procedures together. That's where system and program design is needed. You need to know what CAN be done as well as the best practices for accomplishing the objectives.
4th gen programming removes the programmer from the code in most respects, creating an environment of "building blocks" consisting of code modules. All you need to learn is what pieces to use and how to use them. As I stated, there are tools to make that process graphical -- no coding required.
Systems Engineers, system designers and system level programmers get paid much more than "coders."
I am a Systems Engineer, System designer, and a System level Programmer.
My favorites are "real time" design and systems integration.
I left out the necessity of software design as most people
think all you do is "code".
In many ways being a computer science type is boring
dull work.
I'm also an Electronics engineer so I have done the hardware side as well.
I prefer VHDL tools for modeling, development, validation, and execution.
Contract out the fabrication part.
I assume your point is you just can't take a worker and plug them in
where it takes years of formal education, topical, schooling,
and practical experience to be worthy of a decent paycheck.