• DireTech@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 days ago

    For my projects, finding the cause of a bug is rarely a problem once it’s reported. It’s fixing it in a way that doesn’t negatively impact things upstream or downstream that’s a pain.

    How’s AI supposed to help when we’ve got to negotiate with several other stakeholders on what changes we’re going to make?

    • ryannathans@aussie.zone
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      2
      ·
      2 days ago

      So because you talk to people sometimes, there’s nothing AI can assist on? That doesn’t really make any sense

      • Jack@slrpnk.net
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 days ago

        I think op meant that when you know your project and infrastructure debugging is not that big of an issue. Solving a problem affecting multiple parties can be more complicated.

        • DireTech@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          3
          ·
          2 days ago

          Yeah fixing that one problem isn’t an issue. It’s that the fix probably affects some other service. When you’re dealing with a bunch of integrated systems, some of which are over a decade old, bugs aren’t just fixing a few lines of code in your part and calling it good.

          I’m sure it can be useful for smaller self contained projects. A lot cheaper and easier to review the AIs changes on those too.