|
|
|
|
|
by thewebguyd
14 days ago
|
|
That's the case for most of these LLM tropes or word choices. They are all common lexicon in their respective fields, but the LLM doesn't make that distinction and uses them everywhere making them standout. No one would bat an eye about "ledger" appearing at a high frequency in content about accounting, but it starts to look odd if "ledger" is showing up in other contexts. "Load bearing" is from engineering; "Substrate" is primarily from biology & biochem, etc. I don't know if this is true, but part of me suspects the labs want to make the models appear smarter so they reinforce this word choice in the weights, assigning some words a higher intelligence weight or something. "I will show you a list of options" vs. "I will surface a ledger of your options" and it prefers the later to sound smart to the human reader. |
|
The reason why I chose that specific term to push on is that practically every SaaS has a ledger _somewhere_ in its stack to keep track of customer payments. I'll give you load bearing and substrate, but ledger IMO should be quite common. Certainly a career devoted to say compiler internals or some specific scientific product could avoid it, but I'd imagine a sizable majority of HN users have worked on some system that accepts online payments for services, necessitating some contact with something likely referred to as a ledger.