3 ms·

Meta: I love this style of article and I wish it was more common and in more detail. "How to build perfect software in Django" is incredibly hard to write, but

• jayd16 3y ago
  Have we gone full circle? "10 hot tips for the perfect app" was a style that was so over used and clickbaity that HN rewrites the title to remove the count.
  • jamestimmins 3y ago
    I think my comment was unclear. I don't find the listicle to be the interesting part; rather, articles that focus on anti-patterns. A lot of architectural mistakes are because people make fairly straightforward mistakes that could be easily avoided with good resources focused on what not to do.
• 1920musicman 3y ago
  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.
  • jamestimmins 3y ago
    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.