本文出处[1]
...
It's certainly worthwhile for every programmer to read Design Patterns at least once, if only to learn the shared vocabulary of common patterns. But I have two specific issues with the book:
- Design patterns are a form of complexity. As with all complexity[肯定是复杂了，至少不直接了], I'd rather see developers focus on simpler solutions before going straight to a complex recipe of design patterns.
- If you find yourself frequently writing a bunch of boilerplate design pattern code to deal with a "recurring design problem", that's not good engineering-- it's a sign that your language is fundamentally broken[不同的语言有不同的应用领域，不可能同时满足所有领域要求].
In his presentation , Mark Dominus says the "Design Patterns" solution is to turn the programmer into a fancy macro processor. I don't want to put words in Mark's mouth, but I think he agrees with at least one of my criticisms. [这句话比较搞]
...
备注:Jeff Atwood是Stack Overflow和Stack Exchange Network的联合创始人
[1] http://www.codinghorror.com/blog/2007/07/rethinking-design-patterns.html