Is there any correlation between good programmers and books they owned/read?
I had a pleasuring of hiring a person based on his work experience but soon realized that his skills are sub-par.
So I recommended him a reading list - closely matches with your list except my list included 'Design Pattern' and 'Refactoring'. The response I got is pretty amazing - he did not know any of these books. None.
That signaled me two things
- He did not have desire to better himself.
- He treats his employment as a job.
I put 'Pragmatic Programmer' as the first book to read but I haven't yet got any feedback from him so I'm going to assume that he did not purchase or read it. He treats his work as job - come in the morning and push some keys and collect paycheck. I don't know how many programmers in the wild has similiar attitude.
I personally believe that we need to separate the computer books to two broadly defined categories - a) API-baed b) know-how
API-based books are the one you will throw out in a couple of years. 'Know-how' is the one you will keep forever.
One critical point to make is that reward factor of 'know-how' books. There is no instance gratification from these 'know-how' books because it is timeless advices. So it won't answer your questions to how to write socket programming. But it will teach you how to design network based program.
BTW - loved the fact that you included 'facts and fallacies'. It is one of my favorite books but not well publicized. I think everyone should read it.