Can I play with the design model?

Recently designed Article It's not the first time that a technology has been played or put into the story, there is even a book devoted to design patterns. But can the design pattern be mentioned in the play?

First, let's explore why this method is used. When the design model was just launched, it was touted by countless Titans. All those who want to play Oo must learn, so the design model swept across the north and south, and all the books that were tied to the design model were sold. Render manager does not understand Oo, has no experience, and is a real fake meeting. It is a closed-mouth design mode. I'm sorry to say hello to others if you can't just say a few patterns or draw a UML. However, the four-person gang's original design model is really hard to learn and understand. The text is from zou Zou, a lot of unsuitable environments, and there are more than one implementation method (such as adapter). In addition, the UML between the modes is somewhat similar, it is very difficult to chew a book. Therefore, some articles and books that help you understand and learn design patterns more easily emerge, such as design pattern analysis. However, some people think that the design model is too difficult to comprehend and have expressed their need for a simpler approach. As a predecessor who understands the design model, it is necessary to help the later generation, as a result, there was a book "big talk Design Pattern".

There is a saying: "the value of things that are easy to learn is certainly not high ". If everyone can learn one thing, it will become a natural thing like eating, drinking, and breathing. Everyone will naturally be less valuable. As a method summarized by our predecessors, the design model has great value. Although with the development of software technology, it will become a common thing sooner or later, just like data structures and object-oriented systems, however, its own complexity determines that its value will not change. Even if more and more people are familiar with it, its own meaning still exists, and its value determines that it is equally hard to learn. So how can these books become studious?

After reading "design patterns", I had to memorize it completely. because of lack of experience, I cannot understand the reasons and benefits of many models. Later, in order to better understand, I read the design pattern analysis, a good book that many people admire and praise. However, after reading the design model, I felt that it was not in the same level as the design model. In order to make the design model easier to understand, I removed a lot of content from the design model, I learned less and described less. Of course I learned more. After a few years, I have gained some experience in the design model. I have read the "big talk Design Model" and I have not learned anything related to the design model, let's take a look at it. It's purely because of the drama, not the design pattern itself. It can be said that it is less than things described in design pattern analysis. The more you say, the less things there are, the farther away from the real design model.

The design pattern itself is a way and method to solve specific problems in a specific environment, only because specific problems in a specific environment are common, therefore, it is summarized into a book and 23 and the design model. However, in the actual environment, these problems are not exactly the same as those in these environments, and some environments and problems are inherently different, but the solutions are similar. This results in the author spending a lot of pen and ink to describe what is the motivation of each model (what is the problem solved), what kind of good news, what are the side effects, and some workarounds/variants of implementation methods, of course, there is also a UML and reference implementationCode. However, in some subsequent books that want to make the design model easier to learn, some content is removed more or less. The most common one is the use of the environment and side effects, the code and UML diagrams are the most retained, and the motivation section is generally unclear.

Can you tell me the design model? I think so. It can make your learning easier, smile, and have a better mood. It also makes you more interested in learning the design model. However, the play is just a play, and it cannot be taken seriously. I think this is all about the design model. To really learn the design model, the play is just the beginning. It requires a lot of practice to understand it. It requires a good grasp of OO and project experience. For those who have mastered the design model, it is just a matter of adjustment. For those who have not yet started, it is an interesting stepping stone and a place to help you get started, however, no matter how many scenes you read, what you learn is not a design pattern (but a reference implementation). Finally, you must pick up the design pattern to see the real design pattern.

PS: the design model has gone through more than ten years without knowing it. We look forward to a revised version, and the changes and progress of the design model will be added to the past ten years.