what the timetable misses
Graded work and daily work are different things
- 01
Deadlines teach sprinting, then stopping
A week of nothing, three nights of everything, submit, collapse. It clears the module and leaves no rhythm you can take into a job.
- 02
Your repository is a folder of submissions
Every commit in it was somebody else's idea, sized by somebody else's brief, and written the night before it was due.
- 03
Everyone claims to be building something
Term-time comparison is loud and impossible to check. What your classmates did yesterday you never actually see.
Three tasks in the morning, one report at night
how it runs
- 01 Pick the three before the day gets loud Written in the morning and sized for a gap between lectures, not for the perfect free Saturday that keeps not arriving.
- 02 Close the day in two lines Done, not done. It takes a minute, and it is the only reason day 41 knows what day 40 did.
- 03 Post it where the others post theirs Everybody in the room is on the same count. Reading somebody's day 12 while you write yours is what moves the number.
how it tends to go
The hundred days from inside a term
Calibration: learning to size a task to a real student day instead of an imagined one.
Calibration: learning to size a task to a real student day instead of an imagined one.
Midterms land. The tasks shrink to fifteen minutes and the count survives, which is the whole exercise.
A hundred logged days and a repository that is yours, sitting next to the folder of things that were assigned.
gallery
A hundred evenings at the keyboard
The format is older than this page
who else does this
Repositories on GitHub matching the search “100 days of code”, most of them one person's log of their own run.
sourceThe movement behind the format has two rules and no price: an hour of code a day for a hundred days, and the day posted in public.
sourceEach number is read off the page it links to. We publish nothing about our own results, because there is nothing measured yet.
Three tasks each morning. One report each night. A hundred days of code.
before you sign up
Fair questions
Is this a course?
No. Nobody here sets you material or marks it. You bring what you are working on and the structure holds the days.
Does it survive exam weeks?
That is what the report is for. Fifteen-minute days are still days, and the group sees you shrink the tasks rather than disappear.
Can the tasks be coursework?
Yes. Plenty of people use the hundred days to understand a module instead of surviving it. Nobody checks what you picked.
Do I get a certificate?
No. What you end with is a hundred dated entries written by you, which is a stranger and more useful artefact than a PDF.
What does it cost?
The price is announced when the group opens. This page charges nothing.
The next group starts on a fixed date
Leave an email and we send the date once it is set. Nothing is charged here.
- Three tasks in the morning, one report at night
- A count that survives exam weeks instead of resetting
- People on the same hundred days, reading each other's logs
One email when the start date is set. Nothing else goes to that address.
ask first