4 ms·
Don't you use version control?
by Ralith 14y ago
Don't you use version control?
- bestes 14y agoI read it as s/backup/commit
- evincarofautumn 14y agoTo be fair, version control and backups should be separate things.
- jeremyjh 14y agoRight, because your backup is a VERSION of the code that you want to keep around, in case you need it right? Some version control tools don't let you create local, private versions. That is too bad. That doesn't mean that doing so is not a version control concern.
- georgemcbay 14y agoIMO version control, file versioning and backups should all be separate things and ideally all available. Even when using a version control system that allows for robust local branches, sometimes it is nice to be able to revert a specific file's state to a known recent version that you never bothered to commit. Sometimes editor undo is sufficient for this, sometimes not. Dropbox and Google Drive have both saved me some time in this area (like 15-30 minutes, not days, but even that is appreciated) recently.
- Ralith 14y agoIsn't that just evidence that your commits aren't granular enough? Certainly, simply backing things up generally won't solve your problem, since good backup procedure can involve offsite storage being hours out of date.
- thebigshane 14y agoVersion control won't save you if you start tidying up (and introduce new bugs) before you commit changes.
- Ralith 14y agoYou shouldn't be making commits so monolithic that that becomes an issue.
- jawr 14y agolong long ago, version control was something i avoided as i was yet to see it's benefits and it was an avoidance to the problem at hand (learning to program). with git this isn't as necessary, woopla.