124
Void Linux maintainer orphans 100+ packages over AI policy dispute (www.phoronix.com)
submitted 2 weeks ago by to c/programming@programming.dev
33 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 2 weeks ago (1 child)

I work in tech and I don't use LLMs. From my experience, they're catastrophic especially in those positions where they review code/actions. Reviews are the last line of defense against bad code, bugs, vulnerabilities or destructive actions. Giving that role to an RNG parrot that is often confidently wrong is almost suicidal.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 2 points 2 weeks ago* (last edited 2 weeks ago)

    From my experience, they’re catastrophic especially in those positions where they review code/actions.

    That's interesting. I am currently searching for ways that I can use them a bit to chill-pill our CTO without sinking the company (which is very deep in the water with technical debt).... at least until I get another job.

    Can you expand why they are that bad in this use?

    My current idea is to pin up new architecture by hand, define new interfaces by hand, and then let the LLM occasionally fill in a function body. And maybe, maybe, an "ai refactored" branch which has just the purpose to showcase what happens if one is not careful - and will never be merged, at least not by me.

  • permalink
  • fedilink
  • source
  • parent