Skip to content
This repository has been archived by the owner on Oct 7, 2020. It is now read-only.

Latest commit

 

History

History
51 lines (41 loc) · 3.27 KB

code-review.md

File metadata and controls

51 lines (41 loc) · 3.27 KB
layout title permalink weight parent subnav
page
Code Review
/code-review/
9
General
Peer Code Review

Peer Code Review

  • Peer review should be scheduled at the completion of a feature or a non-trivial bug-fix.
  • Reviewing someone else’s code can almost be as intensive as writing code from scratch. The idea is to question everything from the approach to the implementation and also ensure best practices are being followed. Best practices range from naming conventions to usage of design patterns.
  • Tools to simplify peer review include git diff, patch files, pull requests, etc… The process for each can be defined on a case-to-case basis.

Process

Requester

Requestee

  • Read: http://haacked.com/archive/2013/10/28/code-review-like-you-mean-it.aspx
  • Log into http://code.projspace.com
  • Browse to the particular project
  • Open the Merge Request Tab
  • All the commits are seen there
    • We have an option of viewing a diff of all those
    • By clicking on diff it shows the diff of all the files into which commits are there between the previous commit and that particular commit
    • A snippet is presented for each file and requestee should liberally add comments as per the references guidelines.

Checklists and other references