Reading Python is not writing Python.

Understanding a concept and being able to produce it under pressure are different skills, and only the second survives an interview or a deadline. These are 2,882 problems — programs to write and predict-the-output drills that expose what you only thought you knew. Every problem appears exactly once and is numbered once across the course, so "Program 1,412" names one thing; where the same task had several worthwhile solutions, they are folded into one problem with the trade-off between them stated rather than asked four times over.

Start with the basics View full curriculum 114 problem sets · no account, no sign-up.

The progression

Five states, in order

Every level exists to move you from one of these states to the next. If a lesson does not advance you along this line, it was cut.

I know the syntax

You can read Python and predict what it does — including the surprising parts.

I write clean Python

Your code reads as idiomatic because every idiom is a choice you can defend.

I build applications

Packaging, errors, tests, I/O — the machinery around the logic.

I understand trade-offs

Internals, performance and concurrency, so your decisions have evidence behind them.

I run it in production

Observable, deployable, debuggable at 3am by someone who is not you.

Curriculum

The full path

Eleven modules, in the order the Python course teaches them — so a set can be taken the day you finish the matching lesson, or the whole track run on its own. Every title carries its program range and its subject, so nothing has to be opened to find out what is in it.

Fit

Who this is for

A good fit if

Not the right course if