22
Google says it fixed more Chrome bugs in June than over the past 2 years, thanks to AI (blog.google)
submitted 2 months ago* (last edited 2 months ago) by to c/technology@lemmy.world
14 comments fedilink hide all child comments
 

cross-posted from: https://piefed.world/c/tech/p/1299254/google-says-it-fixed-more-chrome-bugs-in-june-than-over-the-past-two-years-thanks-to-ai

you are viewing a single comment's thread
view the rest of the comments
[–] 28 points 2 months ago (6 children)

What they forgot to add: in the same time, they've also managed to create more bugs than they've fixed, thanks to AI.

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] 4 points 2 months ago (2 children)

    That doesn't seem to be the case, what are you basing this on?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 7 points 2 months ago (1 child)

    Anecdotal but I use chrome for work and the June/July updates this year were the only time all my passwords/history/session cookies were totally wiped by an update. That has been pretty annoying to recover from and I know it happened because I updated Chrome for bug testing.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [+] -6 points 2 months ago

    you represent all of humanity great hedgehog. i will base all my critical thinking based on your singular glorious anecdotes. they make me laugh and cry <3

    CURSES TO CHROME. FUUUUCK AIIIIIIIII

  • permalink
  • fedilink
  • source
  • parent
  • [–] 0 points 2 months ago (2 children)

    I don't see how ai being used by the same software dev would lead to worse work, if they use it correctly on a task by task basis in cases where it doesn't need a lot of context/memory that keeps getting overwritten. I feel like they 100% use it as autofill or for structure that they check through while the companies claim it's just straight up aigenerated with no human input to boost their stock value.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 2 months ago (1 child)

    Because reading code isn't the same act as writing it.

    It is way easier to miss a subtle issue when you are reviewing a bunch of code you didn't write than it is in code you actually wrote yourself using your own brain.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 2 months ago

    That makes sense actually, I haven't programmed since freshman year of college and forgot how you hold it in your head. (which is stupid, while I use ai to mess with threejs, I still use blender geonodes manually which work the same as coding manually kinda, looking at other people's work it can be hard to process compared to when you make the tree yourself)

  • permalink
  • fedilink
  • source
  • parent