After a class or a tutorial, write what you understood — in your own words, as much or as little as you have. PythonRise files it under the right Python topic and shows you how much of that topic you have really covered.
Dark green — you explained it yourself. Light — you only mentioned it. Red — still ahead of you.
A sentence, a paragraph, or the code from today's exercise with your explanation under it. No format, no marking, no deadline.
Whatever you write lands on the right topic — Lists, Loops, Decorators — and is checked against that topic's checklist, built from the official python.org documentation.
Every topic with how much you have covered, and every green mark quoting the sentence of yours that earned it.
A tutorial you followed along with feels understood. Writing one honest sentence about it is where you find out whether it was.
Most people who stumble in interviews can write a loop and are fuzzy on why
range(5) stops at 4, or what aliasing does to a list. Those surface here,
in week two rather than in the interview.
Write something wrong and it asks a question instead of marking you down. Write a bare topic name and it asks for one real sentence. That is the whole of it.
Months of your own explanations, searchable, on a calendar and a map of what connects to what. Revise from your words, not somebody else's notes.
Write what you understood. That is the whole thing.
Start your shelfAt an institute? Use the code your trainer gave you when you sign up. Under 18? Sign up with a parent's email and they are asked first.