Tools for Remote Software Development and Pair Programming
1–10 of 56 posts
Re: Tools for Remote Software Development and Pair Programming
#2At my current place (team of 5), we set up Zerotier[0] to create a LAN between all of our computers and servers. This lets us directly ssh into each-other's machine, simplifies file sharing to an rsync, etc...
I find this works really well, as when someone has a bug and needs help, we can all access :8000" rel="nofollow">http://:8000 to access the instance he's working on, and ssh into the machine to get access to the logs to try and help figure out what's wrong.
Disclaimer : just a happy Zerotier user.
Re: Tools for Remote Software Development and Pair Programming
#3I find https://localhost.run to be a great tool when you need a tunnel to your machine to show things. Just a line of ssh, works everywhere.
Re: Tools for Remote Software Development and Pair Programming
#4I'm surprised this wasn't mentioned, I've used it before with great results.
Re: Tools for Remote Software Development and Pair Programming
#5Hangouts and tmate
Re: Tools for Remote Software Development and Pair Programming
#6I've used a shared tmux session over ssh in the past, which worked quite nicely without installing any extra software (besides tmux obviously)
Re: Tools for Remote Software Development and Pair Programming
#7The system that Slack bought was the best I've seen. Can't remember the name of it though.
Re: Tools for Remote Software Development and Pair Programming
#8The system that Slack bought was the best I've seen. Can't remember the name of it though.
Guessing you're talking about Screenhero.
Re: Tools for Remote Software Development and Pair Programming
#9I find https://localhost.run to be a great tool when you need a tunnel to your machine to show things. Just a line of ssh, works everywhere.
Works better for me without https
Re: Tools for Remote Software Development and Pair Programming
#10I used to think there was a lot of value in the concept of pair programming but I think the Pull Request and Code Review model is simply superior. It allows for a lot of the benefits of pair programming but with lower costs. I've always found that even looking over someone's shoulder to help debug something slows to a crawl. It takes more discipline than most engineers have to keep it truly paired.