Trying to see it from their perspective, I can think of a few edge cases where the commenter might have a valid concern. For example, imagine a rigidly enforce

Trying to see it from their perspective, I can think of a few edge cases where the commenter might have a valid concern. For example, imagine a rigidly enforced style guide a from several years back that talked about the default return value for functions when there is no return value (e.g. always use void or something like that). Such a style guide, if rigidly enforced, might preclude the now-common idiom of method chaining, which has some really nice/useful applications. That said, consistency in code is a good thing. Think of it as another form of convention over configuration. Just don't be so rigid with it as to lock out interesting ideas/experiments every now and then.