I call this 1-dimensional programming and 3-dimensional programming. (i'm working on a catchier title) The sort of "excel but in Java" approach, or the no-code

I call this 1-dimensional programming and 3-dimensional programming. (i'm working on a catchier title) The sort of "excel but in Java" approach, or the no-code lo-code solutions out there work, kinda. They enable the business world equivalent of dropping blood - lots of boxes with if then statements. But try to repeat the blood dripping (or business process encoded in lo-code). Try to use meta-programming techniques to dynamically tweak or even just print it out in logical sequence for the auditors to look at and you have major problems. Computing should be topless - at no point shoukd the format of the code / what it represents be "that's it, no more programming with this data structure". And lo-code deliberately does this for strategic reasons, where as the skull blood coder did it for knowledge and experience reasons And he (?) will have another experience - he will find the ways of being more "professional" with his code, and then he will use his creativity to get what that better structured code affords in the donald norman sense, and he will create something even more awesome than a dripping skull. Mozart was always going to make great music. Giving him an orchestra and teaching him music theory just added rocket fuel.