Live data from Hacker News

Mathematicians should stop naming things after each other

nautil.us

11–20 of 406 posts

Re: Mathematicians should stop naming things after each other

#11
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 integral

Re: Mathematicians should stop naming things after each other

#12
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?

Re: Mathematicians should stop naming things after each other

#15
I think the reason is that the concepts are so abstract, no concrete word makes sense. So in the face of an arbitrary choice people use names.

The situation isn't much better in computer science, where now when you look up half the simple nouns in the dictionary, you get some language, tool, or javascript library claiming it.

Re: Mathematicians should stop naming things after each other

#16
post #2

Some profiling would show that names increase the difficulty of math by 0.001%. I don’t see an issue here.

I'm curious if you feel the same way about programming -- do bad variable and function names only increase the difficult of understanding someone else's code or library by 0.001%?

Re: Mathematicians should stop naming things after each other

#17

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"

Re: Mathematicians should stop naming things after each other

#19

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"

Indeed, and in a previous era, "to google" was "Who wrote the main papers on this, who should I look up?". Honestly; that's true still today.

Re: Mathematicians should stop naming things after each other

#20
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.

For AWS, there's a website called "AWS in Plain English" that explain what each service does. For instance, it's pretty hard to guess what AWS Route53 does unless you've come across it elsewhere.

https://expeditedsecurity.com/aws-in-plain-english/

Azure naming is comparatively more pedestrian.

Post reply on HN