Code review

From ICT research methods
Revision as of 20:36, 9 February 2018 by Ralphniels (talk | contribs) (Created page with "250px|right Category:Workshop ==Why?== With many eyeballs on the code, all bugs are shallow. Colleagues can help you find bugs and improve the qu...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Code review.png

Why?

With many eyeballs on the code, all bugs are shallow. Colleagues can help you find bugs and improve the quality of your source code.

How?

Code reviews can be done in many ways. The code can be presented on a big screen, so the entire team can do the review together. You can also ask one or two peers to simply sit behind your desk while you talk them through your code. Code analysis can also be a part of the workflow (e.g. every commit must be reviewed by someone else).

Ingredients

  • Peers with a critical view.
  • A willingness to improve weak points in your code.
  • Code standards, a code style guide, checklists, etc.

In practice

Code review sessions are often incorporated into software development projects. In Scrum, code reviews can be part of the ‘definition of done’. Pair programming can also be an effective way to let your work be continuously reviewed by a peer.