intro 0% read jk sections · / ask

Python · self-paced, already bought

Day 1 of Python is easy. The rest is why this exists.

The course is sitting there with a hundred lessons in it. Lessons are not days, and nothing in a syllabus decides whether Thursday happens.

how it tends to go

A hundred days against a syllabus

$ hundred status --niche code

day 1 of 100 · 1% done

log

Sizing the tasks. A lesson plus one small thing of your own is usually the shape that survives a working week.

Day 1–10

Sizing the tasks. A lesson plus one small thing of your own is usually the shape that survives a working week.

Day 30

The dull middle of the course, where the topics stop being new. The report is what carries the run across it.

Day 100

A hundred dated entries and Python you have used on your own terms, not only the instructor's.

where the course goes quiet

A hundred lessons is not a hundred days

  1. 01

    The lesson list has nothing to say about Thursday

    It knows the order of the topics and nothing about the evening you skip, and skipped evenings are where a bought course quietly ends.

  2. 02

    Week one runs on novelty

    The real test is an ordinary Wednesday in week six, when the next topic is dull and absolutely nothing happens if you close the tab.

  3. 03

    Typing along leaves you with the instructor's file

    It compiles, it works, and it was their idea. The day the course asks for something of your own, the gap shows up.

Three tasks, then a report, then tomorrow

what a day looks like

01 Name three things you will do to Python today One lesson, one exercise, one thing fixed in a file of your own. Specific enough that at night you know whether it happened.
02 Report the day in two lines What you finished, what you skipped. A hundred of these become a record of how you actually learn, which no course can hand you.
03 Do it in view of the others Everybody is a different number of days in and reporting regardless. The evening you plan to skip quietly is the one that gets noticed.

before you sign up

Questions worth asking

Do you teach Python?

No. We never touch the material. The tasks you write are yours, and so is the course you write them against.

Which course should I use?

We do not sell, bundle or recommend one. The people in the group will tell you what they are using and what they abandoned.

Does this work for other languages?

Yes. This page is written for Python because that is the language most people arrive with.

Do I have to code a full hour?

No. Your three tasks set the length. Fifteen honest minutes is a day that counts.

What if I finish the course before day 100?

The remaining days go to something of your own, which is usually where the learning that sticks turns up.

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

Python every day, for a hundred of them

Leave your email for the start date of the next group. No payment is taken on this page.

  • Three tasks in the morning, one report at night
  • Any course, or none at all
  • A hundred days counted from a shared start date

A single email with the start date. No sequence, no newsletter.

ask first

Not sure it survives your week?

Enter to send · Shift + Enter for a new line
Put me on the next start