My goal at the onset of writing this essay was to celebrate the parts of Django that I, in Buttondown writ large, have found so useful and enduring. The framework’s balanced opinionatedness makes it invisible over time, blending seamlessly with Pythonic code and business logic.

Middlewares are a standout. They’re simple functions that hook into the request/response cycle, enabling routing, tracking, CSP headers, and even stamping every response with the deployed git SHA via the build version header. This single middleware keeps the codebase lean and powerful.

Every model inherits from a base that adds UUIDs, creation dates, type‑prefixed IDs, change hooks, and soft‑delete behavior. Adding provenance tracking or validation is a one‑line method; no migrations or refactors are needed, demonstrating Django’s modular, piecemeal extensibility.

Behaviour lives in action modules, views are pure functions in separate files, and testing relies on pytest‑django with hand‑rolled fixtures for speed. Together, these patterns create a maintainable, testable, and efficient system that the author proudly attributes to Django’s design.