But then people go from the memorable “Ebola” cluster to asynccompletionloggernodeweb where even with names that supposedly explain the function all the name pa

But then people go from the memorable “Ebola” cluster to asynccompletionloggernodeweb where even with names that supposedly explain the function all the name parts are utterly generic and related to implementation not purpose. Not that people should keep Ebola. It should name services with a little skill and based on purpose not implementation. “Log4JarScanner” not “goAsyncFilerTreeScanner”. Tho the repo name is go-tree-jar cause I suck at names. Another cost of rushing is names it becomes hard to refactor out. At least we have hierarchical dns and longer names now, so it can have he data center/as and not be 8 chars. God bless the people that have name rules like Us1aesas02 - ProcessPostEventNodeDaemonServ-0322.Dallas.internal.example.com is more legible.