[seanp2k2]

I've always liked pairing because it ensures that you're both there to get the thing done, and generally I've found that it keeps both of us from goofing off (until the thing is done, then it's time to play). While the theoretical throughput would be 50% (two people doing one thing), it ends up being greater than if we had both tried to work on different things, since the one thing we're doing comes out better since it's getting reviewed while written + any problems which come up can be solved much much faster. Plus, both people always learn at least one little thing, typically more.

Pairing is just great. Works well for sysadmin stuff too, even if I'm mostly leading that and just bringing someone else along for the ride.

[mack73]

I like pairing for those reasons as well. Also, I can keep my concentration up more easily when there is a requirement for me to do so, e.g. when I'm intercommunicating. It's when I talk to myself that I get distracted the most.

[YALocksmith]

I used to do the same as a defence contractor. We coded in a team of two, or sometimes with a third wheel who was learning. About 1.2x more productive, but rewrites and dead ends became rare.