I've tried pair programming in person, and it's almost impossible for me. I have vision problems, and I just really need my own monitor, configured how I want it, with me sitting squarely in front of it. But even beyond that issue, I'm enough of an introvert that I have a whole set up thoughts running through my head when I'm in a social situation, monitoring myself for the image I'm presenting, and the other person for how they're reacting. I can still work, but it definitely takes up some bandwidth, kind of like if I'm working while speaking a foreign language.
But the experience of remote paired work has been surprisingly good, for more than just the vision reason. I'm started recently on a completely-remote development job, with the team spread across multiple continents. No pair programming yet, but I just got off a call a few hours ago where I worked with another developer for more than an hour, troubleshooting build issues.
- Whoever is driving shares their screen, but we both still have access to our own computers, so there's no "hang on, lemme run back to my PC to double-check my notes there...".
- You're never forced to code with someone else's computer/keyboard/monitor/mouse/system setup/chair/etc.
- No awkwardly bumping knees or elbows, no worries about the other programmer having overpowering coffee breath or odd physical tics, being distractingly unattractive or attractive, etc..
So YMMV, but personally I'd rather do pair programming this way even if I was at the office.
Side note: I am simply unavailable for jobs that don't allow telecommuting; that's been the case for years now.
I've tried pair programming in person, and it's almost impossible for me. I have vision problems, and I just really need my own monitor, configured how I want it, with me sitting squarely in front of it. But even beyond that issue, I'm enough of an introvert that I have a whole set up thoughts running through my head when I'm in a social situation, monitoring myself for the image I'm presenting, and the other person for how they're reacting. I can still work, but it definitely takes up some bandwidth, kind of like if I'm working while speaking a foreign language.
But the experience of remote paired work has been surprisingly good, for more than just the vision reason. I'm started recently on a completely-remote development job, with the team spread across multiple continents. No pair programming yet, but I just got off a call a few hours ago where I worked with another developer for more than an hour, troubleshooting build issues.
- Whoever is driving shares their screen, but we both still have access to our own computers, so there's no "hang on, lemme run back to my PC to double-check my notes there...".
- You're never forced to code with someone else's computer/keyboard/monitor/mouse/system setup/chair/etc.
- No awkwardly bumping knees or elbows, no worries about the other programmer having overpowering coffee breath or odd physical tics, being distractingly unattractive or attractive, etc..
So YMMV, but personally I'd rather do pair programming this way even if I was at the office.
Side note: I am simply unavailable for jobs that don't allow telecommuting; that's been the case for years now.