Naming things

Naming things is hard.

"'There are two hard things in computer science: cache invalidation, naming things, and off-by-one errors.' - Martin Fowler"

General advice

 * Avoid ambiguity : search for similar keywords in existing features, extensions, and products, to avoid confusion and a profusion of hatnotes/seealsos. (e.g. Collection vs Collections, Beta vs Beta)
 * Make it easy to pronounce, to type, and to remember : avoid l33t5p34k, difficult capitalizations (e.g. SyntaxHighlight GeSHi), and dashes if camelcase is the local convention
 * Consider the translations : if it is a user-facing feature, this is extra important. Is the word almost-untranslatable or extra-long, in any discoverable language?
 * Check it isn't a restricted keyword in the usual programming languages : (e.g. Echo)
 * Contractions : people tend to shorten anything they can, especially if they write it regularly, as helpdesk people and dev people tend to do. (e.g. visual editor is "VE" to many people)
 * Stick with a single name : try to pick just one identical codename & user-facing product name. (e.g. Page-triage/Page-curation/Newpagepatrol/Newpagesfeed, Echo/Notifications)