Skip to main content
Software Engineering

Return to Answer

added 12 characters in body
Source Link
Ewan
Ewan
  • 84.4k
  • 5
  • 91
  • 189

I've used 1,2 and 3 and 1 is by far the best.

  1. RDP is generally fine, but it relies on the other computer being a 'server' and turned on. If you develop on both machines you are going to get divirgence and complicate your life as you have both local and rdp sessions open on each.

  2. Is good for collaboration on a single file, but doesnt work well for multiple file projects and again has the 'which machine is the server?' problem

  3. Just requires you to commit and push before changing machines. You should be commiting regularly anyway and a feature branch will mitigate the problems of commiting half finished work.

(new list)

  1. Just requires you to commit and push before changing machines. You should be commiting regularly anyway and a feature branch will mitigate the problems of commiting half finished work.

I've used 1,2 and 3 and 1 is by far the best.

  1. RDP is generally fine, but it relies on the other computer being a 'server' and turned on. If you develop on both machines you are going to get divirgence and complicate your life as you have both local and rdp sessions open on each.

  2. Is good for collaboration on a single file, but doesnt work well for multiple file projects and again has the 'which machine is the server?' problem

  3. Just requires you to commit and push before changing machines. You should be commiting regularly anyway and a feature branch will mitigate the problems of commiting half finished work.

I've used 1,2 and 3 and 1 is by far the best.

  1. RDP is generally fine, but it relies on the other computer being a 'server' and turned on. If you develop on both machines you are going to get divirgence and complicate your life as you have both local and rdp sessions open on each.

  2. Is good for collaboration on a single file, but doesnt work well for multiple file projects and again has the 'which machine is the server?' problem

(new list)

  1. Just requires you to commit and push before changing machines. You should be commiting regularly anyway and a feature branch will mitigate the problems of commiting half finished work.
Source Link
Ewan
Ewan
  • 84.4k
  • 5
  • 91
  • 189

I've used 1,2 and 3 and 1 is by far the best.

  1. RDP is generally fine, but it relies on the other computer being a 'server' and turned on. If you develop on both machines you are going to get divirgence and complicate your life as you have both local and rdp sessions open on each.

  2. Is good for collaboration on a single file, but doesnt work well for multiple file projects and again has the 'which machine is the server?' problem

  3. Just requires you to commit and push before changing machines. You should be commiting regularly anyway and a feature branch will mitigate the problems of commiting half finished work.