In my experience the smarter engineers write code that's a bit sloppier. It's the stupider engineers that tend to be more into style. Smarter engineers see the

In my experience the smarter engineers write code that's a bit sloppier. It's the stupider engineers that tend to be more into style. Smarter engineers see the world through a different lens. They don't need ultra clear code because they are too smart and as a result their coding style reflects that. Things that are obviously easy to read to them actually aren't easy to read in general but they don't know that because they're too smart. The stupidest engineer often attacks pointless stylistic choices. First off style in general is more important to them because they aren't as smart... But additionally they can't differentiate between pointless stylistic conventions and ones that arent. For example, I've seen this: // More comments // Comment //This is a comment Get corrected in a review to this: // More comments // Comment // This is a comment Which is fine, but. Stupider engineers tend to follow certain common human ocd conventions. The corrected code does not practically improve the code at all even from a readability standpoint... it's just jarring to the ocd tendencies of the stupider engineers who cant tell the difference between his own ocd instincts and actual practicality of readable code. Auto formatters help alleviate these things a bit, but not always. I admit I'm more on the stupider side in terms of engineering.