I Saw the Notification — and Froze
Last Friday at 3 PM, I was asking my freelance designer to tweak an image on my website. Suddenly GitHub crashed — the foundation that many websites and tools use to store files. We both stared at the spinning loading icon for a full 4 hours, twiddling our thumbs. What did it feel like? Like the courier company you work with suddenly shutting down — your orders all stuck on the road, while clients keep chasing you.
What Actually Happened with GitHub? How Did Peers Handle It?
On August 17, GitHub — the world's largest code hosting service — was down for 4 hours. The cause wasn't complicated: a database connection config issue triggered a chain reaction that took down login, push, and API. My friend Xiaolin (Chengdu, runs an independent design studio) was also panicking that day — her website hosting service runs on GitHub underneath, and her editor just wouldn't open. What did she end up doing? She dug out last week's manual backup from her local hard drive, used another platform as a temporary stand-in, and didn't miss her client deadline.
Replicating an "Outage-Proof" Backup — What's the Cost?
Money: $0 (use your existing cloud drive) or $30–50/month (a separate cloud drive).
Time: Spend 2 hours today figuring out "which things would kill me if I lost them."
Technical barrier: No code needed. If you can drag folders and click a mouse, you're set.
First step: Search your computer for "client files," "contracts," "website files," "designs" — right-click and copy to a cloud drive / USB / WeChat Favorites. This one action, you can do today.
Advice for Peers at Different Stages
Just starting: Spend 1 hour today, drag your most important client contracts and assets to a local copy. The cost of doing backup too late isn't money — it's your client's trust in you.
Have 1–2 clients: Every Sunday night, spend 10 minutes syncing this week's changed files to a second cloud drive (Nutstore, Alibaba Cloud Drive). This is a habit I only recently formed — I was lazy once before and almost lost a client's entire visual identity package. Luckily an old version saved me.
Scaling up: Install an auto-sync tool (Dropbox, Nutstore, both work) — files backup the moment they change, peace of mind. Also, I'd recommend building a WeChat group relationship with your tool vendors — when there's an outage, you get notified first, instead of being caught off guard like Xiaolin.
Honestly, this setup isn't for everyone. But if one day you suddenly realize some tool you can't live without — spend 2 hours today making a backup. Better than getting on your knees to beg clients for forgiveness later.