4 ms·

That sounds like a really great setup. I'm going to have to try this out one day. I've never really considered the specific benefits remote pairing would have

That sounds like a really great setup. I'm going to have to try this out one day. I've never really considered the specific benefits remote pairing would have over in-person pairing...generally the only things considered are the downsides. Obviously, some of the things you mentioned with in-person pairing can be alleviated. At my current client, our setup includes multiple keyboards and mice. A friend of mine uses his own keyboard with a hardware switch to go between dvorak and qwerty. You mention not being able to share a browser which makes me think of the times where it would have been convenient to look something up for a moment while my pair experimented (two pronged problem solving approach... :). Also, what kind of pairing patterns do you use in this setup? Ping Pong TDD, driver/navigator, etc... ?

technomancy 15y ago
> You mention not being able to share a browser which makes me think of the times where it would have been convenient to look something up for a moment while my pair experimented (two pronged problem solving approach... :). Definitely. Occasionally we'll read docs in w3m, but often it's good to go async on looking up some boring details. What we do is probably more driver/navigator since whomever is hosting usually has better latency. The remote guy can still get around just fine, but it's just barely noticeable enough to give an edge to the host. Since we work in a language that makes it easy to do strict FP, (Clojure) test-first is not as important as it would be in an imperative language, though we do have pretty good coverage.