Codenames are good identifiers when lots of projects exist. There are more software projects now than EVER.

I welcome Splorg, Chizzel, Rapunzel, Brap, Titoid, and Chungus - I don't care as long as it's good.

Descriptive naming absolutely helps at first contact, especially when you’re scanning a dependency list or onboarding someone new. No argument there. But in practice, names stop carrying meaning pretty quickly anyway

Love this:

> Name your library after what it does. Use compound terms. Embrace verbosity if necessary. http-request-validator is infinitely superior to “zephyr” when someone is scanning dependencies at 2 AM debugging a production incident.

> The cognitive tax

> Every obscure name is a transaction cost levied on every developer who encounters it.

It’s not a mental burden, it’s a cognitive tax. Moreover it’s a transaction cost? Levied on people? Which loads their RAM?

Where’s the simple everyday English?

And the species of flies "Phthiria relativitae" was named as a pun on "Theory of relativity" and "Reissa roni" after "Rice-A-Roni".

RMS, of GNU's not Unix fame, has opinions on proper naming?

I can't call my new formula translation language FORTRAN because it's been taken, as have many other names. So now to avoid collisions, it's named after my cat.

I like good old names like the foobar2000 audio player. Iconic.

- Starts with lowercase.

- Means nothing.

- Good player.

https://www.foobar2000.org/