How to improve yourself

Rule 0: keep improving
There is nothing to say about this. You must constantly improve yourself. If you do not enter, you will leave. Today, we will raise your mind a little and take a rest tomorrow. In fact, you are similar to everyone's average. The so-called improvement is to make yourself better than others, to ensure that this can only be the best, that is, to constantly improve your own level.

Rule 1: balance your self first
Everyone has their own features, such as thinking or doing things, or optimistic or pessimistic. How can this problem be understood. Generally, it is easier for a person to be biased in some aspects, or even to go to extremes in some aspects. People I know have people who feel too good about themselves, you also have little confidence in yourself. Generally speaking, going to extremes is not a good thing for your own development. Therefore, you need to make a balance between yourself and others, do not stay in your own circle. Changing your work environment is a good thing from this perspective. Let me give you an example:
I have been working in jgtm2004 for a few days and found that I think too much. I found this problem when jgtm2004 constantly asks do it. At the beginning, I still felt quite unaccustomed, but gradually found another feeling that solved some of my confusion. In fact, thinking is the root cause of confusion, while practice is the basic solution to confusion. Thinking can bring us a lot of problems, and the corresponding problems may be solved, but you cannot know the solution before you start to solve this problem.
In fact, I have also observed this problem before. For example, I have seen many people who have just started programming and those who are not very high have a similar problem. For example, if someone is calling a program and suddenly has a runtime error, and doesn't just look at the variables, they are constantly looking at their own code, after reading the screen for five minutes, the page is not displayed. What's the problem? It is just like reading the program code like reading the Prose in the test image. It seems that some code describes when the program will be in a bad mood, so the error is the same. You need to know that reading code is an advanced capability. You can learn the root cause of errors by looking at the code for more than a year or a half. This capability can be achieved only after years of experience. What you need to do is to first check what the error data is, and then estimate the possible source of the Error Data (that is, to estimate where the control flow comes from ), then set the endpoint to run again. Repeat this step to find the source of the error data. If you do not configure the terminal debugging, but are trying to read the code and then think about where the problem occurs, it is estimated that if you write a program for another five years, you can only stay in front of the screen when the program fails. In other words, you cannot improve yourself.
In fact, this is also the case. I often see other examples: I think someone may be able to crack the keyboard in front of the screen and understand debugging to solve the bug. But you will find that this person has a bunch of errors or problems, such as yesterday, today, and tomorrow. Due to lack of thinking, there is no progress. If you think it is painful to write a program all day, it means you need to learn design pattern and think about it. In other words, it is not a good thing to pay too much attention to it.
Here, I would like to extend this rule:

1.1 when you got a problem, go working on it until it is worked out.
China's education system always injects ideas into people, rather than instilling solutions to problems. When faced with problems, we are always used to waiting for someone to help us solve the problem or tell us how to solve it. If not, we can check the information or close our eyes to find out what happened. In fact, the problem may become simple and clear when you try to get started. Remember, thinking only makes the problem complex.

1.2 When you got a problem continually, go learning, thinking and summarizing.
Many times we don't know how to think about it. When a problem repeats, we need to learn and think about it. It is indeed a solution to the problem, but the constant emergence of such problems indicates that your method has encountered a problem and you need to learn some new methods. What you learn is dead. It means that you can provide a reference. As for how you solve your problem, you need to analyze it on your own. Here we are thinking about it. In many cases, there are not only one method to solve a problem, but also many methods to solve the problem. Of course, different methods have advantages and disadvantages. When is it better to use what method, or when it is more important, what method is better, and why? These are all things that need to be summarized. In fact, there is another link in the middle, that is, start-up. Because when you think about it, there will inevitably be a lot of problems. To solve these problems or confirm your ideas, you need to do it first, and make a conclusion after you finish it.

Conclusion: The first thing you need to do before improving yourself is "balance ". It may increase your efficiency, break through the bottleneck, and lead you into a new field. This is a very important thing. You only need to know what needs to be balanced. Of course, the balance does not mean the average value, so it will lose a person's personality, as long as it is not extreme.

Rule 2: Don't try to make a big step ahead for one time. Divide your target into small pieces, until you can achieve them in days.
For example, if I want to design the overall design of a project, it is obvious that I cannot place every part of the entire system at once, the collaboration between each module, and the specific content of each protocol, so that the code of every function is clear. That is not what normal people can do. Therefore, we need to segment the entire process. First, consider what the general structure of the entire framework looks like and what needs to be done. Then I began to make a rough design of one of the parts to confirm that my idea was feasible, although there may be some problems. Test the other part until you have a certain practical understanding of each part through this method. At this time, you will find that your confidence increases and your thoughts become clearer. Then you can improve a certain part, add more details, and implement functions closer to the finished part. With this continuous loop, the goal will get closer and closer to you, and you can see and determine the whole process.
Here, let me extend it:

2.1 stop thinking about the small pieces of tasks you're not doing. Suppose they're done!
When you solve a small problem and think about other small problems that need to be solved, it is of no benefit for you to solve the current problem. As we have already mentioned above, thinking is the root cause of a problem. When can you solve a problem that arises constantly? In the end, you will find problems constantly expanding and even exploding! What should I do? You have to pretend that the minor problems have been solved. If you are really worried about the problems you are not trying to solve, you have to find a way to complete the current work as soon as possible. For example, you can solve this problem roughly, use a relatively simple framework to reduce the number of functions to be implemented, and so on. In short, we need to solve one problem and then another.

2.2 keep doing small things right will makes you achieve big goals.
Obviously, we can see that big things are actually made up of small things. Only by doing small things well can we fulfill our lofty ideals. In fact, this is only one aspect. From another aspect, if you do not divide big things into small things and solve them one by one, you certainly cannot complete the whole thing effectively. You have not done every small thing well, either you have not broken down your major things into small things, or you are still thinking about your major things all day after breaking them down, these are all obstacles to your success.

Rule 3: Keep learning how to improve yourself
My personal experience is limited to my current experience and my writing time. Although this is what I think is the most important, and I think I will often review myself to see if I have done this, it is not all. Therefore, you need to constantly learn the methods that can help you to improve your own level. (Not specific experience)

If you are free tomorrow, I would like to write about what I have learned recently and may have some helpful experience in construction. This article is a warning.