• MangoCats@feddit.it
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 hour ago

    An LLM cannot understand intention, it just makes statistical guesses that are often wrong.

    True, when you give a prompt like: “make me a contact management / constant contact app which I can deploy on AWS and scale to 100,000 users.” you get, mostly garbage. If you specify how you want the UX to flow, what fields are most important, what fields should be included in deeper interfaces, what the scheduling looks like, how it gets tuned, what the reports look like, etc. etc. etc. - in other words: give it real requirements and specifications.

    Then, pay attention as it develops, you’ll ususally find that the requirements you gave it aren’t exactly what you really wanted, and when you see what it built that doesn’t match with your visions, you can have it revise the requirements and specs.

    • ViceroTempus@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      6 minutes ago

      Sure, but for me its just faster to write it myself, in a way that needs to fit into the project. And while I’m aware you can give this context to an LLM, it still can’t read what your previous intentions were, nor what they are currently. So its hard for it to build on it.

      To me they’re best as auto-complete, or research tools in the same vein as StackOverflow. Something to help speed up your existing workflow. Also good at translating both spoken languages, and functions into other coding languages. Everything else seems to get in the way for me.