I can not complain about how the book is structured and the case study it starts with. But from that point onward it’s going straight downhill. As I and other colleagues have come to realize after reading it, no sense of gratification is fulfilled, like other good technical books we’ve read. Basically I have finished the book with the same knowledge I’ve dived into it.

The book is too technically verbose, and lacks a simple way to describe the problems that the patterns solve.

If I weren’t familiar with most of the patterns provided in the book, I don’t think I would have managed to make sense of most of them while at the first read, and that is the excuse the book has to offer. The more you read it, the clearer it gets. Unfortunately that is not an excuse, especially for a book… and that is why I clearly wouldn’t make this book a recommendation for any fellow developer. It may have been da funk when it was first published, but it’s content does not shine that much in current days when we all are already used with design patterns, and do not see them as things that mystically solve problems.

Baseline: the easiest way to learn design patterns, is by facing the problems they solve on a daily basis; through programming.

This website uses IntenseDebate comments, but they are not currently loaded because either your browser doesn't support JavaScript, or they didn't load fast enough.