Even on a solo project, `git bisect` by itself is more than enough reason for me to use source control. I could script something similar that ran against my dai

Even on a solo project, `git bisect` by itself is more than enough reason for me to use source control. I could script something similar that ran against my daily backups, but then I'd have to recursively diff two backups to find out what had changed between them - at which point I'm basically implementing a shoddy subset of what git already does. My 'backups' may as well be a cronned: git add . && git commit -m "Daily snapshot" && git push Ta-da! You are now 'using' source control. This or any other automatic backup solution has a big problem though: if the backup happens while you have a syntax error or something in your code then your test suite will fail and any bisect type functionality you have will be useless.