113
AI is creeping into the Linux kernel - and official policy is needed ASAP (www.zdnet.com)
submitted 1 year ago by to c/linux@programming.dev
26 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 38 points 1 year ago* (4 children)

I would be deeply uncomfortable to work in an environment where one couldn't ask the author of a change for insights or rationale, because the author let some machine write it and therefore lacks any deeper understanding.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 34 points 1 year ago (3 children)

    For me it's grounds to deny a merge request. Can't explain your code? Then it's evidently not clear enough. Come back when it is.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 28 points 1 year ago (2 children)

    Should apply to all code too. Doesn't matter if you, stackoverflow or AI wrote it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -3 points 1 year ago (1 child)

    you think linux kernel problems are solved on stack overflow? app coding vs lib coding is a huge gap in what the code looks like, I don't even want to think of kernel code.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 1 year ago

    Kernel code isn't fundamentally different. Even designing hardware is still basically just coding, despite what hardware designers claim. (They think it's fundamentally different because many things happen in parallel in a single cycle.)

  • permalink
  • fedilink
  • source
  • parent