I don't think there's such a big gap there, either. It's not uncommon for developers to give large, general-purpose applications nondescriptive code names. This actually tends to be useful when trying to distinguish the names that marketing gives a product (which can change) with the names of the applications that back it (which shouldn't).
Even when they did descriptive names, it was all backwards like <instanceID>-<env>-<role>-<project> yielding things like 2-dev-db-something. Trying to explain how that made sorting machines by name impossible was alien speak to them.
I think the reason programmers are better with names is that we get to name many, many more things. Variables, functions, parameters, namespaces, endpoints, the list just goes on both in the small and the large.
Agreed. Nothing confuses me more than finding a network with a bunch of machines named for roles that they don't fulfill.
Even more infuriating is when you have a network like that, but the new machines have names that refer to the old ones -- so for example, the webserver may be "webserver," but the new replacement may be "real-webserver" and then the replacement of that may be "real-webserver-replacement."
I tack on "-linux", "-windows", "-android" and so on when appropriate.
I think it also often depends on how many machines your sysadmins have to manage, and how many they had to manage prior to this naming scheme. Once you've experienced the pain of too many odd names, and trying to figure out how to map them to roles, you don't generally want to go back, in my experience.
I never get why there's such a huge gap between admins and programmers on this. Programmers have sane, intelligent naming conventions beaten into them, and yet when I ask a sysadmin what server the Wiki is running on, half the time the answer is something like "legolas". That name would never make it through my code review.