01
Decide the day before it starts
Three tasks, written in the morning, sized for the evening you will actually have.
why it stalls
The switch rarely fails on talent
- 01
The runway is long and nobody is watching it
Six months of self-study has no manager, no sprint and no review. The only signal is your own memory of last week.
- 02
Bad weeks cost more than they should
One overloaded week at the current job turns into a lost month of study, and the restart is heavier than the stop.
- 03
Progress is hard to see from inside
Without a log, month three feels the same as month one, which is exactly when most people quietly stop.
before you sign up
Reasonable questions
Will this get me a job?
No programme can promise that, and we do not. What it gives you is a hundred days that actually happened, and the work that came out of them.
Do I need a project already?
It helps, but the first week is a fine place to choose one. The daily structure works either way.
What if my job gets busy?
Shrink the tasks, keep the report. A ten-minute day still counts as a day you showed up.
Is there a group call?
The core is written: your tasks, your report, and the logs of the people around you.
What does it cost?
Pricing is set when the next group opens. Nothing is charged on this page.
how it runs
Three tasks in the morning, one report at night
02
Close the day in writing
What moved, what did not. A hundred of these become the record you cannot argue with.
03
Sit with people on the same road
Others mid-switch, reporting the same way. Their logs make yours normal, and vice versa.
the shape of it
What the hundred days usually look like
log
Mostly calibration: learning to write tasks small enough to finish after a full workday.
Day 1–10
Mostly calibration: learning to write tasks small enough to finish after a full workday.
Day 30
The first collision with real life. You miss, you log it, you continue — the habit holds.
Day 100
A hundred logged days, a portfolio project that moved, and evidence you can study around a job.
gallery
A hundred evenings at the keyboard
Three tasks each morning. One report each night. A hundred days of code.
where this comes from
A public pledge that has run for years
- —
- #100DaysOfCode has run since 2016 as a public pledge: code an hour a day, tweet the log. source
Figures here are quoted from their sources, not estimated. Where we have no verified number, we show none.
The next hundred days start soon
Leave an email and we will tell you when the group opens. Nothing is charged on this page.
- Three tasks in the morning, one report at night
- People mid-switch, reporting the same way
- A hundred days, counted from a fixed start date
We write once, when the next hundred days start.
ask first