<pair programming> experience report: the costs and benefits of pair programming

"The adjustment period from solo programming to collaborative programming was like eating a hot pepper. The first time you try it, you might not like it because you are not used to it. However, the more you eat it, the more you like it."

a little bit of cognitive background:

"Anyone who has closely observed the practices of cognition is struck by the fact that the "mind" rarely works alone. The intelligences revealed through these practices are distributed - across minds, persons, and the symbolic and physical environment."

kent beck about extreme (<xp>):

"I took everything I knew and cranked all the knobs up to 10. Testing is a good idea so we tested all the time. Talking to customers is good so we had them sitting in the same room as the programmers. Design is good so we spent time on design every day. That was the initial premise and it's the sense of 'extreme' in extreme programming." (interview)

one question remains: when two people work together in front of one screen, will they learn to have a party at the end??? at least it seems there is some hope:

"It's nice to celebrate with somebody when something works."