Hacker News new | past | comments | ask | show | jobs | submit login

The whole argument seems to be a plea for better mnemonics, but "clearer" meanings aren't often that much clearer because of the ambiguity introduced (and often hidden).

When law does use descriptive terms it's actively damaging to lay people. Too many laws are written where common words mean something similar to but importantly different from what they mean in the field. So then as a layperson you think you know what is legally required to do, but (surprise!) you don't.

This is why in programming, we're so often suggested to name new things non-descriptive terms. As you replace things and split things out and combine them together, you introduce tons of ambiguity if you name things too descriptively.

I'd read the evolution of math to name things how they do to be a collective choice for precision, rather than a move for people's egos.




Using names which mean something is impractical. The whole point of a name is to have a symbol so that we don't have to mention the meaning. The meaning is what the symbol invokes by association, not what it contains literally. The meaning is verbose, far more so than the symbol, and trying to capture meaning in names creates unwieldy, verbose names that far far short of capturing all the meaning.

We include meaning-words in names. That's why it's "Bell's palsy" and "Feigenbaum constant", and not just "Bell's" or "Feigenbaum".

Such shortenings are possible in a narrowly established context surrounding an informal conversations.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: