Developers working on CSE projects should conduct peer code reviews on every pull request (or check-in to a shared branch).
Code review is a way to have a conversation about the code where participants will:
- Improve code quality by identifying and removing defects before they can be introduced into shared code branches.
- Learn and grow by having others review the code, we get exposed to unfamiliar design patterns or languages among other topics, and even break some bad habits.
- Shared understanding between the developers over the project's code.
- Code review tools
- Google's Engineering Practices documentation: How to do a code review
- Best Kept Secrets of Peer Code Review
Last update: February 16, 2022