Upgrade to Pro — share decks privately, control downloads, hide ads and more …

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.

Stephanie Wagner

July 23, 2015
Tweet

Other Decks in Programming

Transcript

  1. Why code reviews? • Find bugs • Better quality code

    • Better developers • Mentoring • Transparency
  2. How to perform a code review well • Read the

    issue before reviewing code • Asking questions encourages discussion • Be supportive and helpful.
  3. 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
  4. Coding Standards • Developers know what to expect • Keeps

    code reviews efficient • Improved development speed
  5. Volunteer-basis/Pull Requests • Efficient, does not interrupt developer • Everyone

    can participate • Fits neatly into existing workflows
  6. Group Code Reviews • Requires meetings • Can take up

    a lot of time • Can drift into problem-solving • Not necessarily more effective than previous method
  7. Pair Reviews • Allows interaction • Can be used for

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