Some thoughts in the daily development process

    In recent days, I have been plagued by bugs. Many bugs were caused by a function that was made before. The layout was too big before, and the gap was too far before. Some problems broke out from this aspect. In fact, it may be other problems. Caused, all these various factors caused today's results.
Think about how you can fix six or seven bugs in a normal working day, but it also includes time for bugs to be returned. At that time, there will be a regression time for testing. Think about a bug, how long does it take from discovery to closure? It has been a long time, so at this time, I think it is very necessary to strengthen the self-test at this time.
    1. I don’t usually write unit test cases, but simply run the program from the business level. I think the code layer must at least ensure full coverage, and it can’t cause full coverage. If you accidentally leave yourself a hole, then there will be some problems.
    2. During functional writing, you can look at other people's code, but try not to touch other people's code. Some code, although it seems to be problematic, has actually been used for such a long time, there should be no problem. If you change someone else's code rashly, especially if you don't know the business scenario, the possibility of changing someone else's code to cause problems is very high.
    3. I still want to explain one point. I would rather develop a slower progress or fix bugs. You can do more self-testing to reduce defects caused by your own code. Look at other people's code and learn more about the entire system. After a period of accumulation, You are probably the one who knows the system best.