How to study effectively: a cheat sheet for video courses
Effective study of video courses rests on four habits: before a lesson, write a question; during it, pause and retell in your own words; after it, practice at once and test yourself from memory; once a week, review older material on a spaced schedule. The main enemy is passive watching, which gives a feeling of understanding without real knowledge.
The main principle
You remember what you actively processed: recalled, explained, applied. Passive watching creates an illusion of knowledge: you recognize the material on screen but cannot reproduce it yourself. Everything in this cheat sheet is a way to turn watching into doing.
Theory → Practice → Check → SkillBefore the lesson
| Action | Why | Time |
|---|---|---|
| Ask yourself: what do I want to learn from this lesson? | The video answers your question instead of playing in the background | 1 min |
| Recall the previous lesson without notes | Connects to the new material and is free review | 2 to 3 min |
| Put the phone away, close messengers | Multitasking breaks learning | 1 min |
| Open a code editor next to the video | Try the code right away, not later | 1 min |
| Set a 25-minute timer | Focus on one stretch of work | — |
During the video
- Pause every 3 to 5 minutes, or after each meaningful block.
- At each pause, write three things: the main idea in your own words, an example from the lesson, your own question.
- Explain the idea aloud, as if telling a colleague.
- Try to guess what the lecturer will write next, before they do.
- Type the code in your editor rather than only watching it.
- Did not understand a fragment? Rewind right away; do not let gaps pile up.
A note template for pauses
Block: list comprehensions
Idea: [x*2 for x in nums] builds a new list from an old one in one line
Example: [w.lower() for w in words if w]
Question: when is a comprehension worse than a plain loop?Right after the lesson
| Action | How to check it is done |
|---|---|
| Close the video and write the code from memory | The code runs and the hints you needed are marked |
| Create your own example on the topic | The example differs from the lesson's |
| Take the quiz or answer the lesson's questions | Answers given without looking |
| Explain the topic in simple words (Feynman technique) | An explanation with no terms you cannot unpack |
| Schedule reviews in the calendar | Events exist for 1, 3 and 7 days later |
Practice by topic type
| Lesson topic | What to do right away |
|---|---|
| Algorithm | Implement it from scratch, then change the condition |
| OOP | Create your own class from scratch for your own domain |
| SQL | Run a query against a real or practice database |
| Tool (Git, Docker, Linux) | Repeat the commands in a terminal on your own project |
| Theory without code | Write an example from your own experience and a question |
Once a week
- Reread your progress log: what was done, what keeps appearing under "hard".
- Solve 2 to 3 tasks on topics from past weeks without hints.
- Group topics by tags (
#python_basics,#git,#sql) and review related ones together. - Remove from the review schedule what comes back easily; add time for what is hard.
- Plan the next week: specific lessons and specific tasks.
Spaced repetition schedule
| When | What to do |
|---|---|
| Day 1 | Reproduce the code and the main ideas from memory |
| Day 3 | Practice with a modified version of the code |
| Week 1 | Solve a new task on the same topic |
| 2 to 3 weeks | Quick check: explain it and write it from memory |
| 1 to 2 months | Apply it in a project |
Recalled it easily? Lengthen the next interval. Struggled? Shorten it.
Traps and how to avoid them
| Trap | Sign | What to do |
|---|---|---|
| Illusion of knowledge | "I saw it, so I can do it" | Test yourself right after watching, without hints |
| Skipping practice | Many lessons watched, tasks not solved | Do not start a new lesson before practicing the previous one |
| Multitasking | The lesson plays in the background and nothing sticks | One task; phone out of the room |
| Cramming back to back | A week later nothing is remembered | Review with gaps, on a schedule |
| Rereading notes | Everything feels familiar | Recall first, then check |
| Piling up unclear material | Each lesson is harder than the last | Close the gaps before a new topic |
Checklist for each study session
- A question for the lesson is written.
- Distractions are removed.
- Pauses and retelling in your own words.
- Code written from memory.
- Quiz or self-test done.
- Reviews scheduled.
- Three lines written in the progress log.
Summary
Effective study: a question before the lesson, pauses and retelling during it, practice and a memory check after it, and a weekly review on a spaced schedule. Keep this cheat sheet handy and follow it for the first few weeks, until the actions become habits. Each technique is covered in detail in the course "How to learn effectively from video courses".
FAQ
Do I need to take full notes for every video lesson?
Full notes are not needed. At each pause, write the main idea in your own words, an example and a question. That is enough for review.
Can I watch lessons at double speed?
Yes, if you can still understand them and pause to retell. If you cannot reproduce the material after fast watching, go back to normal speed.
What if I cannot explain a topic in my own words?
That is a sign you have not understood it fully. Rewatch the relevant fragment, go through the example in code and try to explain it again.
How long should one study session last?
A convenient format is 25 minutes of work and 5 minutes to review the result. One to three such sessions in an evening is enough.
This topic is covered in depth with practice in the course “How to Study Effectively with Video Courses”.
Go to course