3 ms·

isResizableOrGrowableSharedTypedArrayIncludingDataView One of those irrational times of my year is when I inevitably hit something that really deserves a good

• eyelidlessness 3y ago
  I personally love these kinds of names. On a long enough timeline, using them either: - prompts someone to tell you the actual name for the thing, and now you know a name for something - calls out poorly considered dependencies/design - leads to naming a thing that deserves a name - calls out complexity which is inherent either to the domain or other aspects of the underlying architecture Every one of those is a positive outcome, and a less verbose name will never* be a better tradeoff. * There are many apparent real-world exceptions, but they always fall under the “naming a thing that deserves a name” category, even if the resulting name is less clear than the verbose one. And they’re almost always directly involved in core abstractions (i, acc, cons) or core domain concepts. Edited to make this less mistakenly ignorant of lisp.
• nikanj 3y ago
  We used to make fun of Java / Spring for names like this, but it turns out it was just being used for absolutely gigantic systems before other languages. (Yes I know your great uncle Bobert coded 644 million lines of Cobol for a massive app where all function names were less than 4 characters. I'm talking general trends here)