Keep a dump in the program

The main task during this time is to organize CodeIt is similar to code archaeology, so take the time to read "Wukong Chuan" again, otherwise it will be difficult to achieve a balance of mentality.

The revision process is still relatively careful. The bottom line is that tests must be passed, whether self-review, automatic testing, or manual testing,ProgramIt must be consistent with the original logic.

Additional auxiliary tools are required, such as some code review and error correction tools.

The revision steps are basically small pieces to ensure that each module is stable after each revision, and then the common parts of different modules are gradually extracted and summarized, gradually form a unified bottom layer and framework.

Because the code has been revised for a long time, there are a lot of repetitive code and garbage in it, and new functions need to be added according to the requirements, therefore, regular cleaning and sorting are necessary. But how can we centralize changes so that they only have local impacts?

In get thing do, there is a concept of "box", that is, to put some categories into different "Boxes" and then clean the boxes under the agreed conditions, in this way, the work efficiency can be greatly improved.

Therefore, you can open such a "box" in the program to store the newly added functions and code blocks. Of course, the revision is very difficult and can only be solved by marking, I call it a "dump" bin. I only need to regularly analyze the code in the bin and sort it out. When I modify it, if new functions are available, they can be put into the garbage bin temporarily, without interfering with my code archaeology.