The hard part of programming is not the code. It is understanding that there is a problem which is solvable, understanding the shape of that problem well enoug

The hard part of programming is not the code. It is understanding that there is a problem which is solvable, understanding the shape of that problem well enough to arrive at a way to solve it, working out that solution, and then expressing it clearly to another entity, whether human or computer. None of these things are special to programming; they are all specialized skilled work that is still hard in fields that do not involve computers. Mathematicians create and communicate theorems. Legislators create and communicate law. Engineers create and communicate designs for mechanisms. Chefs create and communicate recipes. All but the most trivial fields involving one person talking to another rely on a large body of knowledge shared by the participants, and use domain specific language in order to communicate ideas clearly and unambiguously. It is not absolutely required, but it saves an incredible amount of time, misunderstanding and wasted effort. When discussing matters of any complexity, clear communication is vital. There is certainly room for the jargon and workflow to improve; for us to come up with languages that are more expressive in their domain, and for processes that are more intuitive - whether by being closer to what communicating your ideas to another skilled human would be like, or some other way. But the actually hard work can no more go away than in any other human endeavour.