Avoid Else, Return Early (2013)

Re:Avoid Else, Return Early (2013) by jochung on Monday March 26, 2018 @10:44AM (#16679239)

I have the exact opposite experience. If you find yourself annotating your variables and methods with extra adjectives and nouns, your code isn't simple enough. Those explanations go in code comments.

Often it means you can refactor it so that there is only one of any "thing" so there is no need to clarify which version or role this "fooBarThing" is serving to disambiguate it from the other "bazBarThing".

Functional composition and well structured data is the key to this. It's basically halfway to point-free style.

[ Parent | on HN ]

Re:Avoid Else, Return Early (2013) by fouc on Monday March 26, 2018 @10:30PM (#16684664)

The variable name can just be fooBar, and bazBar, and organized/namespaced such that you could have Thing.fooBar and Thing.bazBar (assuming you want those exposed to the rest of the application).

Readable variable names doesn't mean wordy names. I would avoid using more than 2 words in a variable name.

[ Parent | on HN ]