Live data from Hacker News

Mathematicians should stop naming things after each other

nautil.us

41–50 of 406 posts

Re: Mathematicians should stop naming things after each other

#41
> Imagine how much steeper the learning curve would be in medicine or law if they used the same naming conventions, with the same number of layers to peel back:

I she kidding? Off the top of my head: diseases named after people. Parkinson's disease. McArdle's disease. Bell's Palsy, Hodgkin's Lymphoma, ...

https://en.wikipedia.org/wiki/List_of_human_anatomical_parts...

In Law, precedents are referred to by plaintiff and defendant names: Smith vs. Klein. There are laws named after people, e.g. in the US. Kirsten's Law; Mann Act; Wetterling Act; Sonny Bono Copyright Extension; ...

Re: Mathematicians should stop naming things after each other

#42

Yep; check out how the programming community does it! We have descriptive names for things like "Apache", "React", "nginx", "Rust", and "Java"!

That's because "easy to google" is much more important in the short, medium, and long runs than "easy to guess what it does"

Not everything is easy to Google:

C, D, F, R, COM, .NET, node ...

Re: Mathematicians should stop naming things after each other

#43

Yep; check out how the programming community does it! We have descriptive names for things like "Apache", "React", "nginx", "Rust", and "Java"!

That's because "easy to google" is much more important in the short, medium, and long runs than "easy to guess what it does"

I highly doubt this will work out well in the long term. Considering that once something new comes out with a similar name or even the word which was misspelled to form the name of some JS framework it will rise above in the search results.

Re: Mathematicians should stop naming things after each other

#44

Not sure how feasible or necessary this is in general, but there are certainly some places for improvement. Some more modern examples than "isosceles": - Heaviside function → step function (edit: though maybe this one is, amusingly, already descriptive by accident?) - Fourier domain → frequency domain While I'm here, just a couple suggestions from me: - Markov chain → memoryless chain - Lebesgue integral → horizontal…

Guess would need a different term for Markov chains of higher order. And I'm not sure if there's other concepts that could also be labeled "memoryless chains", where a distinct name might help.

Re: Mathematicians should stop naming things after each other

#45

Earlier quoted context omitted.

That's because "easy to google" is much more important in the short, medium, and long runs than "easy to guess what it does"

Not everything is easy to Google: C, D, F, R, COM, .NET, node ...

io-lang

Re: Mathematicians should stop naming things after each other

#46

Earlier quoted context omitted.

Rust, Go, C, D, R, Flask, Rocket.

Append programming language to the query for searching. Imagine C++ would be named as "Object oriented, generic, general purpose programming language with C compatibility"(of course C won't be named C then).

It could be called Stroustrupilian ... or "The one with Turing complete templates".

Re: Mathematicians should stop naming things after each other

#47
post #8

There's an equally annoying problem in software engineering at large corporations (aka Google), where hundreds of services you need to know about are named with some cute name that gives you no idea what the thing actually is.

So how would you solve it?

I imagine they work around the direct reference issue by having good search algorithms.

Re: Mathematicians should stop naming things after each other

#48
This falls a little flat with me. Let's consider an example from the article- a Kähler manifold. I'm not a geometer, so I looked it up on Wikipedia, and it says that a "Kähler manifold is a manifold with three mutually compatible structures: a complex structure, a Riemannian structure, and a symplectic structure." https://en.wikipedia.org/wiki/K%C3%A4hler_manifold

Two of those things are not named after a person, and none of them are understandable without special training. Naming something after a person doesn't make it any harder to understand unless there are multiple things named after that person and you can't figure out which they mean from the context.

In case you're wondering about those structures, here is what Wikipedia has to say about them:

- A Riemannian manifold "is a real, smooth manifold, M, equipped with a positive-definite inner product g_p on the tangent space T_p M at each point p."

- "A complex manifold is a manifold with an atlas of charts to the open unit disk in C^n, such that the transition maps are holomorphic."

- "A symplectic manifold is a smooth manifold, M, equipped with a closed nondegenerate differential 2-form ω, called the symplectic form."

The only thing in the above descriptions accessible to non-specialists is probably that the Riemannian manifold is probably named after that guy that they heard of in calculus class. Let's not get rid of our ability to honor people in a failed attempt to make the communication more effective. You can call a Riemannian manifold or a Kähler manifold whatever you want, but it's not going to prevent someone from having to spend years before they are able to understand them.

Re: Mathematicians should stop naming things after each other

#49

Not sure how feasible or necessary this is in general, but there are certainly some places for improvement. Some more modern examples than "isosceles": - Heaviside function → step function (edit: though maybe this one is, amusingly, already descriptive by accident?) - Fourier domain → frequency domain While I'm here, just a couple suggestions from me: - Markov chain → memoryless chain - Lebesgue integral → horizontal…

I'd be concerned that memoryless is misleading for markovian. A markov chain can be used to represent a fixed, nonzero memory, since if you have an n-state dfa D you can take the set of pairs of the states of D (or specifically D + null) and reweight them. The markov chain over D^2 has no memory over D^2, but does have memory over D, and this is often a useful property (bigrams). You repeat this operation to get more…

Memoryless isn't even something I came up with, it's practically in the first sentence of everyone's description of the Markov property, e.g.: https://en.wikipedia.org/wiki/Markov_chain#Definition

Also see: https://en.wikipedia.org/wiki/Memorylessness ("memorylessness refers to the Markov property")

All I'm doing is suggesting just using the existing description as the name itself.

Even if there were some cases where it wouldn't apply, though, it wouldn't really matter. Fourier domain also applies to things other than time but that doesn't make frequency domain a bad term. It's just a name meant to carry some intuition; that's all. It's not meant to serve as the formal definition.

Re: Mathematicians should stop naming things after each other

#50
This is one of those articles that might sound convincing to non-mathematicians (because it is annoying to learn names for difficult concepts, and many people can relate to that experience), but will not sound all that convincing to domain experts.

It'd be hard to deny that descriptive terms are easier to memorize. Sometimes a piece of natural and/or physical intuition allows such terminology to arise.

Scientist and mathematicians do tend to think about terminology quite frequently: communicating with other scientist and mathematicians is a major part of doing science, and "the reviewers couldn't follow your argument" is a valid, and not especially rare reason for rejected articles in mathematics. Given the amount of thought put into it, "intuitive" names do tend to come about when possible (as it happened with what we now call the Ham Sandwich theorem, the concept of Fibration, the Squeeze Lemma, and countless others).

Given that mathematicians do put thought into terminology, there's often a good reason for not having more intuitive names: maybe no good common-sense intuition was available (e.g. Chu constructions are too general for this sort of thing), or the thing comes up only in highly specialized contexts where it's not worth bothering with it (e.g. Girard's paradox), or there are too many different metaphors that one would have to invoke to describe the situation appropriately, so that it's more efficient to derive a completely new term from an associated name (e.g. Abelian became such an adjective, which now has its own associations).

It's telling that the author criticizes terms like "Calabi-Yau manifold", but doesn't suggest any alternative: coming up with an insightful name that communicates the key properties of such an object, and is easier to use and remember than "Calabi-Yau" is, let's just say, very very hard.

The same phenomenon is not limited to mathematics. Would Dijkstra's algorithm, the Haber–Bosch process or the Otto cycle be easier to learn and remember if they had snappy, insightful names? Probably. But the same concerns apply. It's hard to come up with genuinely better, more descriptive names for these processes. And even if we were successful in popularizing newer, better names, we would find that the names were not the real bottlenecks that made computer science, chemistry or mechanical engineering difficult to master.

Post reply on HN