3 ms·
Because enforcing it within a reasonably sized organization is still a tall problem. I can't even be trusted to follow my own style preferences from time to tim
by spyspy 8y ago
Because enforcing it within a reasonably sized organization is still a tall problem. I can't even be trusted to follow my own style preferences from time to time. All it takes is one rogue new employee who doesn't know better and now we have to rehash the same arguments again to teach them a lesson - and the lesson is rarely "this other way is better", it usually boils down to "just do it our way and shut up about it".
- staticassertion 8y agoReally? Just have your CI reject builds that don't lint...
- XorNot 8y agoExactly this. The beautiful thing about machine checked formatting and linting is that it's consistent, and the ask to conform to it is generally not onerous. If someone wants to make that the hill they die on, I would argue you're now into culture-fit issues with the employee not the process. This is, in sharp contrast I would add, to all my experience with code-reviews where colleagues are making style criticisms at the same time, which is an utterly useless experience that devalues the entire code review activity.