How Git Actually Stores Your Code
Git makes sense the moment you stop thinking about commands and start thinking about a content-addressed store of objects with pointers into it. Over fourteen mornings, this course builds Git from its hashes upward, until branching, merging, rebasing, and pushing all look like obvious consequences of the storage format.
It opens with
- The Name Is the Content
- Blobs don't know their filenames
- Trees are how files get names
The rest stays hidden — that's the point. Nobody sees the plan after it's accepted, including whoever made it.
Day one is open to everyone — the whole first morning, not an extract. The rest arrives a day at a time once you subscribe.
This is one long call to a model, so there's nothing to watch. Closing the tab won't stop it — whatever gets written turns up under Your reading when it's done.