What version control is (and why you need it)

Imagine a video game with save points. You play a tricky section, you save, you try something risky. If it goes wrong, you reload the last save instead of starting the whole game over. Version control is save points for your project.

Without it, your project has exactly one state: whatever it is right now. If the AI mangles your code, the good version is gone. With version control, you keep a full timeline of every saved state, and you can jump back to any of them.

Git is the most common version control tool. It runs on your computer and quietly records snapshots of your project whenever you ask. A few things it gives you for free:

• A safety net — undo a bad change even hours later.
• A history — see exactly what changed, when, and why.
• Confidence — experiment freely, because nothing is ever truly lost.

That last one is the real prize. Vibe coding works best when you move fast and try things. Git is what makes moving fast safe instead of reckless.

Picture your project's history as a row of save points you can always return to:

   past ──────────────────────────────────────────────▶ now

   ( C1 )───▶( C2 )───▶( C3 )───▶( C4 )───▶( C5 )
     │         │         │         │         │
  "initial" "homepage" "login"  "oops, broke" "fixed it"

   each ( C ) = one commit = one save point you can jump back to