Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
it really depends i am a fan of variables like retVal in functions its fairly obvious whats going to happen to it.
-
brod100268yI lean towards longer descriptive variables but only because my syntax suggestions are absolute 🔥🔥 and it doesn't many more keystrokes..
-
alyx17528yI had to debug a 15-year-old C codebase recently. I *wish* whoever wrote it had used verbose variable names.
-
fonfi8238yDepends on situation but in most cases I'm for. We develop security appliaction with realtime alarm console based on websockets and we use there one- or two-letter named variables in order to minimize amount of data sent to the browser.
-
only and only descriptive names - self explained code, more ease on the eyes and the brains, faster code reading.
-
*agrees*
*looks at own code, with variables like: SomeVar, RandoVar, NeuArray, SomeArray*
"Bloody Idiot" -
zzguy6038yAcronyms are the devil! Its always perl devs that do this, I swear... If I have to look through one more 10 yr old perl script that looks like hieroglyphics, I'm gonna flip a bitch!
-
Yes, of course! But there's a practical limit at which "descriptive" becomes "unreadably verbose." (I'm looking at you, Java...)
-
I do if it's other people's code lol, but I still tend to do acronym vars in my own scripts.
Who prefers long descriptive variable names compared to variables that are acronyms?
undefined