this post was submitted on 04 Jun 2026
446 points (97.4% liked)

Technology

85155 readers
4637 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] uuj8za@piefed.social 77 points 1 day ago* (last edited 1 day ago) (7 children)

Google’s CEO says 75% of the company’s code is AI-generated.

Everyone should take this with a huge grain of salt. Like all other internal company stat reports, it's bullshit and manufactured.

Example: my company has recently introduced a gate on CI. All commits must have "Co-Authored-By: X". Technically, you can set X=None, but most people aren't doing that because we're not stupid and we know the commit history can easily be data mined and used to generate stats on who is or isn't using AI. And we don't want to get fired.

Result: 99% of all new commits use "Co-Authored-By: Claude". Every commit I make now has "Co-Authored-By: Claude". Am I using AI? FUCK NO. But, now I have to add that stupid line to any work I turn in.

[–] mcv@lemmy.zip 10 points 1 day ago

This is insane to me. Having a way to easily distinguish AI generated commits from human created ones makes a lot of sense, but lying that your honest, high quality handcrafted commit is AI slop makes it pointless.

That people feel they need to do this in order to protect their jobs is fucking insane and self destructive.

[–] criss_cross@lemmy.world 31 points 1 day ago

We have a commit skill we’re supposed to use. So for non-trivial work that I don’t want the AI to screw up i do it by hand then use the skill so it can vomit put a commit message and PR.

I get the shiny “Co-Authored-By: Claude” and burn a ton of tokens to make myself look “AI Fluent”

[–] Steve@startrek.website 14 points 1 day ago

Remember that part in The Big Short where the stripper is talking about all the houses she owns? Similar vibes.

[–] 0x0@infosec.pub 4 points 1 day ago

Microslop really went to shit after statements just like that. Can't wait for google to implode too

[–] masterspace@lemmy.ca 3 points 1 day ago* (last edited 1 day ago)

We're a small company so I do the opposite and am avoiding any co-authored tag being applied to the code I publish.

I review and test my code before it's published to make sure that it works and that it's the right solution to the problem, and I'm the one responsible for fixing it if it goes wrong late at night in prod.

That was the case when I was using Intellisense and codegen tools and that's still the case now.

That makes me the author.

Anything else is a lie, a violation of engineering ethics, and is flat out not SOC2, nor regulatorily compliant for anything that matters.

[–] A_norny_mousse@piefed.zip 5 points 1 day ago

Stark reality. Thank you.

[–] one_old_coder@piefed.social 3 points 1 day ago

Can't you script it with a git hook?