intro 0% read jk sections · / ask

Coming back · after a long gap

Getting back to code after a long time away

The syntax returns faster than you expect. What is actually gone is the shape of a day with code in it, and that does not come back from reading about it.

why coming back stalls

The first week back proves nothing

  1. 01

    Enthusiasm covers about five days

    Then the gap that ended things the first time opens again, in the same place, for the same unremarkable reasons.

  2. 02

    Everything moved while you were gone

    New tooling, new defaults, new opinions about all of it. Catching up feels infinite, which makes it an excellent reason to start next month.

  3. 03

    You remember being better than you currently are

    Sitting down means meeting the distance between the two, and it is easier to do that never than on a Tuesday.

what a day looks like

Three tasks, one report, no curriculum

01

Three tasks set against today's ability

Not against the version of you from three years ago. Small, finishable, decided in the morning.

02

One report, whatever the day held

Two lines at night. The early ones are mostly about how rusty it felt, and by day thirty they have stopped being.

03

Be seen restarting

The room holds people mid-run at every level. None of them is measuring you against your old self.

how it tends to go

Rebuilding the habit, in order

$ hundred status --niche code

day 1 of 100 · 1% done

log

Reacquaintance. Expect tasks to take twice what you budget, and start budgeting accordingly around day 4.

Day 1–10

Reacquaintance. Expect tasks to take twice what you budget, and start budgeting accordingly around day 4.

Day 30

The rust stops being the subject of the report. What you are building becomes the subject instead.

Day 100

A daily practice that exists again, and a hundred entries showing how it was put back together.

where people relearn in public

Free rooms full of people doing this

93,150
Members of The Odin Project's Discord, counted by a Discord index in April 2026 — a free room of people learning and relearning in the open. source
—
The hundred-day format and its log template are public and free. What this page adds is the list for tomorrow and a group, not the idea itself. source

Counts belong to the pages they link to, with the dates those pages state. We have none of our own to show yet.

Three tasks each morning. One report each night. A hundred days of code.

before you sign up

What returners ask

How long a break is too long?

It makes no difference to the mechanism. Day 1 is day 1 whether you left six months ago or six years ago.

Do you help me choose what to relearn?

No, that decision stays yours. The group is a decent place to sanity-check it out loud.

What if I only have twenty minutes?

Then the three tasks are twenty minutes long. The count tracks days, not hours.

Is this for beginners or professionals?

Both are in it. The reports read very differently, the mechanism does not.

What happens on day 100?

You stop, or you start another hundred with a different target. Nothing renews by itself.

A hundred days to get the habit back

Leave an email and the start date comes when it is fixed. No payment here.

One email, once the group's start date exists.

ask first

Not sure it survives your week?

Enter to send · Shift + Enter for a new line
Send me the next start date