freeCodeCamp/client/src/pages/guide/english/working-in-tech/code-reviews/index.md

---
title: Code Reviews
---
## Code Reviews

Code reviews are common practice for many software development teams. Code reviews involve 
team members looking into each others' code submissions to check for bugs, incorrect logic or 
potential improvements. To those who have not experienced the code review process before, 
it can be intimidating, however, it is an invaluable process to help you 
grow as a developer.

Is is important to be humble throughout the code review process. Accept your mistakes, 
and be professional when pointing out improvements or errors in the code of your fellow
team members.

Code Reviews exist in order to improve the quality of the code in a software project.
A code review can be done amongst developers of the project under review, as well as developers from other teams in the same company.
Even if a review is just an explanation of the code to another programmer, the feeling that your code is going to be read/ inspected by another programmer as well makes you write better code in many ways (smaller methods, comments and no ["magic numbers"](https://en.wikipedia.org/wiki/Magic_number_(programming))).

As to what is reviewed and when, well there is no clear answer. Many teams have rules that every piece of code that checks-in in the version control system has to be reviewed by another programmer, while other teams have whole days when they dedicate to code reviews across the team.
feat(guide): Import guide in to the client app 2018-10-04 14:47:55 +01:00			`---`
			`title: Code Reviews`
			`---`
			`## Code Reviews`

			`Code reviews are common practice for many software development teams. Code reviews involve`
			`team members looking into each others' code submissions to check for bugs, incorrect logic or`
			`potential improvements. To those who have not experienced the code review process before,`
			`it can be intimidating, however, it is an invaluable process to help you`
			`grow as a developer.`

			`Is is important to be humble throughout the code review process. Accept your mistakes,`
			`and be professional when pointing out improvements or errors in the code of your fellow`
			`team members.`
Enriched definition (#19014) * Enriched definition Added info about review results and common practices. * Fixed grammar mistakes Clarified the purpose of code reviews, re-written a sentence to improve it's clarity. 2018-10-15 10:10:17 +03:00
			`Code Reviews exist in order to improve the quality of the code in a software project.`
			`A code review can be done amongst developers of the project under review, as well as developers from other teams in the same company.`
			`Even if a review is just an explanation of the code to another programmer, the feeling that your code is going to be read/ inspected by another programmer as well makes you write better code in many ways (smaller methods, comments and no ["magic numbers"](https://en.wikipedia.org/wiki/Magic_number_(programming))).`

			`As to what is reviewed and when, well there is no clear answer. Many teams have rules that every piece of code that checks-in in the version control system has to be reviewed by another programmer, while other teams have whole days when they dedicate to code reviews across the team.`