Ask HN: Anyone have process for creating good internal application names?
11–20 of 27 posts
Re: Ask HN: Anyone have process for creating good internal application names?
#12Re: Ask HN: Anyone have process for creating good internal application names?
#13You should check Wikipedia's list: http://en.wikipedia.org/wiki/List_of_Star_Wars_planets_(C%E2...
Re: Ask HN: Anyone have process for creating good internal application names?
#14Re: Ask HN: Anyone have process for creating good internal application names?
#15Re: Ask HN: Anyone have process for creating good internal application names?
#16With 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.
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?
#17For 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).
Re: Ask HN: Anyone have process for creating good internal application names?
#18http://en.wikipedia.org/wiki/List_of_ships_%28The_Culture%29
Perhaps with acronyms for the longer ones e.g.
Sense Amid Madness, Wit Amidst Folly (SAMWAF)
Re: Ask HN: Anyone have process for creating good internal application names?
#19Re: Ask HN: Anyone have process for creating good internal application names?
#20The 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