How to not break your #100DaysOfCode streak
A practical field guide to keeping a daily coding streak alive past the point where most people quit.
Almost everyone who starts #100DaysOfCode quits somewhere between day 8 and day 30. It's rarely because they stopped caring. It's because the day they were tired, busy, or discouraged, the bar they'd set for "a valid day" was too high to clear — and once you miss one day, the identity ("I'm someone who codes every day") cracks, and the whole thing unravels.
The fix is boring and it works: make a valid day small enough that you can do it on your worst day.
1. Separate the ritual from the ambition
Your ambition is to become a much better developer over 100 days. That's real, but it's not the thing you show up for daily. The ritual is what you actually commit to, and it should be almost embarrassingly small: open the editor and change one line. Read one function. Fix one typo. The ritual's only job is to keep the chain unbroken so the ambition has time to compound.
2. Define the minimum viable day in advance
Decide now, while you're motivated, what counts as a completed day when everything has gone wrong. Write it down. A good minimum viable day is something like: "15 minutes of code, or one commit, or one paragraph of notes about what I'd do next." If you don't pre-decide, you'll negotiate with yourself at 11pm and lose.
3. Log the day before you go to bed, every day
Streaks die in the gap between doing the work and recording it. Keep a single running log — one line per day about what you touched. It takes twenty seconds and it does two things: it forces you to notice you did show up, and it makes the missing days visible before they pile up. A public log adds a small, healthy amount of accountability without turning into a second job.
4. Never skip twice
You will miss a day eventually. That's fine and it does not mean you failed. The only rule that matters is: never miss two days in a row. One missed day is a rest day. Two is the start of a new habit — the habit of not doing it. Most quit-events are really two-misses-in-a-row events.
5. Make the streak the reward, not the guilt
If your streak counter only ever makes you feel bad, you'll stop looking at it. Frame it as evidence, not debt: a growing number that proves you're the kind of person who shows up. When you glance at "day 41," that should feel like money in the bank, not a bill.
6. Shrink the unit when life gets hard
When a crunch week hits, don't pause the streak — shrink the unit. The full write-up gets skipped; a single honest line survives. Consistency is a function of how low you're willing to set the bar on the days you least feel like it.
This guide is part of Cairn, a tiny free tool for exactly this: post one line a day, keep your streak, and share a public trail. You can try it without signing up.