At work, a project is often completed by more developers, and those who fail to pass are responsible for different modules and undertake different tasks. Generally, svn is used for code storage and version management, but often many developers do not pay attention to these Details often lead to a series of strange problems. This article picks a few personal problems encountered in the development process.
(1) Error update method
The first thing to talk about is the code update method. When individual developers update the code every day, they often don’t like to compare and look at other people’s submission logs, and update directly. For example, in eclipse, click directly without comparing with the resource library. team"-->"update".
The risks of this update method are: <1> If you update the code in a large space, there may be people who modify the same file at the same time, causing conflicts and making the local code unable to use normally. <2> It is also possible that other people's code has not been submitted in full, resulting in the updated code not running normally, and then it is not known who submitted the code. It will take a long time to locate the problem, and the corresponding person may not be found to solve it, which wastes precious development time.
(2) Wrong submission method
After writing their own code, some people submit the code easily without careful verification, and even do not check their own code when submitting, submit the problematic code, or even miss the submission of the code. Cause others to update the code can not be used correctly.
(3) Feel free to fill in the submission log
In the usual work, you must develop a good habit as much as possible. Before submitting the code, you must know the code that needs to be submitted this time. When filling out the submission log, write some contents that you need to pay attention to in the log, so as to facilitate your own inspection. , and also allows others to intuitively see what the submitted code is.