Intentional writing will likely become more valuable.
459 comments
Writing is fundamentally the transfer of information from your brain to my brain. If you have 1000 bits of semantic information you want to transfer, you can't give 300 bits of semantic information to an LLM and have it fill in the remaining 700, because it doesn't know what those 700 bits are. If it's able to guess those 700 bits correctly, then they aren't true semantic information, and you really only have 300 bits you want to transfer. You might as well transfer those bits to me directly, rather than having the LLM add on an extra superfluous 700 bits that I then have to filter out.
Giving someone the text output of a LLM is very similar to publishing a summary without links to the referenced material. When you were querying your LLM, you could have asked specific questions or asked for a custom focus or point of view. Your intended audience might have questions or different concerns, but they're unable to interact with your LLM. What you have delivered is static and unresponsive. It has all the disadvantages of being machine output without the advantage of being interactive, the way your LLM was for you.
It may have to wait until compute is cheap enough that tokens are essentially free, but we need a system to pass "hyperlinks" to LLM's primed with context, ready to be interactively queried on a chosen context. It's being overly generous to assume that people are putting even 300 bits into a LLM for every 1000 bits of regurgitated writing they try to pass off as their own. When people post LLM output as if it were their own, I have no choice but to assume they had zero knowledge of the subject, but this query taught them what they wanted to learn, and now they're sharing that. That's fine, but please pass an interactive LLM link rather than static text.
Once we have "hyperlinks" for LLM sessions, perhaps we can share LLM output a little more usefully and honestly.
I’m a big fan of this approach.
I still remember a recent example where one of those trivia accounts on Twitter posted an interesting story about some guy whose life completely changed after an accident, but neither linked to a source or named the person in question.
The only way I was able to verify it was true was through someone in the comments asking the platform's AI chatbot, and the chatbot providing context that I could research and verify...
I agree, this drives me crazy. Ironically, one of my favorite uses for Claude is to ask, "What study is this news article talking about?"
It's pretty good at digging up the source and related sources. And most of the time, if you read the source, the article is nonsense and gets everything wrong.
Communication only works if you have multiple levels of representation and abstraction, including but not limited to - letter shapes, grammatical structures, style and register, stylometry, and subtext.
All of that is learned, and writers usually assume they can rely on that learning as the context for the text.
So you don't write to 'transfer information' like a network cable, you write to trigger experiences in the human version of latent space.
Factual information is one kind of experience. But even when that's the goal, there are always layers of implied relationship, social register, role, status, and other implications in everything that's written.
In normal communications the context - business emails, personal messages, mainstream journalism, fiction, and the rest - defines what acceptable language looks like.
The content fits inside that. But it has to fit the context, otherwise it lands in a semantic and psychological uncanny valley - like sending LinkedIn speak to a spouse on a wedding anniversary.
The real problem with LLM writing is that it's good at the technical layer - the grammar and spelling - and has some insights into the rest.
But the default content style is marketing and ad speak. And recently it's developed a weird and unique hybrid style which applies marketing fluff and pretension to technical content like code comments.
So you get one register instead of all of them. It can attempt others, but it's still too limited to generate them fluently. Sometimes the results are outstanding, but often it defaults to mechanical clichés.
So that's why it sucks and sounds so hollow.
Can it be fixed? Yes, but it's very hard work, most people don't have the skills, and it takes time - often too much time to be worth the effort.
When LLMs eventually get good at writing in the correct style for a given context, I'll admit that they have value in that way. But they aren't good at that yet. And even when they do get that good, I'll still dislike it for reasons that are more emotional than rational.
> Communication only works if you have multiple levels of representation and abstraction, including but not limited to - letter shapes, grammatical structures, style and register, stylometry
These are methods of encoding, there's no reason all of these can't be represented in an LLM from a technical point of view.
> and subtext.
This is the other half of the equation to me. Humans communicate by relating shared experiences, an LLM cannot have shared experiences. While it might be able to encode subtext that has been specifically called out and explained, it will never be able to encode the breadth of human subtext, especially that which is reliant on emotion.
I don't believe it is possible to change this until the point mankind truly develops a "wetware interface" to the digital world (and I personally don't want such a thing to exist).
I see this all the time now with LLM generated output. It's easy to have an LLM generate a chunk of content that can be dropped into a chat or comment, and when it took you 20 seconds to have something written up based on the shared understanding you and an LLM have about the context of the situation, but it takes other people 3-5 minutes to read and understand that content, that fundamentally doesn't scale. It's bad enough when one or two people are doing it, but if the whole team is doing it, the only way to keep up with the stream of information is to also consume it through an LLM. At that point you're likely to be missing much of the nuance, and the amount of errors will explode.
This can be alleviated by people reviewing the output of an LLM and making sure it both includes fundamental information that might be assumed by context and reducing it to the parts that are essential for the new context it's in. This takes time, but is extremely important.
Having an LLM write gobs of text to send to other people instead of doing it yourself is the equivalent of a low yield cognitive zip-bomb. Don't do it.
No, I don’t want to read LLM writing because it is BAD at it. It doesn’t really understand how humans think (because it thinks differently), and doesn’t seem to understand core principles very well (presumably due to the lack of world model), so it can’t write something humans enjoy yet.
My instinct says that these systems will expand their complexity to fully fit the cognitive budget of the agents that coded them and then atrophy the same way human-built systems do at lower cognitive budget. Only this time, because of the larger up front budget, the complexity ceiling will be higher, and the potential depth of the problem may be much much larger. It may mostly manifest as increasing cost over time - the agents grind for longer and longer, iterating over and over to fix all the failing tests, and the breaking point will be where it never converges and you come back to millions of dollars in budget spent and still tests are failing and effective gridlock on system changes.
But this may be all my human-biased fantasy that justifies still taking a role in software development.
I'm old enough to remember using CVS and then subversion in companies. People would commit straight to main (which was then called "trunk"), because making feature branches and merging them was cumbersome. And, on regular intervals, the person responsible for some corner of the codebase would do a show-and-tell presenting it to peers, but without the sharply defined boundaries of what the code looked like before vs. after some recent set of changes. People might remember some things from the previous show and tell or from first hand experience with that code, but that kind of memory is necessarily fuzzy, and diffs weren't an artefact that was typical to look at. So, these reviews didn't block people, and any comments that came from reviews defined a direction that things should go from here on out. If a corner of the codebase was deemed to be in a bad shape, the blame around that was equally fuzzy.
Everyone is fatigued by endless code review which you get no credit for and has become massively more of a burden.
All PRs are superficially fine now. There are no typos, there is unit test coverage, but there are deeper issues that require massive amounts of effort and time to spot.
https://github.com/josephmisiti/awesome-machine-learning
It's helped a lot. Agents haven't figured out how to do that yet, or sendgrid, sns, etc are doing the hard work for me.
In the meantime, for business communication, I use AI to shorten my text, to make it more concise.
So far I haven't had a reason to go back through commits to isolate any issues but if I do hoping the 'why' messages may come in handy for my LLM lol
> A pattern I see is that people use AI to build something new, then they use AI to retrospectively summarize what they have already built into a design document. Reading a document like this isn’t just difficult—it is punishing.
TFA's use is more common in "normal" language: "it's not just [minor], it's [major]". (But, as others have pointed out, it was probably deliberately parodic anyway.)
I've only just discovered pangram, but I've seen it referred to a few times in HN recently wit nothing obviously pejorative about it. Take it with all required grains of salt, though
One of the instructions I've hammered into Claude is "Write like a human. I don't want this to sound like AI content. Your standard style of writing would fail miserably if it was reviewed by an English teacher. I want you to write prose that is nice to read. For example, write full sentences instead of bullet points."
It works wonders. Suddenly, my plan documents are something I actually understand, and something I'd be happy to share as an RFC. They still need iterating every time before they're ready to share, but I no longer have "the honest truth is" and other BS in my output. It's so refreshing for my brain to be able to actually focus on the content.
I've noticed this with my partner, too. She used Claude to draft a strategy document and felt completely overwhelmed. A classic moment of "AI did all the thinking for me, but now I don't know what I'm presenting". Once I helped her prompt Claude into writing the strategy in proper English, she understood what the AI was proposing, rejected large parts of it, iterated several times and ended up with a draft document where she edited the finishing touches herself and felt that it was truly hers. The AI was still incredibly useful: it helped her with the blank slate problem, and tremendously sped up her workflow.
So yeah, if you proofread and iterate on your AI's output until you feel you'd be proud if you had written it yourself, I'm happy to read it, too.
Of course Claudeish or GPTish ("unusually") will easily push me away. Just like any repetitive or obnoxious tendencies that might appear in human writing.
If this actually works, it's absurd. The implication is that Anthropic could trivially make Claude sound less obnoxious, but chooses not to. I don't see a way this could be justified as a safety feature or anything, so.
I agree, using LLMs is disproportionately frowned upon, but what matters is if you invested your own attention in the process. I use LLMs a lot for sparing, usually ask it to assume some opposing persona or use web search, not relying on its defaults.
these posts are beginning to make me wince. ai is giving voice to a lot of folks we probably wouldn't even be hearing from otherwise - because not everyone does their thinking in articulate prose, and extracting their realizations as shareable language takes effort, or long, embarassing iterations with ai "workshopping" to get to something they can read back and go yes this is what I am trying to say.
now the sentiment is that whatever these people had to say they could have just come out and said it - and that would be more passionate and less disjointed - no, not necessarily, and the more it gets repeated the more it's sounding elite and pompous to me. for example this:
> I had someone write me a personal message about a sensitive topic that was clearly workshopped with AI in an effort to nuance the conversation and not offend me. But the message became impersonal, dispassionate, and disjointed. It had all of the parts, but it didn’t make sense as a whole. I wasn’t interested in reading it, or responding.
this reads as someone choosing to ignore a personal message about a sensitive topic - because of an assumption they made about their writing: that they workshopped it when they should not have - because whatever it was they were struggling to say they should have isntead trusted the author to be able to understand the precise meaning of their raw, inelegant thoughts no matter how embarrassed they might be to share them in that form. they're complaining about a message they probably weren't otherwise going to see.
That's clearly not the type of people they are talking about. For some people expressing their thoughts in words is really, really hard. It doesn't mean they don't give a damn. Just like being in a wheelchair doesn't necessarily make you lazy.
Everyone is an elitist, when you've enplaned do you assume the pilot is qualified to fly it or do you hope everyone gets a turn? Admittance to the canon is no less a responsibility, would you trust the yoke of human culture to the artless, craftless, and naive?
not everyone does their thinking, if you dont I dont want you to have voice
I still want the imperfect human.
Because while I dislike AI writing, it matters in context. If someone is trying to formulate a coherent thought of work tasks required of me then I don't really care if it reads like AI as long as the point they're trying to get to me is clear.
If there's an attempt at something human, or emotionally important I will quickly balk at anything spat out through an LLM. If you're trying to communicate at the human level with me I want your input, flaws warts and all.
A card with just...nothing personal on it has as much value as machine text. I understand that you took the effort to think of me, but that's the bare minimum. If trying to express yourself isn't worth the time to make it personal then I'd almost appreciate if you didn't try at all because it hurts more to believe I'm not worth the effort.
As for second paragraph, the writing "had no overall meaning". There is nothing to respond to if there is no overall meaning.
What we are seeing here is a Luddite reaction from artisans. A skill has been automated and those that have the skill are not happy about it.
For many writing is painful and the machines ease the pain. And like all machines it takes a while to use them skilfully. In particular remembering that like code it is write once and read many. What the reader needs should be at the forefront of a writers mind - both for code and prose.
Nobody gets on a motorbike and wins the TT in the first weekend.
Read the full thread on Hacker News →
Related stories
- I Don't Want to Read What You Didn't Writeblog.colinbreck.comHacker News · 2 points · 9 days ago
- I Don’t Want to Read What You Didn’t Writeblog.colinbreck.comLobsters · 1 points · 9 days ago
- Hacker News · 1 points · 8 days ago
- Hacker News · 12 points · 8 days ago
- Socrates on the Invention of Writing and the Relationship of Writing to Memoryhistoryofinformation.comHacker News · 1 points · 10 days ago
- Hacker News · 1 points · 3 days ago