Use Code Review

Individuals write their own code without a review process, which is indeed faster. Developers will naturally like and have this kind of preference, because it feels free and there are some ugly places that will not be seen by others...

However, if a program is maintained by many people and requires high quality and stability, code review is needed to ensure code quality.

Code review is not only an effective way to improve the software quality, but also an excellent time for the old team to impart knowledge and experience to new team members.

It takes a lot of time to carefully review the code. New users should seize the opportunity to learn from their experiences. If a review is corrected once and appears again for the second and third time, the developer's attitude may be wrong.

A common mistake in code review is to find a personal review one minute before delivery. In this way, you may find a major problem, modify the progress of the test, or discover a potential but does not affect the function, because it is about to be delivered, so it is not corrected, in this way, more and more traps may be found in the Code or the Code will become ugly...

Code review needs to reserve time for possible modifications and tests after review.

Bytes -------------------------------------------------------------------------------------------------

For more blog posts, please subscribe to RSS. For more Weibo posts, please follow @ Qianli lone row nerd