I see the point of something like euw-69-r47s11-vm420, but a memorisable name is more useful if you are small/specialised enough that you need to remember which box does what.
Also, let people have some fun, the world is bleak enough.
There’s definitely a middle ground there. My previous job used a format like, first two letters were the company initials, third character was a number pertaining to the office location, and the rest was typically a shortened description of the server. If there were multiple there would be a number at the end.
So, the servers were named like, ta2dc1 for a domain controller, which doesn’t look like much to a layperson, but it made perfect sense to everyone in IT. As long as everyone follows the naming convention it will work.
At my new job all of the servers are named after comic book villains, and I have no clue what any of them are for, partly because it’s not written down anywhere.
Names are arbitrary anyway.
I see the point of something like
euw-69-r47s11-vm420, but a memorisable name is more useful if you are small/specialised enough that you need to remember which box does what.Also, let people have some fun, the world is bleak enough.
Is it rfc1178 that says not to use names that look like serial numbers because they’re not mentally distinct enough?
There’s definitely a middle ground there. My previous job used a format like, first two letters were the company initials, third character was a number pertaining to the office location, and the rest was typically a shortened description of the server. If there were multiple there would be a number at the end.
So, the servers were named like, ta2dc1 for a domain controller, which doesn’t look like much to a layperson, but it made perfect sense to everyone in IT. As long as everyone follows the naming convention it will work.
At my new job all of the servers are named after comic book villains, and I have no clue what any of them are for, partly because it’s not written down anywhere.