Re:Pair programming == punishment (Score 1)

You make it sound like typing is the hardest part of developing software. If only that were true. Think of pair programming as a code review that happens instantaneously rather than weeks later when the mistakes in the design have become so much harder to fix (the 1, 10, 100 rule). Think of how much easier it is for you to offer (and your pair to accept) a suggested change before hours of work (and ego) have been invested into a particular design. Successful pair programming isn't about being a typing cop (most of the time I'd bite my tongue on stuff like that). It's about the give and take of two people trying to solve a problem.