A couple questions for the room:
- When do you find pairing most helpful?
- when do you find pairing least helpful?
I had initially focused this talk on the ins and outs of pairing, how it works. But, we're all adults, we've paired with people before. We all know how it works. So, instead, I want to focus on one particular aspect: pairing as a tool for collaboration.
How many people have paired on code generation, not just helping someone get unstuck? On our team, we work very independently. Which is good! I really appreciate the space to work quietly through my thoughts. But, seeing as we work on shared codebases, it can be useful to pair when adding new features to ensure that established patterns are being followed and that the code is comprehensible to the person who didn't write it. In my experience, employing this tactic early on in a project leads to faster code delivery, fewer erroneous bugs and syntax errros, and more widely shared context, as two people can spread context fa