We use naming convention
s here at work. I think. In my opinion, system names
should MEAN something. Unfortunately, they often don't. I've worked a places where they were named after Colorado mountain peaks
over 14,000 feet
, places where they were named after Simpsons
characters, Marx Brothers
ological figures, etc etc etc.
These names do not contribute to usability. At least in a development situation, it would be better to use meaningful machine names. Developer's workstations should be have a name that readily identifies them as that developer's box. Servers should be identified by their function. If there is some systemic reason to not use sensible names, at least configure your internal DNS (or external, if remote access is desired) to alias useful names.
"DevServer01, QA01, Production01, DB01" and "devserver01.company.com, qa01.company.com, production01.company.com, db01.company.com" are far more useful (and easy for people to remember) than "purpleDC0021".