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

How And When To Code Review

How And When To Code Review

Are you a software developer who wants to improve your skills? Are you a team lead who enjoys mentoring other developers and improving both their and your coding skills? Or are you a manager who needs to improve the knowledge sharing among your software developers across different projects? Today we will be talking about how Code Reviews can do just this and also improve the code quality of your software projects in the process. Code Review can be a great way to get to know your fellow developers and even learn a different or sometimes better way to build a software solution. At the end of the session you will have a better understanding of the benefits of Code Review as well as some great tips to use in your team today.

Paul Gower

July 16, 2016
Tweet

More Decks by Paul Gower

Other Decks in Programming

Transcript

  1. Reviewer: Focus on the code Don’t say: “You didn’t name

    these variables well!” Instead: “I don’t understand these variable names, can you help me understand them?”
  2. ““…the average defect detection rate is only 25 percent for

    unit testing, 35 percent for function testing, and 45 percent for integration testing. In contrast, the average effectiveness of design and code inspections are 55 and 60 percent.” - Steve McConnell, Code Complete, 2004
  3. “ “The aim is to catch what mistakes you can

    and to get better – not to attempt perfection.” - Erik Dietrich, “Creating Your Code Review Checklist”, 2015
  4. Review • No more than 60 mins • No more

    than 200 lines of code • Use Static Code Analysis • Use Check Lists • Use A Code Review Tool