On teams I've had success with we've agreed on a style guide, peer reviewed code, participated discussion on a daily basis, and generally evolved the standards

On teams I've had success with we've agreed on a style guide, peer reviewed code, participated discussion on a daily basis, and generally evolved the standards and practices as a group. Agreeing on a style guide is important because it removes those issues from the daily discussion. We usually utilize an existing style guide that is agreed upon by the broader community as well. This doesn't close the door to "house rules", but provides a solid base line for discussing more important topics of design. In matters of style, we also prefer to have some automated formatting when possible. I've know people to set up their own formatter for work, and run it through the "official" formatter to commit. Personally think that is crazy. I can adapt to almost any style, but if that is what somebody is passionate about, who am I to judge?