Ah! Reading your description of delicious pairing ...

2011-02-02T15:12:37.397-05:00

Ah! Reading your description of delicious pairing is almost as sweet as actually doing it. :) When it goes well, it really is like a conversation, isn't it?

So I'm reading this post, and questions are forming in my mind. Foremost is this: Have you experienced the other kind of pairing? Where you're bent over the keyboard and you realize later that your partner was checking their phone, or sitting there in frustration? Or where you're the one sitting next to someone, not finding a way to get into a conversation, eventually giving up?

Is two sets of input devices enough to make it a conversation? I imagine it would help a lot! If it's not enough, what else could we do to influence pairing sessions toward this kind of synergy?

The handful of times I've done pair programmin...

2011-02-02T12:13:42.891-05:00

The handful of times I've done pair programming, I've really enjoyed the process. I agree with your statements about communication and it's different elements.

I think there's much to be gained from collaboration, rather than individual effort. There are countless times when I thought I had a really solid idea, only to have peers/friends expose me to different ways of looking at things (some of which changed my approach).

Hopefully I'll get to do some more pairing in the future.

Keep up the good content. I listened to the .NET Rocks! episode (632) twice already and feel I can learn a good deal from your insights.

Comments on Doc On Dev: Pairing is Conversation

Ah! Reading your description of delicious pairing ...

The handful of times I've done pair programmin...