The purpose of design patterns
The process of writing software, programmers face challenges from the coupling, cohesion and maintainability, scalability, reusability, flexibility, and many other. Design Patterns To make the application more
1. Code reuse (ie: the same function code, do not write many times)
2. readability (ie: Normative programming, programmers to read code)
3. Scalability (ie: when you need to add new features, very convenient, referred to as maintenance)
4. Reliability (ie: when we add new features, there is no effect on the original function)
5 so that programmers do exhibit cohesive, low coupling characteristics
Seven principles of design patterns
1. Single Responsibility Principle
2. Interface Segregation Principle
3. Dependency Inversion principle
4. Richter substitution principle
The opening and closing principle (OCP)
6. Demeter
7. Synthesis of multiplexing principles
Where is embodied in software design patterns in the
Object-oriented (OO) -> function module [+ mode design algorithm (Data Structure)] -> framework [using a variety of design patterns] -> Architecture [Cluster Server]
You may ask questions during the interview
1. What kind of design patterns
2. How to use
3. solve the problem
Share verse
Scott Mayers famous quote in the book is his masterpiece "Effective C ++", "the difference between C ++ and C ++ novice veteran is to have a lot of scars on the back of the former." Meaning that a good programmer is stepped on a lot of pits, we received a lot of hurt in order to grow. Design patterns are summarized in the previous step on the pit and the development process experience, so learn to use design patterns can make a novice programmers to efficiently develop the business.