This reminds me of something I've read about writing:
"A writer is someone for whom writing is more difficult than it is for other people." -- Thomas Mann
I wonder if this also applies to programming.
That is, perhaps the reason programming for Knuth is so hard is that he has such high standards and that he's working on such difficult problems.
http://www.cs.princeton.edu/introcs/42sort/
According to Knuth, the first binary search algorithm was published in 1946, but the first published binary search without bugs did not appear until 1962.
http://googleresearch.blogspot.com/2006/06/extra-extra-read-...
http://www.cs.princeton.edu/introcs/papers/bentley-binarysea...
Programming is sometimes hard and sometimes easy. One of the things that makes it very hard is having a standard that demands the complete absence of bugs.
Fortunately, sometimes buggy programs are useful anyway.
Perhaps programming is so hard ... that teaching it is easy.
If programming is so hard that an older programmer has little teacher younger programmers, then everyone is equal when trying to the mountain.
Charging a machine-gun nest with only bayonet is incredibly hard. Learning all you can learn in attempting this is fairly easy...
Probably not true but worth tossing around in your mind.
Jon Skeet wrote a blog on the topic: http://msmvps.com/blogs/jon_skeet/archive/2009/01/29/program...
Jon Skeet is right. Programming is hard, except the most trivial tasks. And anything that is not trivial is probably broken. But we're OK with things being a little broken, and we've made users bend to our will sufficiently now that we have pushed much of the cognitive load to the users.