[DonaldPShimoda]

I think we have different interpretations of what it means to be "verbose", which is why I instead directed my previous comment towards "clarity".

Wiktionary gives the following definition of "verbose" [0]:

> Abounding in words, containing more words than necessary; long-winded.

My point is that adding words for the sake of adding words is bad, always. It's one thing to say "My code tends to be on the more verbose side of things" and another to say "I prefer writing very verbose code." You should always be seeking to make your code as concise as possible while maintaining clarity.

It's that "while maintaining clarity" bit that's the tricky bit, really. On this, I think we agree. I always try to make my code as short and direct as it can be, but never at the cost of clarity. For example, I don't use cute inlined tricks unless they're idiomatic (or used everywhere in the code and explained in at least a couple places). I try to strive for clarity instead of verbosity.

[0] https://en.wiktionary.org/wiki/verbose

[AnimalMuppet]

> You should always be seeking to make your code as concise as possible while maintaining clarity.

Absolutely.

> It's that "while maintaining clarity" bit that's the tricky bit, really. On this, I think we agree.

Yes.