babyjay If anyone wants to give me advice on backing up your work and what procedures you use, I'd be interested to learn.
I use Git, which is great and is the programming industry standard but has a tricky learning curve. There is also Subversion (SVN) which is an easier version control system for newcomers to pick up, but isn't as good as Git especially for collaborating. Then there's Perforce, which is the AAA gaming industry standard. Perforce is complicated and absolute overkill for a solo dev, so don't worry about it 😛
The nice thing about version control systems (which Git, SVN, and Perforce are) is that each "backup"/commit only requires a tiny amount of space because only changes to your files are being tracked. If you change only a few lines of code and commit them, that commit only needs to store the changes to those lines. In contrast, you can't have as many backups as you want with Dropbox or other filesharing software because each backup is everything.*
*Dropbox and some others actually probably have strategies for mitigating backup size nowadays, idk. Still nothing beats a good version control system in that regard.
