Safety net

Save Points: Never Lose Your Work

Vibe Coder 101 · Phase 2: Leveling Up · Stage 10 of 38 · about 12 min

Picture beating a hard level in a video game, then walking into a trap and losing all of it because you never saved.

That is a normal Tuesday in vibe coding, and it is entirely avoidable.

Why this matters more with AI

When you write code by hand, you change a few lines at a time. When you ask an AI to "clean this up", it might rewrite four files at once — and some of what it changed was working perfectly.

Without save points, your only undo is asking it to put things back, which it cannot reliably do. It does not remember your old version either.

With save points, that whole disaster becomes: go back to this morning. Seconds.

What a save point actually is

The tool for this is called version control, and the common one is Git. Ignore the vocabulary for a moment — here is the whole idea:

  • A commit is a save point: a snapshot of every file, with a short note about what you changed.
  • Your history is the list of save points, and you can return to any of them.
  • A repository (repo) is just your project folder with that history attached.

That is enough to be dangerous with. There is a lot more to Git, and you do not need any of it yet.

The habit

Save before you let the AI make a big change. Save after anything starts working.

Concretely:

  • Got the button working? Save point. Note: "add button works".
  • About to ask for a redesign? Save point first.
  • Redesign came out badly? Go back. No arguing with the AI about what it used to look like.

Write notes for your future self, not for a computer. "checkbox works, before adding delete" is a great note. "update" is useless.

Doing it without the terminal

Git has a reputation for being frightening, and honestly the command line version earns some of that. You do not have to start there:

  • Many AI editors have a save-point button built in.
  • Desktop apps exist whose whole job is making this a button.
  • Vibe Coder Playground has a save button per app: it shows what changed since your last save point, saves with a note, and can undo the last one — and it can suggest the note for you.

Any of these is fine. The tool matters far less than the habit.

One thing to never save

Never put passwords, API keys, or other secrets into a save point — especially in a project you might share. History remembers, so a secret saved once and deleted later is still in there.

Most projects handle this with a file listing things to ignore. If you are unsure whether something is a secret, it probably is.

Your turn

Make one save point on your weekend project right now, with a real note. Then deliberately ask the AI for a change you do not really want, see it happen, and go back.

Once you have done that once, you will never build without it again.