Model-View-Controller (MVC) through the ages and in Django
summary
MVC retains practical value: it maps to Django as template = view and Django view = controller, with models sitting in models.py. Historical examples span Smalltalk (1979) to Java Swing and modern Django. Concrete advice: extract query logic (e.g. latest_book lookup) into model methods to avoid duplication and improve discoverability. Notes on tooling: model managers and custom QuerySets belong to the model, DRF serializers act like views, select_related/prefetch remain a thorny performance edge case (AutoPrefetch only partial fix).
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 0:45History of MVC pattern
- 6:35MVC in 2013 and Django
- 9:05MVC components in Django
- 12:13MVC as mental representation
- 14:41MVC family of patterns
- 16:07Why MVC matters in software
- 19:59Practical MVC in Django
- 23:13Q&A session
related talks
24mMighty Model Managers
39mDjango Views: Functions, Classes, and Generics
01h 06mEffective Django
21mBuilding maintainable Django projects: the difficult teenage years
26mMind your own business view controller
45mKeynote: All The Ways To Use Django with Zags
46mIntroducing Django REST framework
33mThe D is Silent: Challenges in Teaching Django