Comment by hnlmorg
5 hours ago
Whilst I do agree with you on that specific example, it’s worth noting that code standards as a whole are a somewhat blurry line that can be extremely subjective at times.
5 hours ago
Whilst I do agree with you on that specific example, it’s worth noting that code standards as a whole are a somewhat blurry line that can be extremely subjective at times.
I actually don't think it's worth noting. I think, if a particular code standard issue is really of value, it will be obvious. You will propose it and nobody will argue. I think the fact that code standards are contentious is proof they are extremely low value. Subtle effects are indistinguishable from superstition.
I think the particular choice of coding standards is low value, but I think the consistency they bring has a lot of value, at least potentially.
As a father of two boys myself, I know exactly where you're coming from. Like some adults, they'll argue over pointless details and miss the entire thrust of the discussion.
No, to repeat what I said, I think "consistency" to a programmer is like "fairness" to a child: it's not what you think it is and it probably doesn't apply to whatever situation it's being invoked.
3 replies →
I think you’re underestimating how opinionated developers are.
The fact that we are disagreeing on this point is great evidence that there isn’t an easy to define, proverbial line in the sand.
I know very well how opinionated other developers are. I'm explicitly saying it's a waste of energy to be that picky about code style.
There is an easy to define line: there is no line. It's not a boundary where "over here is good code" and "over there, not" we just don't have a good idea of where the line is. No. There is absolutely no line.
1 reply →