MIT DEDICATED A FULL LECTURE TO GIT'S INTERNALS -- BECAUSE THEY FOUND MOST DEVS MEMORIZE THE COMMANDS AND HAVE NO IDEA WHAT THE TOOL ACTUALLY DOES A whole 85 minutes MIT session that refuses to teach git as a list of commands to copy, and instead shows you the... data model underneath -- the thing that makes every command finally make sense. -> The moment it clicks, git stops being scary magic. You stop memorizing "The incantation that fixed it last time" and start actually knowing what's happening. Most people learn just enough git to not get fired. Four commands, blind faith, and a prayer before every merge. In 2026 that's not enough anymore -> git is the literacy test for being in the room, and "I'll just reclone it" is the fastest way to look junior. An AI agent will branch, commit and rebase faster than you can read. When it tangles the history, untangling it runs on understanding the model MIT teaches in this one hour. Anyone can run git push. The person who understands the graph underneath is the one who saves the repo when it breaks. Bookmark & Watch it ↓show more

If anyone wants the youtube link of the original video

it’s next to impossible to actually lose any code once that code has been committed That’s what most devs fear and why the unofficial "mv repo repo.backup; git clone <cloneagain>" is so popular 😝 Compiled a couple more references (and a hopefully truly easy walkthrough) here:

You don't need to know the intervals of every technology you are using. And in fact most don't and do just fine.

join my tg for the actual alpha on ai, financial markets and coding -&gt;

1) I require our devs to use GIT Extensions - visualization makes a big difference... 2) most grads have minimal experience with practical necessities -&gt; GIT, versioning, coding standards, etc... 3) college creates tech debt monsters -&gt; who skip design &amp; never diagram anything 🤯

I taught myself by reading articles about understanding git and using it.

recloning the repo is so junior

BS. Git is a travesty, an ego trip of Linus T. It's a fantastically complicated tool to solve problems that only a small subset of developers have. Its complication doesn't flow from its power but from its chaos - it's largely non-orthogonal, with many islands of cmd groups

during early experiments and git worktrees with orchestrating agent I saw the most tangled git mess concievable - and a single agent was unable to untangle the entire thing in 15minutes which would have taken me hours.

Meh. I know how git works underneath, it's simple and elegant. The syntax always crashes me out, though. The problem most devs have is that they only have a surface level understanding of everything. It's why even AI can code.

If so many people have problems with git then git is the problem.

that's where most ai agents are too, memorizing rules without understanding what they're optimizing for

But what if you dont have 85 minutes to learn git internals - can you learn as you go?

It's very interesting to hear about repositories

Yeah no shit that’s why we use the tool so we don’t have to know the internals 😂

Have watched almost 85 minutes,really smart lecture

Good content, but the low resolution makes the text in the video hard to read and tiring to watch. Is it available anywhere else?

just have claude do the source-control crap.

Better idea: adopt jujutsu.

Very interesting post

1 hour of alpha

"Four commands, blind faith, and a prayer before every merge" is the most accurate description of how most people use git 😭

In 2026 Claude handles git for me.

GitCraft!

the person who understands the data model is the one who saves the repo

a post bashing ai written with ai. nice.

this is how it should be taught honestly, understanding the graph changes everything

This lecture is very useful, I think the students will learn this lesson.

wow, nice share👍🏽

The git-as-DAG mental model changes everything. Once you see commits as immutable snapshots and branches as just pointers, 'scary' operations like rebase stop being incantations you copy from Stack Overflow and become obvious graph manipulations. The AI angle makes this even more urgent — agents that mess up git history need a human who actually understands the model to clean it up. "I'll just reclone it" doesn't cut it when an agent has been autonomously committing for hours.

very interesting lecture

Once you see governance as a graph of decisions, approvals and reversals, the distinction between "software" and "organization" starts to disappear. Git versioned code. I'm interested in versioning governance itself. Repo ↓

Worth watching 100%