News for hackers. Stuff that matters.
Re:What I learned working with a senior engineer as a new grad by nnnnico on Friday August 19, 2022 @10:27AM (#32521385)
>They absolutely do have a cost.

what cost? aesthetics?

Re:What I learned working with a senior engineer as a new grad by patrick451 on Friday August 19, 2022 @11:10AM (#32521973)
Long, verbose variables are hard too read (it literally takes more time to read more characters), cause excessive line breaks, are harder to remember, and in general hurt readability more than they help.
Re:What I learned working with a senior engineer as a new grad by purplerabbit on Friday August 19, 2022 @10:42AM (#32521597)
Cognitive overload. Storing 3-4 succinct variable names in your head takes the same energy as storing 1-2 verbose variable names in your head.
Re:What I learned working with a senior engineer as a new grad by Jcampuzano2 on Friday August 19, 2022 @10:59AM (#32521833)
I think there's some nuance though. If I'm the one writing the code, sure I can keep 3-4+ succint names of things I came up with in my head.

But then somebody else needs to look at this code in the future, and they're scratching their head as to what these names represent. Or somebody didn't really put enough thought into what the variables are, or gave them a name that only half represents what they actually mean.

I basically threw away all care for how long a variable name is long ago and have never had a problem. I just name it with enough words it needs to describe what it represents and don't fuss with making it smaller. With a decent IDE you don't even have to remember the whole name for things half the time, only parts of it.

Re:What I learned working with a senior engineer as a new grad by __Parfait__ on Friday August 19, 2022 @10:58AM (#32521821)
Cognitive overload.. Perhaps it'd be best to provide and example of a "verbose" variable name as compared to a "succinct"

Personally I'm thinking more along the lines of

Succinct ->KEY

Verbose -> MAIL_SERVICE_API_KEY