I use AI as an editor on informational writing all the time and it's good at pointing out flaws in what I wrote. But I don't really love reading a document that's obviously in the voice of Claude if you're asking for my opinion on it. But it kind of depends on the writing -- a change request description, most people are too lazy to do better than the AI would, and there are other kinds of documentation that normally just wouldn't get done. But like for a design doc where you're asking me to pore over it now even though I don't necessarily get anything out of it it's distasteful when I see phrases that are obviously from AI.

If someone manages to devise a way to prove something was written by a human they will make a lot of goola

I see this on my team. I honestly thought as engineers we'd all understand the limitations and nuance a bit better. Right now it's kind of a shit show. In addition to seeing my teammates open huge AI generated PRs and just asking for review without them having done much verification, I'm also seeing my teammates (smart ones whom I respect) use AI to "do code reviews". And we already have automated AI code reviews added to our PRs. So now I'm sometimes getting hallucinated BS responses from "human" reviews.

This makes me absolutely SURE that the general public is fucked and that we're going to start seeing huge AI generated fuckups on a regular basis. If people in this industry, basically experts compared to the general public, are misusing this tech in such seemingly obvious ways, imagine the ways non technical people will misunderstand and misapply it. Of course, with the help of overhyped BS from everyone hyping and selling it.

Yup, I always phrased this as “if you can’t be arsed to write it, I won’t read it”

<begin devil's advocate>

This is extra work on human.

Many artist and content creator is now asked to show the "behind the scene" or a full session recording, which nobody care enough to check. This is frustrating and demotivating the artist.

Expect the same demotivating effect on the software contributor.

If you think reading _forwarded_ AI response are cheap, you can run your own LLM. It is the same amount work on you

</end devil's advocate>

This has been my rule since the moment generative AI hit the scene. If you're not willing to put in the effort to create the thing, why should I put in effort to consume it?

We just agreed on our team that we’re not posting AI-generated text into comms with humans.

Related - this was posted in march: https://stopsloppypasta.ai/en/

> For human code review requests, I always review my AI-generated code first.

I remember a time in the ancient past (2025 maybe) that your PR was your responsibility, whether or not you typed it with your meat fingers or cranked it out of the Giant Plagarism Machine. It’s absurd to think that the above quote is now something approaching controversial.

This is just an old engineering principle of work amplification. For an input of x you shouldn’t routinely do nx. If you do you’ll get flooded. Debounce, throttle, load shed, improve throughput and latency. Lots of solutions. Just map it to the problem and apply.

In the past you had coworker who produced volumes of code. Same principle.