How I Learned to Learn

In school I could learn a hard video game in a weekend, but I was failing math. My grades sat around 60%, and I was teased for not knowing things that other kids knew. I thought I was bad at school.

I was wrong about the reason. I could already practice one thing for hours: I spent whole days on aiming drills in CS:GO and on Dota 2 strategy. The habit was there. It was pointed at the wrong target.

This post is what I learned after I pointed it at school and, later, at software. You will get:

Why the basics come first, and why skipping them makes everything after harder.
3 study methods with good evidence: testing yourself, spacing your reviews, and chunking.
A way to plan your reviews, with a chart you can play with.

Point the practice at the right target

In high school I found the Pomodoro technique: work for 25 minutes, take a 5-minute break, and repeat. It did not make me smarter. It made starting easy, because 25 minutes is short, and it kept me focused until the break.

Within a few months my grades went from about 60% to above 85%. That is my own experience, not proof that Pomodoro works for everyone. The timer was a tool. The real change was that I treated studying the way I treated a game: show up every day and practice the part you are bad at.

Learn the prerequisites first

When I started teaching myself, I often hit material I could not follow at all. The cause was almost always the same: I was missing something it depended on.

Researchers call this the effect of prior knowledge: new ideas are easier to learn when they connect to ideas you already hold. When there is nothing to connect to, you can read the same page 5 times and keep nothing.

It is like fighting a late-game boss at level 1. You might win after 100 tries, but going back to level up first is faster.

So learn what a topic depends on before the topic itself:

Basic algebra before calculus. Calculus problems are full of algebra steps.
Loops, functions and how computer memory works before a framework. A framework is those basics, arranged for you.

It feels slow while you do it. The payoff comes later: each new topic takes less effort, because it builds on what you already know.

What this looked like for me

My path into software followed the same rule:

Basics first. I spent about a year on CS50, Harvard's free intro to computer science, learning what a loop is and how computer memory works.
Then real projects. An internship and Bangkit Academy, a tech training program in Indonesia backed by Google, showed me how code runs for real users. The basics made that easier to follow.
Then new areas. I started as a frontend engineer and moved into backend and DevOps. New languages and tools came faster each time, because most of what they rely on I had already learned.

Test yourself instead of re-reading

Most people study by reading their notes again. It feels productive, because the text looks familiar. But familiar is not the same as remembered. Recognizing a page is much easier than recalling it with the book closed, and an exam asks you to recall.

Retrieval practice means pulling information out of your memory instead of putting it in again. The act of recalling makes the memory stronger. In a well-known study, Roediger and Karpicke (2006) had students read a short text. Some read it again. Others wrote down what they remembered. After 5 minutes the re-readers did better. After 1 week the students who had tested themselves remembered more. A large review of study methods, Dunlosky and others (2013), named practice testing and spaced practice as the 2 most useful of the 10 methods they reviewed, and re-reading as one of the least.

How to do it:

Close the book and write down what you remember. Then open it and check what you missed. That check is your feedback: it shows you what to study next.
Use flashcards, with a question on one side and the answer on the other. Say the answer before you flip.
Explain it out loud, to a friend or to an empty room. The parts where you stop are the parts you do not know yet.

Space your reviews

In 1885 the German psychologist Hermann Ebbinghaus memorized lists of nonsense syllables and measured how quickly he could relearn them hours and days later. The result is called the forgetting curve. Memory of new material drops fast at first and then levels off. Each review made at the right time makes the next drop slower.

This leads to spaced practice: spread your reviews out over time instead of doing them all at once. The finding that spaced reviews beat the same amount of study packed together is called the spacing effect, and it is one of the most repeated results in learning research.

Try it below. Pick a schedule, or click days to build your own, and compare 4 reviews on 4 days in a row with 4 reviews spread over 2 weeks. The main number is your average recall over the whole month, because a review the day before you are measured says little about what you kept.

Forgetting curve

Schedule

Or click the days you review

Average recall

88%

Recall at day 30

78%

Reviews

▬ Your schedule▬ No review● Review

Illustrative model, not measured data. Recall falls as exp(-t / S), where t is days since the last review and S is the memory's stability: the larger it is, the slower recall falls. Each review grows S, more when you had forgotten more, up to a cap. Average recall covers days 0 to 30, so reviews packed into the last few days cannot fake it.

The chart is a simple model with made-up rates, so read its shape, not its numbers. Real forgetting depends on the material, on you, and on how well you learned it the first time. The shape still holds: cramming gives you a high score this week and little a month later, while spaced reviews keep more with the same number of reviews.

A simple schedule to start with: review 1 day after you learn something, then after 3 days, 1 week and 2 weeks. Treat it as a starting point, not a rule. If a review feels easy, wait longer next time. If you forgot most of it, review sooner. Flashcard apps such as Anki do this scheduling for you.

Spacing and self-testing work best together. Each review should be a small test, not a re-read.

Chunk it, and step away when stuck

Your working memory, the part of your mind that holds what you are thinking about right now, can only hold a few things at once. Chunking is how you get around that: you group small pieces into one unit that you can recall as a whole.

Code is a good example. The first time you see this loop, it is a lot of separate pieces: a variable, a start value, a condition, an increment, an index, an addition.

6 pieces, or one chunkJavaScript

let total = 0;for (let i = 0; i < prices.length; i++) {  total += prices[i];}

After you have written it 50 times, you see one thing: "add up the array". That frees your working memory for the actual problem. You build chunks the same way you build any skill: understand the idea first, then practice it until you do not have to think about the steps.

The other half is what to do when you are stuck. Barbara Oakley, who teaches the popular Learning How to Learn course on Coursera with Terrence Sejnowski, describes 2 modes of thinking. Focused mode is when you concentrate hard on one problem. Diffuse mode is the relaxed state when you walk, shower or rest, and your mind makes looser connections.

Treat this as a teaching model, not settled brain science. The practical advice is still sound: when you have been stuck for a long time, take a real break. Go for a walk, sleep on it, then come back. The answer often shows up after you stop pushing.

Time plus a method

I used to say there are no geniuses, only time. The honest version is more careful. Time alone does not make you good: you can practice something badly for years. What helps is time spent with a good method, plus regular feedback that tells you what you got wrong.

With those 3 things, steady progress is likely. It is not guaranteed, and people move at different speeds. But where you start matters much less than I believed when I was the kid with 60% grades.

What to keep

Learn the prerequisite first. If you cannot follow something, find what it depends on.
Test yourself instead of re-reading. Close the book, recall, then check what you got wrong.
Spread reviews over growing gaps. Start with 1 day, 3 days, 1 week, 2 weeks.
When stuck, take a break and come back. A real break, not a different screen.