Download as PDF, PPTX
Uploaded byDaftcode
Pair Programming demystified
This document discusses pair programming and debunks common myths about it. Pair programming involves two people working together on one computer, with one person driving and the other navigating and providing feedback. It is not twice as slow as individual work, works well with most partners, and is effective at all stages of development. Pairing provides benefits like greater code quality, knowledge sharing, learning, and debugging assistance. The document advocates for regular pairing and shares examples of how to structure it, including continuous pairing, ping-pong pairing, and pairing rotations. It also shares the positive results of one company that introduced extensive pairing into their workflow.
More Related Content
Similar to Pair Programming demystified
Pair Programming demystified
- 1.
- 2.
- 3.
- 4. ”I don’t learnthat much anymore”
- 5. I am boredwith technology X / project X / customer X
- 6. Good Code Reviewis hard
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13. 2 > 1+ 1 Truth
- 14. You need theright partner Myth
- 15. For most peopleit works with most partners Truth
- 16. Only good fortraining Myth
- 17. Different kind ofpairing is effective at most stages Truth
- 18. I get nocredit for my work Myth
- 19. Solvable with TaskOwners Truth
- 20. Navigator finds onlysyntax mistakes Myth
- 21. Good pairing hasa tremendous impact on the code's design and architecture Truth
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35. junior & senior extrovert& introvert backend & frontend Types of pairs
- 36. • Started withcasual pairing • One month experiment ~100% pairing • Ping-pong pair programming: 90% • Team decision: continue Introducing pair programming at DaftCode
- 37. @marekkirejczyk Pair early, pairoften www.daftcode.com