• Feathercrown@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 months ago

          “Writing code well” includes several relavant things:

          • Security implications
          • Stability and edge case handling
          • Performance
          • Quality of output (ie. for UI/UX)
          • Readability (Agents need to read to make changes too! Violating DRY/SOLID/etc. could still cause issues!)

          As far as I’m aware you do currently still need a human to ensure stuff like this is followed. People use agents because they don’t care about the above, or because they can get close enough and intervene to fix any issues that appear.

        • hirihit640@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 months ago

          If that’s the case; why use the agent to edit the code in the first place?

          Agents for generation, humans for review

    • brian@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 months ago

      your research paper:

      llm generated agent.md files are harmful. handwritten ones on average don’t have an effect on ability to complete a task

      thread article:

      agents keep signing off on commits wrong. we added it to the agents.md and now they don’t

      benchmarks notoriously don’t measure the likelihood that the results would be merged by maintainers, just that they passed a test

      the old style “repo map” agents.md files that every tool used to create is no longer useful, but of course things that would otherwise be repeated prompts are still good. I cut the ones at work down from hundreds of lines each to tens. without those last few lines the amount of iteration I do - both with agent and when reviewing PRs - goes up significantly