• Pennomi@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    12 days ago

    Because it’s not worth inventing a whole tool for a one-time use. Maybe you’re the kind of person who has to spin up 20 similar Django projects a year and it would be valuable to you.

    But for the average person, it’s far more efficient to just have an LLM kick out the first 90% of the boilerplate and code up the last 10% themself.

    • Feyd@programming.dev
      link
      fedilink
      arrow-up
      15
      ·
      12 days ago

      I’d rather use some tool bundled with the framework that outputs code that is up to the current standards and patterns than a tool that will pull defunct patterns from it’s training data, make shit up, and make mistakes that easily missed by a reviewer glazing over it

      • Pennomi@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        12 days ago

        I honestly don’t think such a generic tool is possible, at least in a Django context. The boilerplate is about as minimal as is possible while still maintaining the flexibility to build anything.

        • Feyd@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          11 days ago

          If it’s as minimal as possible, then the responsible play is to write it thoughtfully and intentionally rather than have something that can make subtle errors to slip through reviews.