Completely agree about the linter suggestion. Whenever there is a squabble over style in any PR in my team, I ask them to merge, decide afterwards on a single

Completely agree about the linter suggestion. Whenever there is a squabble over style in any PR in my team, I ask them to merge, decide afterwards on a single solution and then write a linter rule. Often a custom rule is necessary. IMO the worst codebases to work on are those that have nitpickers that change taste all the time. Newbies join, try to "read the room" and find a lot of code that looks good, so they use it as a template. Only to be nitpicked because "we do things different now".