Transcript
Page 1: Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop and CodeCollaborator Webinar)

Code Reviews Don’t Have to SUCK

Roy PatersonLead Developer

David ShepherdSenior Developer

Page 2: Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop and CodeCollaborator Webinar)

Code Reviews Don’t Have to SUCK

Roy PatersonLead Developer

David ShepherdSenior Developer

Page 3: Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop and CodeCollaborator Webinar)

Do Code Reviews Suck?

Page 4: Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop and CodeCollaborator Webinar)

Yes: Meetings Suck

Intimidating and

Stressful

Page 5: Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop and CodeCollaborator Webinar)

Yes: Meetings Suck

Bottleneck at

Author

Page 6: Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop and CodeCollaborator Webinar)

Yes: Meetings Suck

Interruption from

Developer’s Day

Page 7: Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop and CodeCollaborator Webinar)

Yes: Meetings Suck

Tool Disconnect Lowers Discussion Quality

Page 8: Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop and CodeCollaborator Webinar)

Yes: Logistics Suck

Page 9: Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop and CodeCollaborator Webinar)

Yes: Tool Support Sucks

Page 10: Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop and CodeCollaborator Webinar)

Yes: Tool Support Sucks

Page 11: Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop and CodeCollaborator Webinar)

Yes: Tool Support Sucks

Page 12: Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop and CodeCollaborator Webinar)

CodeCollaborator + TasktopEliminating the Suck from Code Reviews

No Meetings Feedback occurs asynchronously,

online

Automated Logistics are automated and

seamless

Tool Support Developers create + review code

in IDE

Page 13: Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop and CodeCollaborator Webinar)

CodeCollaborator + TasktopToday’s Demo Structure

Create Author creates review

Review Reviewer adds comments,

defects

Complete After fixing feedback, commits code

Rework Author fixes code, uploads fixes

Verify Reviewer verifies code fixes

Page 14: Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop and CodeCollaborator Webinar)

Demo

Page 15: Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop and CodeCollaborator Webinar)

CodeCollaborator + TasktopEliminating the Suck from Code Reviews

No Meetings Feedback occurs asynchronously,

online

Automated Logistics are automated and

seamless

Tool Support Developers create + review code

in IDE

Page 16: Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop and CodeCollaborator Webinar)

Q&ARoy PatersonLead [email protected]

David ShepherdSenior Developer@davidcshepherd