you are viewing a single comment's thread
view the rest of the comments
[–] 46 points 3 days ago (28 children)

Funny story about those backups

And because the damage extended to the .git project’s ‘objects,’ ‘refs’ and ‘logs’ folders, there was no way to recover the files and undo the catastrophe. The files were just gone in a puff of smoke.

  • source
  • parent
  • hideshow 28 child comments
  • [–] 89 points 3 days ago (16 children)

    No push to remote? If you’re working on something you care about you shouldn’t only have a local copy.

  • source
  • parent
  • hideshow 16 child comments
  • [–] 64 points 3 days ago (2 children)

    Backups are for smart people. Not who we're dealing with here.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 3 days ago (4 children)

    Maybe I'm old fashioned, but I feel like programming tools shouldn't blow away your checked in changes, even if you haven't pushed yet. You do you, though.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 8 points 3 days ago* (3 children)

    A power surge or some other force majeure could though. Push your shit off site.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 3 days ago (3 children)

    I learned about thst that one day…

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 3 days ago* (2 children)

    I learned the hard way

    I was going to the high school of hard knocks when they offered me a scholarship to the college of hard knocks, I TOOK IT!

  • source
  • parent
  • hideshow 2 child comments
  • [–] 11 points 3 days ago (7 children)

    My backup scheme:

    Computer --> 3 different cloud drives and github.

    Also

    Computer --> Wyoming home NAS --> USB external drive (weekly), swapped out every year and the old one stored in a waterproof gunsafe in the basement.

    Wyoming home NAS --> Florida office NAS -- > USB external drive (weekly)

    Wyoming home NAS --> Austin office NAS --> Tape (monthly) --> IronMountain for 7 years.

    If you are a single dev, all it takes is 14 USB sticks. 12 monthly backups and two for daily backups that you rotate weekly.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 3 points 3 days ago (2 children)

    Just for my sanity, do you have to power up usb drives every so often or they corrupt?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 3 days ago* (last edited 3 days ago)

    If you mean USB sticks (thumb drives), I have a few 20 year old ones that I dust off from time to time when all I need is something small. Some have been in a drawer for years before I touched them again.

  • source
  • parent
  • [–] 1 point 3 days ago (1 child)

    My backup scheme is either Github or Google Drive, whatever I have uploaded in Discord DMs, and a snowballing pile of unorganized hoarded files, which One Day™ I will sort.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 6 points 3 days ago

    One thing you could do is buy the.largest external drive you can get on black friday sales. Then just copy everything in it. No sort. Just dump it all in there. Think of it like clearing the table unto a large garbage bag. Then unplug it, put it in the closet, and do it again whenever you remember.

    Even a mess like that is better than no backup at all.

  • source
  • parent
  • [–] 4 points 3 days ago*

    If you don't include .git/ in your backup you simply have no backup.

    The .git folder is the heart of a Git repository. It is the hidden directory that Git uses to store all the information necessary for managing your project's version control history. This folder is where Git keeps track of all the changes made to your files, allowing you to revert to previous versions, collaborate with others, and maintain a complete history of your project.

  • source
  • parent