Here's a work in progress listing some naming-related red flags in code: https://www.natemeyvis.com/naming.html What am I missing?
-
-
Replying to @NateMeyvis
Are these variable names? If so probably just straight out length - maybe a recommended number of characters
2 replies 0 retweets 0 likes -
Replying to @Trabendo_daze
Eh, it’s 2021, autocomplete works well. Long names are often bad, but not usually because of the length per se.
1 reply 0 retweets 0 likes -
Replying to @NateMeyvis
For me they are bad because they take up a lot of space in the IDE or in tables when viewing some form of data frames. Not necessarily about remembering or having to type them.
1 reply 0 retweets 1 like -
Replying to @Trabendo_daze @NateMeyvis
If it takes a long variable name to add clarity to the code, please use a long name. However, needing a very long name to add clarity is a sign that something could to be extracted to isolate that complexity and make the instant use easier to name.
1 reply 0 retweets 0 likes
@butchhoward, I agree with pretty much everything you say here. FWIW, I think I described my note badly. I am interested in warning signs that a name is bad. So, for example, if I see foo and the_foo near each other in code, you know immediately that something's gone wrong.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.