Once the last lesson of a track is ticked and the progress ring has moved, it is tempting to treat the material as filed away. It is not filed yet. The weeks right after you finish are when most of it fades, and they are also when a small, regular effort keeps it.
That effort is about ten minutes of reviews a day, one small project, and a few habits that make you recall the ideas instead of rereading them. The four-week plan at the end puts them in order.
Why the reviews keep coming
Memory fades fast at first and then more slowly. The shape has a name, the forgetting curve: a steep drop in the days after you learn something, then a long tail that flattens out. Each time you pull an idea back out of memory, the curve starts again from the top and falls more gently, so the next drop takes longer.
The school's review schedule is built on that shape. Every quiz question you have answered is a card in a spaced repetition system: it comes back at growing intervals, each timed to arrive before you are likely to forget it. The school uses the FSRS algorithm with its default target, so a card falls due when the algorithm predicts your chance of recalling it has dropped to nine in ten. A right answer pushes the next review further out. A wrong one brings it back soon.
In practice, if you answer a question right each time it falls due, it returns after a few minutes, then after about two days, then about eleven, then about a month and a half. That is why finishing a track does not end its reviews. The questions from your last few lessons are still on short intervals. For the next month or so they will keep turning up in the daily mix, because that is exactly the period in which you would otherwise lose them. Read those reviews as the plan working, not as the school failing to notice you are done.
Build one small thing within a week
A quiz question checks that you can recall an idea when someone asks about it. A project checks that you can use it when nobody has told you which idea the moment needs. That second skill is the one you came for, and it only grows by doing.
Start the project in the first few days after the last lesson, while the material is fresh enough that you can get unstuck without rereading everything. Have it working by day seven, and keep it small enough to finish in two or three evenings. A rule that works: one page, three ideas from what you just learned, no new libraries.
- After lessons on forms, build one sign-up form with validation and a list of errors at the top.
- After lessons on stores, build a shopping list whose items live in a store and survive a page refresh.
- After lessons on testing, take a component you already wrote and give it five tests.
Write the code without the lesson open. When you get stuck, try for ten minutes first, then look up the one thing you need and close the tab again. Every time you get stuck and recover, you have done a review no quiz can give you.
Explain it to someone else
Explaining forces you to put ideas in order and to notice the gaps between them. You find out quickly which parts you can only nod along to.
You do not need a student. Write a short note, one page at most, as if a friend who knows a little Vue had asked what the topic is for and when to use it. Write it from memory first. Then open the lessons, check what you got wrong or left out, and fix the note. The checking is where the value is; the first draft just shows you where to look.
If you would rather talk than write, walk a colleague through your project's code, or say it out loud to an empty room. Explain why each piece is there, not what each line does. When you hear yourself say "and then it just works", that is the part to look up.
Mix topics instead of practising in blocks
Most courses, this school included, teach one idea per lesson, in order. That is the right way to meet something for the first time. It is the wrong way to keep practising it.
Practising in blocks means doing all the questions about one idea, then all the questions about the next. It feels smooth, because you know which idea each question is about before you read it. Interleaving means mixing the questions up, so any one of them could be about several topics. It feels slower and harder.
Yet experiments, many of them in maths classes, have found that interleaved practice does better on a later test, because it trains the step that blocked practice skips: working out which idea a problem needs before you apply it. Real code never arrives labelled with the lesson it belongs to.
The practice page already leans this way. Today's mix starts with the cards that are due and draws its five questions from the lessons you have touched, never more than two from the same lesson. The topic drills go further: each takes eight questions from several lessons that share an area, such as state management or routing, often from more than one track, again with at most two per lesson.
After a track, run a drill that covers it alongside something you learned earlier, rather than retaking its quizzes one by one.
Go back to what you missed, on purpose
A missed question is the most useful thing a quiz gives you. It points at one specific misunderstanding, and the explanation shown after you answer states the rule you got wrong.
Do not leave misses to the schedule alone. From the third week, once the project and the note are done, open Review weak spots on the practice page once a week. It collects questions from finished lessons where most of your recent answers were wrong, and it puts the questions you missed first.
Before you answer each one, say what you think the trap is. Afterwards, if the wrong option still looks reasonable, write one sentence on why it is wrong. That sentence teaches you more than another pass through the lesson.
When to start the next topic
Start it in the second week, once the project works. Do not wait until you feel you have mastered the last one. That feeling arrives late or not at all, and waiting for it costs you momentum. The reviews keep the old material alive while you learn the new, and a new topic that builds on the old one is a review in itself.
Two signals mean you should slow down instead. If the practice page shows lessons from the finished track that need review, clear those first. If your project stalled because one basic piece would not work, go back to the lesson that covers that piece before you move on. Otherwise, move.
A four-week plan
Ten minutes a day for reviews, plus a few evenings for the project. Shift the days to fit your week, but keep the order.
Week one:
- Do today's mix every day, before anything new.
- Build the small project, and have it working by day seven.
Week two:
- Keep the daily mix.
- Write the one-page note from memory, then check it against the lessons.
- Start the first lesson of the next topic.
Week three:
- Keep the daily mix and keep going with the new topic.
- Open Review weak spots, and write a sentence for each question you still miss.
- Run one topic drill that covers the finished material.
Week four:
- Keep the daily mix.
- Open Review weak spots again, then add one feature to the project that uses the idea you missed most often.
- Retake the quiz of the finished track's first lesson without rereading it. If you pass, you kept it. If you do not, the missed questions go back into the schedule, which is where they belong.
After that, the reviews from the finished track thin out on their own as each card's interval grows. Keep the daily mix as a habit and let the schedule decide when the old topic needs you again.