Great as always.
Very dense, a lot of food for thought. ( )

after A Pattern Language / Christopher Alexander classics

Design Patterns is a very important reference and its contents are also important, but it is a rather dull book to read. This is mainly because the bulk of the book contains a catalog of patterns. Like most catalogs, it works better when you come to it looking for something specific.

I have two main criticisms of the patterns themselves, both of which stem more from the time the book was written than from any inherent problems with the patterns. First, each pattern contains a list of benefits and consequences. This section never considers the pattern from the view point of testability. This is a pity because most of the patterns, in my opinion, serve to make the relevant components easier to test.

A more serious complaint is that many of the patterns show their age by suggesting implementation inheritance as a good way of implementing these patterns. While implementation inheritance still has its place in the programmer's toolbox, current wisdom shies away from using it merely because it is convenient. Instead, current belief leans more toward preferring interfaces (in the Java sense of only defining operations and not implementations) and reserves implementation inheritance for when it provides a tangible benefit.

That said, most of the patterns still have a useful core, even if some of the details of pattern structure or implementation should be modified to fit better into common practice. Just remember though, if you want to read through it you need will power or a reading group (preferably both). ( )

[I am only going to include 10 tech books, a represtative sample]

Compulsary reading. At the time, (when it first came out) this really affected me. I have always thought that IT is a backwards field, compared to making any other objects, and this is the first step in the right direction. ( )

A classic in the field of computer science, this book describes how object-oriented software can be used to develop meaningful (and reusable) classes. It is written by the so-called "gang of four" affiliated with a working group at the University of Illinois. It has achieved notoriety for its assistance in helping programmers write code more effectively in languages like C , SmallTalk, and (my current language) PHP. The book has started a large movement in identifying design principles that are inherent in all computer science problems.

The book reads like a catalog of class types. After an initial critique on the state of computer programming, it reads like a textbook and a reference manual to be used. It is academic, analytical, and brilliant. Obviously, the book is only for the serious programmer who aspires to master her/his trade. It is not for the casual programmer or even for the intermediate programmer. It does not hold the reader's metaphorical hand as the book is perused. Instead, it provides data and analysis like a research paper. Of course, in such a style, wisdom is distilled into compact sentences.

I'll be happy to put this book on my bookshelf at work and refer to it when designing software. ( )