Pair (or more) Programming

These are "design" notes taken after interviewing Chouser about his pair-programming workflow (current and ideal). He drew inspiration from google docs.

To me (cgrand) pair-programming should have one driver at a time. It means one input, one history and many views. Synchronization for ownership of the input is done out of band (e.g. voice as actually practiced by Chouser's team).

Other synchronizations (e.g. knowing a file has been opened etc.) would be a plus. This clearly isn't related to REPL. However if all participants are already sharing a REPL, using it as the synchronization point makes sense.

The more touchy subject is live view over the input area -- or more precisely a related subject: dirty input stream (one participant has submitted half a form and no one can see that). Maybe a :received event which would happen before :read could be generally useful.