PROFESSIONAL DJANGO ENGINEERING SERIES #7 The MRO is not magic. Once you understand what dispatch() does and why mixin order matters, class-based views become entirely predictable. Class-based views are one of Django’s most divisive features. Some developers swear by them. Others find them opaque, hard to debug, and more trouble than they are worth. Both camps have a point. The difference, in my experience, is almost always understanding. Developers who find CBVs confusing are typically using them without understanding three things: what dispatch() does, how Python’s MRO determines which method gets called, and why mixin order is not arbitrary. Once those three things click, CBVs become predictable. Let me show you each one. The problem with class-based views is not that they are complex. It is that their complexity is hidden. A function-based view shows you everything. A class-based view shows you only what you override — the rest is inherited, and inheritance is invisible until it breaks.…