Hacker News Reader

Comment by N_Lens | Hacker News Reader

So many easy tells, AI, particularly Claude, has a characteristic writing style (Can be alleviated by using smaller/local models).

View on HN

Your comment would've been more valuable if you actually included at least one actual example of evidence.

My pattern recognition is a lot less costly to me than your request for proof

I'm pretty sure this comment/article is AI...

Says HN a thousand times on articles that are older than LLMs. I'm not saying this article is or isn't AI, what I am saying is that randos on HN saying something is AI with any definitive certainty hasn't been a great bet. All you do it does is add noise to the conversation.

Agreed, a lot of noise, but for actual data, all of the research into stylometry is also available to LLM vendors, and chasing that target is a major issue in academia and publishing.

So the pushback on the pushback on slop is also noise.

The most obvious ones to me are the sentences that aren't actually sentences but just lists of stuff (and sometimes not even proper sentences). It starts at the third sentence and there's one in the majority of paragraphs. LLMs love writing like this but humans don't do this.

"Support tickets, lead follow-ups, reports, internal updates, research, data entry, task assignment, status checks."

"Real work has missing data, unclear requests, old records, broken integrations, private context, bad formatting, vague instructions, and exceptions nobody wrote down."

"They still need ownership. They need monitoring, logs, fallbacks, permissions, updates, and someone who understands both the business and the software."

"People are busy tuning prompts, adjusting workflows, adding tools, joining calls about the automation, reviewing outputs, and fixing strange mistakes."

"It can speed up writing, coding, research, support, operations, and internal tools."

"It can fail, drift, break, make bad assumptions, and produce bad output with confidence. It can depend on tools that change, APIs that fail, and data that gets messy."

"It has to be designed, shipped, watched, fixed, and improved when the business changes."

"The part where the system meets real users, real data, real edge cases, real failures, and real Mondays."

Thanks for the examples. I actually kinda like it, as almost being a form of spoken word poetry; but yes, these lists do seem unusual on a second read-through.

Reply on news.ycombinator.com