Have you ever been focused on writing software and had to come up with a temporary variable name? At times like that, my creativity is focused on the code and not on picking that variable name. I used to pick names like “junk”, “junk1”, etc and they would later come back to haunt me when I used the same name twice in a piece of code. Then a very smart programmer showed me that, built right into my keyboard, was a nice selection of unique names!
If you are interested, please see
Your comments are welcome. All of us are smarter than any one of us.
You Tube Channel: https://www.youtube.com/user/rgsparber1
Here is an example of where the meaning isn't important:
Say I want to swap A and B:
qaz = A
A = B
B = qaz
These "keyboard" names would never be used outside of the immediate vicinity.
For names that are passed around, I like to use the initial caps format. For example, LongTermAverageFlowRate. It takes more typing, but like you said, in 5 years, it will still make sense. At my age, I will be confused tomorrow so need this long form.
Never try to tell me it can't be done
When I have to paint I use http://kbs.justoldtrucks.com/
I started coding with Fortran back when you wrote programmes on fixed format paper forms. So there was limited space for a line of code and it was usual to use the shortest variable names possible. As it was engineering/scientific work names like x,y,z and i,j,k and a,b,c fitted the job quite well. With that background added to a healthy helping of laziness I carried the short variable naming through for decades. I have still a tendency to do that but I have realised that it is much quicker overall to use unambiguous descriptive names as you show. The extra time taken for the increased typing is way less than the time taken to understand a non-descriptive bit of code the day after you wrote it.
It was late when I replied to your post and to some extent i misunderstood your meaning of temporary. During development I often add "temporary" variables to monitor values. These are temporary in the sense that they are removed once the code is finished, I try to use meaningful names for these.
That use of "temporary" is, of course, different from that in your "swap A & B" example, where the temp. var. qaz is actually a permanent part of your code. Anyway I still don't like it and I'd use something like "temp" or "C" in similar situations, but hey "different strokes for different folks" is what makes life interesting.
BTW. the phrase "once the code is finished" is of course jocular.
Quote Posted by Frank S "Makes me glad I'm not smart enough to write code"
Quote Posted by C-Bag "LOL! Luckily I just swallowed my coffee because it would have gotten all over the iPad"
Comment offered by Toolmaker51. Coffee isn't one of my beverages; couldn't fill watch crystal with that consumed so far. Glad and lucky enough to not have purchased equipment dependant on additional code or decoding. Bletchley Park this is not!
Post your reply!
Join 41,949 of us and get our 173 Must Read Homemade Tools eBook free.
...we'll learn more by wandering than searching...
There are currently 1 users browsing this thread. (0 members and 1 guests)