• HiddenLayer555@lemmy.ml
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    3
    ·
    edit-2
    3 days ago

    This is where commit based version control can help mitigate the damage or detect it early. The golden rule in AI assistance in programming (if you’re going to use it) is to check the changes to make sure you understand everything before you commit it. If documents had a git-like version control system it would be easier to detect corruption early.

    Or just use Markdown files in a git repo IDK

    • eldavi@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 days ago

      Or just use Markdown files in a git repo IDK

      my pleas to my new management to do this fall on deaf ears, but they’re gung-ho about ai.

    • jtrek@startrek.website
      link
      fedilink
      arrow-up
      6
      ·
      3 days ago

      That’s not how humans work. We’re lazy.

      You ever use snapshot tests? They’re garbage. They’re garbage because people glance at a 300 line diff and go “that seems right”, because a good chunk of the time it is. But some portion of the time, it’s borked up.

      Having it in git doesn’t solve that problem.

      • SineSwiper@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        2
        ·
        2 days ago

        That’s not how humans work. We’re lazy.

        I’m not. Stop being lazy. Review your damn code.

        LLMs don’t work if you don’t put the effort in. They save time when you do.