Free & open-source

You can have Claude finish the lesson. DevRecess is designed so that's the worse option.

A free, open-source collection of narrative-driven sessions for developers who want to understand what they built, not just ship it. The first story now includes comprehension gates — you don't advance by generating code. You advance by explaining why it works.

Start the first session on GitHub

DevRecess started from a simple premise: environments shape learning more than content does. The original design put you inside a story — a space mission, a detective case — so the technology became the medium, not the subject. That design philosophy has not changed. What has changed is the moment of reckoning.

In the first story, there are now points where the session stops. Not to show you an answer. Not to run a test. The session stops and asks you to explain what the AI-generated code does and why it works. You type your reasoning. If your explanation accounts for the behavior, you advance. If it doesn't, you try again. This is the Explain-Back Gate. It exists because "have Claude finish it" is always an option — and DevRecess is designed so choosing that option costs you something.

If you have shipped features with AI and occasionally wondered, mid-PR, whether you actually understand what you just submitted — this is the gap DevRecess is designed to close. Not by blocking AI (you can use it freely throughout). By making sure you cannot pass through a comprehension checkpoint on generated code you haven't understood.

Does any of this feel familiar?

You shipped the feature. You can explain what it does. You're less certain you could explain why the AI wrote it that way — or what breaks first when the next developer changes it.

You finished the tutorial. The code ran. You closed the browser. A week later you opened a similar file in a real project and realized you'd watched someone else solve that problem, not solved it yourself.

Someone asked you a question in the PR review. It was a reasonable question about your own code. You knew the answer was in there somewhere. You pasted the function back into Claude to check.

Most platforms right now are racing toward zero friction. Faster feedback loops. Smarter autocomplete. Inline AI that finishes the lesson before the learner does. That is a reasonable bet if you believe understanding is an obstacle to learning, or that comprehension happens automatically after enough exposure. DevRecess makes the opposite bet: that the moment a learner reaches for AI to finish a hard section is exactly the moment the real learning could happen — if there were something that made them stop and account for what they're about to accept. Deliberate friction at the comprehension gate is not a design limitation. It's the design.

Current Sessions (All Free)

Technology Sessions

Beyond Technology

Linear Algebra

Noir City

Coming Soon
Intermediate~60 min

Research Papers

Fantasy Realm

Coming Soon
Beginner~45 min

More subjects added bi-weekly

How it works

The Explain-Back Gate mechanic — deliberate friction at the moment of comprehension.

1

Download the session

Browse the DevRecess GitHub repo, choose the first story, and download the Markdown file. Open it in Claude, ChatGPT, Cursor, or any AI assistant you already use. No account. No install. No course dashboard.

2

Follow the story

The session puts you inside a scenario. You're not reading documentation — you're in the middle of a situation where something needs to be diagnosed, built, or fixed. The AI guides the narrative; you make the decisions.

3

Reach a gateExplain-Back Gate

At certain points in the first story, a gate appears. The session does not move forward until you explain, in your own words, what the code in front of you does and why it behaves that way. The AI can help you build the code. It cannot help you pass the gate.

4

Explain your reasoning

Type your explanation directly into the session. The gate checks whether your reasoning accounts for the key behavior — the thing a developer who actually understands the code would know. Vague answers do not clear the gate.

5

Advance when you've understood it

Once your explanation holds, the story continues. By the end, you have not just completed a session — you have evidence that you understood what you built.

Join the Learning Revolution

Want a Session Built Just for You?

Our pre-built sessions cover popular subjects. But what if you want to explore Kubernetes through a detective story, or linear algebra with a space adventure? We're building a session engine that generates play sessions tailored to your exact preferences.

  • Choose any subject + story setting + difficulty combination
  • Add custom notes about specific topics or your learning goals
  • Get a personalized session file ready for any AI assistant

We'll only use your email to notify you about custom session availability. No spam. Unsubscribe anytime. Privacy Policy