Not my list. This list is derived from the SWEBOK project, an IEEE Computer Society list. It is a very process oriented list. Seven books on UML. I don't know anyone who uses UML. I've never worked at a company that actually used it. At least as many books on Agile Programming; how many do you need? A book on CORBA. Really! Knuth is there; I guess he is mandatory. No other good books on algorithms, but lots on patterns.
The author said that he explicitly left out books on technology. Sure there is a lot of technology cruft out there, but surely there a few language specific books that a good software engineer should read. Or maybe I'm just a hacker.
Since there isn't anything else positive on here right now..
It's a pretty good list, and I think he did a pretty decent job. Sure, everybody's list would be different, but there are some really good books on there that would serve people well to read them. It's interesting that Psychology of Computer Programming didn't make the list, as it frequently does.
It'd be nice to see another list without the exclusions though. K&R (C) and the Llama (Perl) book especially were very helpful to me. SICP made the list, and I kinda consider that a Scheme book.. I certainly learned plenty of programming/CS from other language-specific book. The 4.4 BSD book helped a lot of people too. Had I come up later, Accelerated C++ is a really nice book too.
> No other good books on algorithms, but lots on patterns.
CLRS is on the list; 28.
And I, likewise, was unhappy with his exclusion of technology-specific texts. It seems as though he is asserting that generalizable ideas can only come from books that purport to be general.
The author said that he explicitly left out books on technology. Sure there is a lot of technology cruft out there, but surely there a few language specific books that a good software engineer should read. Or maybe I'm just a hacker.