Recently I am very interested in unit testing.

I have been thinking about what a great programmer I have been talking to since I talked with chunge last time. I think the best thing I can do now is to control my own system, because from the very beginning, this system was developed by myself. I was new to Linux this year and new to python at the end of last year, so I am not familiar with the entire environment. I roughly estimated that I took the most time to test. In addition, problems still occur after testing, and online products are directly suspended. Later, our technical boss told me that it is best for computers to do everything, including publishing, including monitoring, log analysis, and testing. Later, I decided to write a unit test for each function to be developed. In this way, I only need to write the test code once, and then I only need to execute the test, instead of starting the environment manually.

However, I have read a lot of articles, but unit tests are not very useful .. Ah ~~ Come on.

I was told a few words by my boss today, mainly because I was too careless... When I came back today, I tested my typing speed and found that my typing speed dropped a lot. I lost my previous 250 scores, and I didn't need to use the standard method for typing, I went home every day for a week and contacted the standard fingering Method for typing at a speed of over 250. Unfortunately, I didn't develop the standard fingering habit, so I didn't have a good practice. Now I am new to the standard fingering method. I recently went home to write code every day. I haven't read the QQ space for a long time. Today, I visited the QQ space and found that I was watching the fastcoloredtextbox control on codeproject for 12 years. At that time, I helped Zhu kaidi write the OJ offline submitter, think about it. Then I went to the space of the evil spirits. This guy is always so passionate. From compilation to mode, from the bottom to the top, he has thoroughly studied it, it seems that I am really too watery. So I decided to go home later and do not do anything about the company, but to learn and summarize. I believe that I will have a qualitative change after a period of time ..

Record what I want to do next

Read tornado source code,

Learn the C language, write small works in the C language, and cultivate sentiment. (C language is really powerful. I regret that the university did not study C language well, but had to learn. net)

Continue Learning unit testing. Take a look at the profile performance test.

The following are relatively good books:

Python source code analysis, agile development, and resolution eXtreme Programming