Agree on quality standards that the code must meet, such as readability, maintainability, and performance. Develop a coding standards document collaboratively, incorporating best practices from various team members. This document should serve as a reference for everyone.

When a team is split on coding practices, I bring everyone together for a constructive discussion, encouraging each person to share their perspective. I focus on finding common goals, such as maintainability, performance, or scalability, to align our objectives. To guide consensus, I propose implementing best practices or industry standards, sometimes backed by documentation or small trials to evaluate impact. If needed, we agree on compromises that respect both sides. This collaborative approach not only finds a solution but also builds a culture of respect and shared purpose.

Organize a workshop or brainstorming session to review different coding standards and practices, allowing the team to collaboratively evaluate their pros and cons. Establish a coding style guide based on best practices that incorporates input from all members, ensuring it aligns with project requirements and promotes consistency

If it's a 2 - 3 option scenario and there's no time constraints, get the strongest advocate for each position/ practice to 'Steelman' the others position. Just as a Strawman argument seeks to misrepresent the opposing view, a Steelman argument tries to ACCURATELY present the opposing view to the others satisfaction. This is an excellent way to find common ground through shared understanding of the teams goals.

Division of Teams on Coding Practices is the one which we regularly see in the Organizations which is one of the facts should be taken care of. -->Bringing everyone together to have a regular discussions and sharing different perspectives is one of the Key aspect. -->Also by developing the work preparation and having its progress by following defined structured Standardized Documentations is the other important aspect.