the security list went from 2-3 reports a week to 5-10 a day because everyone is running the same AI on the same code and nobody bothers to write a patch. finding bugs stopped being a contribution when the same tool hands everyone the same results
CompleteBrush9489 on
I think I’m seeing this “news” over and over again since 3 weeks ago.
more click bait spam story on a already cover topics a month or two go
Sixstringsickness on
I think the issue is not that they are AI generated, but whether or not they are of value.
Bug reports and tickets in general were previously gated by human resource, they were time consuming to diagnose and submit. Now that paradigm has been completely up ended.
I run into this same issue on my own projects, I am creating more tickets than I can resolve at this point in time. In theory, as the code base matures this will improve (barring feature creep), however; that will take a considerable amount of time.
Surfacing a bug, and determining the location of the problem often omits the blast radius of the associated dependencies. Sure, I can fix this, but now it just opened up another 10 issues that were relying on this sub-optimal original solution to fix one bug. I often find these issues like pulling on the thread of a sweater, at some point you’ll end up with a pile of yarn and no clothes on your back.
5 Comments
the security list went from 2-3 reports a week to 5-10 a day because everyone is running the same AI on the same code and nobody bothers to write a patch. finding bugs stopped being a contribution when the same tool hands everyone the same results
I think I’m seeing this “news” over and over again since 3 weeks ago.
Add it to the pile: https://www.reddit.com/r/linusrants/
Love it or hate it, the guy doesn’t hold back.
more click bait spam story on a already cover topics a month or two go
I think the issue is not that they are AI generated, but whether or not they are of value.
Bug reports and tickets in general were previously gated by human resource, they were time consuming to diagnose and submit. Now that paradigm has been completely up ended.
I run into this same issue on my own projects, I am creating more tickets than I can resolve at this point in time. In theory, as the code base matures this will improve (barring feature creep), however; that will take a considerable amount of time.
Surfacing a bug, and determining the location of the problem often omits the blast radius of the associated dependencies. Sure, I can fix this, but now it just opened up another 10 issues that were relying on this sub-optimal original solution to fix one bug. I often find these issues like pulling on the thread of a sweater, at some point you’ll end up with a pile of yarn and no clothes on your back.