(1) When you find the wrong code, don't rush to modify, let's think about it, will this code will not cause other problems? If there is no problem, you can make peace of mind. If there is a problem, it may be necessary to change the program structure, not only one line of code.
(2) Some time, many errors that may latency in the software (eg, caused by poor programming habits). It's hard to catch one, and you should win the chasing, all annihilation.
(3) Be sure to return to test immediately after the error is changed, so as not to introduce new errors. Changed a program error is just a happy event, but it is necessary to prevent the music. More stringent requirements are: whether or not the original procedure is absolutely correct, as long as the procedure is changed (even if it is insignificant), it is necessary to return.
(4) Every time you change a often or more important mistakes, you have to analyze it carefully. Why do you have such problems, and more than people around them, you learn from each other, and you can make your own knowledge base.
