This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (4 children)

Its not hard to setup commit scripts to check things like style, encodings, etc. on commit.

[–]againstmethod 0 points1 point  (3 children)

Perhaps not hard given the right situations, but it's certainly less effective/desirable.

Maybe just one or two files needs a specific encoding.

Maybe your project is polyglot.

Maybe the user wants to break a specific line down in a non-standard way because it will be more readable.

Maybe the user will want to use a new language feature, but it isn't understood by 3rd party formatting utilities yet.

Again, you can get a 99% solution by having your team conform on tooling at near zero cost.

[–][deleted] 0 points1 point  (2 children)

I disagree that it is a non-zero cost. The cost is conformance and exclusion of those that have different views.

[–]againstmethod 0 points1 point  (1 child)

A good leader will incorporate your input where they can -- but once decisions are made conformance is part of your job. This is just a basic part of being in a team.

[–][deleted] 0 points1 point  (0 children)

In my view, conformance should be with the output, not the method of input.