• Appoxo@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      1
      ·
      5 minutes ago

      How about this:
      Humans (or humans assisted by AI) write documentation
      Users (devs includes) can either choose to read the manual the old fashioned way or utilize it like a sort of swagger api documentation to give

      1. Information to a question (How to do x)
      2. Provide a general example
      3. (Assuming it’s used with an IDE or has information about the project) Provide a personalized example on the implementation.
    • Hupf@feddit.org
      link
      fedilink
      arrow-up
      13
      arrow-down
      1
      ·
      edit-2
      1 day ago

      Have you tried to use AI for <thing>? It’s pretty shit.

      • Tja
        link
        fedilink
        arrow-up
        5
        arrow-down
        1
        ·
        1 day ago

        Translation, proofreading, summarizing, brainstorming, boilerplate code, protein folding…

        • stetech@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          1 day ago

          protein folding

          We’re at the point where, due to how b2c tech services work, I think a lot of people think AI === LLM

    • milicent_bystandr@lemm.ee
      link
      fedilink
      arrow-up
      7
      ·
      edit-2
      2 days ago

      I’ve used AI to give me a good enough guess that I know the right keywords to search for too find the real documentation.

    • thedeadwalking4242@lemmy.world
      link
      fedilink
      arrow-up
      4
      arrow-down
      3
      ·
      2 days ago

      I’ve had pretty good experience with using AI to find what I’m looking for in documentation, especially if the docs are in context

      • SatyrSack@feddit.org
        link
        fedilink
        English
        arrow-up
        16
        ·
        2 days ago

        I think they mean having an AI read code and then write documentation for it. Not having an AI read documentation.