The “Final Final v2” Problem
You’ve probably seen a folder like this. Maybe you’ve made one.
Someone is afraid of losing their work, so they save a copy. Then another. Then final, final-v2, FINAL-final, USE-THIS-ONE…
A week later, nobody knows:
- Which copy is the latest?
- What actually changed between them?
- Which one was the version that worked?
Version Control Fixes This
Version control is a tool that keeps every version of your project for you, neatly, behind the scenes.
- Your folder only ever shows one copy of each file: the current one.
- Every earlier version is still kept, each with a note saying what changed.
- You can go back to any of them, any time.
Version control means nothing is ever lost, and every mistake can be undone.
Meet Git
The version control tool almost everyone uses is Git. You installed it in the last part.
Git lives on your computer and quietly watches your project folder. When you tell it to, it takes a snapshot of everything, and files it away with your note.
| Without Git | With Git |
|---|---|
| Copies everywhere | One clean folder |
| “Which one is the latest?” | Always obvious |
| “What did I change?” | Every change has a note |
| One bad mistake can ruin everything | Go back to any earlier version |
Why This Matters So Much for Vibe Coding
When Claude writes your code, it can change a lot of files very quickly.
Most of the time, that’s great. But sometimes a change goes wrong, and you’ll want to get back to “the way it was an hour ago, when it worked.”
Git makes that a one-sentence request.
The faster your builder works, the more you need save points.
You Won’t Type Git Commands
Here’s the good news: you won’t have to learn Git’s commands. Claude runs them for you.
You just need to understand two ideas, and that’s what the next two notes are about:
- Commits: the save points themselves.
- Branches: safe copies for trying out ideas.