本文出處[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 "Design Patterns" Aren't[2], 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

[2] http://perl.plover.com/yak/design/samples/

轉載于:https://www.cnblogs.com/hanhuilee/archive/2012/12/19/5221416.html

總結

以上是生活随笔為你收集整理的Rethinking Design Patterns - from Jeff Atwood的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。