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
Pair programming: Good, bad and ugly
Knowledge transfer / sharing
Better morale – fun!
Improve communication, learning and
Clever code != clean code
Complex code is not always clean code
It can confuse your pair
Belittling your pair – “Don’t you know
Arrogant and egotistical
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