3 ms·
I'm not against pairing more but there are some people who are incredibly uncomfortable with it. For a short period of time, you don't need much more than a pe
by brightball 8y ago
I'm not against pairing more but there are some people who are incredibly uncomfortable with it.
For a short period of time, you don't need much more than a person having a suggestion and dictating if they want to jump in.
I'd have serious reservations about mandating too much of it.
There's a gap between, "I need to type in this environment for a few minutes" and "I need to become proficient with this environment so I can work in it just as well as my preferred."
In small doses, the proficiency and work environment preferences don't need to bend much (even to share the keyboard a little).
- RandallBrown 8y agoHaving worked at a company where we did all pairing, all the time, I think it's absolutely "the right way" to do software development. After doing it enough, I think that most people will get over their dislike of it. But you're right that it isn't for everyone. You kinda need to build your team around it and have your interview process select the kind of people that will enjoy it. I really like the idea of pairing with someone for two hours after you finish up a ticket. I think that would be a great way to introduce the team I'm currently on to pairing.
- wpietri 8y agoYeah, I've talked with a number of people who've had bad experiences. A while back I wrote up a list of things that can make pairing unpleasant: http://agilefocus.com/2009/01/06/21-ways-to-hate-pair-programming/ http://agilefocus.com/2009/01/06/21-ways-to-hate-pair-progra... I get the thing with environments, but it got a lot easier for me when I'd just ask people to do the magic I didn't know in their tools. Especially if it's two keyboards and two mice, it's easy enough to say, "Ok, now jump back to the test" and have them seize control for a few seconds.