Best Practices for Code Reviews

Code review is a critical examination which software engineers collaborate with other engineers, feel the team, improve their abilities, share their knowledge, and find defects early. This talk aims to show importance of the code review, give best practices about it by explaining good behaviours from both reviewer’s and reviewee’s perspective, with supporting real life examples, and stories.

• Like for other methodologies in engineering, to have good communication skills is the most critical requirement for review. You can start by being polite and humble.

• Good reviewee should review his code before committing, be grateful, and positive about comments. Also, not to understand comments in personal is very important.

• Reviewer should understand problems, and requirements before starting review. He/she must check for whether all requirements are satisfied, or broken things, affected areas. Looking for future, considering all test cases, and maintenance issues are also in the plate of reviewers.

At the end of this talk, you will be aware of communication skills helping you to be a good team mate, have a good understanding of code review, software development cycle. Then, you will be able to make your team happy both as being reviewer and reviewee.

You will learn lots of best practices like above, which help you to be not only a good reviewer, but also be a good software engineer the one everyone wants to work with.