Learn something new every day.
- I am a senior software engineer working in industry, teaching and writing on software design, SOLID principles, DDD and TDD.
Location
Buenos Aires
Education
Computer Science Degree at Universidad de Buenos Aires
IMHO, using abbreviations makes code less readable and less declarative
Even being common in many mainstream languages they are code smells
Again, in my opinion.
to achieve 100% declarativeness, you should stop using abbreviations.
I've used both prolog and JS
Learn something new every day.
- I am a senior software engineer working in industry, teaching and writing on software design, SOLID principles, DDD and TDD.
Location
Buenos Aires
Education
Computer Science Degree at Universidad de Buenos Aires
Learn something new every day.
- I am a senior software engineer working in industry, teaching and writing on software design, SOLID principles, DDD and TDD.
Location
Buenos Aires
Education
Computer Science Degree at Universidad de Buenos Aires
Learn something new every day.
- I am a senior software engineer working in industry, teaching and writing on software design, SOLID principles, DDD and TDD.
Location
Buenos Aires
Education
Computer Science Degree at Universidad de Buenos Aires
Accumulator, maximum, array. Common names for library development in javascript.
However, the code above is also only slightly declarative because it’s still a command.
100% Declarative style imo doesn’t really exist in Javascript. Spend some time getting to know Prolog and you’ll see the difference.
IMHO, using abbreviations makes code less readable and less declarative
Even being common in many mainstream languages they are code smells
Again, in my opinion.
to achieve 100% declarativeness, you should stop using abbreviations.
I've used both prolog and JS
The variable names don't really come into whether it's imperative or declarative.
Abbreviations are a readability issue. I'd agree with you that they're generally less clear in most places except for examples and generics.
good names are clean and declarative.
bad names are not imperative, they are just bad
Code Smell 33 - Abbreviations
Maxi Contieri ⭐⭐⭐ ・ Nov 24 '20 ・ 2 min read
Yes, but the way you’re using the terms “declarative and imperative” is not aligned with the computer science definitions of those words.
Imperative code tells the computer to do something. “Reduce over this list of orders by summing their cost”
Declarative states an axiom or truth. “This value is the result of applying a fold right operation using the function
aonx”you are right.
I am abusing the concept.
It is declarative code with bad names
I don't agree because it should never be set on stone.
"Max" is pretty descriptive even if you don't use "maximum", inside that scope it's ok. Wouldn't be true if "m" were used.
However, in this example:
I would say one letter is the correct choice, since:
Having no abbreviations actually hurt how to read and generate just extra clutter.
My rule of thumb is to have the name length inversely proportional to the scope.
A dozens of lines function calls for bigger, descriptive names.
A one liner? Maybe one letter is enough.
'My rule of thumb is to have the name length inversely proportional to the scope'
It is fine.