Why do you need to conduct code review?

    1. Improves the code quality: two heads are better than one. Knowing that the code will be reviewed by someone the developer writes code more attentively. The developer will comment code in a better way to avoid a big amount of questions from the auditors.
    2. Improves the developer’ skills. The developer will not commit the same mistakes. The developer also will write more understandable code to avoid repeated explanations how this code works.
    3. Helps in beginners learning. Junior programmer gets access to the code of experienced programmers and thus he can get wise to coding style and documentation style.
    4. Helps to find errors and react instantly. First of all in reviewing the code when an error or a bug is found, they immediately will be corrected. Thus, the developer spends much less time to correct mistakes than if the error would be detected during the application testing or, in the worst case, during the application operation. Secondly, during testing far fewer mistakes that need to be corrected later is discovered. It also helps to find such errors that is not possible to detect when testing (misprints, typos). => The code review really speeds up the application development and testing.
    5. Helps to learn other developers skills.
    6. Helps to create programming and documentation style, which will be followed by all developers.
    7. Helps to understand some parts of the program or the entire application in the aggregate.