gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Adding more description on how teams approach reviews (#22930)

Browse Source 
Adding description on how teams approach code reviews and what an effective code review is
This commit is contained in:
tktgius
2018-11-28 12:20:28 -06:00
committed by nik
parent fd89b4a813
commit f848bae00b
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
guide/english/working-in-tech/code-reviews/index.md
View File

@ -14,7 +14,7 @@ the feeling that your code is going to be read/ inspected by another programmer
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.
while other teams have whole days when they dedicate to code reviews across the team. Teams, within an organization, create internal Coding Standards for the various languages used, as a guidance for developers, and code reviewers. An effective code review is one where functionality, testability, security, and readibility/styling issues are addressed.
It 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