Some Days the Method Is the Work

The plan was simple. CS50P Lecture 1, Conditionals. Fifteen minutes of David Malan on if, elif, else. Cache the transcript, drill the vocab, press play. A 25-minute vocabulary block to build schemas, then watch with the schemas pre-built. The kind of session that should run on rails.

It didn’t.

The vocabulary block ran 70 minutes instead of 25. The video never got watched. What broke wasn’t the content — the verbatim transcript was cached, schemas ready, source-check rule firing. What broke was the method. The first attempt tried fourteen vocabulary terms in one batched cluster — definitions, code anchors, Malan quotes, retrieval questions all stacked into a single response. I disengaged immediately. Every term was tangled with every other term; the lock state was unverifiable.

So we stopped and codified. Four pivots in seventy minutes, each a real correction. The final shape: ground zero per term, simplest possible definition in five to ten words, one retrieval question, confirm the lock, add one layer of complexity, confirm again, move on. No batching. One layer per bite.

Process Improvements Compound; Headline Wins Don’t

The honest scoreboard: three durable method codifications landed, the actual learning benchmark missed entirely. That trade reads bad on paper. The 15-minute video was the explicit goal. It didn’t happen.

But the construction analog matters. You don’t pour the second floor before the foundation cures. The kindergarten definition is the foundation. The retrieval question is the curing pass. Pouring all five layers at once produces walls that LOOK done — until the first stress (a tricky question, a debug, a real interview) shows the cracks. Today was four foundation pours. No tower yet. But every future session pours into structure that holds.

The pattern transfers. Code reviews have the same failure mode — fifteen concerns in one thread, none of them locked individually. Memory anchoring works the same way: one image plus one association, then move on. The Kindergarten Ladder isn’t a learning hack; it’s a method primitive that compounds across every teaching context I’ll touch.

Tomorrow the deferred fifteen minutes is the first move of the session. Non-negotiable. The method tax was paid today; the content has to execute next session or the codification becomes meta-tourism. Showing up isn’t always headline content. Sometimes it’s just the next foundation pour.