Python Backend Path

PROBLEM

Backend tutorials usually skip the fundamentals or stop at a demo. This 12-week path rebuilds them in order: Python first, then Django, then FastAPI. Every module adds one piece to one project, and every exercise is checked by tests rather than by reading an answer.

WHAT'S IN IT

• +Python fundamentals through typing, testing, and packaging, ending in a task-tracker capstone with 22 acceptance tests.
• +Gameya, a rotating-savings tracker, built one module at a time: models, admin, views, templates, a DRF API, an audit log via signals, and a pytest suite with factories.
• +Module 09 measures N+1 queries with a query-count test, then caches a computed summary and clears it on every relevant change.
• +The FastAPI track builds the Study API: async SQLAlchemy with Alembic, JWT auth, background jobs, Docker, and a Gemini call with rate limits, all tested without the network.
• +Public on GitHub with no solutions committed, and CI that checks lint, links, and that every test still loads.

ROLE

Solo author: the curriculum, lessons, exercises, reference solutions, the Django and FastAPI projects and their test suites, CI, and the review of each module.

NOTABLE DECISION

Modules were checked by breaking a working reference on purpose: a wrong cache key, an N+1 query, a model call made on the event loop. Every planted fault had to fail at least one test, so the suites prove they catch real mistakes, not only that the happy path runs.