[windows2020]

IME, writing code as concise as possible (semantically and syntactically) is almost always the best route. I don't believe superfluous assignments, parenthesis, braces, visibility modifiers or comments make things more easily understood by others. In time, experience and mastery of the language will reveal superfluous code as something that does the opposite as well as much cleverness as mere utilization of the language or abstraction.

[watwut]

Strongly disagree. Working on codevase that was written by "short is better" people was harder and I hated it.

I don't care for your saved strokes. Make it apparent.

[windows2020]

From a syntax perspective, I would argue the grammar of a language does make it apparent.

[jcelerier]

You're generally not supposed to think about grammar rules when you read or write a language you know (code or prose)

[windows2020]

Your omission of a period is ironic.

[shkkmo]

He is doing exactly what he says; that isn't irony in any sense of the word. You could call it emblematic, but not ironic.

[jcelerier]

You're making my point: the period being there or not does not matter, what matters is that you were able to parse my sentence and understand it without issue, and without needing to think about its grammar, thanks to the pattern-matching abilities of your brain.

[blacktriangle]

That's the key...in time.

In time doesn't help when the majority of your devs are junior which is a common case in large internal dev shops.

[windows2020]

How will they learn to better express logic or master the language without experience?

[JanisL]

I think this blog post is highly relevant https://daedtech.com/how-developers-stop-learning-rise-of-th...

[Pet_Ant]

They won’t. They’ll be mentoring other juniors and then onto management long before then.