The first plateau is operational, not theoretical. You will learn expressions, names, collections, branching, loops, functions, and tracebacks in the app runner. The exercise produces a small program that can be run twice on two labelled fixtures with the same in-app entry file.
Level 0 lessons
0 of 4 done
Make a Python program run predictably, then observe what it actually did.
Done against a real organisation you choose, not a case study. The gates below are about what these produce.
01
Exercise 0.A - A repeatable inspection script
Choose one supplied fixture or paste a permitted small dataset into the app workspace. Produce a program that reads a virtual file or in-memory value, reports a count or summary, and includes a deliberate malformed input. Add a short note in the workspace describing the entry file and expected output. Timebox: four hours. It fails if the app run cannot be repeated from the entry file, if a missing virtual file is reported as a successful empty result, or if you cannot show the traceback and smallest repair for one deliberate bug in run history.
Level 0 gates
0 of 6 ticked
What you should be able to do after this level. Tick each one when it is true. Nobody marks these. Sign in to tick them.
You can predict and run expressions, then explain each changed output in the app run history.
Not ticked
You can explain whether a function mutates or copies each mutable argument it receives.
Not ticked
You can choose a list, set, or dictionary and state the invariant that choice preserves.
Not ticked
You can read a traceback from the failing line to the violated input assumption.
Not ticked
You have saved a program with two labelled fixtures and recorded both outcomes in the app workspace.
Not ticked
You can reproduce one failure from the in-app entry file without relying on hidden device state.
