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

    It lets me focus on the software architecture, not the minutiae. It feels exactly like when I ran a team of brand new interns. They require a lot of hand holding but with the right direction they get good at their jobs very fast.

    • astropenguin5@lemmy.world
      link
      fedilink
      English
      arrow-up
      23
      arrow-down
      1
      ·
      2 days ago

      I think the problem is that for now, it will always continue to require that hand-holding, whereas interns/new programmers will need less and less over time and become more independent over time

      • MangoCats@feddit.it
        link
        fedilink
        English
        arrow-up
        2
        ·
        12 hours ago

        I find that I get the best results when I develop a suite of documents in parallel with the code: requirements, architecture, designs, lessons learned, indexes into those documents, traceable ID tags on atomic, testable item descriptions. Development plans. When a new agent is introduced to the project, it can “get up to speed quickly” by jumping to the current working point on the development plan and indexing into all the relevant details in the other documents before even starting to read the existing code.

        That working method itself is evolving, and each new LLM driven project builds on the previous successful projects’ processes…