This is a previous post posted on the Forum. Today, I am talking about the concept of design patterns over the structure in the QQ group. I will move it to my blog and hope more people will see it. I also welcome your comments. I have always considered this topic boring, because I know that the most cheerful and angry people talking about it are often people who do not know much about the thought and structure of the model, or even do not know much about it. Writing this article reminds new users of the design model to stop talking about it, saving time for reading more books and implementing it.
In one of my blogs, some friends said that the learning model should "do not pay attention to its shape, but pay attention to its God ". I don't know how others understand "shape" and "God?
I do not agree with the idea of "don't pay attention to its shape. What is the mode? Where is the god of patterns? The spirit of the model (my own point of view) lies in: inheritance, polymorphism, encapsulation; a higher layer: interface-oriented programming, encapsulation changes, better combination than inheritance; a higher layer: SRP, dip, OCP, LSP, ISP. All these things are available, and before the appearance of the design pattern book. The significance of this book is precisely that it shapes the form, the typical form, and the form of success. The author has made great effort in the orthogonal and pluggable aspects of the 23 modes. If we ignore the "shape", we will not see the pure mode. How can we make comprehensive use of it?