The month-old screencast that lies
Last spring I opened one of our own lessons to answer a student question. The lesson walked through a flow step by step. Click here, then here, then this panel opens. Except the panel did not open. The tool had moved the button two weeks earlier, renamed it, and tucked it under a menu. Our video was confidently pointing at empty space.
Nobody wrote a bug report because nothing crashed. The video still played. The narration still sounded right. But a beginner following along hit a wall, assumed they were the problem, and quietly gave up. That is the worst kind of failure, the silent one.
When you teach a fast moving tool, your material has a shelf life measured in weeks. A model changes its defaults. A setting gets renamed. A keyboard shortcut moves. Each small shift turns one more sentence of your course into a small lie. Not a lie you told on purpose. A lie that time wrote for you while you were not looking.
We watch the release cycle like a build pipeline
So we stopped treating the course as a finished object and started treating it like a running service. Services have monitoring. Ours does too.
Every week someone on the team reads the release notes for the tools we teach. Not skims. Reads. New features, deprecations, changed defaults, anything that touches a screen a learner will see. We keep a plain list of every place in the course where a specific button, menu, or model behavior gets named on camera or in text. When a release note lands, we grep our own list the same way you would grep a codebase for a deprecated function call. If the release touched something we reference, that lesson gets flagged.
Then we do the thing most course teams skip. We click the flow ourselves, as a learner would, from a clean account. Fresh eyes, no muscle memory, following our own written steps literally. If a step does not match reality, it goes on the fix queue. This catches the drift that release notes miss too, because tools ship quiet changes that never make the notes.
Reshoot the stale piece, not the whole thing
Here is the part that keeps this sustainable. We do not relaunch the course every quarter with fanfare. A big quarterly relaunch sounds responsible and is actually the trap. It batches all your rot into one giant event, which means for eleven weeks out of twelve your material is decaying in public while you wait for the big fix.
Instead we ship small. If one short segment is wrong, we reshoot that segment and swap it in. The rest of the lesson stays. Students who already watched it do not lose their place. The fix goes out the day we catch the break, not the day the quarterly calendar allows it.
This only works because we built the course in pieces from the start. Short segments, each covering one flow, each independently replaceable. It is the content version of small functions and small commits. When everything is one long monolith, changing a single button means rerecording the whole thing or living with a wrong whole thing. When it is thirty small pieces, you replace the one that broke and move on.
What this costs and why we do it anyway
I will be honest about the cost, because pretending it is free would be its own kind of lie. This is real work. Someone reads notes every week. Someone reclicks flows that already worked last month. Someone reshoots segments that were fine until a release broke them. It is unglamorous maintenance, and maintenance never trends.
But the alternative costs more, it just hides the cost inside your students. Every stale step is a beginner deciding they are too dumb for this, when really the material was pointing at a button that moved. You do not see that cost in a dashboard. You see it in the people who never come back.
At AGINE Academy we teach building with Claude, and Claude changes. That is the whole reason the subject is worth learning and also the reason the teaching can never sit still. We made peace with that. The course is a thing we run, not a thing we finished. The first lessons are free with no signup, partly so people can check whether the steps still match reality before they trust us with anything. If we did our job that week, the buttons are where we say they are.
Treat your teaching material like code that ships to production, because in a way it does. It runs inside someone else's afternoon. When it breaks, they feel it. So watch the release cycle, click the flows a learner clicks, and fix the broken piece fast. The reward is boring and worth everything, a student who follows the steps and has them simply work.
AGINE Academy is an independent product by AGINE AI (not affiliated with Anthropic). We teach building with Claude by doing the work, not watching lectures.
Top comments (0)