~actual prompt i sent in to claude last week. doing what you propose would be basically impossible / nonsensical, and further undo the entire exercise, sending all the money spent on the tokens down the toilet.
put differently, if you use agents in any actually useful manner, the principle you describe erases whatever value they did end up providing. though since the whole underlying premise is that ai never provides any value, maybe that's the intended result and is as expected. in which case, i'd argue such an expression of desire is more than a bit demagogue.
> AI;DR (AI; didn’t read) is the solution for AI slop.
Maybe I'm the odd one out here and didn't plumb the worse-depths of social media, but I feel I need to defend good old TLDR as a slightly different, and less-hostile animal.
It can be a moral condemnation of the poster, where they're disrespecting everyone else's time by posting something big and vague... But it usually isn't. At least half the time TLDR is someone providing a summary because they think it'd be useful. (Or as hostile critique.)
I'd say that sounds about the same for ai;dr. I could see myself posting a prompt like that in front of the generated report.
>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.
did you formerly hire copywriters for this task?
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.
- Why does it matter who or what wrote a thing? And how would you know if the /content/ is worthwhile, unless you read it...
- The ability to "detect AI" is imperfect at best. 90% AI written? 5%? How would you know, unless you read it....
- If you didn't read it, then why brag about it with an "AI;DR"?
- If you are wrong, and you announce it to the world, how would it feel to someone who spent a lot of time and energy writing?
Bragging about it is weird, but I will use it like I use 'RTFM'.
And detectability - My AI-DAR (radar), is fairly fined tuned but not perfect, so if I make a mistake, oh well, the point is I'm protecting my time.
I already saw someone getting fired for only producing AI text as part of their entire output, after being unable to explain what they “wrote” in multiple situations.
And recently my company enacted a mandate that text made for humans should not be AI generated.
Sooner or later every company will start realizing that this is just people too lazy to actually work and coasting on a paycheck, at the expense of every other worker.
Much how like essay's have a word limit - and people think you should max it out.
We will go in the opposite direction - which I'll be glad about!
I think sometimes people have a big long thread with Claude where they feel enthusiastic about the back and forth being very productive -- and then they genuinely want to share the summary of the conversation with their colleagues so that they can feel it too. It's not just typing a short prompt and copy/pasting the response.
But, Claude, especially Opus is so unnecessarily flowery, and smug -- and it's so identifiably characteristic.
It somehow rubs salt in the wound: "I didn't take the time to write this out in my own words, so now you get to listen to this petulant asshole mansplain it to you".
If it would get to the point, and with some humility, it would be a much different proposition.
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?
I do feel like there is some middle ground where AI helps, but there's this one guy who keeps emailing everyone with walls of dumbass text and does not integrate or understand the feedback he gets when we are telling him what he needs to do. He just runs it though the LLM and replies and then forgets half of it in the next email engagement which functions as /clear on his end apparently. Like... dude I have ChatGPT and Claude, too. Actually read your goddamn emails.
it probably doesn't help that the US education system is so deeply broken with how rooted it is in segregation-era practices [0][1][2]. the average gets dragged down quite a bit when some districts receive so much money that they're flying their Spell Bowl teams to nationals and putting them up in hotels while another one a few miles away can't afford to pay for textbooks. average reading levels suffer and consequently so too does the effort that people put into writing well and reading critically
[0] https://www.shankerinstitute.org/segfunding
[1] https://www.jchs.harvard.edu/research-areas/working-papers/s...
[2] https://edlawcenter.org/research/the-color-of-opportunity/
Why would you think it would?
You didn't put any meaningful thought into it.
Hell no. Sourcing ideas? From AI? Are you kidding? Essentially guaranteeing they won't be original? Refining prose? Making it much more likely it'll be generic as hell. Call me old fashioned, but while I can certainly understand asking LLMs concrete questions - how do I fix this, where can I unsubscribe from that - using AI to help communicate seems bass-ackwards. LLMs have no idea what you're talking about - they're free associating probabilistic sentences! What on earth value could that have in communicating. They self contradict, hallucinate, speak most frequently in a weird smug corporatese. How is this an attractive use case of the technology?
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.
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.
Write REVIEW.md.
I have CC check itself pretty well.
I also put into agent/claude/review instructions to write using simple English skill and humanizer skill. Then not to write redundant comments.
It’s not perfect but definitely catches lots of slop.
> I’ve been thinking about it ever since. Why? Because there is growing grumbling among everyone about AI writing. And it’s not just others; it’s me!
Classic AI "its not just, its..."
I, of course, had no choice but to apologize. I hope I was right, but clearly there is some chance I was wrong.
Before I think he was using AI and other tools to translate his messages since english isn't his first language. His own words, then AI translated it. Sounded kinda clunky, but I could sense the human behind the words and I gave grace since I can only imagine how hard it is to properly communicate your ideas when English isn't your first language.
But now it's gotten to a point where I can tell he's not using it for just translation. I'm gonna need to chat with him.
Redacted example below
```Hey @PERSON_WHO_ASKED_QUESTION Both good, and the retrieval one isn't written down anywhere. In order.
One corpus or four. My lean is one. Same chunks and embeddings tables, source_type column to tell them apart.
Values I'd propose, flat rather than nested: paper, dataset_description, dataset_readme, dataset_contributors, dataset_records, dataset_files. Description and readme split because their units already differ, one row versus one row per paragraph. A discriminator that can't separate those isn't doing much. The existing 440 rows would need backfilling to paper.
Chunk id in the same spirit: dataset doi, source type, ord. So EXAMPLE_DOI.
Worth checking before any of this matters: does chunks.doi carry a foreign key to papers.doi in 0001_init.sql? If it does, a metadata chunk with a dataset doi can't go in that table at all, and separate storage stops being a choice. Ten second read, I haven't done it. Shout if you get there first.
Retrieval is the one that's bigger than it looks. Search once across everything and nothing guarantees a paper chunk and a metadata chunk both land in the top k. The facts we want relate the two, and the generator can only write those if it sees both sides in the same window. So if one type systematically wins the ranking, that class of fact doesn't get worse. It becomes impossible.
Which way it goes I don't know. Two mechanisms pull opposite ways. Metadata chunks are short, tens of tokens against roughly 450 for a paper chunk, so they may just lose. But we embed context header plus text, and on a short chunk the header is most of the vector. The header is the dataset name, which is also most of the query. That points the other way.
Cheaper to measure than argue. Load one dataset's metadata, run a normal dataset level query, record the rank of the first chunk of each source type. Runnable as soon as any one of our four subtasks lands.
After that it's one pool, per source with quotas, or one pool with a floor per source type. I'd rather not pick before there's a measurement. ```
i have what ill call a "condition" where i fear assuming someone did something stupid is insulting. i try not to patronize people because i also assume that would be insulting. this leads to issues where sometimes people really want to be lead to water rather than make an implied connection themselves
this is a roundabout way of saying, is there a genuinely polite way to tell colleagues posting ai copypasta makes them seem ignorant? i dont think ai:dr is workplace appropriate. id like to tell people gently and avoid patronizing if possible
Claude, post that wall of output to Slack yourself. Make no mistakes.
The implication is that expertise is being devalued in real time, and in a sense it really is, but I think that most people really do need to face the reality of their emotions and where it comes from. For myself personally, I have no qualms about reading or even engaging with AI content, as long as the content itself is of quality and truthful.
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.
It turned out his prompt was equally uninspired... 1 or 2 sentences. That was the thought he put into it, which then had us spending hours trying to figure out the AI reply. He could have saved the whole team a full day by just sending the prompt... or nothing at all.
"Here is the prompt and model I used, here is the portion of the output that stuck out to me as relevant and useful, and here, in my own words, is why I think that is so."
i.e. Highlight the good part of the output for me and, preferably, explain why you think it's good. Otherwise it's the same thing as posting slop, only with extra steps. You thought it was worth posting and I thought that made it worth looking at, but now I'm sorting through a bunch of monkey garbage looking for what made you think that. Being a different person, I may not find that hidden gem and I may become quite frustrated with you.
________________
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.
The purpose of writing is to communicate. The person communicating is an important part of the message.
Consider the sentence "I'm waiting for you at home." It really matters if it's said by your loving wife or an evil clown. You can extrapolate from this.
Depends on his countenance and how good a mood I'm feeling in!
In any case I might well ask how much time went into at least reviewing the output. Or I say (rather than a flat AI;WR) "I'll scan that and have an AI summerise it for me later".
arm32•39m ago
sermah•36m ago
hinkley•35m ago
em-bee•34m ago
spudlyo•29m ago