Uploaded on

Tips and best practices for conducting code reviews and pair programming.

Tips and best practices for conducting code reviews and pair programming.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,335
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
78
Comments
0
Likes
8

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. 30 April, 2009
    Introduction to Code Reviewsby Mel Gerats
  • 2. Definitionhttp://en.wikipedia.org/wiki/Code_review
    Code review is systematic examination (often as peer review) of computer source code intended to find and fix mistakes overlooked in the initial development phase, improving both the overall quality of software and the developers' skills.
    30 April, 2009
    Introduction to Code Reviews, by Mel Gerats
    2
  • 3. Why
    30 April, 2009
    Introduction to Code Reviews, by Mel Gerats
    3
  • 4. 30 April, 2009
    Introduction to Code Reviews, by Mel Gerats
    4
    Why
    Improve quality of code
    Share Knowledge
    Check conformance
    Verify completeness
    Educate
    Reach a consensus
    Try other approaches

  • 5. 30 April, 2009
    Introduction to Code Reviews, by Mel Gerats
    5
    What?
    Inspection
    Team Review
    Pair programming
    Walkthrough
    Peer review
    Ad hoc
  • 6. 30 April, 2009
    Introduction to Code Reviews, by Mel Gerats
    6
    Inspection, Team Review
    Formal
    Planned, prepared
    Clear roles (moderator, author, reviewers, note taker…)
    Goal: find defects
  • 7. 30 April, 2009
    Introduction to Code Reviews, by Mel Gerats
    7
    Walkthrough
    Author takes the lead
    Less detail
    Higher level
    Reviewers take notes
    Goal: knowledge sharing, find defects
  • 8. 30 April, 2009
    Introduction to Code Reviews, by Mel Gerats
    8
    Pair Programming
    Lessformal
    Share knowledge
    Short sessions
    1 task
    Goal: Prevent defects, share knowledge
  • 9. 30 April, 2009
    Introduction to Code Reviews, by Mel Gerats
    9
    Peer review
    Informal
    Asynchronous
    One or more people
    Find defects, improve quality
  • 10. 30 April, 2009
    Introduction to Code Reviews, by Mel Gerats
    10
    Ad Hoc
    Can you take a look at this?
    Goal: second opinion
  • 11. 30 April, 2009
    Introduction to Code Reviews, by Mel Gerats
    11
    How
    Peer reviews
    Pair Programming
    Ad hoc
  • 12. 30 April, 2009
    Introduction to Code Reviews, by Mel Gerats
    12
    How: Review
    Code, not the programmer
    Substance, not style
    Constructive criticism
  • 13. 30 April, 2009
    Introduction to Code Reviews, by Mel Gerats
    13
    How: Pair Programming
    Short sessions
    One problem at a time
    Plan!
  • 14. 30 April, 2009
    Introduction to Code Reviews, by Mel Gerats
    14
    Resources
    IDesign Coding Standard
    Effective Code Reviews Without the Pain
    Pair ProgrammingonWikipedia
    http://www.processimpact.com/pubs.shtml#pr
    Seven Truths About Peer Reviews
    Seven Deadly Sins of Software Reviews
    When Two Eyes Aren’t Enough
    http://stackoverflow.com/questions/tagged/code-review
    http://en.wikipedia.org/wiki/Code_review
  • 15. 15
    Introduction to Code Reviews, by Mel Gerats
    30 April, 2009