IMO "15 common Django architectural mistakes" is a less useful focus for these types of posts. Architecture can't be taught by listing quick tips. Or at least not only by listing quick tips.
The unfortunate reality is that in many (most?) cases when inexperienced engineers face these challenges, it's too late to follow quick tips... their company's Django app has been set up 10 years prior, and now they have dozens upon dozens of layers of abstraction in the codebase.
Teaching how to think about architecture, how to evaluate options and how to make decisions is a more reliable and applicable skill.
It definitely wouldn't be sufficient on it's own, so it's no substitute to understanding architecture. I think it's more a useful technique for ways of learning architecture that is often underexplored. Most posts focus on what to do, and few seem to focus on what not to do. Shifting the balance somewhat would be valuable IMO.
The unfortunate reality is that in many (most?) cases when inexperienced engineers face these challenges, it's too late to follow quick tips... their company's Django app has been set up 10 years prior, and now they have dozens upon dozens of layers of abstraction in the codebase.
Teaching how to think about architecture, how to evaluate options and how to make decisions is a more reliable and applicable skill.