How does the team code code be standardized without too much restriction?

Title, code format specifications can use existing generic specifications, such as the PSR recommended format, or can be checked with related tools. What I want to ask here is the logic of the code, naming and other tools that cannot be checked. Many times it is a subjective preference. Of course, the premise is that functions are implemented normally.

Reply content:

Title, code format specifications can use existing generic specifications, such as the PSR recommended format, or can be checked with related tools. What I want to ask here is the logic of the code, naming and other tools that cannot be checked. Many times it is a subjective preference. Of course, the premise is that functions are implemented normally.

Implement code review system, for each function branch merger, must through the team within the level of at least one person or many people audit, and thoroughly implemented

@ The point of view I think is very inappropriate, internal implementation is entirely personal responsibility of the behavior is not reliable, the company will always have personnel flow or back to add the situation of the newcomers, if the laissez-faire eventually become difficult to maintain a big pit

In the case of multi-person development, the basic is that everyone is responsible for a module or a few modules (the withdrawal is each class or each code file is managed by a single person), so to unify is the external interface of these modules (that is, the method name called each other), This, of course, is what you can think of when designing a module.
Inside the module, it is up to the person to be responsible, and the inner function How to write, depends on his preferences. Do not emphasize the unified style too much internally, after all, it is difficult to unify, and will consume a lot of time.

