Against the Money Shot
Against the Money Shot
I’ve never learned anything important from a tutorial.
That’s not modesty or some weird flex. I’ve watched hundreds of them. Courses, YouTube breakdowns, conference talks, Twitter threads that promise to teach you distributed systems in 12 tweets. And every time, there’s this feeling at the end — this warm glow of comprehension. I get it. I understand now. I could do that.
Then I open my editor. And the screen is blank. And I realize I don’t understand a goddamn thing.
What I understood was the performance of understanding. Someone stood on stage or sat in front of a camera and walked me through their finished understanding — the clean, linear, compressed version. Here’s the problem. Here’s the elegant insight. Here’s the solution. Here’s the money shot.
But understanding doesn’t work that way. It never has.
The Tutorial Industrial Complex
There’s a whole economy built on knowledge porn, and it’s enormous.
Udemy has over 200,000 courses. YouTube is the world’s largest university that grants no degrees and produces almost no practitioners. Every week there’s a new “Learn X in Y minutes” post that racks up thousands of upvotes from people who will never build X.
This isn’t an accident. Knowledge porn follows the same compression algorithm as every other pornification: identify the climax (understanding), strip away everything that isn’t the climax (struggle, confusion, failure, the slow accumulation of hard-won intuition), and deliver the climax directly.
Here’s what makes it insidious. Real understanding is layered. You know things in different ways — with your body, through your perspective, by participating in the process, and finally in propositions you can state. When you actually learn something, all four layers build from the ground up. You participate first: you fumble with the material, you make it real by touching it. Then your perspective shifts: you start seeing the problem differently. Then your procedures develop: your hands learn what to do without your conscious mind directing them. And only then can you articulate it propositionally — in the clean sentences the tutorial starts with.
Knowledge porn inverts this entirely. It gives you the propositional layer — the clean conclusion — and skips everything underneath. You can state the insight. You can repeat the framework. But the three layers that give it meaning — the participation, the shifted perspective, the embodied procedure — were never built. What you’re holding is a roof with no building underneath it.
And the result feels like learning. The same way food porn feels like eating and social media feels like connection. Your brain registered “comprehension achieved.” But you didn’t comprehend anything. You watched someone else comprehend it and your mirror neurons fired.
Strip away enough layers and what’s left isn’t knowledge at all. It’s stimulation — bare neural activation that mimics the sensation of understanding without any of its substance. The warm glow at the end of the tutorial isn’t insight. It’s the ghost of insight, haunting the place where participation should have been.
The Paralysis of Watching
Here’s the thing about tutorials that nobody acknowledges: they break something.
When you watch someone explain a system beautifully — perfect diagrams, intuitive examples, elegant buildup to the key insight — you are receiving one-way scaffolding. Information flows to you, but nothing flows back. You don’t act on what you’re receiving. You don’t test it against reality. You don’t fail and adjust. You sit there, functionally paralyzed while visually omnipotent.
You can see the whole system. You can zoom in on any component. You feel like you’re flying over the territory with perfect clarity. But you never touch the ground. And the gap between seeing the map and walking the territory is not a gap of degree — it’s a gap of kind.
The question is simple: does the compression scaffold future action, or does it replace it? A map is good compression — it reduces the territory into something navigable and then sends you into the territory. A cooking show that makes you want to get in the kitchen is good compression. A yoga tutorial you follow with your body on the mat is good compression. The compression serves the doing.
But when the watching becomes the thing — when you consume the tutorial instead of building, browse the map instead of exploring, watch the yoga video instead of moving — the scaffolding collapses into substitution. You’ve replaced the action-perception loop with pure perception. And the more you do it, the more the gap between your confidence and your competence widens.
The Builder’s Epistemology
Here’s my claim, and I’m going to state it plainly: you cannot understand something you haven’t built.
I don’t mean this as gatekeeping. I’m not saying you’re not allowed to have opinions about things you haven’t built, or that watching tutorials is worthless. I’m making a statement about the nature of knowledge itself.
There is a kind of understanding that can only exist in your hands. Embodied knowledge. Tacit knowledge. The kind that lives in the gap between “I can explain this” and “I can do this.”
We know more than we can tell. A master potter can’t fully articulate why they apply pressure here and not there. A seasoned developer can’t always explain why one architecture “smells wrong.” The knowledge is in the doing. It was created by the doing. And it cannot be transmitted except through doing.
When you build something, you encounter every piece of reality that the tutorial edited out. The dependency that doesn’t install cleanly. The race condition that only appears under load. The design decision that seemed elegant in theory and turns out to be a nightmare in practice. These aren’t obstacles on the way to understanding — they ARE understanding.
The setup is the thing. The cooking is the meal.
I’ll be specific. I once watched a beautiful 40-minute talk on how CRDTs work. Conflict-free replicated data types. The speaker was brilliant. Clear diagrams, intuitive examples, the whole thing built up to a moment where the mathematical elegance just clicks. I walked out of that talk feeling like I understood CRDTs.
Then I tried to implement one. And I spent three weeks in a pit of confusion that the talk had carefully, skillfully compressed out of existence. The edge cases. The garbage collection problem. The fact that “conflict-free” doesn’t mean “problem-free.” The way your intuitions from regular data structures actively mislead you.
Those three weeks taught me what CRDTs actually are. Not the talk. The talk gave me the roof. Implementation built the building.
Implementation IS Understanding
There’s a popular idea that understanding comes first and implementation comes second. You learn the theory, then you apply it. You understand the concept, then you build the thing.
This is the pornified epistemology. It assumes understanding is the climax and implementation is just… execution. Mechanical. Menial. Something you do after the real intellectual work is done.
It’s completely backward.
Implementation is not a path to understanding. Implementation IS understanding. They are the same thing. When I implement a consensus algorithm, I don’t understand it and then implement it. The implementing IS the understanding. Each bug I hit reshapes my mental model. Each edge case reveals an assumption I didn’t know I had. Each failure teaches me something the paper couldn’t, because the paper presented a finished proof and reality presented an unfinished system.
This is why the best engineers I know are deeply skeptical of people who “understand” systems they’ve never built. Not because they’re gatekeeping — because they know, from hard experience, that the understanding you get from reading about something and the understanding you get from building it are qualitatively different things. Different in kind, not degree.
It’s the difference between reading about swimming and being in the water.
The fix isn’t more content. It isn’t better tutorials or more immersive courses or AI that explains things more clearly. The fix is building something. Anything. Building it badly, breaking it, rebuilding it. Getting your hands in the material and letting the material teach you what no compression can convey.
The setup isn’t what you endure to reach understanding. The setup is understanding.
Stop watching. Start cooking.
