Skip to main content

Peer Code Review

Improve knowledge and processes for writing code that scales and is easy to change


Tips for useful, respectful code reviews:

  • Assume competence (author may have a different context)
  • Provide specific, actionable feedback
  • Focus on the code (avoid personal criticism)
  • Clearly mark nitpicks & optional comments
  • Provide rationale (e.g refs to a style guide)

How to make better code reviews


  • Velocity
  • Reusability
  • Sprint Burndown
  • Release Burndown
  • Cycle Time
  • Cumulative Flow
  • Flow Efficiency
  • Code Coverage
  • Code Stability
  • Code Simplicity
  • Code Churn


  1. Templating — Reusing code by wrapping it up inside of a component
  2. Configuration — Using configuration props to allow for varying behaviour
  3. Adaptability — Allowing components to become future-proof
  4. Inversion — Letting other components control the process
  5. Extension — Using reusability throughout our component
  6. Nesting — Creating powerful hierarchies of components