Ah, must’ve been a fortran developer. I swear they have this ability to make the shortest yet the least memorable variable names. E.g. was the variable called APFLWS or APFLWD? Impossible to remember without going back and forth to recheck the definition. Autocomplete won’t help you because both variables exist.
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”.
Especially when you also have company and county tables. It forces people to look up what the c is aliased to before beginning to comprehend what you’re doing.
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.
Ah, must’ve been a fortran developer. I swear they have this ability to make the shortest yet the least memorable variable names. E.g. was the variable called APFLWS or APFLWD? Impossible to remember without going back and forth to recheck the definition. Autocomplete won’t help you because both variables exist.
He did write some Fortran in his past! What made you think it was Fortran influence?
72 characters per line/card.
Your first few programming languages usually influence you the most for the rest of your career.
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.
And the rest of you are COBOL programmers.
I vomit whenever I have to read one letter alias SQL. And then… I dealias it.
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”.
Especially when you also have
companyandcountytables. It forces people to look up what the c is aliased to before beginning to comprehend what you’re doing.At a previous job I had to work with an old database where all the tables and columns had 6-character names
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 😅
This film from 1975 is still relevant today: https://www.youtube.com/watch?v=7hdJQkn8rtA