This is a real challenge, and I believe the key is empathy and open communication. Senior developers often resist changes because they have strong reasons based on experience — sometimes it's fear of unnecessary complexity, other times it's concern about productivity. In my experience, the best approach is to involve them in the decision-making process. Instead of just presenting the new standards as a rule, open a discussion about the "why" behind the change. Show how it improves code quality, collaboration, or long-term maintenance. Also, bringing real examples, small experiments, or gradual adoption can help reduce resistance. When seniors feel heard and part of the solution, they are much more likely to support the change.

Approach the senior developer respectfully to understand their concerns. Explain the reasons for the coding standard changes, involve them in refining the standards, and suggest a trial implementation. Emphasize team consistency and offer support. Recognize their contributions to encourage buy-in and foster a collaborative, forward-thinking development culture.

I would first talk to the senior developer and try to understand why they don’t agree with the new coding standards. Maybe they have a good reason or past experience. Then I would explain why the change is needed—how it helps the team write better, cleaner code. I’d also ask for their ideas so they feel included. If they’re still unsure, I might suggest trying the new standards for a short time to see the results. The goal is to work together and do what’s best for the whole team.

If my senior developer resists changes to coding standards, I ask that person the question, “Why?”. I may learn the proposed coding standards are... - defective or inefficient, or improper for the given language. If the senior developer makes a valid point, I look to alter the proposed coding standards. - personal preference, and the senior developer is on the losing end. I remind the developer we follow the standard and, if standards are set by committee, recommend joining that committee. - good, and the senior developer’s standards are poor. I explain a senior developer is expected to model following the standards to others, as standards save the company money through reduced friction when maintaining the code.