Tips for Building High-Quality Django Apps at Scale
I&#x27;m so glad to see the mention of &quot;app&quot; directories here. I&#x27;ve only dabbled in Django development, but I&#x27;ve always thought the desire to divide things into apps didn&#x27;t really make any sense. It felt like the developers of Django had said &quot;well, intuitively, there <i>must</i> be some unit of reuse at this level&quot; and then stuck the notion of apps in there in an attempt to provide that reuse.<p>This seems to me to be somewhat unpythonic, unnecessary complexity introduced right from the start - why not make the reuse optional?. The file system layout becomes confusing as a result. More generally, I would expect that the most minimal Django site would be a single file, that would seem most Pythonic, but it isn&#x27;t designed like that. Django doesn&#x27;t &quot;feel&quot; like most Python projects do.<p>I&#x27;ve always assumed this must be because I&#x27;m a total noob&#x2F;idiot when it comes to real-world development, and that projects like Django must be doing things right and I just don&#x27;t get it  (although it remains entirely possible that this is the case).<p>It&#x27;s heartening, however, to see I&#x27;m at least not _entirely_ wrong for having a gut unease about this, and it makes me wonder how on earth I can judge whether it&#x27;s me or a given framework&#x2F;language in the general case.<p>Do I have reverse Dunning–Kruger? Or did I just guess right in this case? I have no idea.