The Contest Clock
Self-timed sprint framework: five sprint lengths, the midpoint switch rule, the two-pass read, and what to do when the clock wins.
The Contest Clock
Speed in contest is not typing speed. It is decision speed: how quickly you commit to a plan you can actually finish. This module is a gym for that skill. Every sprint below is SELF-TIMED — the platform cannot hold a stopwatch for you, so set a real timer and respect it. Breaking your own clock is the failure being trained against.
The five sprints
| Sprint | Clock | Skill | |---|---|---| | Recognition | 15 min | Read, classify, start the right algorithm | | Implementation | 20 min | Known algorithm, zero-defect delivery | | Medium | 30 min | One observation + clean implementation | | Hard | 45 min | Two ideas fused, careful edge cases | | Synthesis | 60 min | Multi-structure problem, full pipeline |
The switch rule
At the midpoint of any sprint, ask exactly one question: "Do I have a complete plan, or only a hope?" A plan names the algorithm, the state, the complexity, and the I/O. A hope names a direction. Hopes at the midpoint mean: switch problems now. Problems are not loyal to you; points are.
The two-pass read
Pass one (3 minutes, all problems): titles, constraints, sample I/O. Mark each problem fast / plan / skip. Pass two: work only the fast and plan piles in descending order of confidence. The skip pile is revisited only after everything else is submitted.
After the clock
When the sprint ends, you get the editorial cycle: attempt record, hint, retry, submit, debug. The sprint is the attempt; the cycle is the learning. Self-timed honestly, the cycle turns 30 minutes of contest into a week of practice value.