• Limerance@piefed.social
    link
    fedilink
    English
    arrow-up
    9
    ·
    12 hours ago

    Realistically what happens is the code review is done under time pressure and not very thoroughly.

    • TehPers@beehaw.org
      link
      fedilink
      English
      arrow-up
      2
      ·
      31 minutes ago

      This is what happens to us. People put out a high volume of AI-generated PRs, nobody has time to review them, and the code becomes an amalgamation of mixed paradigms, dependency spaghetti, and partially tested (and horribly tested) code.

      Also, the people putting out the AI-generated PRs are the same people rubber stamping the other PRs, which means PRs merge quickly, but nobody actually does a review.

      The code is a mess.

        • TehPers@beehaw.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          6 minutes ago

          Because if I spent my whole day reviewing AI-generated PRs and walking through the codebase with them only for the next PR to be AI-generated unreviewed shit again, I’d never get my job done.

          I’d love to help people learn, but nobody will use anything they learn because they’re just going to ask an LLM to do their task for them anyway.

          This is a people problem, and primarily at a high level. The incentive is to churn out slop rather than do things right, so that’s what people do.