4 ms·
Just put all your project files in Dropbox! Seriously, it's so easy. Every time you hit save, you'd have to try to lose the file. Pair this with git going to g
by christiangenco 13y ago
Just put all your project files in Dropbox!
Seriously, it's so easy. Every time you hit save, you'd have to try to lose the file. Pair this with git going to github or bitbucket and it would take several well placed nuclear explosions to destroy your work.
If my laptop instantaneously combusted at any point in time I would, at maximum, lose approximately 6 seconds of work (or the last time I hit "save"), and could set up a new laptop and be productive on it in about an hour (to install Dropbox and give it time to sync, Sublime, iTerm, Chrome, and custom keyboard hacks). Pet peeves, man.
- meowface 13y agoDropbox has been a life saver for me. The ability to restore previous files in particular has helped me in many situations.
- fitzpasd 13y agoI used to do this, but then when compiling the project the Dropbox client would shoot to over 70% CPU usage and the fan on my laptop would go into overdrive. Switch to GitHub/BitBucket
- ValentineC 13y agoA suggestion off the top of my head would be writing a script that pauses Dropbox syncing before running a compiler. (From a quick Google search, there seem to be a couple of scripts already written that do this.)
- brianwawok 13y agoThis is due to churn on the compiled files right? The fix would be to compile these files someplace outside of dropbox. (Because the important artifact you want to back up is source code, not binaries). Depends on your language / build tool for how complicated this would be...
- jevinskie 13y agoCMake encourages out of tree builds. I find them superior to in tree builds in most cases. But if it is just a random utility that I'm compiling from the Internet and do not intend to dev on, in tree works fine for me.