[dimmke]

I have to pair program all the time at my job. It's just the nature of a lot of the work I do. However, all the pair programming I do is over screensharing where we aren't physically next to each other. The tips in this article are excellent.

The two big ones that will make me hate pair programming with you: Leaping on errors too quickly and giving low-level instructions.

The big sin I commit: Driving too fast

When pair programming is going well, it really does speed up development time and increases the amount of people who know about a section of a codebase which is always good. But when it's bad, it's really really bad.