LeetCode burnout: why it happens and how to come back

LeetCode burnout usually isn't caused by the volume of work. It's caused by sustained effort with punishing feedback and no visible progress — which is a fairly precise description of grinding Mediums alone for six weeks.

Three things stack. First, the feedback is frequently negative: failing a problem after fifty minutes is the normal case, not the exception, and it registers as failure even when it's productive. Second, the reward is remote — an interview months away, possibly hypothetical. Third, progress is invisible from the inside, so a month of genuine improvement can feel like a month of nothing.

Add a daily volume you set during a motivation spike, and the arrangement is close to optimally designed to exhaust someone.

The classic sign isn't exhaustion — it's avoidance dressed as productivity. You reorganise your problem sheet. You watch a video about approaching problems. You read about the patterns you should be practising. You do everything adjacent to solving, and no solving.

That's not laziness, it's an entirely rational response to an activity that reliably makes you feel worse. Your brain is doing exactly what you'd expect. The fix is to change the arrangement, not to push harder against it.

Not zero — absurd. One Easy problem a day, or fifteen minutes of attempting. The instinct after burning out is to stop entirely and "come back fresh in a couple of weeks," which almost always becomes four months.

Keeping a trivially small daily action alive preserves the identity of someone who practises, and identity is the expensive thing to rebuild. Volume is cheap to rebuild once you're showing up again.

For a few weeks, count attempting as success. Fifty minutes on a Hard you never solve is a genuinely good session — you did retrieval, you found the gap, you'll recognise the shape next time. Counting only accepted submissions makes your emotional state a function of a binary judge that ignores most of the value.

Find or build a representation of progress that isn't your own memory: patterns you've now covered, a streak count, a solved-by-topic breakdown. Burnout thrives on the belief that nothing is improving, and that belief is usually just an absence of measurement.

Sheet-shopping is a burnout symptom. Pick any reasonable problem list and stop evaluating alternatives — the difference between good lists is far smaller than the difference between practising and researching how to practise.

If practice is bleeding into sleep, health, or your existing job, take a real break with a defined end date — a week, marked in a calendar, rather than an open-ended pause. Open-ended breaks from DSA have a poor return rate, for the same reason open-ended goals do.

DSAMotivator is built around this failure mode specifically: a minimum you set yourself, freezes so one bad week doesn't erase months, and a Pattern Mastery Map that makes a month of quiet work visible. You do the coding — the part that keeps you coming back is the part we handle.