Stuart Halloway has an article in his blog on Relevance LLC entitled Design Patterns are Code Smells.

Am I missing something or is this stating the downright obvious? A Design Pattern is a commonly used solution to a design problem in that particular context, i.e. using that particular language. Taking that solution out of its original context (by moving it to another language, say) means that it needs a complete re-evaluation of both the nature of the problem and the solution itself.

I think Stuart misunderstands ‘Design Patterns’ as ‘Code Patterns’ - they are not. They are design solutions where, for convenience, code examples are given. Of course that means that, for the purposes of code reviews, each team needs to formulate its own set of acceptable code templates, adapting each pattern to the language and framework being used.