3 ms·
Ok. Now I've heard it from one person. But I think "there's almost never the need to have two people continuously coding together" is a pretty strong conclusion
by wpietri 11y ago
Ok. Now I've heard it from one person. But I think "there's almost never the need to have two people continuously coding together" is a pretty strong conclusion from one person's experience. Do you mean that you haven't noticed the value in it?
One possibility is that your team was maybe not so good at it. Sometimes that happens:
http://agilefocus.com/2009/01/06/21-ways-to-hate-pair-programming/ http://agilefocus.com/2009/01/06/21-ways-to-hate-pair-progra...
Another is that you were working in a domain where the benefits of pairing don't matter so much. For me, they include improved code quality, less siloing, making it easier to bring people on to the team, faster iteration, and a greatly increased ability to actually take vacations due to improved truck factor.
On long-lived code bases with high business value and fast iteration, quality and collaborative ease become very important to me. Basically, I put pairing in the same category as code reviews, but I think it's much more efficient. And others do as well:
http://slesinsky.org/brian/code/pair_versus_review.html http://slesinsky.org/brian/code/pair_versus_review.html