Revision: the deck and the contest gauge
The two-layer revision system, the day 2/7/30 deck, and how the weekly contest tells you when solving has gone passive.
Solving a problem once is not revision. This page covers the two layers that keep solved problems solvable, and the signal that tells you a problem has not stuck.
Mocks are a separate ladder on the mocks page.
The two layers
Layer 1, the sheet itself. Log in on takeuforward. The sheet's built-in module contests (about 2 hours) are the exit gate for every module. Redo any contest you failed 3 days later.
Layer 2, your own deck. Every solved problem enters a revision deck (Obsidian, Anki or a plain spreadsheet). Revisit it on day 2, day 7 and day 30.
On every revisit, re-solve blind in 20 minutes with no notes. If you fail, the problem goes back to the queue at day plus 2.
Keep the log line short: module • time • what broke. Those tags become your revision syllabus in mock season.
The contest gauge
The LeetCode Weekly Contest is a real time audit of the same skill the deck tracks. It costs one hour and gives you a number.
If your rating stalls for 3 weeks in a row while your sheet count keeps climbing, your solving has gone passive. You are reading editorials too early. Cut editorials by half and rebuild the next three problems yourself before opening one.
The rating is a CV number and a diagnostic, not an ego number. A flat week is data, not a verdict.
Revision dos and don'ts
- Do the module contest before moving on. It is the sheet's own gate, and it makes "I did A2Z" a claim you can defend.
- Tag every log entry. Untagged problems cannot be revised, only re-solved by accident.
- Close the Pro-tagged problems even when they are demoralising. They preview the hard follow-ups on site.
- Keep the Weekly Contest weekly, all the way to the end.