• Gork ( Gork@sopuli.xyz ) 
    link
    fedilink
    English
    arrow-up
    31
    ·
    8 months ago

    Sounds like all the hard work they did refactoring Windows 10 is gonna go to waste with the new AI vibe coding in Windows 11.

  • maria ~ ( Smorty@lemmy.blahaj.zone ) 
    link
    fedilink
    English
    arrow-up
    12
    ·
    8 months ago

    just 30%?..

    that should cause much less harm.

    are the devs there that lazy? do they just not review the code?
    I thought that especially these companies do code review and such…

    • gegil ( gegil@sopuli.xyz ) 
      link
      fedilink
      English
      arrow-up
      8
      ·
      8 months ago

      30% is last year news. Now windows 11 in entirely developed by ai. How it works:

      1: Ai hallucinates a new feature.

      2: Ai agents generate enough code to meet investors demands.

      3: Ai Qa agents are being gaslighted into verifying code.

      4: The result is a feature which does not even work, while also ten breaking changes in core system features, which worked completely fine, but ai rewrote them anyway.

    • megopie ( megopie@lemmy.blahaj.zone ) 
      link
      fedilink
      English
      arrow-up
      7
      ·
      8 months ago

      I suspect it’s largely more the result of failing internal organization. Like, a detached from reality and ideologically motivated faction with in corporate leadership has seized control of the company and fired anyone who told them they were being idiots or opposed their initiatives. People are probably getting promoted or hired to management positions based on their ability to tell leadership what they want to hear rather than their ability to actually run things. Everyone lower down has internalized that telling the higher ups what’s going on will get them fired and only is telling them what they want to hear. Resources and people got diverted away from projects that the management doesn’t care about (have no potential to drive growth), and they’re just assuming that the “increase in productivity of AI” will make up the difference. Now everything is melting down and their core product is losing market share while the new products intended to drive growth are failing to see meaningful adoption. Heads will probably role, but it’s unlikely it will be the people who are causing the problem.

      That’s what it looks like to me from the outside.

    • Ephera ( Ephera@lemmy.ml ) 
      link
      fedilink
      English
      arrow-up
      6
      ·
      8 months ago

      I mean, for the bugs in the screenshot, it is more than plenty, if even just 1% of bad code slips through.

      And AI-generated code is extremely time-consuming and tricky to review, because you can’t assume there to be rhyme and reason to the changes, so I would be surprised, if they actually put in all the effort to properly review.

    • Actually more recently I was setting up an older, but still great, canon printer, with a new windows 11 machine. I had to install a driver for windows 7/8/8.1/10 because there is no working windows 11 driver and the 7/8/8.1/10 driver still works. XD

  • 1rre ( 1rre@discuss.tchncs.de ) 
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 months ago

    I’ve started using AI pretty heavily for writing code in languages I’m not as confident in (especially JS and SQL) after being skeptical for a while, as well as code which can be described briefly but is tedious to write, and I think the problem here is “by” - it would be better to say “with”

    You don’t say that 90% of code was written by code completion plugins, because it takes someone to pick the right thing from the list, check the docs to see it’s right, etc.

    It’s the same for AI, I check the “thinking”/planning logs to make sure the logic is right, and sometimes it is, sometimes it isn’t, at which point you can write a brief psudocode brief of what you want to do, sometimes it starts on the right path then goes off, at which point you can say “no, go back to this point” and generally it works well.

    I’d say this kind of code is maybe 30-50% of what I write, the other 50-70% being more technically complex and in a language I’m more experienced in, so I can’t fully believe the 30% figure when you’re going to be having some people wasting time by not using it when they could use it for speedup, and others using it too much and wasting time trying to implement more complex things than it’s capable of - this one irks me especially after having to spend 3½ hours yesterday reviewing a new hire’s MR that they could’ve spent actually learning the libraries, or I could’ve spent implementing the whole ticket with some time left over to teach them.