Some ideas on knowledge point sorting

In the previous article "a little feeling of Program Development", I mentioned that there are as many knowledge points in software development as leaves, and this situation is often encountered, I forgot a lot of knowledge points soon after reading them. When I used them again, I had to go back and continue to check the information, which greatly affected the development efficiency.
In fact, it is very easy to avoid the above errors. We just need to calm down and carefully analyze the knowledge points. Taking the "class template" as an example, consider: Why use class templates and when to use class templates, what are the benefits of using it, how to declare it, how to define implementation, what should be paid attention to during use, what common methods it has, and what errors it often makes when using class templates. By analyzing and sorting this information, you will surely learn more about the knowledge point. The uncertain understanding of a certain knowledge point in the past will also deepen your memory and understanding.
Of course, some knowledge points may be large or difficult. In this case, we need to decide based on the frequent use of the program, and it is difficult to understand those knowledge points, we do not need to spend too much time on the knowledge points that we usually don't use. We should focus on the most common knowledge points.
For example, enumeration, structure, array, String, overload operator, client-server architecture, and activity object are all frequently used knowledge points. We need to analyze and organize them, convert your understanding of them into text records, and you can read them frequently later.