How To Study — The Pattern

You don’t have a discipline problem. You have a system problem.

Most people study backwards: consume first, build maybe, recall never. Then they’re surprised when a concept they “learned” two weeks ago is gone.

That’s not a character flaw. It’s the Ebbinghaus forgetting curve doing exactly what it does to every human brain: without review, most of what you learn today fades within days.

The fix isn’t trying harder. It’s a loop that fights forgetting by design.

The Daily Loop

This is the whole system. Run it every study session.

flowchart TD
    A[Prime 5 min] --> B[Learn 30 min]
    B --> C[Build 60 to 90 min]
    C --> D[Recall 10 min]
    D --> E[Log 5 min]
    E --> F[Tomorrow start at Prime]
    F --> A

Total: roughly 2 to 2.5 hours. Exactly the window you have.

Why This Order Works

Three reasons, all backed by real research, none of them obvious.

1. Recall beats rereading — by a lot.

This is the testing effect, one of the most replicated findings in learning research. Pulling an answer out of your own head strengthens memory far more than reading the answer again.

Rereading feels productive because the material looks familiar. Familiarity is not knowledge. You can recognize a page you couldn’t reproduce a single sentence of.

That’s why Recall is a mandatory step, not a nice-to-have. The Check Yourself questions are not a quiz at the end of studying — they ARE the studying.

2. Building is encoding.

When you type the code, break it, and fix it, your brain files the concept under “things I did,” not “things I saw.”

A concept you’ve built survives. A concept you’ve watched evaporates. That’s why Build gets the biggest block of the loop, every single day.

3. Priming closes the gap between sessions.

You forget between days. Everyone does — including the version of you that felt so clear about it yesterday.

Five minutes of “where was I, what’s today’s goal” reconnects yesterday’s work to today’s. Each session compounds instead of starting cold. This matters double for you, because your sessions are squeezed between two jobs and your brain has been elsewhere all day.

A Worked Example

What one real session looks like, so there’s no ambiguity:

That missed question? It just became tomorrow’s free win. Which brings us to the most important schedule on this page.

The Re-Test Schedule

Here’s the part almost nobody does, and it’s the highest-leverage 10 minutes in the whole system.

Memory decays on a curve. Each time you successfully recall something just as it’s about to fade, the curve flattens — the memory lasts longer before the next fade. That’s spaced repetition, and it’s the single most reliable trick in the learning-science toolbox.

flowchart LR
    A[Finish a module] --> B[Retest day 1]
    B --> C[Retest day 3]
    C --> D[Retest day 7]
    D --> E[Retest day 21]
    E --> F[Yours for good]

The rule: when you finish a module, redo its Check Yourself questions on day 1, day 3, day 7, and day 21 after finishing it.

How to actually make this happen — because “I’ll remember to review” is a lie you tell yourself:

1. The day you finish a module, open the Tracker.
2. Add four future targets: “Re-test [module] CY” on day 1, day 3, day 7, and day 21.
3. On those days, the re-test is a 10-minute target like any other. Answer from memory, check it off.

That’s the entire mechanism. Spaced repetition without flashcard overhead — the questions are already written, you just answer them again without looking.

Scoring a re-test:

• Answered everything cleanly → move on, see you at the next interval.
• Stumbled on a question → reread only that part of the module, then add one extra re-test 3 days out.
• Blanked on most of it → the module didn’t stick. Redo its Build This. Building it again will fix what rereading won’t.

Want the power tool? Anki is a free flashcard app that automates exactly this scheduling per question. If the tracker system works for you, you don’t need it. If you find yourself wanting per-question scheduling — make Anki cards from the Check Yourself questions you keep missing, nothing more.

The Feynman Technique

Once a week, pick a concept you think you know. Explain it out loud — to an empty chair, or record a voice note on your phone. No notes. No peeking.

When you stumble, slow down, or reach for “…it just kind of works like…” — that exact spot is the gap. You’ve found precisely what you don’t understand, with surgical accuracy and zero tooling.

Then:

1. Reread only the part you stumbled on.
2. Explain again, from the top.
3. Repeat until the explanation runs clean.

This works because explaining forces you to retrieve and connect — you can’t hide behind recognition the way you can while reading. It’s also direct interview training: an interview is just the Feynman technique with a stranger and stakes.

If the empty chair feels ridiculous, good. Feeling slightly ridiculous and doing it anyway is most of what separates people who can explain their stack from people who can only nod at it.

Interleave, Don’t Block

Mixing related-but-different practice beats grinding one topic in a long block. This is interleaving, and the research is consistent: it builds stronger, more flexible recall — even though it feels harder and slower while you’re doing it.

In practice: a session of Java module work plus one DSA problem beats a session of pure Java, because your brain has to keep asking “which approach applies here?” instead of running on autopilot. The daily schedule already interleaves for you. Don’t “optimize” it into single-topic days — the slight friction of switching is a feature, not a bug.

What NOT To Do

These four feel like studying. They aren’t. They’re the four horsemen of wasted evenings.

The common thread: all four avoid the discomfort of retrieval. Effective studying feels slightly hard — like the answer is just out of reach and you have to stretch for it. If a study session felt smooth and pleasant from start to finish, you probably consumed content. You didn’t learn.

One honest test: at the end of any session, close everything and write down what you can recall. If the page stays empty, the session didn’t happen — no matter how many hours it took.

The Honest Minimum

Some days you’ll have one hour and half a brain. Two jobs, bad sleep, life. This system is built for that reality, not for the fantasy version of your week.

On those days the loop shrinks. It doesn’t break.

The 1-hour bad day:

Notice what survived the cut: Build and Recall — the two steps that actually create memory. Notice what got dropped: new Learn content. On a bad day you don’t add. You reinforce.

A 1-hour day with recall in it counts. It keeps the streak, it flattens the forgetting curve, and it’s worth more than a 4-hour binge of passive video.

Never zero. That’s the only rule with no exceptions.