And those same ones commit stuff like the LoC I&#x27;m looking at right now that returns the results of a ternary, and there&#x27;s a fucking bang symbol in front of every boolean, topped off with a bang preceding the parens around that ternary (IOW, some of those bangs should cancel out, and aren&#x27;t needed). I ask myself, &quot;how did this escape code review?&quot; and the answer is probably that the senior dev who wrote it thumped the junior dev reviewing it with something along the lines of &quot;that&#x27;s how real Java devs do it&quot;, or something. I dunno, just guessing based on personalities. Same dev that self-admits he hasn&#x27;t written unit tests before, yet argues with me (who has written thousands) about how to write unit tests.<p>Though I wonder if what you describe isn&#x27;t just plain ol&#x27; bike shedding. I&#x27;ve seen it plenty in code reviews. Super sharp dev who generally writes great code puts a commit up for review, and someone feels like they ought to have <i>some</i> input, and because the code is otherwise solid they pick on grammar.