Study Notes on design patterns (16)
------
Summary Here, the "design pattern refinement" is basically finished. The authors of the following chapters did not introduce other patterns, but summarized some methods and precautions for using patterns, the book is summarized. Unfortunately, the author has not completed all the 23 design patterns summarized by gof. However, the author's contribution in this book is to guide readers to learn the design model. In each model, the author repeatedly emphasizes two points: L Object combination rather than inheritance is preferred; L Discover and encapsulate changes. In the book, the author presents his practical experience to readers in a popular analogy. This gives readers a more in-depth understanding of OO and a brand new understanding of OO. The design pattern can be said to be Program The only way to grasp the object-oriented thinking. However, memorizing each mode does not play a major role, just like Algorithm As with the data structure, it is meaningless to allow you to write a quick sort or a search algorithm separately. It is important to use it flexibly in actual development. The same is true for design patterns. The significance of learning is how to apply it to our systems, how to Use crowdsourced security testing to give us a summary of the methods and experience to enhance our system's rationalization and robustness, as well as flexible Scalability (scalability. In this way, we truly grasp the OO idea. (A question mark is required here.) The book design patterns is complete, but the design patterns are not yet complete. As gof described in their book, "design patterns" are by no means a well-shelved book. In the same way, the design model does not need to be learned once, but needs to be learned and learned repeatedly. Therefore, the next task is to continue learning, and the road is still bumpy. The next study should be based on the design model, through the first 10 models and other messy knowledge, now I can understand the design pattern book. In my previous studies, I found that my understanding of polymorphism is very simple. The knowledge of UML is far from enough. In the next study, these two types of knowledge should be further supplemented. I hope the study will be fast and smooth!
Trackback: http://tb.blog.csdn.net/TrackBack.aspx? Postid = 954101
