Why do programmers have so little imagination when it comes to names? It should almost never be the case that project names conflict
For another, to do that we'd have to follow something like the prescription drug naming process https://globalhealthnow.org/2024-07/why-do-prescription-drug...
That way, instead of "Gemini", they could have named it something like "Cymbalta", "Xeljanz" or "Cialis" :P
Side note: I noticed that more "boring" and less sexy projects had cooler names a lot of the time, and my theory was that people were compensating for doing unsexy work.
Pick a descriptive name. Everyone else who is not in your team will thank you.
https://medium.com/better-programming/software-component-nam...
I wonder how much they pay Google for the top spot.
At most there might be a world where Google puts someone else's ad above the organic results.
-- Phil Karlton
It turns out that there really aren't that many possible project names before you get into the made-up "that sounds stupid" words.
Sure, if you want projects to have the same naming strategy as Chinese Amazon Marketplace vendors.
Away from that, significance in naming begins to cluster quite quickly.
> Why do programmers have so little imagination when it comes to names?
I assumed that you had a better than average method that you could share. But I guess you answered your own question:
> There is no such thing as a good name.
My corollary to this is "You should never reach for a language you are not fluent in for a name. Especially, just stop it with using Japanese words to name stuff please ffs"
I agree, but that still doesn't stop funny name related issues between languages. One of my favourites was Pidora (a Fedora release for the RPI) which caused offence to some Russian speakers.