Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Pairing
Why Pair?
Better code
Knowledge transfer / sharing
Better morale – fun!
Higher productivity
Improve communication, le...
The Good
What is good pairing?
Drawing out a solution to focus the mind
Communicating – talk a lot
Being patient and courteous
...
Good Driving
Focus on the task
Complete the code
Syntax
Trust the navigator
Good Navigating
Review the code
Pay total attention
Talk not show
Think about the bigger picture
Think about alternat...
The Bad
What is bad pairing?
Anti - patterns
Navigator dictating – backseat driving!
Keyboard hog and keyboard snatching
Menta...
The Ugly
Clever code != clean code
Complex code is not always clean code
It can confuse your pair
Steam training
Belittling you...
Dreyfus Model
Novice
Advanced Beginner
Competent
Proficient
Expert
How to be good…
 Define your task and agree on a solution
 Rely on each other
 Sync up frequently
 Celebrate your succ...
Remember…
Pairing is sharing

Questions?
Sara
Email: sara@sarastephens.com
Blog: www.developerdame.com
Twitter: @developerdame
Rachel
Email: rlaycock@th...
Upcoming SlideShare
Loading in …5
×

Pair programming: Good, bad and ugly

1,758 views

Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Pair programming: Good, bad and ugly

  1. 1. Pairing
  2. 2. Why Pair? Better code Knowledge transfer / sharing Better morale – fun! Higher productivity Improve communication, learning and cooperation
  3. 3. The Good
  4. 4. What is good pairing? Drawing out a solution to focus the mind Communicating – talk a lot Being patient and courteous Encouraging and mentoring
  5. 5. Good Driving Focus on the task Complete the code Syntax Trust the navigator
  6. 6. Good Navigating Review the code Pay total attention Talk not show Think about the bigger picture Think about alternatives Are we doing the right thing?
  7. 7. The Bad
  8. 8. What is bad pairing? Anti - patterns Navigator dictating – backseat driving! Keyboard hog and keyboard snatching Mentally checking out No collaboration You can’t do both roles It’s not fun!
  9. 9. The Ugly
  10. 10. Clever code != clean code Complex code is not always clean code It can confuse your pair Steam training Belittling your pair – “Don’t you know that” Arrogant and egotistical
  11. 11. Dreyfus Model Novice Advanced Beginner Competent Proficient Expert
  12. 12. How to be good…  Define your task and agree on a solution  Rely on each other  Sync up frequently  Celebrate your success – High 5!  Switch roles regularly  Be courteous, respectful and understanding  Talk and listen  Don’t check your email/twitter/facebook etc  Have short regular 5 minute breaks
  13. 13. Remember… Pairing is sharing 
  14. 14. Questions? Sara Email: sara@sarastephens.com Blog: www.developerdame.com Twitter: @developerdame Rachel Email: rlaycock@thoughtworks.com Blog: www.rachellaycock.com Twitter: @rachellaycock

×