181–190 of 327 posts
Earlier quoted context omitted.
load-bearing was/is used frequently on the ops side of things, I assume the LLMs picked up from physical engineering texts or sysadmin type blogs.
"Load-bearing" is an apt metaphor in the https://xkcd.com/2347/ sense.
Earlier quoted context omitted.
In the enterprise, we are already adopting them. “Seam”, I term I’d never heard used before, is now not only our defacto way to describe the boundary between systems/workflows/components, it is encoded into our organizational roles and responsibilities descriptions. I am the proud owner of several seams, and am considering giving them person-names. The empty space between my inventory APIs and their clients might be…
"seam" is a cop-out term for when someone (usually AI) lacks the imagination to come up with something more descriptive. It's like saying "middle thing". Just name it by what it does, and if you can't, remove it because it's not doing anything. "load-bearing" on the other hand is just a weird way to say "required" or "prerequisite" without drawing any attention to the fact that one cannot articulate what something is…
Earlier quoted context omitted.
Is it the obnoxious style that causes this?
I think it's the hierarchies of agents summarizing each others' summaries before presenting a final answer to the user. The principal agent has the full context from all its workers, but when it distills this down to a message to the user it summarizes it into a mess of confident jargon that pertains to a conversation the user wasn't a part of and never saw.
I don't understand why we tolerate this. We'd never hire someone that interviewed with this communication style and if we did we'd probably pip them fast.
I've recently seen this mentioned more and more, both on HN and on reddit. It seems these output patterns are getting worse. It's not just Claude, my impression is that all of the current models have this style issue. Their writing can get borderline incomprehensible. Is there some feedback loop or compounding happening with each model generation? Maybe newer models are ingesting too much AI content? If the ratio of…
I was pleasantly surprised when I attempted to scroll down and realized everything the author wanted to present fit on-screen. It's almost ironic that this site is able to make such an obvious, compelling presentation without being overly verbose or complicated (something which LLMs have a hard time doing). I wouldn't read TOO deeply into what is being presented, but the author has done a good job to not inject their…
>I suspect, as we continue forward, humans will slowly start to adopt the language of LLMs I'm already seeing it. A coworker said something like " added the color to the ticket here" meaning that someone added details to a ticket. I've started seeing Opus 5 talk about "hermetic testing" when it just means "unit testing", so I hope that doesn't catch on...
Earlier quoted context omitted.
>I suspect, as we continue forward, humans will slowly start to adopt the language of LLMs I'm already seeing it. A coworker said something like " added the color to the ticket here" meaning that someone added details to a ticket. I've started seeing Opus 5 talk about "hermetic testing" when it just means "unit testing", so I hope that doesn't catch on...
The idiom "added color to" as an expression of adding detail or nuance to something goes back much further than the AI era. I've certainly used it at various times in my career spanning 4 decades now.