3 ms·
> because I do weird things like declaring variables that are as long as a highway Don't let people talk you out of descriptive variable names. It makes code m
by al_borland 4mo ago
> because I do weird things like declaring variables that are as long as a highway
Don't let people talk you out of descriptive variable names. It makes code much more readable, easier to understand, and will help when you come back to it later. We're not battling to save every bit anymore and editors have auto-complete.
Congrats on the project, I can't say much more, because GitHub locked me out for clicking between files too fast... I guess that's a thing now.
- DamixLord 4mo agoThanks
- bruce511 4mo agoNaming is hard. The name needs to be long enough to make the variable meaningful, but not longer. I have encountered a programmer (in the corporate space) who bought into the "longer name" concept, to the point where he started complaining that the compiler had a 128 char limit for variable names. For example instead of a variable called say "tax" he'd use something like "CustomerSalesTax". That was mostly bearable, but the context (and the fact it was the only tax field) made the extra description redundant. That habit expanded though. Until he had names 50+ characters long. By then the code is illegible. Especially when the difference in variable names is minor. As in TotalDepreciationAnnualisedInterimTaxValue versus TotalDepreciationAnnualisedInterimBookValue So yeah, descriptive names good. Verbose names bad.