Why not set up a private bitbucket repo, and just always push your code to bitbucket when you're done working, and pull when you start? It's a free offsite bac

Why not set up a private bitbucket repo, and just always push your code to bitbucket when you're done working, and pull when you start? It's a free offsite backup, and if you ever need to add another machine (or developer) to the project, your code is already sitting there on bitbucket. And you never need to worry about firewalls, NAT, one of the machines being off, whatever, because bitbucket is (almost) always up and accessible. And if you forget to push after working, or if bitbucket is down, you can still fall back to your existing workflow. In addition, if you're doing anything web based, sooner or later you'll need to deploy to a sever out on the internets. Being able to pull from bitbucket makes deployment really easy, again without tinkering with firewall ports or anything. It's not so much a question of "need" it's "why not do this thing which has some benefits, and no real downside?"