AI;DR: The New Policy Against Unedited AI Slop
AI;DR (AI; Didn't Read)
The author, jealous of a viral tweet, adopts a new policy: if you don't bother to review and edit your AI output, they won't bother reading it. They explain the growing frustration with unedited AI writing, distinguishing between acceptable uses like customer support and unacceptable ones like Slack messages or newsletters. The piece coins 'AI;DR' as the solution to AI slop, urging a human touch in communication.
If you’re not bothered enough to review and edit it... ...then I’m not going to bother reading it.
- LPisGood
My coworkers continue to dump hundreds of lines of AI documentation in every PR and every other line of code has between one and ten lines of AI generated comments, talking about the real unlock and how things are byte for byte identical on the load bearing path or how the acceptance ladder is misleading.
Features are coming out and metrics are improving, but we’re basically in a post readability code base, with the occasional performative comment about a variable name.
I don’t really know how to address this situation or if it needs addressed. I certainly don’t read the long-winded AI comments or the AI documentation, but perhaps it’s useful for the AI on its next pass.
- heurist
I find after 4 or 5 rounds of targeted feedback and requests to tighten the text AI can produce exceptionally readable documentation.
- afr0ck
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. Th […]
- gortok
The part that astonishes me is that in the year of our common era two thousand twenty-six that it's not universally offensive and reviling to post an AI-generated response to another person.
If I'm reading something on the internet, I'm either reading it to learn, or I'm reading it to be persuaded. If I wanted the LLM to teach me (thank you, no), I would ask an LLM. I'm reading your website/newsletter/email because I want to hear from you.. If you can't be bothered to put your time into writing it and teaching me what you think, why should I be bothered to read it?
- cortesoft
I really like the point I read somewhere the other day; instead of sending me the AI output, just send me the prompt you used to generate it. That is the only part that contains only the information you are trying to convey. The rest is just guesses flowery language added, and it confuses the actual message being sent.
- neilv
> Look, I get it. It’s Q3 2026, and we should expect that everyone is utilizing AI at SOME point in their process (sourcing ideas, creating outlines, refining prose, etc.).
Sounds like this isn't everyone, but rather, it's people who have nothing to say, and -- even after they've "sourced ideas" -- they don't know how to reason about it, nor how to communicate it.
This isn't everyone. This is people engaged in generating noise, for the sake of noise.
- sega_sai
If some text is AI written as a response to a much shorter prompt, then the prompt and/or sources used to make the text should be published instead (or at the very least together with the text).
- keithnz
Not sure how others are using AI, but for us, an AI dump is actually much better than some human editing/writing it. What we've found is that people become gatekeepers of context due to their role in the company they have privileged access to certain context, so when some question is asked, the person who's AI has the right context can look at it and generate a response making sure not to leak anything important and making sure the question is not nefarious. Also important that your AI doesn't generate a wall of text but is super concise. This works incredibly well for us.
- jannyfer
https://hn.algolia.com/?dateRange=all&page=2&prefix=false&qu...
- slybot
3 years ago; https://news.ycombinator.com/item?id=35638229