How to keep a LeetCode streak alive (when you have a job)

Most advice about streaks is just encouragement with extra steps. "Stay consistent!" is not a method. So here is the actual mechanics of keeping a LeetCode streak alive when you have a job, a commute, and a life that occasionally catches fire.

The core insight: a streak does not break on the day you skip. It breaks on the day you decide the streak is already ruined. Everything below is designed around that single failure mode.

Pick the smallest unit you could complete on the worst day you can reasonably foresee — post-deadline, 11:40pm, running on four hours of sleep. For most people that is one Easy problem. For some it is fifteen minutes of genuine attempting, solved or not.

This feels like cheating. It isn't. A streak's job is to protect the habit, not to constitute your training volume. On good days you will do far more than the minimum, and nobody will stop you. The minimum exists so bad days produce a small win instead of a break.

If your minimum is three Mediums, you have not set a habit — you have set a trap that springs the first busy week.

"I'll do LeetCode daily" fails. "After dinner, at my desk, 9pm, one problem" works considerably better. This is the implementation-intentions finding from Gollwitzer and Sheeran's meta-analysis of 94 studies: pre-specifying the when and where of an action reliably improves follow-through, with a medium-to-large average effect.

The reason is mundane. A vague intention requires you to decide, every single day, when to act — and that decision gets made by whoever you are at the moment, which on Thursday is someone tired who would rather not. A pre-made decision doesn't get re-litigated.

Write it as one sentence. Attach it to something that already happens daily — after dinner, after your last standup, after you close your laptop for work.

Some days you genuinely cannot solve anything: a flight, a fever, a production incident at 2am. A streak system with no allowance for reality will eventually punish you for reality, and the punishment is what ends the run.

This is why freezes exist — a banked allowance that absorbs a missed day automatically. The important part is that they are earned and finite. Unlimited skips mean the streak stops meaning anything; zero skips mean one flu ends four months of work.

Whatever tool you use, decide your rule for missed days before you miss one. Deciding in the moment, while feeling guilty, produces the worst possible answer.

If a day is lost, the entire game becomes the next 24 hours. One miss is noise. Two misses is a new pattern, and the third is a decision you've already made without noticing.

Psychologists studying relapse call this the abstinence violation effect: after a single lapse, people frequently reinterpret the whole project as failed and abandon it — the lapse causes far more damage through that interpretation than through the lost day itself. Dieting research documents the same thing as the "what the hell" effect.

So the recovery protocol is not to do double the next day. It is to do the absolute minimum the next day, and refuse to treat the gap as meaningful.

Loss aversion is the strongest lever available here. Kahneman and Tversky's prospect theory found losses weigh roughly twice as heavily as equivalent gains — meaning a 40-day streak on a screen is psychologically a possession, and skipping stops being "no progress today" and becomes "losing forty days."

This is the mechanic Duolingo built a retention engine on, and it transfers cleanly to algorithms. It only works if the number is somewhere you actually see it, and if it represents something you'd be annoyed to rebuild.

One problem a day, held for a year, is roughly 365 problems — more than most people accumulate in three sporadic bursts of enthusiasm, and spread across enough time for spaced repetition to actually consolidate the patterns. Intensity does not survive a bad week; consistency does.

DSAMotivator automates exactly this loop: it detects your accepted submissions, keeps timezone-correct streak accounting, earns you a freeze every 7 days, and sends back the one sentence you wrote about when you'd practise. Bring your own problem sheet — the streak infrastructure is the part that's hard to build yourself.