SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
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.
Good Driving
Focus on the task
Complete the code
Syntax
Trust the navigator
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?
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!
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.
Dreyfus Model
Novice
Advanced Beginner
Competent
Proficient
Expert
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
One workstation Driver – Concentrates on just coding Navigator – Reviews code Checks for errors Considers overall design
simpler design, reduce bugs, more maintainable – code base and coding, removes knowledge silo’slogin
Think about: Possible bugs Larger issues Ways to simplify the code Alternatives Are we doing the right thing? Wait until the driver has finished the piece of code to bring issues and design up Jot down any tasks to discuss when driver has finished typing
Studies have shown you can’t navigate (think about larger issues) whilst driving. Two roles exist so it isn’t about one getting a break while the other codes!
Pairing is hard!
If you are doing pairing right you will be very tired at the end of the day as you will have been very focused all day
0 likes
Be the first to like this
Views
Total views
2,039
On SlideShare
0
From Embeds
0
Number of Embeds
1
You have now unlocked unlimited access to 20M+ documents!
Unlimited Reading
Learn faster and smarter from top experts
Unlimited Downloading
Download to take your learnings offline and on the go
You also get free access to Scribd!
Instant access to millions of ebooks, audiobooks, magazines, podcasts and more.
Read and listen offline with any device.
Free access to premium services like Tuneln, Mubi and more.