Challenge 2: A Solo Developer's Small Django App — Solution Walkthrough

Recommended tool:

PyCharm.

Applying Chapter 8's own five questions:

  - Task duration/scope: sustained project work, not a quick edit —
    favors a real editor or IDE over nano/Vim.
  - Project complexity: a small-to-medium Django application — enough
    structure (models, views, URLs, templates) to genuinely benefit
    from Django-aware tooling specifically.
  - Environment: a local laptop with everything installed — no remote/
    minimal constraint ruling out a full IDE.
  - Language-specific tooling needs: genuinely high here — Django-
    aware project structure, template completion, and virtual
    environment management (Chapter 6's own material) all apply
    directly to this exact kind of project.
  - Budget: not stated as a constraint, and PyCharm's own free
    Community edition doesn't even require paying — though Django
    tooling specifically is Ultimate-only (Chapter 6), so Ultimate
    would genuinely be worth it here given how directly Django support
    applies.

Why PyCharm specifically, not IntelliJ IDEA or WebStorm:

This is a Python-specific project with real, applicable Django tooling
needs — exactly the profile Chapter 6 described PyCharm as built for,
distinct from IntelliJ IDEA's own Java/Kotlin focus or WebStorm's own
JS/TS focus.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that Chapter 8's own framework can be applied to
a genuinely new scenario not covered directly in the capstone's own
five examples, correctly reasoning through each question rather than
just pattern-matching to "Python project → PyCharm" without
justification.