Hand holding mode-Reading Notes for "fun of mode"

Obviously, from the very beginning, I didn't expect that such a thin book would have been worth more than two months, and I am always excited to buy it (now I still follow the old saying "books are not borrowed and cannot be read ). He remembered that he talked to Decland about "DesignPattern" that day. He felt that the book was too thick and there were too few samples. Now I feel the same way. Indeed, "DesignPattern" is too rigorous, and it lacks the desire to get close to it for beginners of OO. This booklet can be an auxiliary book for reading "DesignPattern", like a snack outside the banquet.
"In short, a pattern is also a kind of thing that appears in the world. Its rules tell us how to create this kind of thing and when it must be created. It is both a process and a thing. It is both a description of an existing thing and a description of the process of creating such a thing. -- Alexander [1, 1979]"
"For software, algorithms and data structures are the basic components, and patterns are the same. They are even more like molds that define algorithms and data structures"
"One of the main objectives of a pattern is to capture solutions to repeated problems in a way that is easily accepted by others (and constraints and scenarios that can use these solutions )", from the perspective of semantic expression, the model can convey more information and be more precise. This is also why it is difficult to grasp. Like a couple with a tiny look, if there is no day and night together, it cannot be achieved.
"Each mode should be a supplement to other models. Every new mode should make the system stronger. Such a system can continue to develop without increasing the maintenance pressure or reducing the performance of the entire system. This result is usually caused by an increase in the system. We want to create a complementary framework for each part, and hope that each new part can make the other part stronger"
"The mode does not exist in a vacuum. In fact, a pattern depends not only on itself, but also on all other patterns in the entire architecture. Each mode is composed of other interdependent components ". Patterns are more like the social attributes of software. In a well-designed system, many simple objects contract collaboration to complete complex tasks. It can be seen that the mode can be mapped by the management mode of people. People who are good at understanding models must also be good at discovering social synergy mechanisms.
"Inexperienced developers often do not understand the differences between design and implementation, so these habitual syntaxes become the only way they express their design ideas." "If your only tool is a hammer, you will treat everything as a nail"
"The pattern is independent of the programming language (the opposite of the regular syntax is unique to the programming language ). To some extent, a pattern forms a language, which takes a step further than a programming language, allowing developers to exchange design ideas with each other ....... The pattern itself surpasses any specific language. It is not important to ignore the importance of choosing a programming language, but to realize that programming languages should not limit the valuable technical capabilities we provide"
"When a person is engaged in design activities, his behavior is completely dominated by the existing pattern language in his mind. Of course, with the increase of experience, the pattern language in everyone's mind will change over time. However, at the specific time when a design decision must be made, he must rely entirely on the Mode language he has accumulated before that. No matter how small or complex his design is, his design activities will be at full control of his existing patterns and his ability to combine these patterns with new designs-Alexander [1979]"