1208

Is Windows FOSS now? (lemmy.blahaj.zone)

submitted 2 days ago by not_IO@lemmy.blahaj.zone to c/programmer_humor@programming.dev

227 comments fedilink hide all child comments

https://zomglol.wtf/@jamie/116059523957674208

https://www.congress.gov/crs_external_products/LSB/PDF/LSB10922/LSB10922.8.pdf

you are viewing a single comment's thread
view the rest of the comments

[-] Michal@programming.dev 32 points 2 days ago

Counterpoint: how do you even prove that any part of the code was AI generated.

Also, i made a script years ago that algorithmically generates python code from user input. Is it now considered AI-generated too?

[-] Dyskolos@lemmy.zip 2 points 2 days ago

Guess you can't really prove that, unless you leave comments like "generated by Claude" in it with timestamp and whatnot 😁 Or one can prove that you are unable to get to that result yourself.

So nonsense, yes.

[-] mattvanlaw@lemmy.world 2 points 2 days ago* (last edited 2 days ago)

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 2 days ago* (last edited 2 days ago)

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.

[-] sunbeam60@feddit.uk 2 points 1 day ago

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 1 day 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.

[-] mattvanlaw@lemmy.world 1 points 1 day ago

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 1 day ago

Hence the "took down production"

[-] mattvanlaw@lemmy.world 1 points 1 day 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!