Learning Without AI

Your understanding, your decomposition, your pseudocode, your attempt — then hints one rung at a time. Explain it back, build from memory, find where you hesitate.

Learning Without AI
▶ lab

In this mode the AI does not write solution code. It may ask questions, explain a concept, review your reasoning, give a hint, or point at the documentation — everything except the part that would replace your attempt. The rule is about what is delegated, not about the tool.

Q · You want to learn to build things, and you have a tool that will build them for you. How do you use it so that you end up able to build the next one — and how would you know whether you can?
No AI on the First Attempt
▶ lab

Problem → your understanding → your decomposition → your pseudocode → your attempt → then ask for help. The order is the lesson: help given after an attempt corrects it; help given before one replaces it.

Q · You are facing a problem you have never solved and a tool that would solve it in seconds. What do you produce before you ask, in what order, and why does the order matter more than the quality of what you produce?
The Hint Ladder
▶ lab

Hint one: the conceptual direction. Hint two: the relevant abstraction. Hint three: pseudocode. Hint four: a partial implementation. Then the reference. Each rung gives less than the next, and the rung you stop at is the measure of what you still own.

Q · You are stuck after an honest attempt, and you want help that unblocks you without taking the problem away. What are the rungs of help, how do you ask for one at a time, and how do you tell that you took one too many?
Explain It Back

Explain it in your own words, draw it, apply it to a case it was not explained with. Three checks that turn "I read it and it made sense" into evidence — and that fail, usefully, exactly where understanding stops.

Q · You have read an explanation — of webhooks, of idempotency, of a data model — and it made sense. How do you find out whether you understood it or only followed it, before the difference costs you?
Build From Memory

Close the reference. Rebuild the core idea from nothing. Compare with the reference. Fix the understanding, not the code. The differences are the only precise map of what you did and did not learn.

Q · You have built something with a reference open — a tutorial, a generated solution, a colleague's code — and it works. How do you find out how much of it you could build again, and what do you do with the answer?
The Feynman Check

Can you explain it simply? Where do you hesitate? Which term are you hiding behind? The hesitation is not a failure of nerve — it is the most precise locator of a gap in understanding there is, and the term you reach for is the gap's name.

Q · You believe you understand something and you want to find the exact place where you do not. How do you use a simple explanation as an instrument, and what do you do with the place it points at?