This is why I spend a good amount of time setting up linters on new repos before even starting to make the application. It saves a ton of time in peer reviews because no one has to think about formatting. Some people may not like the rules chosen but official direction from the boss is "get over it". There are 0 comments on PRs about formatting which only ever annoys people and is a waste of good dev time.
Programmer Humor
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
On my current team, when we were trying to choose a style, my only input was "any style that can be checked/applied with a git commit hook."
I get some people prefer reading code in a particular format. Let them configure their editor to apply it, but let's keep the version history in one unavoidably consistent style. Pretty please.
for a second I thought I read
publ;c
Nah, it's actually publ;c
I felt that. I have a colleague whose coding style is different to mine and whenever they work on code that I originally wrote, I have to resist the temptation to modify things to camelCase.
Linters make these kind of things easier. Then you get mad at the tool rather than your coworker.
Does Prettier count as a linter?
I always thought linters were more to find bad practice and possible errors than control the code style
Some linters can do both. Getting one set up as an automated job whenever code is pushed to the repo is on my TODO list...
I don't get it
java_devs_when_they_see_snake_case