Plan any subject, week by week

Pick a subject and say how many hours a week you actually have. You get the real order the skills have to be learned in, the graded work each stretch ends in, and an honest total in weeks. It is arithmetic over a published skill map, not a plan a model wrote on the way to you.

No accountNo email7 subjects
SubjectSubject
01 · The estimate

9 weeks at 4 hours a week

34.8Hours of work
9Weeks
20Things to do
3Marked
That assumes you hit 4 hours every week, which nobody does. The plan does not expire if you don’t.
02 · The plan

Week by week, in the order it has to be learned

Each line is one thing to be able to do. The order is the skill map’s own: nothing appears before what it needs.
  1. Week 14h starts here
    • Reading a tracebackLocate the cause of a failure from its traceback and say which line is at fault1h
    • Values and typesPredict the type of an expression and convert between types deliberately1.5h
    • Strings and formattingBuild and take apart strings without reaching for a loop where a method exists1.5h
  2. Week 25h starts here
    • Names and referencesPredict whether a change through one name is visible through another2h
    • Conditionals and truthinessWrite a condition that says what you meant, including when the value may be zero or empty1.5h
    • Lists and tuplesChoose between a list and a tuple and justify it from how the data is used1.5h · runs into week 3
  3. Week 34h starts here
    • Dicts and setsUse a dict or set to replace a linear scan, and explain what it costs2h
    • Choosing a data structurePick a structure from the access pattern and say what the alternative would have cost2h · runs into week 4
  4. Week 43.5h starts here
    • Loops and iterationIterate over a collection idiomatically, including in parallel with another2h
    • ComprehensionsRewrite a build-a-list loop as a comprehension, and say when you would not1.5h · runs into week 5
  5. Week 55h starts here
    • Defining functionsWrite a function with a clear signature that returns its result rather than printing it2h
    • Mutable default argumentsSpot a shared mutable default and fix it without changing the function's interface1h
    • Scope and closuresPredict which value a nested function sees, and fix a late-binding closure2h · runs into week 6
  6. Week 64.5h starts here
    • Raising and handling exceptionsHandle a specific failure without hiding the failures you did not anticipate2h
    • Writing testsWrite a test that fails for the right reason before the code is fixed2.5h · runs into week 7
  7. Week 74h starts here
    • Files and pathsRead and write a file safely, with paths that work on someone else's machine1.5h
    • Working with structured dataLoad a real, imperfect data file and produce a summary that states what it skipped2.5h · runs into week 8
  8. Week 83.3h starts here
  9. Week 91.5h starts here
This is the same plan we would give anyoneThere is no box here for how good you already are, because saying so has never made it true. This is what Python Fundamentals takes, and the only thing that takes work out of it is work of yours that has been marked. What the ten-minute check gives you is the other half: where you stand in it before you start.
Check where you stand in Python FundamentalsAbout ten minutes. No account.
The plan above is Python Fundamentals in full, and the marked work in it is published with its checklist before you start. Want a subject nobody has written? Ask for it — that one does need an account, and a few minutes.

One cookie, so we can see which subjects people finish and where the site loses them — plus a replay of where you click. Nothing you type is recorded, and once you’re signed in the words on screen are blanked out too. No advertising, nothing sold. The detail.