Top
Best
New

Posted by mooreds 16 hours ago

I don't want to read what you didn't write(blog.colinbreck.com)
834 points | 347 commentspage 3
saulpw 16 hours ago|
It's tricky because I don't want to write what no one is going to read (but that for some reason I'm required to write).
CuriouslyC 14 hours ago|
Nobody is going to read anything regardless of whether you used a LLM to write it or not (but if you use a LLM they'll use that as their excuse for the virtue signalling aura farm), so honestly why bother writing.
Leynos 12 hours ago||
If it's written down in a form that can't be repudiated, a succinct message to any stakeholders covering any decision of substance is good practice. They might not read it, but they cannot pretend I did not make a good faith attempt to inform them.

(And I try to be judicious about what counts as "of substance" so they can't accuse me of flooding them with messages)

cjlm 12 hours ago||
I wonder where this discourse is headed, we[0] keep making the same observations over and over again.

[0] myself included https://www.google.com/goto?url=CAESbQHrOzAViiJizn8otPF3AAeE...

idreyn 16 hours ago||
These last few days, there has been a small stream of blogposts on HN expressing similar things, and I have enjoyed them all.

My question recently has been how to broach this subject with colleagues who really enjoy producing prose with AI. There is not yet a better cultural shorthand for this sort of thing than "slop" which is a harsh-sounding word and itself sort of a thought-terminating cliché. "I don't want to read what you didn't write" is maybe closer — but it needs a pithier and somewhat more encouraging encapsulation, like "I want to hear it from you".

Has anyone had good experiences setting up professional boundaries or team norms around AI-written docs?

TheBolivianNavy 14 hours ago||
It's something that my company has been struggling with. Developers are generating mountains of code, documentation, and Jira ticket comments. It's incomprehensible and overwhelming.

For the team I lead, my guideline is AI generated is fine but it needs to be human-edited and/or summarized. You want me to read what you're offering? Put some effort into it and meet me halfway. I don't want AI generated gibberish with made-up terms. You'd better also understand what you are presenting as your work. It's been fairly well-received though we're still working on it.

I have some co-workers on other teams who use AI to generate responses to literally everything. Ask a simple question? Get pages of AI generated nonsense in response. They are proving a tougher nut to crack.

thinkingemote 7 hours ago|||
Ask questions about how the audience is taking the blog posts. Say that many people seem to really not like LLM writing and ask how are they listening to their readers on this point.

You may find that brings a better and more human focused discussion. Who is the audience and what is best for them? Don't frame it about your preferences but about the real persons that your colleagues seek to talk to.

skyberrys 15 hours ago|||
There is one person who is so good at writing with AI assistance.

Everyone else, including me, not so much. I envy his talent and ability to so successfully use the new tools. It's just something to think and talk about regularly. Maybe one day we will all be able to use the tools as well as that guy.

eMinor72 11 hours ago|||
In my current position(DevOps) we are getting this kind of messages or issues a lot recently. While forwarding these issues to my team lead, i don't have to deal with them which feels great but once its assigned to me... Its another long process to understand what issue actually means and what i need to do.

Thats said, i don't know any professional way for this but currenlty trying to communicate with peers in order to work without a problem.

boogieknite 15 hours ago|||
im sensing about a 20 month lag between hn sentiment and normy-coworker sentiment. managers and business-types pointing out the benefits and challenges of working with an llm i told them about early 2025. im just politely nodding along waiting for them to catch up. theres some emperors new clothes happening at my company so maybe im complicit
jayd16 14 hours ago|||
"Hey, the comments are too wordy. Can you clean it up so its only important information?"

As much as you want to say "actually do your job, jackass." Being goal oriented has had the best results for me.

speg 15 hours ago|||
I’ve been away. Does anyone have a collection of these posts?
idreyn 15 hours ago||
Here are the two I was thinking of:

- https://news.ycombinator.com/item?id=49767937

- https://news.ycombinator.com/item?id=49784816

intended 9 hours ago|||
I’ve seen the problem crop up in several places.

At a broad level, the issue isn’t generated content, it is the ratio of verification capacity to generation capacity (V/G). Your pain is because generation capacity has increased significantly, while verification is laborious and capacity has not (and can not) catch up.

Unlike spam which is from external sources and can be ignored, messages from other employees have to be responded to. I guarantee this is creating bottlenecks all across the firm, outside of the individuals who are feeling productive.

For fixes, theres theoretical approaches that might work?

If you need leadership to help you, then this issue has to become something that is on their radar, which means that something needs to go wrong or costs need to be registered.

The shortest conversation for that is to make people aware that generation has improved individual productivity, while moving the costs of that production to the rest of the firm.

If leadership is not at the stage to listen, then you need to move the costs you are incurring to the people who are sending them to you. Maybe set time aside to sit down with whoever sent a PR and then read what they sent together, to understand it.

It also makes a difference if tokens are being subsidized or not. If the firm doesn’t care how many tokens are being used, then you are naturally going to have over production.

cnrcode 15 hours ago||
[flagged]
jeffbaumes 3 hours ago||
> I also see more and more pull request summaries clearly written by machines for machines. They are rich in detail: this was changed to that, these things were split, those things were merged, this was left untouched, tests were added for this, and so on. But I’m left asking: Why are we doing this? What is the value? How risky or urgent is this work? Where do you want my input? What should I pay attention to?

My own solution for this (for now at least) is to add a preamble section “AI;DR” to PR descriptions, filling what a TL;DR section would have done in the past. I’ve socialized to my peers that no part of such a section will be written by AI, and it should contain exactly this missing high-level content described by the author.

pmlnr 8 hours ago||
> Reading a document like this isn’t just difficult—it is punishing.

At this point I can't tell if it's a pun or the anti AI article is AI written as well. This sucks.

almondfestival 15 hours ago||
this is intended as a silly observation and not an actual accusation, but for an article about not writing with AI, the following is one AI-ass sentence:

“Reading a document like this isn’t just difficult—it is punishing.”

stevage 11 hours ago||
There's nothing AI about that sentence.
herdst 11 hours ago|||
You are oblivious to AI smells then. This is a very common AI writing pattern.
ecwilson 9 hours ago|||
AI didn’t invent the em dash nor “It’s not just X, it’s Y” and sometimes those are appropriate for the situation. Prose should be judged accordingly.
ShadowOfThePit 15 minutes ago||
Using both at the same time, tho? Eh.
prmoustache 8 hours ago|||
LLM didn't invent it themselves, they are plagiarism machines. Obviously these kind of patterns had to be popular in the first place to be overused by LLMs

Also we have reached the point where LLMs are pubkishing more contents than humans so we have probably reached a point where humans will inconciously start copying and using LLMs style too.

almondfestival 9 hours ago||||
c'mon, it's literally the top 2 AI writing tropes in a single sentence. i googled "AI tropes", and here are the first 2 tropes listed in the first search result:

1) negative parallelism: "It's not bold. It's backwards."

2) em-dash addiction: "The problem -- and this is the part nobody talks about -- is systemic."

again, i'm not saying the author wrote this sentence using AI. i was just tickled by how stereotypically AI it sounded. for better or for worse, those characteristics are just going to set off the AI detector in people's heads now, as evidenced by the fact that there are like 10 separate comments on this post that picked up on the exact same thing.

AppleBananaPie 11 hours ago|||
It's the stereotypical example of AI in my experience. I.e it's not this it's that.
stevage 10 hours ago||
It's a super common writing and speech pattern.
_the_inflator 8 hours ago||
To me it is just a bittersweet irony: people who don’t know what a book is for 30-40 years or in earlier days got the RTFM (gif smiley not included) treatment dump one liners to produce a giant load of text corpus that needs to be processed by an AI to get the gist out of it with sometimes quite some refinement by asking many questions.

So there it is: cruel people who don’t even read their own prompts while happily believing others read their text load and pat the genius on the shoulder for being such a great guy in writing, while in essence it turned the RTFM movement on its head: UUOAI - “Use your own AI.”

People cannot communicate better by using the digital equivalent of logorrhea.

kingcauchy 14 hours ago||
I don't disagree with the main points of the article. But I feel like soon with all the writing that's been hating on AI writing recently on HN, the LLMs are going to be really good at writing articles about how bad AI is for writing...
Reason077 12 hours ago|
The irony is that this article reads a lot like it was written by AI.
paritosh31 6 hours ago|
Yes, you can easily prompt this writing style.
More comments...