4 ms·
Remote pair programming sucks. I don't know why there isn't a higher level protocol that would send simple tab changes, text highlights, text deletion, and oth
by aantix 15y ago
Remote pair programming sucks. I don't know why there isn't a higher level protocol that would send simple tab changes, text highlights, text deletion, and other high level common tasks. This way the two connected programmer could actually be using different editors but still experience the same editor actions. And each user could maintain their own separate key bindings.
Who cares if I press cmd-t to open a file or my pair prefers to open a file with cmd-shift-n? Just send me the action that a file was opened.
I wrote up my detailed thoughts on fixing remote pair programming here.
https://gist.github.com/1999816 https://gist.github.com/1999816
- pyre 15y ago> Who cares if I press cmd-t to open a file or my pair > prefers to open a file with cmd-shift-n? Just send > me the action that a file was opened. I don't think that this was an affirmative design decision. I think it has to do with the architecture of software, and is merely a side-effect of that architecture. Pair programming isn't the main use-case for terminal multiplexers.
- pestaa 15y agoAs with Google Documents where you can see other changes in real-time? Yes and no. Would be really fun for five minutes and really irritating for the rest of the time.
- aantix 15y agoThat is what pair programming is about. Collaborative changes in real-time.
- adambyrtek 15y agoI would say that pair programming is primarily about close collaboration between people, code is just an artifact of that.