We need code review

1. Purpose of code review
Code review is a process of improving code quality by reviewing code. It plays an extremely important role in the XP method. Code review mainly achieves the following objectives:
1). Improve code Quality
2) Early detection of defects to reduce the cost of defect handling
3). share and improve the development level of team members

2. Code review content
Three levels of code review content:
1). Implementation correctness: It mainly includes whether to implement the expected functions, whether there are bugs, and whether there are performance problems;
2 ). design Rationality: mainly includes implementation methods, data structures, design patterns, and scalability, whether there are a large number of repeated code and other components, whether the package structure design is reasonable, etc, whether there are performance problems.
3). Code Readability: mainly including the Code style and aesthetics.

Implementation correctness and design rationality I think it is necessary to review the content, code readability because each developer's habits and style are different, so it is recommended to make a low-level review, such as whether there is a comment.
There is a special concern in implementation correctness and design rationality. The performance problem here refers to whether it is caused by design and implementation, this may cause the review part to become the bottleneck of the entire module or system, rather than a local optimization that is insignificant. Otherwise, the entire review will become a complete quarrel.

3. Code review mode and time
Code review has many methods, including review meeting, email pass-around, over-the-shoulder, and tool-defined ed code review.
The specific method can be selected based on different teams and projects.
We know that there is a long whip effect in software development, that is, the more problems will be discovered later, the greater the impact will be. Therefore, code review should be performed as early as possible. We recommend that you review code in each iteration.

4. Code review personnel
To review the code, you can specify the owner for each module. Each module has at least two owners, other team members perform code review on the module owner to upgrade the module, and the owner performs code review on each other.

5. Code review tool
Code review has some good tools for reference: http://blog.csdn.net/haoel/article/details/4469462

Code review is the process of discovering problems and also the process of learning and communicating. It requires a flexible, free, and proactive attitude, rather than administrative control and rules and procedures. Consistent with the core idea of agile development, the team can give full play to individual enthusiasm and motivation for learning and sharing after clarifying the ideas, functions, and objectives of code review. Code Review, discussion, reconstruction, and improvement anytime, anywhere.

Refer:

Http://msdn.microsoft.com/en-us/library/ff648637.aspx

Http://www.programmer.com.cn/1310/

Http://www.cnblogs.com/panshuiqing/articles/1147065.html