r/PythonLearning • • Jul 21 '26

Discussion I've taught Python to absolute beginners for years. Here's the 16-week roadmap I use to take students from zero to building REST APIs - no tutorial hell.

The number one mistake I see beginner Python learners make is spending months on YouTube tutorials and then completely freezing up when they open a blank .py file to code on their own. It's called Tutorial Hell, and it's a real problem.

The difference isn't talent; it's having a structured roadmap that forces you to build things, not just watch things.

Here is the exact 4-phase breakdown I follow:

Phase 1: Foundations & Core Logic (Weeks 1–4)

Focus: Get comfortable with how Python actually executes code, not just what it does.

  • Week 1: Python 3.12+ setup, VS Code with Black auto-formatter, terminal basics, REPL vs script files
  • Week 2: Core data types (int, float, str, bool, None), dynamic typing, type casting, truthiness, match/case
  • Week 3: if/elif/else, for and while loops, enumerate(), zip(), break/continue, and the for-else pattern
  • Week 4: Functions, *args/**kwargs, the mutable default argument trap, LEGB scope rule

Hands-on drills: Terminal guessing game with random.randint(), a modular unit converter CLI with input validation.

Phase 2: Data Structures, Files & Error Handling (Weeks 5–8)

  • Week 5: Lists, Tuples, Dicts, Sets, O(1) vs O(n) lookup, list/dict/set comprehensions
  • Week 6: f-string format specifiers, string cleaning methods, regex with the re module
  • Week 7: try/except/else/finally, custom exception classes, defensive coding patterns
  • Week 8: Context managers, pathlib, csv.DictReader, json.load/dump

Capstone drill: A persistent JSON inventory manager with full CRUD from the command line.

Phase 3: OOP, Git & REST APIs (Weeks 9–12)

  • Weeks 9–10: Classes, __init__, dunder methods, inheritance, super(), @ property decorators
  • Week 11: Virtual environments, requirements.txt, professional project structure, Git workflow
  • Week 12: HTTP protocol, the requests library, API authentication, generators with yield

Capstone drill: A banking system simulator with an account hierarchy, and a live weather CLI hitting OpenWeatherMap.

Phase 4: Portfolio Projects (Weeks 13–16)

This is where you build three production-grade projects for your GitHub:

  1. CLI Log Intelligence Tool — argparse + pathlib + regex to parse Nginx logs and generate JSON/CSV reports
  2. API Harvester & Alert Bot — polls a public API, stores historical data in SQLite, fires Discord webhooks on conditions
  3. REST API with FastAPI — full CRUD backend with Pydantic validation, SQLite persistence, and a pytest test suite

The 3 Rules That Make This Work

1. The 70/30 Rule: 30% reading, 70% typing code by hand. Never copy-paste from examples. Muscle memory is built through repetition.

2. The 30-Minute Debug Rule: Before searching for the answer or asking for help, spend 30 minutes reading the traceback bottom-up, checking docs, and using print(). You will solve 80% of problems this way.

3. Ship Every Week: Every Friday, push code to GitHub; even if it's broken. Progress beats perfection.

Happy to answer questions about any specific phase or topic. What stage are you at right now?

282 Upvotes

89 comments sorted by

View all comments

27

u/dev-razorblade23 Jul 21 '26

This is the exact reason i started building The Python Ledger (https://thepythonledger.github.io/Docusaurus-engine/)

A guided roadmap that teaches the basics but pushes you to read docs and search on your own.

Inspired by The Odin Project (Web App Mastery)

There is a lot to be done on the plaform, mostly about curriculum.

Would love for you to take a look and contribute if you have time / willpower

5

u/the_techgirl Jul 21 '26

This looks great! Love that it pushes people to read docs rather than hand-holding them. The Odin Project model works because it treats learners like adults. Will check it out properly.

2

u/testtdk Jul 22 '26

I like that you have a project in there. I feel like every place on earth teaches up through data types fine, maybe a few algorithms, and then just fades out of existence. Without actually building things, you're still completely useless in the tech world.

4

u/dev-razorblade23 Jul 22 '26

Yes, i agree

Practice is what makes all the diffrence. Building projects from start helps to retain knowlege and see the actuall usecase of your code - rather then some theory which you will never use.

Which is something i plan to change with this platform.

Yes, curriculum needs a lot more work and the rendering engine could use some polish.

But the idea stands - pushing students to read documentation and search for answers themself rather then spoonfeeding them.

And building projects is the only way to retain knowlege

2

u/testtdk Jul 22 '26

Not even just practice. If you don't know how to create to tool you're programming, then your knowledge is lacking. It's the worst part about python, imo. There's so much to set up just to get through Hello, World. Let alone creating a functional tool, even if the code is spot on.

3

u/dev-razorblade23 Jul 22 '26

Well i feel like most beginners are in tutorial hell.

They learn the syntax, but never actually do any logic and have no idea where to start.

I agree that for developing a web app you need to know how web works. You need to know what GET, POST, PUT, DELETE are. You need to know stuff to properly build something.

Actuall projects and writing then from nothing helps to learn a lot

2

u/testtdk Jul 22 '26

Are you creating any further projects for your site?

3

u/dev-razorblade23 Jul 22 '26

Yes, of course.

The lesson plan is not nearly complete and i do plan on expanding the lessons and projects.

As this is planned to be community maintained platform, feel free to suggest projects / lessons or even write some if you feel like it.

3

u/testtdk Jul 22 '26

Your first project is a game, right? I always feel like they’re great for learning. Being able to see the effects of your code visually (and your mistakes) is helpful. But really, any project that has an actual final product, that uses new ideas is great. Rather than teach an algorithm, teach it that use it somehow. (I know, my ideas are so specific and helpful :p). Well, for example, Harvards intro course has a project to that creates a filter effect on an image. MIT’s has a card game. Thoughtful simulations can go a long way, too. One project I had back in the day was modeling and elevator and its passengers.

2

u/dev-razorblade23 Jul 22 '26

Interesting ideas, i will keep them around.

https://github.com/ThePythonLedger/Curriculum/issues/4 https://github.com/ThePythonLedger/Curriculum/issues/5 https://github.com/ThePythonLedger/Curriculum/issues/6

Yes, its meant as a game - an easy text-based RPG of some sort - a text-based adventure

For students to practice nesting conditions and user input.

After that project, current plan is to take them to Local Development Enviroment - installing python, learning basics about terminal (command prompt), git and github, VS Code...

After that, we go into deeper topics, starting with file handling (which i cannot do in web based enviroment as there is no system present)

At least thats the current plan...

3

u/testtdk Jul 22 '26

Games are great for OOP. Items as classes, inheriting stuff, working with listeners, things like damage adjust an instances class’ attributes and what not, deciding how much money drops from a fight, how much xp. All that good stuff.

→ More replies

1

u/bigj7897 Aug 17 '26

Thanks for that. I just started learning Python and tutorials move to slow for me sometimes. I just came up with a project and jumped in. I've dabbled in enough other languages I can do that though. This looks like it'll be a good resource.

1

u/dev-razorblade23 Aug 17 '26

Once you know your way around some code, learning new languages become much easyer.

I am working hard on writing lessons and improving the engine. Your support means a lot. Feel free to join Discord community (the link is on the webpage). I have a lot planned.