This is my recent life as I started a (hopefully temporary) phone support role and the place I work has desktops with names like that but also, inexplicably, using all the hard letters in to hear well over the phone.
Ex: HPDHHPDEDPD-TS
Thanks goodness the folks I'm talking to can use a semblance of the phonetic alphabet.
Again, in my view (based on several years as a support monkey at the beginning of my career), desktops/laptops should be named based on their asset tags, LT891334 or DT993115 etc. That way, when you ask the user 'what's the machine name' and they have no idea, you can say 'read me the number that's on that big white sticker on the lid'.
I wasn't disagreeing with you at all and I really like your solution. I was trying to provide an example of desktops I deal with now that are sometimes impossible to distinguish on the phone without going full NATO alphabet.
It's untypable on a command line since you have to shoot all over the keyboard, and it probably won't auto-complete until you get to the last number.
There's other subtle problems to: its not sparse enough for the same reason. You're putting a lot of stock in an operator always seeing the right sequence of numbers, especially if your fleet grows and you now have a LDNTCADSP101 and LDNTCADSP110 for example.
They're also unpronounceable - you can't communicate them to other people verbally quickly or reliably.
The best thing we've currently done at my work is assign single-use mnemonic names to all the servers (and, I'm pushing for it to be everything) - so we have "subsidy", "until", "wedding", "opulent" as server names. Easy to remember when you're debugging, easy to say, and a sparse namespace - you're exceedingly unlikely to mistake one for the other, and they'll autocomplete easily. It plays right into the human associative memory too.