5 ms·
I have the opposite problem as a recent new hire: when "cute" project names show up in a conversation, it signals something company-specific I need to learn abo
by fiddlerwoaroof 4y ago
I have the opposite problem as a recent new hire: when "cute" project names show up in a conversation, it signals something company-specific I need to learn about. When descriptive project names are used (especially if the projects are using really generic one or two word names like "routing-service"), it is harder to realize that people are talking about an implementation of a concept rather than a well-known concept.
- mattigames 4y agoThis is basically by fast the best argument to use cute names over some main components, and by "main" I mean when there are few of them, less than a dozen or so. An old name made of well-known technical words can easily suggest a level of complexity much smaller than what it has evolved into and therefore developers -specially new devs- should look it up instead of assuming what it does based on potentially misleading namings.
- leeches 4y agoSolved with company name or product name prefixes, like “discord-routing-service”
- ghostpepper 4y agoexcept nobody at discord would ever call it "discord routing service" in a conversation with other discord employees
- sirsinsalot 4y agoHandily, DRS and other D-prefix acronyms are easy to spot, hear, use and map to useful names.
- hooverd 4y agoWhat's not to understand about the account-provider-router-service? It's key to the business-data-sync service. We're working on a new account-provider-aggregator to replace it though.
- atom_arranger 4y agoI tend to jump to the opposite conclusion. If a name is cute I assume it’s something open source, named for marketing or SEO. If a name is descriptive I assume it’s probably internal.