This document provides a guide to best practices in pair programming. It defines pair programming as two people working together at a single computer to write code that will be deployed to production. It describes different styles of pair programming such as driver-navigator and mob programming. It also discusses remote pair programming and antipatterns to avoid like navigators giving low-level instructions or drivers not taking breaks. Finally, it outlines some lesser known benefits of pair programming like reducing distractions and regressions.

1. Best practices
in
Pair Programming
lucasaquiles@gmail.com
2019

2. Who am I?
Lucas Aquiles
github/lucasaquiles
lucasaquiles@gmail.com
linkedin/lucas-aquiles

3. Guide
● What is it and what is not Pair programming
● Pair Programming Styles
● Remote Pair Programming
● Pair Programming Antipatterns
● Lesser-Known Benefits

4. What is Pair programming
“All code to be sent into production is created by two
people working together at a single computer.”
http://www.extremeprogramming.org/rules/pair.html

5. What is Pair programming
Navigator
Driver
Problem?Goal?

6. What is not Pair programming
Problem?

7. What is not Pair programming

8. Pair Programming Styles
● Driver/Navigator
if a % 2 == 0

9. Pair Programming Styles
● Strong style
I have an
idea, please
Take the
keyboard

10. Pair Programming Styles
● Ping pong
write a failing test
make it pass,
refactor, write
the next test

11. Pair Programming Styles
● Mob programming
https://pt.slideshare.net/lucasaquiles/pocket-talk-mob-programming

12. Pair Programming Styles
https://pt.slideshare.net/lucasaquiles/pocket-talk-mob-programming

13. Pair Programming Styles
https://pt.slideshare.net/lucasaquiles/pocket-talk-mob-programming

14. Remote pair programming

15. Pair Programming Antipatterns
For navigators
● Leaping on errors too quickly
● Giving low-level instructions
● Not bringing a keyboard
For Drivers
● Driving too fast
● Allowing a checked-out navigator
● Unequal screen access
● Not taking breaks
● Listening without hearing

16. Pair Programming Antipatterns
For both
● Allowing unproductive distractions
● Not swapping roles
● Flow is easier to recover
● be quitet

17. Lesser-Known Benefits
● Fighting bad architecture
● Being distracted
● Regressions
● Coworkers interrupt less
● Your hands get a break
● You’ll default to collaboration

18. References
● https://medium.com/codingzeal/a-guide-to-remote-pair-programming-tools-9ee20e06aa0c
● https://tuple.app/pair-programming-guide/styles
● https://medium.com/@weblab_tech/pair-programming-guide-a76ca43ff389
● https://www.jamesshore.com/Agile-Book/pair_programming.html
● https://medium.freecodecamp.org/how-remote-pair-programming-works-and-why-it-can-change-
your-life-cd7b767dc60f
● https://docs.google.com/presentation/d/1IATcrM89-rvqkGKPMx8H4XiD24-
2dDXqP60x18HpK3w/edit#slide=id.g546acb955e_0_36
● https://collaboration.csc.ncsu.edu/laurie/Papers/XPSardinia.PDF