The document discusses pair programming, emphasizing that it is a collaborative practice involving knowledge sharing rather than simply reviewing or fixing code together. It outlines the benefits, such as improved morale and reduced bugs, and provides tips for effective pair programming, including sharing the keyboard and maintaining communication. The author encourages its use in various contexts, including onboarding and bug fixing.

1. Effective Pair
Programming

2. Hey!I’m James Thompson
Engineering Team Lead @ Mavenlink
@plainprogrammer

3. @ Mavenlink we Pair
It’s our normal practice

4. What Pair Programming is not
× It’s not having someone fix a bug with you
× It’s not having someone explain code to you
× It’s not having someone review your code

5. What Pair Programming is
It’s about collaboration
It’s about knowledge sharing
It’s about working better

6. Benefits of Pair Programming
Knowledge
Shallower Bugs*
Business
Design
Morale

7. Risks of Pair Programming
Personnel Quality
Speed
Cost
Ubiquity

8. Good
Two chairs &
share well

9. Better
Two chairs,
two screens &
two inputs

10. How to pair well
● Talk more than you think you ought to
● Share the keyboard
● Experiment with workflow

11. Test driving pair programming
● Start with bugs
● Use it for on-boarding
● Just use it for an iteration

12. Questions?
AMA IRL!

13. THank you!