how it ended last time
There was no moment you could point to
- 01
It stopped without a decision
No dramatic quit. The list for tomorrow stopped getting written, and a week later there was nothing left to come back to.
- 02
The intimidating task is where the run dies
Somewhere ahead sits the project you feel unready for. The days before it get slower, and then one of them does not happen.
- 03
Restarting at day 1 feels like an admission
So the restart waits for a clean Monday, a clean month, a clean January, and the date keeps sliding.
before you sign up
What people ask on the second attempt
I quit at day 12 last time. Does that predict anything?
No. The first run had no list in the morning and nobody reading at night. That is what changes here, and it is not a personality fix.
Does a missed day reset the count?
No. You write what happened and carry on. The number is days you showed up, and it only goes up.
Can I use the same project as last time?
Yes. Picking it back up is a fine first task, and the group is a reasonable place to admit it scares you.
What if I stop again?
Then it stops in public this time, which is a different experience and usually a shorter one.
Is there a group call?
No calls. Everything is written: your list, your report, and other people's.
The two habits that hold the count
what is different this time
- 01 Write the three in the morning, every morning Planning is the thing the first run lost first. The days went dark only after the list stopped appearing.
- 02 Report the bad days too Especially those. A logged miss stays inside the run; an unlogged one is how the last attempt ended.
- 03 Do it beside people who have also stopped before Nobody here treats a broken streak as news. What they notice is four days of silence.
how it tends to go
Past the point where it stopped
Familiar ground, and the temptation is to write bigger tasks than last time. Write smaller ones.
Familiar ground, and the temptation is to write bigger tasks than last time. Write smaller ones.
Beyond where the first attempt ended, because a missed day got reported instead of hidden.
A finished run, and the useful part is knowing exactly which days were hard and what you did with them.
gallery
A hundred evenings at the keyboard
Three tasks each morning. One report each night. A hundred days of code.
Runs end in a recognisable place
the same break, written down by someone else
A public postmortem of an unfinished run traces the break to the same spot: the planning ahead stopped, and a missed day followed.
sourcePublic repositories on GitHub carrying a log of the hundred-day format, finished and unfinished alike.
sourceBoth come from the pages linked here. Nothing about completion rates is claimed, because nobody has measured them.
The second run has a start date
Leave an email and we send it as soon as it is fixed. Nothing is charged here.
- Three tasks in the morning, one report at night
- Missed days logged, never wiped
- People who read the log and notice the silence
One email, once the next hundred days have a date.
ask first