I sent remote hands to pull a server for a customer that was done with their contract and another for failure not pay.
Got the wrong boxes, disconnected two customers, put the servers on the shelf and left for the weekend.
So I cut a ticket to the next remote hands guy and tell home to get the boxes back up and running and we'll deal with it Monday.
Cut another ticket to a third text Monday to pull the boxes. Yeah, you guessed it wrong boxes again. Same customers, what the fuck.
Have the boxes reracked and drive out there to do it myself. Count the servers, wrong label, do some digging around, 'OH'. Pull the right server. Loose two customers. Cut tickets for all racks to be relabeled starting from one.
People don't expect 0 index in the physical world. It's just too clever by half.
It's still likely bad. Your brain is simply not wired to zero index physical objects.
Building floors are more ambiguous - there can be basement, ie "negative" floors. So, floors in continental Europe are generally indexed 0-based (basements ..., -2, -1, ground floor = 0, upper floors 1, 2, ...). A German friend of mine caused some confusion when she checked into her student dorm at a US college, and having being told that her room was on the first floor, asked whether there was an elevator, as she had heavy suitcases.
US D F
3 2 2
2 1 1
__1__0__RdC
B1 -1 je ne sais pas
At first, people name the machines after the software they install on it. Then, when you get to about 4-5 machines, you start finding a "cute" naming convention (Constellations, Star Trek ships, mythological figures). As long as there is only a handful of machines, it's easier to remember which machine does what.
Then, as you start to scale up, between a few tens to a hundred, finding names gets harder, so you switch to a more standard naming conventions. Something that communicates the physical/logical location and the organizational unit, as well as an index for duplicates / replicas / redundant machines.
So I think it's fine to be clever as long as it's manageable. The moment it's going to start getting out of hand you can switch to a more scalable approach.