I think this is the direct consequence of the way IT is taught in many places. The guy was truly a researcher, a scientist. He was able at doing theoretical tasks well, and this is also an important work and good calling. But as I understand he chose the "commercial IT" career. This is not science, in fact they don't need smart people, although they hire them. And the result is you work in a wrong place: too much chore, brain not needed, technical dishonesty, and often you cover your management's ass with your work.
I think programming is easier for those who learned it at non-IT work: they don't have passion for theoretical, ideal things, and every chore solved is a holiday. I did like this. I had no time to argue about semantics/approaches/OOP, just to resolve problems with very limited time. Then I went to professional IT companies, and except for money and some smart guys around, the work isn't inspiring.
I think programming is easier for those who learned it at non-IT work: they don't have passion for theoretical, ideal things, and every chore solved is a holiday. I did like this. I had no time to argue about semantics/approaches/OOP, just to resolve problems with very limited time. Then I went to professional IT companies, and except for money and some smart guys around, the work isn't inspiring.