LeetCode Journal

LeetCode Journal

Current rotation topic

—

Set a start date to begin tracking

Weekly Plan

0 / 7 done

Problem Log

No problems logged yet

Contest Log

No contests logged yet

Dashboard

Activity

0 problems in the last year

Less More

Topic weak-spot trend

Contest score trend

Appearance

Light Dark System

Theme Color

Data

Your data is stored only in this browser. Export a backup regularly, or move it to another browser/device via import.

Monday — Upsolve + Review

4-5 hrs

Revisit yesterday's real contest: solve whatever you missed (Q3/Q4), spending 45-60 min per problem before checking editorial
Read editorials even for ones you solved — check if there was a cleaner/faster approach
Log the pattern used for each problem in a notes doc (this becomes your personal pattern library over time)

Tuesday — Topic Day 1

4-5 hrs

Pick ONE topic: e.g., DP (start with 1D DP, knapsack variants, then 2D)
Solve 6-8 problems in the 1700-2100 rating band on that topic, untimed
Goal: recognize the pattern fast, not just solve — after finishing, ask "what was the trigger that told me this was DP?"

Wednesday — Topic Day 2

4-5 hrs

Different topic: binary search on answer, prefix sums/difference arrays, sliding window
Same format — 6-8 problems, untimed, focus on recognition speed

Thursday — Topic Day 3 + Mini Timed Set

4-5 hrs

Morning: another topic — monotonic stack/queue, union-find, or graph (BFS/DFS/Dijkstra/topo sort)
Afternoon: 90-min timed set of 2-3 problems (mix difficulty) to start reintroducing time pressure without a full contest

Friday — Virtual Contest

4-5 hrs

Full virtual contest, strict 90-min window, all 4 problems, real contest conditions (no notes, no hints)
After: immediately review — where did time actually go? Did you get stuck on Q1/Q2 execution, or purely stuck on Q3 logic?
Spend remaining time upsolving anything unsolved

Saturday — Biweekly Contest / Weak-Topic Deep Dive

Biweekly week: compete live in the evening; earlier in the day do a lighter topic practice (3-4 problems) so you're not mentally fried before the contest
Off week: full day dedicated to your weakest topic — identify this from your Monday logs (whichever topic keeps showing up when you fail Q3)

Sunday — Weekly Contest

Compete live in the morning
Rest of the day: light — upsolve 1 problem max, or just rest. Don't burn out right before the week resets.

Operating principles

Rotate topics on a cycle, don't practice the same one forever. Suggested 2-week rotation: DP → Binary Search → Graphs → Monotonic Stack/Greedy → repeat, going slightly deeper each pass.
Track a simple log after every contest (real or virtual): which problems you solved, time taken, and — critically — why you got stuck on the one you didn't solve (didn't see the pattern / saw it but coded too slow / made a bug).
Don't skip Q1/Q2 in virtual contests even though they're easy for you — speed there is what buys you time for Q3.
Adjust practice-day topics based on real signal. If after 2-3 weeks your logs show a topic is consistently the wall, give it 2 days a week instead of 1 until it stops being the wall.

Add Problem

Title Topic

Difficulty

Type

Time taken (min) Date

Solved?

Stuck reason

Notes

Add Contest

Name

Type

Date

Problems solved Rank

Notes