Pair Programming demystified

1. Pair programming
DEMYSTIFIED

2. Problems, problems,
problems…

3. Silos

4. ”I don’t learn that
much anymore”

5. I am bored with
technology X / project X / customer X

6. Good Code
Review is hard

7. What is pair
programming?

8. 2 people
1 computer

9. Driver
Navigator+

10. Swap roles
often

11. Myths
of pair programming

12. Double
the workload
Myth

13. 2 > 1 + 1
Truth

14. You need
the right partner
Myth

15. For most people it works
with most partners
Truth

16. Only good
for training
Myth

17. Different kind of pairing is
effective at most stages
Truth

18. I get no credit
for my work
Myth

19. Solvable with
Task Owners
Truth

20. Navigator finds
only syntax mistakes
Myth

21. Good pairing has a tremendous impact
on the code's design and architecture
Truth

22. Pair synergistic
behaviours!

23. Pair pressure

24. No pair pressure

25. Pair negotiation

26. Pair reviews

27. Pair learning

28. Pair trust

29. Pair courage

30. Pair debugging

31. Details, details,
details…

32. Rotation

33. Ping-pong pair programming

34. Environment

35. junior & senior
extrovert & introvert
backend & frontend
Types of pairs

36. • Started with casual pairing
• One month experiment ~100% pairing
• Ping-pong pair programming: 90%
• Team decision: continue
Introducing pair
programming at DaftCode

37. @marekkirejczyk
Pair early, pair often
www.daftcode.com