• joey_builds@eviltoast.org
    link
    fedilink
    English
    arrow-up
    40
    ·
    6 hours ago

    What gets me is that this is roughly the best-case scenario for “capable hands” — Linus knows this codebase better than anyone alive — and a race condition plus a 9% read regression still slipped through on the first attempt. Reviews and testing caught it, which is the system working, but it moves the bottleneck from writing code to reviewing it. And review doesn’t scale the way generation does; skimming a patch is quick, but actually proving an LLM-assisted one is correct takes real effort. I say that as someone who uses AI tooling daily — reading code you didn’t write is genuinely more tiring than writing it, and that tax compounds the more you lean on generation. The maintainer-burnout angle might end up being the real story here, more than the AI one.

    • raspberriesareyummy@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      3 hours ago

      reading code you didn’t write is genuinely more tiring than writing it

      What I keep saying. Good take except that you don’t use “AI” tooling, you use copyright evasion slop tooling.

      • partofthevoice@lemmy.zip
        link
        fedilink
        English
        arrow-up
        5
        ·
        edit-2
        3 hours ago

        Verifying 10 pounds of incoherent architectural choices and over engineered submodules is certainly harder than reviewing tee bits of coherent human work.

        • Railcar8095@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 hours ago

          And verifying 10 pounds of incoherent architectural choices and over engineered submodules of human work is certainly harder than reviewing tee bits of coherent agent work.

          You are? I can also make false dichotomy fallacies!

          • partofthevoice@lemmy.zip
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            14 minutes ago

            The difference is that AI is prone to this issue, even a single agentic process. Humans only really run into this issue with large, disorganized teams.

            Humans burn out.

            https://maevyn.codes/decoherence

            edit: hold up. Presenting as though what I said works in reverse,

            verifying 10 pounds of incoherent architectural choices and over engineered submodules of human work is certainly harder than reviewing tee bits of coherent agent work.

            as though agentic and human contribution is equatable… wouldn’t that be false equivalency? Tisk tisk…

            Human work is not swappable with agentic work without tradeoffs, which is kind of why I was making a point at all.

    • Orygin@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      9
      ·
      5 hours ago

      Linus knows this codebase better than anyone alive

      Does he? Is it even possible to know the entirety of the Linux kernel within one head?

      • Bizzle@lemmy.world
        link
        fedilink
        English
        arrow-up
        8
        ·
        5 hours ago

        Does one need to know the entirety in their head to know it better than anyone else? If not Linus, who?

        • Orygin@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          5
          ·
          5 hours ago

          I’d argue the people who wrote the code for the various subsystems know more about it than the guys who “just” review and merge them.