Why You Forget Everything You Learn (And How Spaced Repetition Fixes It)

I spent a full Saturday once grinding through Kubernetes networking. Pod-to-pod communication, Services, Ingress controllers — the whole thing. Drew diagrams on my whiteboard, felt like an expert by dinner.

Monday standup. Someone asks the difference between ClusterIP and NodePort. Total blank. Four hours of study, evaporated in a week.

I used to think that meant something was wrong with me. It doesn’t. It means my brain was doing exactly what brains do.

The Forgetting Curve Is Worse Than You Think

In 1885, Hermann Ebbinghaus ran memory experiments on himself. Nonsense syllables, timed recalls, obsessive logging. The man was basically running QA on the human brain.

His results are rough. Within twenty minutes, about 40% is gone. After an hour, more than half. A day later you’re down to maybe 30%. A week? Scraps.

That’s not a gradual fade. That’s garbage collection on an aggressive cron job.

Here’s the thing, though. Ebbinghaus also discovered that each well-timed review resets the curve — and flattens it. First review, you forget slower. Second, slower still. After several reviews at the right intervals, information sticks for months. Sometimes years.

Your brain isn’t broken. It’s optimizing for recency by default, and you can override that.

Spaced Repetition Isn’t Just “Review More”

Most people hear “spaced repetition” and think it means reviewing stuff regularly. Close, but it misses the point. The key word is spaced — you review right before you’d forget, not on some fixed daily schedule.

The intervals stretch over time. Learn something today, review tomorrow. Remember it? Three days. Still got it? A week. Then two weeks, a month, three months. Fail at any point and the interval shrinks back down. If you want exact intervals mapped to a 12-week certification plan, grab our spaced repetition study schedule template.

Piotr Wozniak formalized this into the SM-2 algorithm in 1987 — it’s what powers most spaced repetition tools today. You spend more time on what’s hard, less on what you’ve nailed.

What makes it work at a deeper level is what UCLA researcher Robert Bjork calls “desirable difficulty.” The harder your brain works to retrieve something, the stronger that memory gets. Too easy and nothing consolidates. Too late and there’s nothing left to retrieve. Spaced repetition keeps you in that narrow productive zone.

Honestly? I resisted this for a long time because it sounded too mechanical. Too boring. But boring and effective aren’t mutually exclusive — they’re often the same thing.

Why Most People Fail (It’s the Cards)

A lot of developers try spaced repetition, last two weeks, and quit. The system didn’t fail them. Their cards did.

Here’s a terrible card:

Q: What is Kubernetes? A: An open-source container orchestration platform that automates deployment, scaling, and management of containerized applications.

That tests your ability to recite a definition. You’ll “know” it on the card and freeze when someone asks a real question.

Compare that to this:

Q: Three replicas of a web app running in pods. One crashes. What happens next? A: The ReplicaSet controller sees desired state (3) vs actual (2) and schedules a new pod.

Or this:

Q: Deployment vs StatefulSet — when do you pick which? A: Deployments for stateless (interchangeable pods). StatefulSets for stateful (persistent identity + storage). Database = StatefulSet. Web server = Deployment.

See the difference? Good cards test application and distinction. They make you think, not parrot.

Here’s a mildly controversial take: don’t use shared Anki decks. Making the card yourself is half the learning. Downloading someone else’s deck feels efficient but skips the hardest part — deciding what matters and how to frame it.

Anki is still the best tool. Free on desktop and Android, open-source, handles all the scheduling. But the tool matters less than what you put into it.

Active Recall: The Part People Skip

Spaced repetition handles when you review. Active recall handles how. And most people get the how completely wrong.

Re-reading notes feels productive. It isn’t. A 2011 study in Science found retrieval practice beat re-reading and concept mapping by 50% on one-week retention tests. Not 5%. Fifty.

Three approaches that have actually worked for me:

Blank page method. Before you open your notes, dump everything you remember onto a blank page. Then compare. The gaps you find? Those are your next flashcards.

Immediate questions. Learn something, then immediately write three questions about it and answer them without looking. Takes two minutes. The payoff is disproportionate.

Teach-back. Explain the concept out loud as if you’re onboarding a junior dev. Where you stumble is where you’re weak. No way to fake it without a script — I’ve tried.

How to Not Sabotage Yourself

I’ve made every one of these mistakes. Some of them more than once.

Too many cards too fast. Start with five to ten new cards a day. Every card you add today is a review you owe tomorrow, next week, and next month. Twenty a day sounds fine until week three, when daily reviews eat 45 minutes and you bail.

Cards that do too much. If your question contains “and,” split it. One card, one atomic concept.

Prioritizing new material over reviews. This kills the whole system. Reviews come first, always. New cards without reviews is just future forgetting with extra steps.

Look, spaced repetition isn’t glamorous. It’s fifteen minutes a day doing something your brain resists — pulling up information that feels just out of reach. But after a month you’ll have a few hundred cards in rotation with 85-95% retention. Without a system, you’d keep maybe 10-20%.

That Kubernetes knowledge I lost after one Saturday? I rebuilt it with spaced repetition in the same total study time. Six months later, I still had it. That’s the whole pitch.

FAQ

How long does spaced repetition actually take per day?

About 15-20 minutes once you’ve got a decent deck going. Some days less. The catch is you need to show up daily — miss a few days and your review pile stacks up fast. I keep mine right after morning coffee, before I can talk myself out of it.

Can I use spaced repetition for things besides technical knowledge?

Absolutely. I’ve used it for API details, system design patterns, even language learning. Anything with discrete facts or concepts works well. Less useful for procedural skills — you won’t learn guitar with flashcards. But for factual and conceptual knowledge, it’s hard to beat.

Is Anki the only option?

No, but it’s the one I keep coming back to. RemNote, Mochi, and a few others exist. Some people use Notion with a manual schedule, which… works in theory but adds friction that usually kills the habit. The best tool is the one you’ll actually open every day.

What if I already forgot everything — is it too late to start?

Not at all. You relearn faster than you learned the first time — there’s solid research on that (the savings effect, if you want to look it up). Start with whatever you’re working on now and build from there. Don’t try to backfill six months of topics on day one.

Want to build a learning system that actually sticks? Check out SkillRealm Learn →