14,726 karma · joined June 25, 2013
I think this is one reason why LLM text is pretty exhausting to read for long stretches.
or use just use actual files instead of pipes with a permissions dialogue gate on write. That would work already in Claude I think, and with IDE integration it would show each step as it went.
Of course buffering every step of a pipeline will have its own side-effects.
https://www.iata.org/en/pressroom/2025-releases/2025-12-09-0...
(I don't actually care that much if it is LLM text, I care when something reads like it is, because it means everyone writing blogs using this style sounds like everyone else. it's alienating!)
LLM text often just is missing the cadence of human-written text. It never slows down or speeds up; it keeps a relentless pace. Sure, a human can write like that, and I'm sure people do, but I find it enervating to read, whether it was a human or an AI that wrote it.
https://www.pangram.com/history/c0a9cde2-7a5c-4588-83a3-0269...
And Pangram flags it, too.
https://www.pangram.com/history/126831e1-562f-4e65-9874-5250...
Apparently it's mostly this:
// ENCODE — pack(html) → one .hmml (a Uint8Array you store or send)
// · lifts every data: image out of the HTML into raw bytes (no base64)
// · gzips the HTML/CSS/JS and frames it all as one binary blobLLM output has conditioned in me a near reflex response to just close a tab as soon as I smell LLM-authored text. Like, I'm not mad or anything, I just frequently find most default LLM-voiced text very unpleasant to read so I just don't continue reading.
If you want me to read your analysis, you are going to have to make it not read like Claude wrote it. What does "placement" even mean here?