我认为您需要检查一些您作为开发人员遇到过的问题，当您因为另一个设计更改而不得不第十次修改代码时，您会感到非常紧张。你可能有一个项目清单，你觉得有很多返工和痛苦。

From that list you can derive the scenarios that the Design Patterns intend to solve. Has there been a time where you needed to perform the same series of actions on different sets of data? Will you need to be able to future capability to an application but want to avoid reworking all your logic for existing classes? Start with those scenarios and return to the catalog of patterns and their respective problems they are supposed to solve. You are likely to see some matches between the GoF and your library of projects.

I would think it is also difficult to study design patterns. You have to know more about OOP and some experiences with medium to big application development. For me, I study as a group of developers to make discussion. We follow A Learning Guide To Design Patterns that they have completed the patterns study. There are C# and JavaScript developers join together. It is fancy thing for me is the C# developer write codes in JavaScript and the JavaScript developer do the same thing for C# codes. After I leave a meeting I also research and read a few books at home to review. The better way to understand more and remember in my mind is to do blogging with examples in both C# and JavaScript in here http://tech.wowkhmer.com/category/Design-Patterns.aspx.

我建议首先在去了解每个设计模式之前请先了解模式的名称。此外，如果有人知道这个概念，请解释并给出一个例子，不仅是编程，而且是阅读世界。

例如:

工厂方法:

阅读世界:我只要给钱5美元、10美元或20美元，它就会生产出披萨，而不知道它是如何生产的，我只会得到一个小的、中等的或大的披萨，这取决于我投入的钱，这样我就可以吃或做任何事情。

编程:客户端只需将参数值$5，$10或$20传递给factory方法，它将返回Pizza对象。因此客户端可以使用该对象，而不知道它是如何处理的。

我不确定这能帮到你。这取决于与会者的知识水平。

问自己这些问题:

他们做什么?

它们是如何耦合的?

什么时候使用它们?

什么时候不应该使用它们?

什么缺失的语言特征会让它们消失?

使用它会导致什么技术债务?

有没有更简单的方法来完成工作?

对于这样一个老问题，我只有两分钱

有些人已经提到，实践和重构。我认为学习模式的正确顺序是:

学习测试驱动开发(TDD) 学习重构 学习模式

大多数人忽略了1，许多人相信他们可以做2，几乎每个人都直接去做3。

对我来说，提高软件技能的关键是学习TDD。这可能是一个痛苦而缓慢的编码过程，但首先编写测试肯定会让您对代码进行很多思考。如果一个类需要太多样板文件或者很容易崩溃，你很快就会注意到不好的味道

TDD的主要好处是你不再害怕重构你的代码，并迫使你编写高度独立和内聚的类。如果没有一套好的测试，触摸没有损坏的东西就太痛苦了。有了安全网，你将真正冒险对你的代码进行巨大的更改。这是你真正开始从实践中学习的时刻。

Now comes the point where you must read books about patterns, and to my opinion, it is a complete waste of time trying too hard. I only understood patterns really well after noticing I did something similar, or I could apply that to existing code. Without the safety tests, or habits of refactoring, I would have waited until a new project. The problem of using patterns in a fresh project is that you do not see how they impact or change a working code. I only understood a software pattern once I refactored my code into one of them, never when I introduced one fresh in my code.

练习练习再练习。我认为4到5本书在没有大量练习的情况下是一种过度的阅读练习。我认为，做到这一点的最佳方法是开始使用这些模式重构您当前的项目。或者，如果你没有任何正在积极进行的项目，那么就按照你自己的方式来做，然后尝试重构模式。

如果你没有亲身经历过他们所解决的问题，你就无法充分欣赏他们。请记住，它们不是银弹——你不需要记住它们，并在飞行中努力应用它们。我的意见…

你试过《四人帮》这本书吗?

设计模式:可重用面向对象软件的元素