The problem is that you're not a sysadmin. I'm going to assume that you are a programmer since you are assuming this is simply a programming problem. I am a sy

The problem is that you're not a sysadmin. I'm going to assume that you are a programmer since you are assuming this is simply a programming problem. I am a sysadmin, and I can tell you that I outgrew cute server names many years ago because they hurt more than they could ever help. Reading this thread, it is painfully obvious to me that most people here have not been meaningfully exposed to large server installations. The last time I had servers with cute names, there were 12 machines total. Since then, I've worked in environments with hundreds and thousands of hosts. Even past a couple dozen servers, cute names become a liability and a significant distraction. Divining purpose, location, and other meaning by looking at a cute name when you have 30 servers is difficult and unnecessary. Applying the 3am standard (can a sleep deprived sysadmin do this task with minimal error at 3am?) cute names actually become rather cruel. The answer is to build an inventory system that lets the sysadmin map cute names to functional information. Or simply build that functional information in to the naming scheme. So sorry guys. As a professional sysadmin and fellow engineer I appreciate that you are looking out for what you perceive to be our sysadmin needs, but cute names are one thing we don't want or need. Unless perhaps you can come up with a justification for renaming the functions and classes in your code with cute names...