Yes, this is a problem that has existed for a long, long time. Consider the origin of HLLs. Waaaay back when COBOL was born, at least some of the people involve

Yes, this is a problem that has existed for a long, long time. Consider the origin of HLLs. Waaaay back when COBOL was born, at least some of the people involved, seemed to be thinking that, instead of writing a new program each time one was needed, they only needed one program: a compiler. Non-programmers could interact with an easy, human-readable description of the software (in COBOL), and the compiler would do the actual coding. For those who prefer to think of the "inner platform" effect, the above is a clear example. The two platforms are the HLL and the machine code. But then we can see that the idea of having multiple platforms, might not be a bad thing (unless you'd prefer to do all your coding in machine code?). A lesson to be learned from all this, is that duck programming is not a problem with the tools or the code itself, but with the way we think about and manage these. > ... that is thought to be “not programming” .... Exactly.