Nearly lost 2 weeks of work because I skipped git commits

I was coding a Python script at a coffee shop near Union Station last Tuesday. Forgot to commit for about 6 hours and then my laptop froze during a forced update. Ended up recovering most of it from a temp file in my user folder, but lost about 45 minutes of changes. Has anyone else had a close call like that?

3 comments

3 Comments

mila_harris25d agoMost Upvoted

Eh a commit every hour is way too slow for me, I just hit ctrl+s every few minutes like a maniac.

the_hayden25d ago

I started setting a timer on my phone for every hour when I'm deep in code. That little buzz saves me from these disasters. Now I just do a quick commit even if it's messy.

skylerrobinson25d ago

Had a similar thing happen at a library once. Spent 3 hours debugging then my battery died. Realized I never saved a single file. Now I just commit every time I finish one small thing like fixing a typo. Even if the commit message is just "wip".