Naming things is hard, because you need to spend time thinking on:
context (yours and your audiences’) …and it needs to be future proof
semantics (does the name reflect the purpose) …and it needs to be context and local scope proof
pragmatics (does the name make sense in the scope of all other local names) …and it needs to be semantic and global scope proof
I mean if we had to spend that much effort on every single name, nothing would ever get done. So instead, we only think hard about names that have the widest audience (if that). Things that you really need to name right are:
branding names
project names
API names
So taking some examples from the article naming something ‘new’ isnt a good idea, but if you have 100 issues to fix and you need to prioritize, then maybe you can’t spend more than 10 seconds thinking about the name!
I think you should still take at least a little time to analyze even private variable names. I can’t tell you how many times I’ve see apples refer to a single apple object and vice versa.
Naming things is hard, because you need to spend time thinking on:
I mean if we had to spend that much effort on every single name, nothing would ever get done. So instead, we only think hard about names that have the widest audience (if that). Things that you really need to name right are:
So taking some examples from the article naming something ‘new’ isnt a good idea, but if you have 100 issues to fix and you need to prioritize, then maybe you can’t spend more than 10 seconds thinking about the name!
I think you should still take at least a little time to analyze even private variable names. I can’t tell you how many times I’ve see
applesrefer to a singleappleobject and vice versa.