You read a section on recursion, close the textbook, and feel that the explanation makes sense. The next day, you try to write a recursive function and cannot decide what the base case should be. You read the section again. It feels clearer—but when you attempt a new problem, you get stuck once more.
This is a common experience in technical subjects. Recognizing an explanation while it is in front of you is not the same as being able to recall, explain or apply the idea on your own.
Rereading is not useless. It can help you understand a confusing passage, notice a detail you missed or correct a misconception. The problem is relying on rereading as the main evidence that learning has happened.
For difficult material, you need to move beyond recognition and practise retrieving and using what you have learned.
Why rereading can feel more effective than it is
Familiarity can be mistaken for understanding
When you see the same explanation repeatedly, the words and examples become familiar. That familiarity can make the material feel easier to understand. But while the book is open, it is supplying many of the cues you will not have during an exam, interview or problem-solving session.
Try closing the page and explaining the concept without looking. If you cannot describe the main idea, identify the conditions under which it applies or work through a basic example, you have discovered something useful: the next step is not simply another passive pass over the text.
Technical learning requires more than recognizing definitions
In technical subjects, understanding often involves several connected abilities:
- explaining a concept in your own words;
- recognizing when a method applies;
- following a process step by step;
- solving a problem with changed inputs;
- interpreting a diagram, result or error;
- knowing why an approach works and where it fails.
Rereading may help with the first encounter, but it does not automatically provide practice in all these abilities. A student can recognize the definition of a stack and still struggle to trace a sequence of push and pop operations.
Rereading does not always reveal what you cannot do
While reading, the explanation is visible. It can be difficult to distinguish between “I understand this” and “I can follow this when someone else explains it.”
A small self-test gives you better information. Attempting to recall the main steps or solve a problem without looking can reveal gaps that another quick read might leave hidden.
What research says about rereading
A widely cited review by John Dunlosky and colleagues evaluated ten learning techniques, including rereading, practice testing and distributed practice. The authors rated practice testing and distributed practice as high-utility techniques across a range of learning conditions, while rereading received a low-utility rating because its benefits were less consistent and often weaker than those of more effective approaches.
You can read the review through the Association for Psychological Science or its PubMed record.
That conclusion needs a little care. It does not mean you should never reread. Rereading can be useful when you need to clarify an explanation, and rereading after a delay may work better than immediately repeating the same reading. The practical lesson is that rereading alone is a weak way to judge whether you can remember and use material.
For technical subjects, combine reading with activities that make you retrieve, explain and apply the concept.
Four ways to study technical material more actively
1. Close the material and retrieve the idea
After reading a small section, close the book or switch away from the notes. Write down or say:
- What problem is this concept meant to solve?
- What are its main steps or properties?
- Why does it work?
- What is one example?
- What is one limitation or common mistake?
Then reopen the material and compare your answer. Correct what is missing or wrong. The attempt matters because it shows you what you can produce without the explanation in front of you.
This is often called retrieval practice or practice testing. It does not have to be a formal exam. A few questions, a blank-page explanation or a short set of flashcards can work as a check.
The U.S. Institute of Education Sciences’ practice guide recommends using quizzing to re-expose learners to key content and describes active retrieval as a way to support longer-lasting memory. See Organizing Instruction and Study to Improve Student Learning.
2. Work through a problem, then change it
Technical knowledge becomes useful when you can apply it. After studying a worked example, cover the solution and try to reproduce the reasoning. Then solve a similar problem with different values or conditions.
For example, after reading a binary-search explanation:
- Explain why the search interval shrinks at each step.
- Trace the algorithm on a short sorted array without looking.
- Try an array where the target is absent.
- Explain what would go wrong if the interval update were incorrect.
Do not jump immediately to the hardest problem. Begin with a manageable example, check your reasoning and increase the difficulty gradually.
If you are completely stuck, inspect the relevant step in the worked example, understand why it is needed, then close the solution and continue on your own. The objective is not to avoid explanations; it is to practise producing the solution rather than only recognizing it.
3. Explain the concept in your own words
After a section, pretend you are explaining the idea to a classmate who has not studied it. Use simple language, but do not remove the important technical details.
For a concept such as a database index, you might explain what it helps the database do, what information it organizes and what trade-off it introduces. If you cannot explain a step, mark the exact question and return to the source.
Self-explanation is especially useful when a procedure has several steps or when two concepts appear similar. Ask not only “What happens?” but “Why does this step follow?” and “What would change if this condition were different?”
Your explanation does not need to be polished prose. A short note, annotated example or diagram may be enough.
4. Review across separate sessions
Studying a topic repeatedly in one sitting can create a strong sense of familiarity. Instead, return to it after some time has passed. Start each review by attempting to recall the main ideas or solve a problem, then check your notes.
A simple pattern might be:
- First session: learn the concept and attempt an example.
- Later session: explain the idea from memory and solve another problem.
- Following review: identify what you still forget or misunderstand, then practise that part.
The best interval depends on the topic, your current understanding and when you need to use the knowledge. You do not need a perfect universal schedule. The important change is to spread meaningful retrieval and practice over time rather than treating one long rereading session as completion.
A practical study loop for a difficult topic
Use this loop for one small concept at a time:
Read → Close → Recall → Apply → Check → Revisit
- Read: Study a short explanation or worked example. Identify the central idea.
- Close: Put the source out of view.
- Recall: Explain the idea or list the key steps from memory.
- Apply: Solve a small problem or create an example.
- Check: Compare your response with the source and correct errors.
- Revisit: Return in a later session and test yourself again.
For a complex subject, repeat the loop across the important subtopics. Keep track of questions you could not answer, not just pages you have read.
Use diagrams when the relationships are hard to follow
Some technical topics involve a process, hierarchy or set of dependencies that is difficult to hold in mind. A diagram can make those relationships visible.
For example, draw the steps in a process, trace the state of an algorithm, or map how two concepts depend on each other. Then explain the diagram without looking at the original source. If the arrows or labels do not make sense to you, that is a useful signal to revisit the concept.
The Institute of Education Sciences practice guide also recommends combining graphics with verbal descriptions and connecting abstract representations to concrete examples. See the guide’s recommendations.
A diagram is not automatically effective just because it looks clear. You should be able to explain what it represents and why the relationships are correct.
What should you do when you get an answer wrong?
Getting an answer wrong during practice is not a reason to abandon the method. It is information about what needs work.
When you make a mistake:
- Identify the exact step or idea that failed.
- Return to the relevant explanation, not necessarily the entire chapter.
- Work out why the correct approach works.
- Close the source and try again.
- Revisit the same skill later with a slightly different question.
Keep a small list of recurring errors. For example: “I confuse a process with a thread,” “I forget why the loop terminates,” or “I can state the formula but do not know when to use it.” These are more actionable than a general note saying “I don’t understand this chapter.”
Where notes fit into this approach
Notes are still useful. Their purpose is to help you understand, explain and revisit ideas—not to become a substitute for practising them.
For each difficult topic, consider keeping:
- a concise explanation in your own words;
- one worked example with reasoning;
- a diagram if it clarifies a relationship;
- a few questions to answer without looking;
- a short record of errors or uncertainties.
When you return to the topic, start with the questions or an attempt to explain it. Use the notes to check and repair your understanding afterwards.
The Study OS provides a structured workspace for subjects, topics, notes and diagrams. That can help keep these learning materials connected to the topic they support. You can explore The Study OS features. Regardless of the tool you use, the learning principle stays the same: organize the material so that it supports active practice rather than replacing it.
A 25-minute experiment
Choose one difficult topic and try this once:
- 8 minutes: Read a small section and inspect one worked example.
- 5 minutes: Close the source and write down the main idea and steps.
- 8 minutes: Solve one problem or explain one example without looking.
- 4 minutes: Check your work, correct errors and write one question to revisit later.
This is not a scientifically fixed schedule. It is simply a manageable way to replace part of a passive study session with retrieval and application.
The takeaway
Rereading can help you clarify material, but familiarity is not proof that you can recall or apply it. Research reviews find stronger general support for practice testing and distributed practice than for rereading alone.
For difficult technical subjects, keep reading—but give yourself regular opportunities to retrieve ideas, explain why they work, solve problems and revisit them after a delay.
Do not measure a study session only by how much you have read. Check what you can explain and do when the explanation is no longer in front of you.