Getting the most out of code review

Getting the most out of code review

Code reviews are one of the best ways to improve code quality - however, they can be even more complex than writing the code itself. This talk will help you understand how to conduct effective code reviews and benefit from a strong peer review culture.

0e85a3a83f2c10bf4d279bbc9a1fb867?s=128

Stephanie Wagner

July 23, 2015
Tweet

Transcript

  1. 1.

    Getting the most out of code review Stephanie Wagner, Software

    Developer at Namely Twitter: @stephwagner Email: stephanie.wagner@namely.com
  2. 2.
  3. 3.

    Why code reviews? • Find bugs • Better quality code

    • Better developers • Mentoring • Transparency
  4. 4.

    How to perform a code review well • Read the

    issue before reviewing code • Asking questions encourages discussion • Be supportive and helpful.
  5. 5.
  6. 6.

    How can the author make code reviews better? • Each

    set of changes should be one coherent thought • Good version control comments • Self-documenting code • Be a “team lead” in your own task
  7. 7.

    Coding Standards • Developers know what to expect • Keeps

    code reviews efficient • Improved development speed
  8. 10.
  9. 11.

    Volunteer-basis/Pull Requests • Efficient, does not interrupt developer • Everyone

    can participate • Fits neatly into existing workflows
  10. 14.
  11. 15.
  12. 16.
  13. 17.

    Group Code Reviews • Requires meetings • Can take up

    a lot of time • Can drift into problem-solving • Not necessarily more effective than previous method
  14. 18.

    Pair Reviews • Allows interaction • Can be used for

    mentoring new developers • Author can skip a change • Review is driven by the developer