In general the best way to develop any code is to use a Version Control System. As long as the version control system is hosted in a shared resource, such as online, then any computers with access to that shared resource will have access to the latest changes that have been committed (and in some cases pushed) to that resource and can make changes, commit (and possibly push) those changes to a) preserve those changes & b) make them available to other computers &/or developers.
That said you next need to distinguish between:
- The Version Control System Software
- The hosting service &
- The client software.
Popular examples of the Version Control Software include:
- Many more
Issues to consider include:
- Personal Preferences
- Usability & Support
- Cost although many are available free some others are very pricey
- Available hosting solutions
But consideration needs to be made on the basis of:
- Cost e.g. While GitHub is free for public repositories there are charges for private ones.
- Availability & Accessibility (e.g. Can you access it from all of the locations that you might need to access it from)
- Security & Privacy
- Support for your preferred version control software
The hosting service can be any of:
- A shared computer or your own server
- Services such as GitHub, GitLab & many others
- In the case of distributed version control systems such as git, mercurial, etc. you can simply use shared media or even email to pass the changes around as well as or instead of a central server.
Your client software is what you use to commit your changes, etc., GitKracken is one example for git. You need to consider:
- Support for your chosen VCS
- Cost (lots of free options available)
- Availability on the platform(s) that you are developing on and may need to develop on in the future.
It is also worth noting that many IDEs and even some editors include clients for one or more of the popular VCS systems.
If you are developing this software as a part of your work there may be other constraints to consider.