Live data from Hacker News

Ask HN: Anyone have process for creating good internal application names?

news.ycombinator.com

11–20 of 27 posts

Re: Ask HN: Anyone have process for creating good internal application names?

#16
post #2

With internal applications you likely won't have concerns about domain name availability, trademarks, etc., so how about a simple, plain English naming scheme, e.g., "Timesheet," "Expenses," "Inventory"?

There are often several systems being used concurrently that do the same thing: either due to different departments reinventing the wheel, or by somebody rewriting an application without retiring the previous one.

True, but that sounds like "security through obscurity" with regard to naming conflicts--two departments could both invent the same acronym as easily as a plain English equivalent (there must be a ton of "CMS" systems out there, considering "case" and "content" management).

As always it's a people problem that requires communication and coordination (and until that happens we're stuck with CLOTS, BUGR, and NIPL).

Re: Ask HN: Anyone have process for creating good internal application names?

#17
We once used the Latin names for constellations.

For example:

Pyxis -> "Compass"

Orion -> "Hunter"

There's usually a good mapping from the constellation name to a meta-feature of the app, for example, a large bloated app might be called Cetus (the whale).

http://stars.astro.illinois.edu/sow/const.html

Re: Ask HN: Anyone have process for creating good internal application names?

#20
Sure. We usually come up with job titles describing the "human" equivalent of what function the application performs; e.g:

The Warden - an set of scripts to manage chroot jailed workers

The Middleman - a heavily customized MQ/ESB

The Coxswain - an app that monitors/controls system components

Post reply on HN