C.W.K.
Stream
Lesson 01 of 05 · published

Why final_final_REAL.zip Always Loses

~18 min · version-control, mental-model

Level 0Untracked Rookie
0 XP0/47 lessons0/14 achievements
0/100 XP to next level100 XP to go0% complete

final_final_REAL.zip is a confession

You have seen the folder. report_final.docx, report_final_v2.docx, report_ACTUALLY_final.docx, and the closing argument project_final_v2_REAL_USE_THIS.zip. That naming scheme is not a workflow. It is a confession that the project has no memory and the human is the memory.

A backup tool answers can I recover this file? Git answers a different question: how did this project become what it is, and can I move safely through that history? A real project is a web of source files, configs, generated artifacts, experiments, bug fixes, and decisions. Git gives that web a timeline you can walk forwards, backwards, sideways into a parallel universe, and back.

That is why the rest of this quest is not a list of commands. It is a model. A commit is a named checkpoint for the whole project, not just a save of one file. A repository is a history database that lives next to your working files in .git/. GitHub is useful, but Git itself is local-first — you can commit, branch, diff, blame, and recover without the network. If you finish this lesson with one upgrade, let it be this: stop saving copies, start writing history.

Code

Replace zip-as-version with init-and-commit·bash
# Old habit:
cp -r project project_final_v2_REAL_USE_THIS

# New habit (run once per project):
cd project
git init
git add .
git commit -m "Initial import: working baseline"

# After this, every change is recorded by intent, not filename.
Sanity check: this is a real Git repo·bash
git status         # working tree state
git log --oneline  # what history exists yet
ls -la .git/       # the actual database

External links

Exercise

Pick a small folder you currently version with copies (a notes directory, a side script, a writing draft). Run git init inside it, then git add . && git commit -m "baseline". Make one tiny change, commit again. Then run git log --oneline. Write two sentences describing what is now possible that was not possible with copy-folder versioning.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.