Code-Review: Glossary

Reviews benefit a software project by fostering a sense of community, improving overall quality, and spreading knowledge of the codebase between developers.

Reviews benefit developers by allowing them to learn new design patterns or language features, distilling knowledge throughout a team, and providing some socialization between members.

Code reviews can range from immediate pair programming to post hoc repository reviews and everywhere in between. When developers say code review, they most often mean at the level of an individual pull request.

Pairs consist of a Driver, who does the typing, and Navigator, who directs the Driver and provides assistance when needed.

Pair programming is most beneficial if the task is complex or programmers are unfamiliar with the code.

Pair programming is a skill and practice will improve your experience as a driver and navigator.

Code review saves time, money and reduces error. The more formal the review, the bigger the savings.

During a code walk-through, the author is present to discuss the changes. A read-through does not require the author during the review.

Review no faster than 500 lines per hour

Decide on a checklist for a project and use it during a review

Strive to review PRs that solve a single issue.