A Study Routine That Actually Sticks

Motivation gets you through the first week. A routine built around recall, small projects and honest review gets you through the first year.

Short and regular beats long and rare

Programming is a skill, and skills fade between sessions. A modest daily session keeps yesterday's material warm, so you spend less time relearning. Pick a length you can keep on your worst day, not your best one. The exact number of minutes matters far less than whether you show up again tomorrow.

Test yourself instead of rereading

Rereading notes feels productive because the material looks familiar. Familiar is not the same as usable. The testing effect is the finding that long-term memory improves when some of the learning time is spent retrieving the information rather than reviewing it again. For a coder, retrieval means closing the tutorial and writing the thing from a blank file.

Space your reviews

Spaced repetition is a technique in which newly introduced and more difficult items are reviewed more often, while older and easier ones are shown less frequently. Flashcards suit syntax and vocabulary: what a method is called, what an error message means. They do not replace writing programs, but they stop you looking up the same small thing fifty times.

A weekly shape that works

• Most days: one new idea from your course, followed immediately by a tiny exercise of your own invention.
• One day: no new material. Rebuild something from earlier in the week without looking.
• One day: project time. Add one feature to a small program you care about.
• One day off. Rest is part of the routine, not a failure of it.

Escape the tutorial loop

Following along with a video produces working code and very little learning, because the instructor made every decision. After each tutorial, change the result in three ways the instructor did not show: a new input, a new rule, a different output format. The moment you get stuck is the moment the learning starts.

Keep notes you will reread

Write notes in your own words, with your own example, and date them. Good notes answer three questions: what is this for, what does the smallest working example look like, and what mistake did I make the first time? The third one is the most valuable and the one tutorials never contain.

Measure the right thing

Hours watched and streaks kept are easy to count and say little. Better measures: how many small programs you finished this month, and how many of last month's exercises you can still write unaided. If the second number is falling, slow down and review before adding more.

Plan for the bad week

Illness, exams and work will interrupt you. Decide in advance what the minimum looks like, for example one flashcard session and nothing else, so that a bad week is a pause and not the end of the habit.

// revised 2026-11-12 by Ilya Kessler