Journal · The AI Architect · 2026-07-16
Copy real files before your AI touches them. A backup is a seatbelt — you put it on before you drive.
Copy real files before your AI touches them. A backup is a seatbelt — you put it on before you drive.
The tension isn’t whether backups matter. Everyone nods at that. The tension is that backing things up feels like an insult to the moment — you’re excited, the AI is fast, the task is small, and stopping to duplicate a folder feels like bringing an umbrella to a sunny picnic. So people skip it exactly when they shouldn’t: on the fast, casual, “this’ll only take a second” tasks, which are precisely the ones where a misread instruction or an overeager rewrite can quietly erase an afternoon’s work.
The illusion of the small task
The riskiest moments aren’t the big, scary migrations where everyone is already careful. They’re the small requests — “clean up this script,” “reformat these notes,” “merge these two files” — where the stakes feel low enough that caution seems unnecessary. But an AI doesn’t know your files are irreplaceable. It doesn’t know which folder is your only copy and which is a throwaway draft. It just does what you asked, sometimes more thoroughly than you meant.
Try this: before any task where the AI will edit, delete, or rewrite files directly, copy the whole folder — not just the one file — into a sibling directory with today’s date in the name. notes becomes notes-backup-0314. It takes fifteen seconds and it means the worst-case outcome is “I redo fifteen seconds of copying,” not “I lose the only draft of something I cared about.”
Backups are for you, not for catastrophe
People imagine backups as insurance against disaster — server fires, ransomware, the dramatic stuff. That’s part of it, but the more common use is much smaller and more personal: you asked the AI to do one thing, it did a slightly different thing, and now you want to compare. Without a backup, “compare” means trying to remember what the original looked like. With a backup, it means opening two files side by side.
This reframes backups from a chore into a tool. A copy of the original isn’t just protection — it’s a diff partner. It lets you ask, calmly, “did this change help or not?” instead of relying on memory or gut feeling. That question is at the center of working well with AI: you’re constantly evaluating whether an edit made things better. You can’t evaluate well against a version that no longer exists.
Make the habit automatic, not heroic
The problem with “remember to back up first” is that it relies on remembering, and memory fails exactly when you’re in a hurry — which is often. The fix isn’t more discipline. It’s less reliance on discipline in the first place.
Try this: if you’re working in a folder regularly, set up a tiny script or a scheduled task that snapshots it daily, regardless of whether you’re about to do anything risky. Many systems can do this with a single line in a scheduler. You’re not trying to build a perfect backup system — you’re trying to remove the moment of decision. A seatbelt you have to consciously buckle every time is less reliable than a car that won’t start until you do. Where you can, build the equivalent: version control for code, a synced backup folder for documents, autosave with history for anything else. The goal is that “did I back this up?” stops being a question you have to ask.
And when automation isn’t set up yet, keep the manual habit boring and specific: copy, rename with a date, then start. Not “I’ll back up important stuff” — a vague intention that dissolves under time pressure — but a fixed, two-second motion you do every time, on every file, no judgment calls required. Judgment calls are where the habit breaks, because in the moment, everything feels like an exception.
None of this requires trusting the AI less. It’s not about suspicion. It’s about acknowledging that any tool operating on real files, quickly, at your instruction, will occasionally do something you didn’t intend — and the cost of that mistake should be measured in seconds, not hours.
I go into more of the mechanics of this — what to back up, how often, and how to build the habit so it survives contact with a busy week — in the book. But the core of it is simple enough to carry with you starting today: copy first, then let the AI work. The backup isn’t a sign you don’t trust the tool. It’s a sign you understand what you’re driving.
Go deeper. The full method is in The AI Architect. New here? Start with the free companion pack, or explore the series.