The easiest problem
The easiest problem
I worked with a developer who insisted on using the shortest names possible. God I hated debugging his code.
I’m talking variable names like AAxynj. Everything looking like matrix math.
Same. Old DB2 base from the 80’s that was migrated to Oracle in the 90’s then to Postgres in the 2010’s.
And the people there know all the column names by heart 😅
I don’t understand why people think that it’s acceptable.
As developers, we’ve had it drummed into us from day one that variable names are important and shouldn’t be one or two letters.
Yet developers deliberately alias an easy to read table name such as “customer” into “c” because that’s the first letter of the table. I’m sure that it’s more work to do that with auto completion meaning that you don’t even need to type out “customer”.
company and county tables. It forces people to look up what the c is aliased to before beginning to comprehend what you’re doing.
And you can write more than six characters, but only the first six are recognized. So APFLWSAC and APFLWSAF are really the same variable.
And without namespaces, company policy reserves the first two characters for module prefix and Hungarian notation.
Make it 63 (31?) to align with what C99 can distinguish.
Also: I really like unicode in identifiers. So if at all possible don’t just have a random string of letters and numbers, make sure to include greek letters and all the funny emojis. (I just forgot which languages and compilers etc allow that.)
Nah, I name all my variables after my homies.
int dave = 0;
Or Fortran variables that collide with Fortran built-in functions.
Keep in mind that array subscript and function call are both () in Fortran.
Single character variable names are my pet peeve. I even name iterator variables a real word instead of “i” now… (although writing the OG low level for loops is kinda rare for me now)
Naming things “x”… shudder. Well, the entire world is getting to see how that idea transpires hahah
That’s very reasonable, I can get behind that. (my stance is a partly irrational overreaction and I’m totally aware of it lol)
Abbreviations are definitely annoying. My least favourite thing to do with them is “Hungarian notation”. It’s like… in a statically typed context it’s useless, and in a dynamically typed context it’s like… kind of a sign you need to refactor
Most people use the term “Hungarian Notation” to mean only adding an indicator of type to a variable or function name. While this is one of the ways in which it has been used (and actually made sense in certain old environments, although those days are long, long behind us now), it’s not the only way that it can be used.
We can use the same concept (prepending or appending an indicator from a standard selection) to denote other, more useful categories that the environment won’t keep straight for us, or won’t warn us about in easy-to-understand ways. In my own projects I usually append a single letter to the ends of my variable names to indicate scope, which helps me stay more modular, and also allows me to choose sensible variable names without fear of clashing with something else I’ve forgotten about.
We have auto-complete just about everywhere now
vim
Older C compilers would truncate a variable name if it was too long, so VeryLongGlobalConstantInsideALibraryInSeconds might accidentally collide with VeryLongGlobalConstantInsideALibraryInMinutes.
Legend says that they used to do it after a single letter with Dennis declaring “26 variables ought to be enough for anyone”.
installing operating system: 15 minutes, give or take.
give a name to the computer: 45 minutes