Hi all, For those who don't me I'm Divakar, Passionate developer with 5 years of experience in web and mobile development. I learned software development the hard way, following lots of confusing tutorials, failing to understand core concepts and finally having no idea how things work. So I wanted to help the community to understand it in a better way without any hassle.
Code review has been widely adopted by and adapted to open source and industrial projects. It is a process where someone other than the author(s) of the chunk of code evaluates the code. Most of the companies adopted this process to ensure quality of the code and product.
The purpose of code review is to make sure that the overall code health of codebase is improving over time , having said that this becomes tricky since over time codebase degrade when a team is under significant time constraints and they feel to take shortcuts inorder to complete the tasks.
As a reviewer you want to ensure that codebase stays consistent and maintainable.
Before proceeding with a code review I always prepare myself to accept these things
- No Fear The first and most popular is the fear of offending an author of the code. Don't pretend that you didn't see his/her bugs today ,so that tomorrow he/she will ignore your mistakes.This is the kind of attitude this fear produces.
- No Perfect code Key point is that there is no such thing as "perfect" code only a "better" code. Don't make the author to change every tiny piece of the code ,before granting the approval.Rather, you should seek continuous improvement in terms of maintainability , readability and understandability of the system.
- Mentoring Sharing knowledge is part of improving the code health of system over time. You can leave comments that help a developer to learn something new .