I saw this somewhere in my daily reading list (I religiously browse my Google Reader at the start of the day).

I thought to myself that the blog author probably had negative experiences with programmers or architect types who place too much emphasis on design patterns.  I agree that people who give too much importance (or "cool factor") on design patterns will probably see the trees but not the forest.

Personally, I agree with the author that the problem has to be understood before a solution can be applied.  It was said that there was supposed to be this app whose developers wanted to implement all 23 GoF design patterns -- of what use is that?!  It's like putting the cart before the horse.  One has to feel the pain of a particular problem before a solution can become suitable and be appreciated.  That's why I believe in refactoring to patterns.

But that doesn't make me conclude that design patterns are from hell.  Just because one thing can be used negatively by some doesn't mean it's evil -- see for example the internet, or TV.  I had to eat my words not too long ago when I said that enums are evil. I see design patterns as useful in enabling developers to share a common design vocabulary ("you plan to use the state pattern there? that's too complicated, why not use strategy instead...") and it helps me identify possible solutions to design problems.  I wouldn't be proud of my code just because it implements this and that pattern -- I would be proud if it meets user expectations and runs relatively bug-free!