My two cents on this beaten-up subject.
Any decent IDE Editor will show you the type of variable type - string,
numeric, pointer, constant, etc. when you hover over it. So variable
names are only of value for readability of the person who will maintain
the code when they scan the lines of code. If it is the same person who
wrote the program, or one versed in the shop standard, then that
expectation of readability changes. The audience brings expectations
and experiences with them, so if the shop standard is such and such, and
your eye is used to skimming and seeing variable names of xyz format,
and can comprehend them quickly, so be it.
My own naming standards . . . procedure names with uppercase letter of
the alphabet followed with a numeral.
But procedure names (the Actions) become the most important pieces of a
program, and they should have readily identifiable names. Names that
indicate intent. Because with actions, there is no "hover to discover"
attributes like with variables.
If you need to delve deeper, then it requires a click and file-open to
delve into what the Action is really doing if the name is not
descriptive. And that open-file breaks the train of thought.
And you are often left with naught but a comment line to describe the
action, and we all know what happens to comments, like when underlying
things change or actions move within a program.
midrange.com
