Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop...
-
Upload
smartbear -
Category
Self Improvement
-
view
1.601 -
download
0
description
Transcript of Code Reviews Don’t Have to Suck: Best practices to streamline code reviews in Eclipse (A Tasktop...
Code Reviews Don’t Have to SUCK
Roy PatersonLead Developer
David ShepherdSenior Developer
Code Reviews Don’t Have to SUCK
Roy PatersonLead Developer
David ShepherdSenior Developer
Do Code Reviews Suck?
Yes: Meetings Suck
Intimidating and
Stressful
Yes: Meetings Suck
Bottleneck at
Author
Yes: Meetings Suck
Interruption from
Developer’s Day
Yes: Meetings Suck
Tool Disconnect Lowers Discussion Quality
Yes: Logistics Suck
Yes: Tool Support Sucks
Yes: Tool Support Sucks
Yes: Tool Support Sucks
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
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
Demo
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
Q&ARoy PatersonLead [email protected]
David ShepherdSenior Developer@davidcshepherd