01
Write three tasks you could finish badly
One broken thing fixed, one function written with no video open. Small enough that a tired evening still clears them.
not just you
The loop has a name and a lot of witnesses
- —
- A widely read post on DEV describes the same pattern from inside: finishing one resource, hopping straight into the next, never feeling the concepts had landed. source
- 11,561
- Forks of the public log template for the hundred-day format on GitHub — one per person who set themselves up a journal. source
Both figures are read off the linked pages. No numbers about our own participants appear here, because none have been measured.
why the next course won't fix it
The loop is comfortable, which is the trouble
- 01
Finishing a resource feels like progress
One tutorial ends, the next begins, and the suspicion that nothing landed gets postponed by another twelve hours of video.
- 02
Following along skips the part that is hard
Every decision in a lesson was made before you got there. The gap you feel in front of an empty file is those hundred small choices, unmade.
- 03
Quitting your own project costs nothing
Nobody knows the project existed, so dropping it on Tuesday leaves no mark. Dropping it in front of people who read yesterday's log does.
the mechanism
Two habits, and nothing else to install
02
Say what happened before you close the laptop
Two lines, written whether the evening went well or not. The bad ones turn out to be the useful ones to have on record.
03
Sit in a room where nobody is teaching
Everyone is building their own thing and reporting it. Questions get answered by people one step ahead, not by a curriculum.
how it tends to go
What leaving the loop looks like
log
Uncomfortable. You will want to open a tutorial for safety, and mostly you will not.
Day 1–10
Uncomfortable. You will want to open a tutorial for safety, and mostly you will not.
Day 30
You notice you started today without looking for a lesson first. That is the shift the hundred days are for.
Day 100
A project you can explain line by line, because every line was a decision you made and wrote down.
Three tasks each morning. One report each night. A hundred days of code.
gallery
A hundred evenings at the keyboard
before you sign up
Questions that come up
Do you give me the material?
No. No lessons, no videos, no reading list. If you want one, the group will happily argue about which.
What if I don't have a project?
Then the first three tasks are choosing one. People in the room will tell you when it is too big, which is the usual mistake.
Do you review my code?
No. Nobody here reads your diff. What gets read is your daily report.
How long is a day meant to take?
However long your three tasks take. Most people size them to under an hour.
What if I fall back into a tutorial?
Write it in the report. Watching something is not a crime; hiding in it for three weeks is what the log makes visible.
The blank file is the whole course
Leave an email and we tell you when the next hundred days start. No payment is taken here.
- Three tasks in the morning, one report at night
- A hundred days without a single lesson from us
- People building their own things in the same window
One message when the next group opens. That is the only use of the address.
ask first