3 ms·

I can appreciate your efforts here. It isn't trivial to put something like this together but I'm going to go ahead and state the obvious: Face to face is far su

by fjabre 9y ago

I can appreciate your efforts here. It isn't trivial to put something like this together but I'm going to go ahead and state the obvious: Face to face is far superior to a solution such as this one for what I think are self evident reasons. You're better off, by orders of magnitude, getting on a plane or train and going to see your code buddies. When I'm coding with someone we're not usually on the same files or piece of code anyway. And I don't get any value from seeing them type away at the code file that they are focused in, or knowing which file they're in beyond the name. It's a simple "hey mate what line are you on?" question. I get excellent value from talking to and seeing the other devs face to face figuring out where their head's at and what 'page' they're on. That's the stuff of a proper realtime and face to face code sesh IMHO.

seveneightn9ne 9y ago
Being together in person doesn't solve the problem of wanting to edit the same code simultaneously. For some projects, git is enough, but for something really small this seems like it would really help.
- fjabre 9y ago
  I'm not saying it isn't a legitimate problem but I've never had it. For me, if we're not using git I could get the other dev's latest changes by simply doing a file copy of whatever I needed and then get it into my own environment. I work offline with most of my dev mates. We are rarely ever coding at the same time of day given time zone differences and sleeping patterns. If we're a small team we're probably quite aware of where the other one is in the code and what they're working on. I don't need real time for that. I think being able to see the other dev type in real time in the same file doesn't solve anything for me and may in fact be distracting and counter productive. I'm not sure 'real time' fits here.
  - brandall10 9y ago
    "We are rarely ever coding at the same time of day given time zone differences and sleeping patterns." This is to aid pair programming. I work on a remote team as well, but there are times we pair when hashing out of a particular issue that either myself or one of my teammates is having. It's far quicker to do this than to work disconnected and go back and forth, esp. if it may impact the schedule/sprint. In the past I've worked with devs that had as much as a 10 hour time difference and we literally scheduled times where our schedules crossed so we could pair on a specific issue. One person drives at a time but it's common to switch back and forth so tools like this are helpful.
- segmondy 9y ago
  dual keyboards & mouse.
segmondy 9y ago
yeah, I use tmux, ssh for this. dev session in a container incase the person does something stupid. hangouts for voice/video
greggman 9y ago
Don't know Atom's features here and my first thoughts were somewhat negative but the video here of VSCode's similar new feature dispelled many of my initial objections. In VSCode's feature you can even debug together and the remote user can inspect your machine. You aren't sharing a screen, you're just sharing program state and file changes. https://code.visualstudio.com/blogs/2017/11/15/live-share https://code.visualstudio.com/blogs/2017/11/15/live-share

by fjabre 9y ago

seveneightn9ne 9y ago

Being together in person doesn't solve the problem of wanting to edit the same code simultaneously. For some projects, git is enough, but for something really small this seems like it would really help.

fjabre 9y ago
I'm not saying it isn't a legitimate problem but I've never had it. For me, if we're not using git I could get the other dev's latest changes by simply doing a file copy of whatever I needed and then get it into my own environment. I work offline with most of my dev mates. We are rarely ever coding at the same time of day given time zone differences and sleeping patterns. If we're a small team we're probably quite aware of where the other one is in the code and what they're working on. I don't need real time for that. I think being able to see the other dev type in real time in the same file doesn't solve anything for me and may in fact be distracting and counter productive. I'm not sure 'real time' fits here.
- brandall10 9y ago
  "We are rarely ever coding at the same time of day given time zone differences and sleeping patterns." This is to aid pair programming. I work on a remote team as well, but there are times we pair when hashing out of a particular issue that either myself or one of my teammates is having. It's far quicker to do this than to work disconnected and go back and forth, esp. if it may impact the schedule/sprint. In the past I've worked with devs that had as much as a 10 hour time difference and we literally scheduled times where our schedules crossed so we could pair on a specific issue. One person drives at a time but it's common to switch back and forth so tools like this are helpful.
segmondy 9y ago
dual keyboards & mouse.

segmondy 9y ago

yeah, I use tmux, ssh for this. dev session in a container incase the person does something stupid. hangouts for voice/video

greggman 9y ago

Don't know Atom's features here and my first thoughts were somewhat negative but the video here of VSCode's similar new feature dispelled many of my initial objections. In VSCode's feature you can even debug together and the remote user can inspect your machine. You aren't sharing a screen, you're just sharing program state and file changes. https://code.visualstudio.com/blogs/2017/11/15/live-share https://code.visualstudio.com/blogs/2017/11/15/live-share