3 ms·
I've found shared tmux/screen sessions are ideal. + each person can have their own font/resolution + it doesn't dominate the entire screen, allowing each pers
by brrrrrm 5y ago
I've found shared tmux/screen sessions are ideal.
+ each person can have their own font/resolution
+ it doesn't dominate the entire screen, allowing each person to keep their own notes/etc on the side
+ at any point someone can "jump in" and take control of the session
+ interacting in a confined shared space radically reduces "over communication" issues. i.e. if you want to show something it's got to be demonstrable in a small textual window
+ you have a shared command-line, which is more useful than it might initially seem
+ seamlessly scales to in-person and remote pair programming
There are some downsides:
- it requires both users are familiar with a terminal based editor
- it may present security issues for folks operating in locked-down/low-resource environments (e.g. can't spin up a temporary machine with a shared account)
- sharing graphical information requires a separate communication layer
- reidrac 5y agoEven considering how easy things are using tmate, it is really challenging because there are a lot of Software Engineers that don't really know how to use a terminal to the point that asking to do a SSH is a bit too much. So we end sharing the screen over hang outs, that is basically very inefficient and wastes a lot of CPU. But because it is normalized, it is "the standard". EDIT: my comment was a bit unfair. I guess I could install VS Code, change my daily editor, and use it with the Live Share plugin with those using VS Code. So hang outs it is.