Linguistic Antipatterns

Even as a very grey bearded dev I love articles like this. Is it "basic", it sure is, and right on every count!!

"Unexpected side effects" is one of my pet peeves (No magic!!!).

Its a sin on two counts, bad design and a "linguistic antipattern"

Except it should probably be called semantic identifier antipatterns because the subset of language that has to do with meaning is the essential idea.

By choosing identifiers wisely combined with reducing cyclomatic complexity by describing actions with specific semantically-correct meanings, the amount of required comments and documentation to support a codebase properly can be reduced to essential familiarization material, defining of terms where needed, gotchas, and the explanation of specific engineering decisions and complex code.