Re:Ask HN: Anyone have process for creating good internal ap...
by percept on Friday November 26, 2010 @09:11AM
(#1942404)
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"?
[ Parent
| on HN ]
Re:Ask HN: Anyone have process for creating good internal ap...
by timrobinson on Friday November 26, 2010 @09:21AM
(#1942422)
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.
Re:Ask HN: Anyone have process for creating good internal ap...
by percept on Friday November 26, 2010 @10:16AM
(#1942517)
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).