How to convince developers to adopt a single style code?

Question

C++ / C#

The administration instructed, as one of the experienced programmers, to develop and implement a unified coding style. Mostly C++ development sometimes C Most of the 15 programmers agree to follow a common style. But there are a few people who balk. They think that there is no need to put spaces and brackets in the same way, but they need to relearn the type. I even played democracy, arranged a vote and worked out the most general version, it does not help. Punitive measures, as experience suggests, do not help much, more often, on the contrary, they harm.

Tomorrow I have a debriefing meeting scheduled. Everything will be officially approved there. As a result, an order will be issued either simply for the department, or, if necessary, and the General will approve.

Can you generate ideas and arguments? I invented / copied and pasted 7 theses, but suddenly you say something else.

Answer 1

we solved a similar question for c# - it's just that the majority agreed on the format and screwed the settings into the resharper - after which everyone can reformat with one touch, even though the whole solution disagreed a little grumbled and got used to it

well, punitive measures are simple - if there are commits, the whole meaning of which boils down to "incorrect formatting" - a person gets in a thoughtful place

given the review - it naturally happened

ps some wrote out of habit - then in one click they formatted the finished one in "like everyone else", it did not cause any special problems to anyone

Answer 2

Democracy rarely runs on teams of over 5 people. In general, it rarely works in principle, but in less than 5 people - you can still agree.

You have done everything you could to provide arguments in the plan. Now you just need to insert the code-style at the build level, so that it falls if it is not followed, and that's it.

Answer 3

In the case of using a CI system, you can put a code style check along with testing and in case of problems - reject

It’s hard to work in this mode in the first month, then everyone gets involved

Answer 4

A unified code style is an axiom for working in a company / team: it increases readability, perception, support and subsequent edits. Easier to document. Within the framework of one project, it should be observed, but it is in a company (if there are more than one projects, of course) that you can use different ones, although it is better to choose a single style. This is from personal experience. He himself resisted for a long time, but after seeing the result, he changed his point of view. My advice - try to offer even as an experiment, and in the end - let the programmers read not their own code.

Answer 5

oblige.