FREE GUIDE
Python roadmap for beginners: the order that actually works
No sign-up needed to read this, and it assumes you have never written a line of code.
Most people who quit Python did not quit because Python is hard. They quit around week three — after six hours of tutorials and very little typing — when a small program refused to run and they had no idea which of the six half-learned things was the problem. Order fixes that. Each stage below uses only what the stage before it handed you.
The eight stages
The times assume roughly two hours a day, which is the pace most people with a job or college can keep. They are estimates, not promises: the hours you spend typing code count, the hours you spend watching it mostly do not.
| Stage | What you learn | What you can build after it | Realistic time |
|---|---|---|---|
| 1. First program | Installing Python, running a file, print(), comments | A program that prints your own introduction | 1–2 days |
| 2. Values and names | Variables, int, str, float, bool, input(), f-strings | A bill splitter, an age-to-days converter | 1–2 weeks |
| 3. Decisions | if / elif / else, comparisons, and / or / not | A quiz that grades your own answers | 1 week |
| 4. Repetition | for, while, range(), break, continue | FizzBuzz, a number-guessing game | 1–2 weeks |
| 5. Collections | Lists, dicts, sets, tuples, slicing, comprehensions | A contact book, a word-frequency counter | 2 weeks |
| 6. Functions and modules | def, arguments, return, scope, import | Your stage-3 quiz split into reusable pieces | 1–2 weeks |
| 7. Files and failures | Reading and writing files, JSON, try / except | A to-do list that survives closing the terminal | 1–2 weeks |
| 8. One real project | All of the above, plus reading documentation | Something you would actually use | 2–3 weeks |
Classes and object-oriented programming come after stage 8, not inside this list. A beginner who learns __init__ before they can build a small program has learnt syntax with nothing to attach it to.
What to practise in each stage
"Learning" gets confused with "watching" more than anything else on this roadmap. Every stage needs drills that use only that stage's tools:
- Stage 2: read three numbers from the user, print one sentence that uses all three, then print the same sentence with the money value to two decimal places.
- Stage 3: read a mark and print a grade. Then type a letter instead of a number on purpose and read the error Python gives you.
- Stage 4: FizzBuzz from memory. Then the multiplication table of any number. Then a loop that stops the moment the answer is right.
- Stage 5: count how often each word appears in a paragraph with a dict, then do it again with
collections.Counterand compare the two. - Stage 6: turn the grade program into a function that takes a mark and returns a grade, then use that function twice in the same file.
- Stage 7: save a to-do list to a file, close the program, open it again, and make it load what you saved.
Which project to build in stage 8
Pick it from the reason you started, not from what looks impressive:
- A job in data: download one free CSV, load it with
pandas, answer five written questions about it. - Boring work you want gone: a script that renames a folder of files, or reads every invoice in a folder and prints the total.
- Websites and apps: a small Flask app with two pages and one form, then put it behind a real URL.
- Proving it to yourself: a command-line game with a score saved to disk — it uses every stage above.
The four traps
Collecting courses instead of finishing one
Three half-watched courses teach less than one finished. The topic you are bored of in course two is the topic everybody needs in month three.
Copying code that works
Typing it yourself is not pedantry. The mistakes you make while typing are what teach the syntax, and paste-first learners hit a wall the moment an example changes.
Practising only when you feel confident
Confidence is the output of practice, not the input. Ten minutes daily beats a four-hour Sunday that never happens.
Stuck for twenty minutes and saying nothing
Being stuck is where learning stops unless the block gets cleared. Write the exact sentence you are stuck on — "why does this loop run one extra time" — and ask it. That is the whole skill of getting help.
Doing this with an AI tutor
The roadmap above is fixed: everybody gets the same eight stages in the same order. Orbit builds a path around your answer instead. It asks what you want to learn, what you already know and how many minutes a day you have, then writes a path of about 40 lessons for exactly that — and teaches it one concept at a time: a challenge on that idea, your wrong answers scaffolded instead of marked, and a mastery gate before the next concept unlocks.
Doubts get answered in the same chat, mid-lesson. Ask why that loop runs one extra time, get the answer, and the question you were working on is still waiting for you. Python is one of many names it takes — the same path gets written for Excel, accounting, English grammar, or an interview you have on Friday.
Start your own path — first 30 days free
Every new account gets the full Pro allowance for 30 days with no card asked for. After that the free plan keeps working at 15 tutor requests and 2 new paths a day, and every skill you started stays yours. Full details on the pricing page.
More free guides
Start with Python? · How long it takes · print() guide · Hindi mein coding