Imperative ≠ low level. That’s the fundamental issue with this essay. >One way of thinking about programming is that you are ordering a computer to do your bid

Imperative ≠ low level. That’s the fundamental issue with this essay. >One way of thinking about programming is that you are ordering a computer to do your bidding: you, the programmer, sit at the helm of your CPU, afloat on a sea of data, and you have various levers and knobs that you can pull and twist to make the CPU get from point A to point B: load this value into memory slot i. Now add five to it. Now print that back out. Etc. This is called imperative programming, because you tell the computer every step it should take. I can tell the computer complex, high-level things too, not just this pseudo assembly.