Gitlab hero border pattern left svg Gitlab hero border pattern right svg

What is a code review?

What is a code review, and why is it important?

Code reviews act as quality assurance of the code base. Software developers should be encouraged to have their code reviewed as soon as they’ve completed coding to get a second opinion on the solution and implementation. The reviewer can also act as a second step in identifying bugs, logic problems, or uncovered edge cases. Reviewers can be from any team or group as long as they’re a domain expert. If the lines of code cover more than one domain, two experts should review the code.

Code reviews are methodical assessments of code designed to identify bugs, increase code quality, and help developers learn the source code.

Developing a strong code review process sets a foundation for continuous improvement and prevents unstable code from shipping to customers. Code reviews should become part of a software development team’s workflow to ensure that every piece of code has been looked at by another team member. The code review process is an important part in spreading knowledge throughout an organization and shipping high quality products to customers.

A computer screen with lines of code surrounded by four people, one trashcan, and one symbol to show work in progress

What are the benefits of code reviews?

What are the disadvantages of code reviews?

Ready to learn more about code reviews?

Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license