1213
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Feb 2026
1213 points (95.6% liked)
Programmer Humor
29765 readers
1044 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
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.
Oh shit… I’ve got terabytes of code I’ve written over the years that I’d be hard-pressed to even begin to understand today. The other day I discovered a folder full of old C++ libraries I wrote 20+ years ago, and I honestly don’t remember ever coding in C++.
There is absolutely no way you wrote terabytes of code lmao.
True enough, and I expected to get checked on that.
Regardless… along with the archives, assets and versioned duplicates, my old projects dating back to the 90s somehow now fill multiple TB of old hard drives that I continue to pack-rat away in my office. Useless and pointless to keep, but every piece was once a priority for someone.
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!