Coding Horror: Programmers Don't Read Books -- But You Should
codinghorror.com
codinghorror.com
Not exactly what I would consider "being a programmer", but to each his own, I suppose.
I agree with point #2, and perhaps he does as well. He has said much the same thing, openly, and he has also said that his mission is to provoke them into hoisting themselves up a little beyond that.
I apologise for the terrible analogy, but perhaps Jeff's blog is like a car's first gear. It exists to overcome a large amount of inertia and get an object at rest to start moving, slowly. Other gears take it from there.
I personally wish he would push them to explore towards more free software and tools rather than stay on the Microsoft plantation, but if he can get anybody to read just one more book this year, the essay is a win.
Heck, if it can remind me that I need to read one more book this year, it's a godsend for me.
But I get your point.
Atwood definitely does write about simple ideas, though. His blog is packaged to be consumed for programmers of all skill levels. As a result, it's often a little bit mundane for those with higher levels of knowledge.
That said, I think the reason that I enjoy Knuth so much is that he is a mathematician; admittedly, I'm biased, as my formal education background is rooted in mathematics as well. The nice thing about this is that Knuth not only knows what he is talking about, but that he doesn't tend to skip fundamental steps. Nor does he play the notation games that are so often found in computer science texts.
Speaking of 'notation games', why do they use 'equals' for 'set inclusive'?
So, yes, to learn how to program in language X, the Internet is probably a better resource than the average book. But to learn how to program well, a proper bookshelf is invaluable.
Not one of his best sessions, in my opinion, but still pretty damned interesting.
One example of this is "JavaScript: The Definitive Guide" (the Rhino book). In some respects this is exactly the kind of book that the article is criticizing: it's huge, it tries to be a reference book, it's specific to a single technology, it's about something that real programmers should be able to figure out on their own. But it was much quicker to read it than to try and make sense of the scores of tutorials out there that each explain one small part of the language. Yeah, I could have all figured it out anyway, but that doesn't mean it would have been the best way to do it.
Heck some people probably have books like "Rails for PHP developers" or "Rails for Java developers" or "Moving to Rails" (if exist).
Computer book fan