2 ms·
The thing that more often than not that list of 'random' names isn't random. Exactly. For instance, my firewall is called "charon". Personification is a good
by blhack 17y ago
The thing that more often than not that list of 'random' names isn't random.
Exactly. For instance, my firewall is called "charon". Personification is a good thing and should be encouraged. It's easier to visualize things that way. From an inside-out perspective (people such as accountants who see everything but, for the most part, do not understand it), naming servers like $function_$row_$rack_$slot or whatever else makes sense...it will simplify things.
The problem is that it simplifies things from an inventory perspective, not from a "I'm trying to visualize this so that it all works" perspective.
Think about it like this: you have things in your kitchen, right? Say you have a toaster, a refrigerator, a mixer, and a microwave. You would NEVER call them things like "appliance_counter1_left", "appliance_floor_right" etc. This would be confusing. It is for this reason that humans give things names; toaster, refrigerator, and mixer are all names, they're just very common ones.
- jodrellblank 17y agoIf you worked managing a supermarket you would call them City17_shop5_aisle4_refridgerator2. > The problem is that it simplifies things from an inventory perspective, not from a "I'm trying to visualize this so that it all works" perspective. That depends - I'd much rather a firewall rule that told me that Glasgow Database Server 2 can talk to London Mail Server 3 for SMTP traffic than one that told me MissPiggy can talk to Kermit for χάρτης traffic. Especially when it's not a system I deal with every day and I haven't cached the name/function mappings in my head. On the other hand, the UK postal system works well with a mixture of numeric sequences (house and flat numbers), cutesy names (road names, city names) and arbitrary government assigned gibberish (Post Codes).