Python Full Stack
Lab Curriculum.

BUG FOUND: theory-strong graduates who cannot debug a Django/React app or ship a feature.

$ step-01 brushup // weeks 1–2 — Topics taught:

1. Django models, views, URLs, and the admin — reading and fixing a starter app.
2. Django ORM queries, migrations, and common query mistakes.
3. React components, props, state, and hooks — fixing a broken form and a stale list.
4. REST APIs with Django REST Framework: serializers, status codes, and error responses.
5. Git branching, commits, and pull requests; reading stack traces and browser / server logs.
6. Authentication basics: sessions, tokens, and protected routes.

$ step-02 debug // weeks 3–4 — Production Debugging. Tools: Git, Django shell, browser DevTools, pytest, PostgreSQL / SQLite logs.

• BUG #1: Login API returns 500 for valid users — trace the traceback, find the broken serializer field, fix it, add a regression test.
• BUG #2: Auth token refresh fails after expiry — reproduce, fix the refresh flow, prove old and new tokens behave correctly.
• BUG #3: A list page slows to seconds — find the N+1 query, fix it with select_related / prefetch_related, show before/after query counts.
• BUG #4: React state bug loses form data on navigation — reproduce, fix state handling, verify no data loss on back/forward.

$ step-03 navigate // weeks 5–7 — Codebase / System Navigation:

• Trace a user request end-to-end (React → API → Django view → ORM → database → response) in a large legacy Django + React codebase with incomplete docs, and document the flow.
• Refactor one messy module (split a god view, rename misleading variables, extract a helper) without changing behaviour; all existing tests must still pass.
• Add a new feature (e.g. search + filter + pagination) in unfamiliar code, with tests and a reviewed pull request.
• Review a peer's pull request: find at least one real defect, one missing test, and one readability issue.

$ step-04 ship // weeks 8–9 — Shipping Features: capstone sprint — build and deploy a full product with auth, CRUD, API, and frontend; write a README, demo it live, and present a post-mortem of one bug found during the sprint.

$ ship → PROOF — exact output: live-deployed product URL, GitHub repo with reviewed pull requests, a regression-test report, and a one-page fix report for the capstone bug.

$ run --lab python-full-stack → ✓ SHIPPED, job-ready