[weilawei]

This article really hits the mark. I wish more companies would adopt a pair programming discipline. My experience with it has been largely positive. It takes some getting used to, at first, especially getting down a good system for reading code aloud and directing each other's attention to a particular location in the code.

After a while, it feels pretty natural. And productive. Also, there's less burnout, more useful socialization. We've also gone the Nerf gun/slackline/juggling balls route for taking quick breaks between chunks of features. After the first person you seriously pair program with, it becomes easier in general. You're free to find your own similes.

It's easier to flow. See http://www.c2.com/cgi/wiki?MentalStateCalledFlow and http://www.c2.com/cgi/wiki?MyMindKeepsWandering