entombed in the shrine of zeroes and ones

Our conference rooms are named after the three tallest mountains in the world; however, the difficulty of spelling and pronouncing Kangchenjunga has led many to simply call it Kang, which has led me to start referring to K2 as Kodos.

Really, the wiki host should've been called library-of-babel, but that's an unwieldy hostname.  aleph would've been better suited to the monitoring host, but that one has the boring sjl-monitor1 moniker, as it's a production machine.

I've had my issues with naming hosts before.  Even though the sane choice is to go with the boring but practical scheme for the production systems, it still feels like i'm giving up a fundamentally fun part of my job.

I'm also occasionally toying with the idea of changing my journal's name (and have been for a couple of years).  I keep coming up with cool names that unfortunately are not representative of, well, me.

So, we used to have an incredibly obnoxious and cumbersome naming scheme, where the first letter was either S for system or N for network, then a four-digit location code, which started with 1 for East Coast and Europe and 2 for West Coast and Asia-Pacific. Then a 3-letter code that gave a vague hint regarding the machine's function or model, then a 2-digit serial number. Thus, s2009mgw06 is the sixth mail gateway machine at location 2009 (our current colo).

The new and improved naming scheme is: one letter, P for production, D for development, Q for QA; a two-digit location code; a mandatory 3-letter, "vague hint" code; an optional 3-letter supplementary code; and a 2-digit serial number. Thus, p01dnsi03 is the third 'i'nternal DNS server at location 01 (the new colo).

Someone explain to me how the latter is an improvement. I really, really loathe this.