• keisatsu@infosec.pub
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    13 days ago

    and in the process he introduced a race condition, a performance regression costing up to 9% when making reads of files around 1 MiB and dumped the responsibility of fixing his mess on co-maintainers and went on vacation.

    • monkeyslikebananas2@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      13 days ago

      Yeah but it sounds like three steps forward half a step back. Also, reviews/testing caught it. Sounds like the system is working. I’ve written quite a few race condition bugs in my 25 year career. That nobody caught until weeks in prod.

      I understand the reluctance of AI but there’s no denying that AI in capable hands can be useful.

      • keisatsu@infosec.pub
        link
        fedilink
        English
        arrow-up
        1
        ·
        13 days ago

        if Linus, who has worked with the language AND the project for decades, can’t find a race condition and a performance regression in his VERY FIRST LLM-assisted commit, then just maybe we should accept that humans are fucking horrible att catching the mistakes that clankers make and stop deluding us into thinking that this is the future of software engineering.