←back to thread

Programmers and software developers lost the plot on naming their tools

(larr.net)
311 points todsacerdoti | 1 comments | 11 Dec 25 18:06 UTC | HN request time: 0.21s | source
Show context
marifjeren ◴[11 Dec 25 18:36 UTC] No.46235167[source]▶
There is actually a good reason not mentioned, not to name tools by their purpose:

- the purpose will change

Your "silicon-valley-bank-integrator" tool will eventually need to be updated to do something else.

Or your "login-page-config-service" tool may eventually do more than just logins.

Using gibberish or mythological names gives a nice memorable name that doesn't lead (or mislead) you to believe it does a particular thing which may or may not be correct anymore.

replies(3): >>46235330 #>>46235354 #>>46235368 #
1. dietr1ch ◴[11 Dec 25 18:49 UTC] No.46235368[source]▶
Also, being too precise and succinct about what the tool does ends up in a race for the name in competing implementations.

Project names should be unique enough to allow them becoming their Id,

- It allows to find the project.

- It allows the project to change, extend it's scope or narrow it.

Having an Id is really important, making that Id related to the project's original intention is nice, but secondary. (as long as it doesn't change enough that it becomes misleading).