Hi, I am currently trying to figure out which design pattern book is "the best"/"worth the money spend". Can you please recommend some from your experience? level: intermediate/advanced/very advanced (if it matters) What about Head first design patterns (2004)? Patterns of Enterprise Application Architecture (2002)sounds fancy, too? Design Patterns. Elements of Reusable Object-Oriented Software (1995)? thanks in regard

As has been said before, the patterns in the GoF book (Design Patterns. Elements of Reusable Object-Oriented Software) are pretty much considered to be part of the required vocabulary to communicate with other developers these days.

I'd read that first.

Quote: What about Head first design patterns (2004)?

Pretty good for an intro, but some of the examples are godawful. Still, if you're completely new and can find a used copy on the cheap, go for it. At its better moments, it's quite inspirational.

Quote: Patterns of Enterprise Application Architecture (2002)sounds fancy, too?

Read the foreword, then run away. Fowler's book is specifically focused on enterprise software, which he clearly defines as the kind of situation where you have a database, business logic, etc. It's a good book, but highly specialized.

Quote: Design Patterns. Elements of Reusable Object-Oriented Software (1995)?

GoF is the definitive reference, but it's terse and can be difficult to understand unless you already "get it".

Head first, you either love it or hate it with a passion. It induces too much cringing for me, at the least get a sample chapter to see if it's for you.

I partly agree with drakostar about POEAA. Nearly half of the book deals with database related problems and for everything a web application is assumed. Then again, it's not as specialized as you might think. It is also on the introductory level.

The GoF book is good, but a little dry. You can probably do better, but I would still recommend this one out of the tree. When you don't understand something, you just google and it'll work out fine.

Head first and GoF deal the the same subject matter, POEAA is a bit different. You could get both POEAA and GoF.

While I don't agree fully with this guy, I would still suggest you take a read of this and his followup here.

What he has so say is pretty blunt and extreme, however he does have a point. It's mostly just as the saying suggests. When all you have is a hammer everything looks like a nail.

Quote: Original post by instinKt
When all you have is a hammer everything looks like a nail.

Meh. Anything can be misused, particularly by the inexperienced. The common image of someone running around applying as many patterns as they can, wherever they can is not how anyone suggests they should be used.

It's worth noting that design patterns are, by definition, not something one guy pulled out of his ass. They're common solutions to problems that have been independently invented time and time again. Like a dictionary, a collection of design patterns is *descriptive* of current practice, not *prescriptive* advice from on high.

Quote: Original post by drakostar

Quote: Original post by instinKt
When all you have is a hammer everything looks like a nail.

Meh. Anything can be misused, particularly by the inexperienced. The common image of someone running around applying as many patterns as they can, wherever they can is not how anyone suggests they should be used.

It's worth noting that design patterns are, by definition, not something one guy pulled out of his ass. They're common solutions to problems that have been independently invented time and time again. Like a dictionary, a collection of design patterns is *descriptive* of current practice, not *prescriptive* advice from on high.

I agree with you and that's why I mentioned I do not agree entirely with him. I do think it's important to hear what he has to say. It's very easy to be given a tool and be a little over zealous in its use. What Christer gives IMO is a little perspective and warning.