In a business with tens of thousands of servers, it makes sense to have long complicated names.
I’m actually not convinced of this approach. It’s one of those things that makes perfect logical sense when you say it - but in practice “DBDWWHORCLHHIP01” is just as meaningless as “Hercules”. And it’s a lot more difficult to say, remember and differentiate from “DBDWWHORCLHHID01”. You may as well just use UUIDs at that point.
Humans are really good at associating names with things. It’s why people have names. We don’t call people “AMCAM601W” for a reason. Even in conversations you don’t rattle off the long initialism names of systems - you say “The <product> database”.
At this point I’m just tired of the acronym salad we all tend to deal with at work
“Wait, was I supposed to bounce CDBWINPROD02 or DBCWINPROD02?”
Figured if I had a choice I would use more “human” names that allow the servers to have more of a “personality”
Perse for example has been having an issue with it’s bios and it’s been spending quite a lot of time in the underworld LOL
God I hate the “stuff as much information into a server name as you can with no separators in all caps” naming conventions…
In a business with tens of thousands of servers, it makes sense to have long complicated names.
For a homelab ? Not really.
I’m actually not convinced of this approach. It’s one of those things that makes perfect logical sense when you say it - but in practice “DBDWWHORCLHHIP01” is just as meaningless as “Hercules”. And it’s a lot more difficult to say, remember and differentiate from “DBDWWHORCLHHID01”. You may as well just use UUIDs at that point.
Humans are really good at associating names with things. It’s why people have names. We don’t call people “AMCAM601W” for a reason. Even in conversations you don’t rattle off the long initialism names of systems - you say “The <product> database”.
Amen, feels cold and unimaginative
Home server larping as a real enterprise server.