Computer output cannot be copyrighted, don’t focus on it being “AI”. It’s not quite so simple, there’s some nuance about how much human input is required. We’ll likely see something about that at some point in court. The frustrating thing is that a lot of this boils down to just speculation until it goes to court.
OP is obviously ignorant of how much tooling has already helped write boiler plate code.
Besides AI code is actually one of the things that’s harder to detect, compared to prose.
And all that said, AI is doing an amazing job writing a lot of the boilerplate TDD tests etc. To pretend otherwise is to ignore facts.
AI can actually write great code, but it needs an incredibly amount of tests wrapped around and a strict architecture that it’s forced to stick to. Yes, it’s far too happy sprinkling magic constants and repeat code, so it needs a considerable amount of support to clean that up … but it’s still vastly faster to write good code with an AI held on a short leash than it is to write good code by hand.
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.
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.
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.
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.
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!
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?
Computer output cannot be copyrighted, don’t focus on it being “AI”. It’s not quite so simple, there’s some nuance about how much human input is required. We’ll likely see something about that at some point in court. The frustrating thing is that a lot of this boils down to just speculation until it goes to court.
OP is obviously ignorant of how much tooling has already helped write boiler plate code.
Besides AI code is actually one of the things that’s harder to detect, compared to prose.
And all that said, AI is doing an amazing job writing a lot of the boilerplate TDD tests etc. To pretend otherwise is to ignore facts.
AI can actually write great code, but it needs an incredibly amount of tests wrapped around and a strict architecture that it’s forced to stick to. Yes, it’s far too happy sprinkling magic constants and repeat code, so it needs a considerable amount of support to clean that up … but it’s still vastly faster to write good code with an AI held on a short leash than it is to write good code by hand.
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.
deleted by creator
There is absolutely no way you wrote terabytes of code lmao.
deleted by creator
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.
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.
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.
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.
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.
Hence the “took down production”
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!
Uh, yes, that’s what they call a generative ai