How to eat a java project?

knows that the netizen asks:

Let me talk about my own situation first: I just knocked on the Java project against the video. The bugs encountered in it can still be solved, but every time I finish typing a project, I feel very empty. The knowledge points in the project seem to be understood but not Understand, how can I master the knowledge points used in a project? At least I won't be able to remember what this project is after a month and a half.

Write a blog record? , Draw a mind map? Or what? Is anyone here who can give some experience?

---

My answer:

First of all, it’s far from enough to just do the project against the video, because you follow the author’s normal ideas, and the author generally doesn’t tell you the process of stepping on the pit, and it is often presented in front of you. Very complete project with few bugs. So you lack a process of proactive exploration, and the process of exploration is the process of real growth!

Then, you are missing the necessary notes. As you said, after learning, I don’t know what I have learned. Regardless of whether it is the way of notes or maps, I think it is necessary. The map can sort out the knowledge points, but the map can't record a lot of text, and can't paste code. So, in fact, I suggest writing a blog record.

There are two types of project notes, one is called project interpretation notes and the other is project development notes.

So next, I teach you how to write these two note-taking blogs

1. Project development notes

This kind of note generally refers to a note blog that gradually completes the development process of a project from 0 to 1. This type of blog is usually popular with readers and is the most detailed.

I usually do this, for example, I plan to do a blog project. I will directly use idea to create a new springboot project, and then write a readme.md file, first simply define the functions, technology stacks, and database tables I want. After having these few things, in fact, basically what the project needs to be made is already known. Next, I will develop the entire project according to the function points. There will be many pit-stepping processes, description of the problem and repair process. All records are simply in the readme.md file. Or the design process of developing a certain function can be simply written first. In short, this readme.md is actually a simple note-taking process. You don't have to care about the good-looking notes, because this is not the final project development process notes.

For example, I recently planned to develop a simple note for a programmer's daily note project:

After the entire project is developed, that is, after the project has a final presentation, I will start to consider writing notes on the project development process.

Then I will create a new project, and then what needs to be done in the first step, and what to do in the second step, I will first define the directory framework of the entire note.

back-end development directory:

Front-end development directory:

In fact, the development architecture of a springboot project is somewhat similar, which can be roughly divided into: architecture code and business code.

The architecture code is roughly divided into:

• Framework integration
• Global exception handling
• Unified result package
• Entity verification
• Security attack defense
• Common tools
• Permission and session control
• System security monitoring
• and many more

For business code, specific business functions are basically added on the basis of the basic system architecture, such as adding, deleting, modifying, and checking blog entries, column display, and search functions.

So if you think about it this way, the development process of a project is simple, first write the process of building the system architecture, and then write the business code. Not at all lost. Just apply the knowledge you have learned step by step. Write more about your experience in the process.

I have written the development process of three projects myself, a blog project vueblog with separated front and back ends, a front-end back-end management system vueadmin, and a traditional blog project eblog.

All three projects have videos and documents. If you are interested, you can go to study:

1. Super detailed! 4 hours to develop a SpringBoot+vue front-end and back-end separation blog project! !

Article: https://www.zhuawaba.com/post/17

Video: https://www.bilibili.com/video/BV1PQ4y1P7hZ/

2. Vueadmin, front and back background management system

Front-end notes: https://www.zhuawaba.com/post/18

Back-end notes: https://www.zhuawaba.com/post/19

Video: https://www.bilibili.com/video/BV1af4y1s7Wh/

From 0 to 1, complete the Springboot open source blog project eblog! https://juejin.cn/post/6844904176938385421

2. Project interpretation notes

The project notes are relatively simple, which is the interpretation of open source projects, such as the renren-fast project. Like project development notes, I usually look at the basic system architecture and business code. When I encounter a design that is different from mine, or a design that makes my eyes bright, I will record it. Usually I just post the code and then add it. My own explanation, make this functional point clear. Similarly, after reading the entire project, I will start to write a note list to see what needs to be written. At the beginning I will generally explain the role, function, technology stack, interface, etc. of the project. Information, and then the following is the anatomical function point.

For example, the renren project:

If you want to see specific articles, you can go to this link. They are all my original articles. You can follow my official account: Java Questions and Answers. grateful.

1. must-read classic project, web development framework -fast project interpretation 161a8841aa097e: https://www.zhuawaba.com/post/86

2. see the cloud stepping pit record of the spring cloud open source project Pig : https://www.zhuawaba.com/post/87

3. Another classic open source project Guns is completely interpreted, the small Hub is great! : https://www.zhuawaba.com/post/88

The above is all, I hope to thank you, thank you for inviting to answer!