The Code Review Pyramid (2022)
From what I've seen so far, people <i>love</i> debating code style.<p>The main problem is that those programmers mostly care about superficial syntax and don't actually care about code readability or design. They just go for the lowest hanging fruit and criticise variable naming or whitespace because it is easy; they don't talk about the object graph or the event lifecycle of the program, because that's hard.<p>A very common thing I see nowadays is a forced adoption of gofmt/black/whatever, hoping it would solve the obsession with the formatting. However, this just locks in a (often substandard) coding style and removes <i>any</i> kind of personality from the code. This is good if you are a manager trying to treat your employees as fungible units of work, but is bad for actually maintaining a codebase. Also, it doesn't stop obsession with style, it just forces a specific style on everyone which most of the time, everyone slightly hates.<p>This is a really good article which summarises the problem way better than me. <a href="https://luminousmen.com/post/my-unpopular-opinion-about-black-code-formatter" rel="nofollow noreferrer">https://luminousmen.com/post/my-unpopular-opinion-about-blac...</a>