>However, I have a new policy.

>If you’re not bothered enough to review and edit it...

>...then I’m not going to bother reading it.

Just playing Devil's Advocate here, but we've had copywriters and editors for generations now. Not reading something because AI did the post-writing work feels kinda weak. Skip stuff started from AI, fine, but this is just because it's AI, not because the author didn't do the task. And I do get the point is that if an AI did /most/ of the work, ok to that, too, but not post-write processing alone.

I think the main reason many people (including me), very often, lack the motivation to read content that is likely generated by AI is the suspicion that it comes from a place of intellectual laziness. Another reason, based on personal experience, is that AI content may suffer from too much verbosity, too much jargon and over-confidence, which makes the reading experience feel fake and border-line irritating. In many cases the content may have very little to no nuance, which is ultimately a waste of time.

As an anecdote, someone posted a blogpost on Linkedin on using agents to implement a driver to access PCIe devices over TCP/IP. I was intrigued because that's not an easy task for several reasons, like handling PCIe interrupts and DMA. For exmaple, how does the remote machine map the device's PCIe BARs? And when it issues I/O to the devices registers, how are these reads and writes transferred to the remote device. In the end, this is just some virtual memory. In a local machine, this is either directly mapped to the PCIe physical addresses or some IOMMU virtual address space which is then translated by the hardware upon CPU/device/VM access.

After reading the long verbose promising article, in the end, the guy (with the help of the agent) only managed to implement access to the PCIe config space so that lspci on the remote machine works and shows the remote PCIe device, but that's all. It never addressed the issues above nor even mentioned them. The code was AI generated. The article was AI-written. The article never made a reference to DMA, interrupts, MSIX-X, IOMMU, IOTLB, virtual memory, etc, but it made big claims on next-gen datacenter disaggregated architecture, boosting GPU utilization, reducing large scale inference costs, etc.

Anyway, you get my point: big long beautiful words, but zero nuance.

>But if you’re my colleague and we’re in a Slack discussion and you post a wall of Claude output

did you formerly hire copywriters for this task?

And how could you possibly distinguish those scenarios without wasting all your time?

The problem with copywriters is that they wrote "copy" - which turns out to be writing that I don't want to read. And the problem with AI is that much of what it trained on is copy, so it trained to write stuff that I don't want to read.

So in the end, I don't care if a human wrote it or an AI, I don't want to read it either way.

What's wrong with copyrighters? They write like corporations, not like humans (see the Cluetrain Manifesto for more on this). They sound like nobody - literally inhuman. I don't want to read that. I want to hear a human voice. If I can't hear that in your writing, I don't need to read it.

that is load bearing information, and i won't tiptoe around it.