Does XP and pair programming actually require two people to be simultaneously working together at the same time? My understanding is that this includes one person who codes while another person looks at the results and reviews them afterward. The two are still working closely together and exchanging feedback, just at different points in the process in an iterative loop.
My understanding is that original meaning was that pair programming requires the pair work together at the same desk and machine.
With the ability to share screens/IDEs remotely the need to be at the same desk may have shifted, but working together is intrinsic to pair programming I believe.
The original text went into some detail about making the desk work for 2 people, and having screwdrivers available to do so, which for some reason always amused me.
No, the point is that both "driver" and "navigator" (as some pair programming referred to the roles) are looking at the coffee simultaneously, just one has the keyboard at the time.
This is extended to "mob" programming where you have whole team of "navigators" and one person at keyboard.
