Cursor, an ai/agentic-first ide, is doing this with a blame-style method. Each line as it's modified, added DOES show history of ai versus each human contributor.

So, not nonsense in probability, but in practice -- no real enforcement to turn the feature on.

[–] Rooster326@programming.dev 2 points 17 hours ago* (last edited 17 hours ago) (2 children)

Why would you ever want this?

If you pushed the bug that took down production - they aren't gonna whataboutism the AI generated it. They're still going to fire you.

[–] mattvanlaw@lemmy.world 1 points 11 hours ago (1 children)

Sorry, but as another reply: pushing bugs to production doesn't immediately equate to firing. Bug tickets are common and likely addressing issues in production.

[–] Rooster326@programming.dev 1 points 9 hours ago (1 children)

Hence the "took down production"

[–] mattvanlaw@lemmy.world 1 points 4 hours ago

I guess you mean like full outtage for all users? My bad just a lot of ways to take the verb "down" for me. Still, though, what a crappy company to not learn but fire from that experience!

[–] sunbeam60@feddit.uk 2 points 13 hours ago (1 children)

It makes little difference IMHO. If you crash the car, you can’t escape liability blaming self driving.

Likewise, if you commit it, you own it, however it’s generated.

[–] mattvanlaw@lemmy.world 2 points 11 hours ago

It's mainly for developers to follow decisions made over many iterations of files in a code base. A CTO might crawl the gitblame...but it's usually us crunchy devs in the trenches getting by.