A thorough analysis of 23 design patterns with one tank battle, with notes, tutorials, and PPT

Introduction

Design patterns represent best practices and are usually adopted by experienced object-oriented software developers. Design patterns are solutions to general problems faced by software developers in the software development process. These solutions are summed up by many software developers after a long period of trial and error.

A design pattern is a set of code design experience that has been used repeatedly and is known to most people. Using design patterns is to reuse code, make it easier for others to understand, and ensure code reliability

Why learn design patterns

1. Understand the source code: If you don’t understand the design, try to look at the source code of Jdk, Spring, SpringMVC, I0, etc., you will be very confused and you will be hard to move
2. Take a look at the code of the predecessors: when you go to a company, are you taking over new projects? It is very likely to take over, don't the development of the predecessors use design patterns?
3. Write your ideal code: I personally do this anyway, I will be very serious about my own development projects, I treat him better than my girlfriend, and treat the project like my own son

Best practice

Design patterns have undergone a long period of development, and they provide the best solutions to common problems faced in the software development process. Learning these patterns helps inexperienced developers to learn software design in a simple and quick way.

23 design patterns

1. Creation mode

• Singleton mode
• Abstract factory pattern
• Factory method
• Builder mode
• Prototype mode

 

 

 

2. Structural model

• Adapter mode
• Decorative pattern
• Appearance mode
• Agency model
• Bridge mode
• Combination mode

 

 

 

3. Behavior pattern

• Chain of Responsibility Model
• Command mode
• Parser mode
• Iterator mode
• Intermediary model
• Memo mode
• Observer mode
• State mode
• Strategy mode
• Template method
• Visitor mode

 

 

 

Due to the length of the copywriting, the 23 design patterns in a simple and simple way are all sorted into a practical document. Friends who are interested in this document, forward + comment, follow me and add VX: MXW5308 to receive it for free.

Use a tank battle to thoroughly explain 23 design patterns (video, notes, PPT)

Lecturer: Horse Soldier

 

Teacher Ma Yingjun takes you to a thorough understanding of the inner strength of design

The content of these design patterns is actually applied in an engineering project (Tank Battle).

For a technical point, if the difficulty of understanding is 1, the difficulty of self-realization is 3. The difficulty of integrating the application in the project is 10.

It's like practicing martial arts and learning tricks. It's easy to watch other people play, but it's hard to practice by yourself. It's even more difficult to master all kinds of tricks and fight against your opponent.

In these modes, I did not stop at the theoretical explanation (that is actually very simple), but insisted on using the code to speak, using the code that can actually be used.

For example, in the factory model, I directly talked about the SpringIOC principle.
For example, in the dynamic proxy mode and the Visitor mode, I directly talked about ASM.

Also, I didn't follow the ordinary way, first talking about theory and then about practice. The teaching method I adopt is to practice first and then summarize the theory.
According to the feedback, this method is easier for students to understand.
Almost 100% of the students will feel the substantial improvement in programming skills after listening to the design pattern.

Project tutorial notes PPT