An internal memo dispatched by senior execs at Red Hat suggests the software biz is starting to push AI tooling within its Global Engineering department. RHEL may be about to get some Windows 11-style “improvements.”

It carries the heading “Engineering that’s evolved and amplified for the AI era,” and for any AI skeptics in the developer teams at Red Hat, the tone of the email may raise alarm bells. The times are changing, it states.

  • bookmeat@fedinsfw.app
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 days ago

    The real concern here is that they intend to push velocity. Senior devs are already struggling to keep up with vetting these velocitized changes and are sending out warnings that quality and security will suffer. IMO the tech isn’t mature enough to run unsupervised and transforming senior devs into code reviewers is a big mistake.

  • becausechemistry@piefed.social
    link
    fedilink
    English
    arrow-up
    1
    ·
    7 days ago

    Duh, it’s run by IBM. The most brain-rotted management suite on earth. All they do is chase the cool new hotness, and unfortunately it works for them – they’re mostly selling to other brain-rotted manager types. (The end users, as usual, get hosed.)

    • ag10n@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 days ago

      IBM like Apple has been cautious about generative AI Not to say they don’t, their Granite models work great for personal machines.

      Choice is always key, embedding it in the OS is a terrible idea.

  • IrateAnteater@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    7 days ago

    Hopefully it’s just AI tools for development they’re talking about (though that will be bad enough if RHEL becomes vibecoded slop) and not stupid AI “features” baked into the OS.

    • badgermurphy@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 days ago

      I think the inverse might actually be preferable. If there’s slop in the code base, that will be harder to avoid than whole modules that you can just not install.

      While neither is preferable, putting it in the development is more insidious.