Code review in the area of software development is a good thing or a bad thing

In the area of software development, code review appears to be a controversial, fairly peaceful topic.

The prevailing view is that code censorship is a good thing. Some companies or organizations even force the requirement to audit the code as a necessary process.

Review is a good measure to catch bugs and problems. The ability to share domain knowledge and improve code quality through code reviews. Code review provides a good opportunity to monitor, educate, and strengthen the team.

At least in theory ...

When you roll up your sleeves, code review is likely to turn into a bad thing when you face the pressure of a real project plan.

Censorship is an activity that leads to hatred and fragmentation. It makes people wonder whether the code is written correctly, and it provokes people to preach sermons about their own coding standards. Code review is a day-to-day activity, and whether it executes correctly or not is the result of a team's development efficiency or strangulation.

For a team, effective code review is a middle-of-the-road route-it will not be a silver bullet to solve all problems, nor a poison to hurt the team.

After some thinking and discussion with some colleagues, I think that the success of the code review is about the factors of trust and training.

Team members must believe that feedback from code reviews is not a judgment of individual attacks or of their abilities. The censor must believe that the censor will not resent you for making improvements.

Team members must look at code reviews as a platform for ongoing constructive feedback, rather than as a tool for rating team members or creating negative radical statements.

When a team is composed, trust is not inherent in the team members.

and training people on how to properly conduct a code review allows people to build trust in the review process.

Of all the project teams I've been in, I've found that learning how to do code reviews correctly is to get people to review their code. After that, you will know how to do code review for others! This approach provides a number of real-world scenarios to explain how to conduct code reviews.

Train the novice how to correctly present a review opinion and tell them what to focus on in order to give valuable advice to experienced programmers. Directs the team leader to give the reviewer support at the appropriate time, point out the meaningful appraisal opinion, this can strengthen the trust of the team, make the team members respect each other.

So is code review a good thing or a bad thing?

It depends on the desire of your team to make it a positive measure. As with any development methodology, it is not possible to simply bring it in-you have to make sure that you are using it in the right way.

This article in the original English link: Code reviews:good idea?