logoalt Hacker News

falcor84yesterday at 1:08 PM2 repliesview on HN

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


Replies

cwmooreyesterday at 2:02 PM

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

show 1 reply
khueyyesterday at 1:39 PM

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."

show 1 reply