4 ms·

"My account" is innocent enough, compared to some other real life examples. And it sometimes doesn't come from marketing, but from development too. I've worked

"My account" is innocent enough, compared to some other real life examples. And it sometimes doesn't come from marketing, but from development too. I've worked in company which added a "funny" codename to everything: features, libraries, sprints, sections of backoffice interface. I don't know, maybe for some developers it makes things more engaging, for me it added a ton of unnecessary stuff to memorize or look up. Also one of the reasons I don't like AWS. You really can call a router just "router", virtual machine "virtual machine" and so on.

justin_oaks 2y ago
I also don't like AWS's odd names, but there are competing priorities when choosing to name something. I thought of some things to consider when you're naming which may make you choose a (possibly terrible) proper noun instead of a generic term. * Is what you're naming a product which you can trademark? Or is it just a feature that would be silly to trademark? (EC2, Sagemaker, CloudFront vs account, billing profile, user) * Does the name help with people differentiating your product from your competitors product? * Does the name help people find the product when searching online? * Does the name help ensure that the product isn't regarded as "Just a (generic term)" when it is more than that?
grahamj 2y ago
My Account is not too bad but I dislike the trend towards calling every customer portal “MyAcme(TM)” Literally yesterday I saw a message on one of these saying “Log into your MyAcme” - announcing the top issue with this naming scheme to everyone.