I apologize for the long quote, but I promise that if you read to the end, you will see that the discussion is germaine.

"I want to point out again the difference between writing a logical and a psychological language.
Unfortunately, programmers, being logically oriented, and rarely humanly oriented, tend to write and extol
logical languages. Perhaps the supreme example of this is APL. Logically APL is a great language and to
this day it has its ardent devotees, but it is also not fit for normal humans to use. In this language there is a game
of “one liners”; one line of code is given and you are asked what it means. Even experts in the language have
been known to stumble badly on some of them.

A change of a single letter in APL can completely alter the meaning, hence the language has almost no
redundancy. But humans are unreliable and require redundancy; our spoken language tends to be around
60% redundant, while the written language is around 40%. You probably think the written and spoken
languages are the same, but you are wrong. To see this difference, try writing dialog and then read how it
sounds. Almost no one can write dialog so that it sounds right, and when it sounds right it is still not the
spoken language.

The human animal is not reliable, as I keep insisting, so low redundancy means lots of undetected errors,
while high redundancy tends to catch the errors. The spoken language goes over an acoustic channel with
all its noise and must caught on the fly as it is spoken; the written language is printed, and you can pause,
back scan, and do other things to uncover the author’s meaning. Notice in English more often different
words have the same sounds (“there” and “their” for example) than words have the same spelling but
different sounds (“record” as a noun or a verb, and “tear” as in tear in the eye, vs. tear in a dress). Thus you
should judge a language by how well it fits the human animal as it is—and remember I include how they are
trained in school, or else you must be prepared to do a lot of training to handle the new type of language you
are going to use. That a language is easy for the computer expert does not mean it is necessarily easy for the
non-expert, and it is likely non-experts will do the bulk of the programming (coding if you wish) in the near
future.

What is wanted in the long run, of course, is the man with the problem does the actual writing of the code
with no human interface, as we all too often have these days, between the person who knows the problem
and the person who knows the programming language. This date is unfortunately too far off to do much
good immediately, but I would think by the year 2020 it would be fairly universal practice for the expert in
the field of application to do the actual program preparation rather than have experts in computers (and
ignorant of the field of application) do the progam preparation.

Unfortunately, at least in my opinion, the ADA language was designed by experts, and it shows all the
non-humane features you can expect from them. It is, in my opinion, a typical Computer Science hacking
job—do not try to understand what you are doing, just get it running. As a result of this poor psychological
design, a private survey by me of knowledgeable people suggests that although a Government contract may
specify the programming be in ADA, probably over 90% will be done in FORTRAN, debugged, tested, and
then painfully, by hand, be converted to a poor ADA program, with a high probability of errors!"

- Dr. Richard Hamming, "The Art of Doing Science and Engineering..." Written in the late 1990s