The problem with using warnings on my team is that they are largely ignored. 😢 So if we really want your rule to make a difference, we set it to error. We preempt the pipeline build failures by running our git hooks before any push, so devs usually fix their transgressions (😅) before anyone else sees them. Of course, there are those who know they ways around the git hooks...
I do understand that warnings will frequently be ignored. But my point is that there are many things that "linter Nazis" have decided MUST LOOK EXACTLY AND PERFECTLY THE SAME throughout the entire code base. They use this same logic to make it sound like it's so hard to read code that has the opening curly brace on the conditional line - and then read other code that has the opening curly brace on a new line.
And I'm serious. These people make it sound like it's just so got-dang impossible to grok the code if they're affronted by different opening-curly-brace styles. They act like they couldn't even code before the use of linters, cuz there was just no way that they could ever be expected to read code that wasn't lock-step to "standards".
My whole thing with the warn vs error idea is that some devs really need to just get over themselves. If it's ruining your ability to read the code cuz my opening-curly-brace style is different than yours, and you can't possibly work in the codebase until all the opening-curly-braces conform to the same rule - then you should really consider a career in auditing.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The problem with using warnings on my team is that they are largely ignored. 😢 So if we really want your rule to make a difference, we set it to error. We preempt the pipeline build failures by running our git hooks before any push, so devs usually fix their transgressions (😅) before anyone else sees them. Of course, there are those who know they ways around the git hooks...
I do understand that warnings will frequently be ignored. But my point is that there are many things that "linter Nazis" have decided
MUST LOOK EXACTLY AND PERFECTLY THE SAMEthroughout the entire code base. They use this same logic to make it sound like it's so hard to read code that has the opening curly brace on the conditional line - and then read other code that has the opening curly brace on a new line.And I'm serious. These people make it sound like it's just so got-dang impossible to grok the code if they're affronted by different opening-curly-brace styles. They act like they couldn't even code before the use of linters, cuz there was just no way that they could ever be expected to read code that wasn't lock-step to "standards".
My whole thing with the
warnvserroridea is that some devs really need to just get over themselves. If it's ruining your ability to read the code cuz my opening-curly-brace style is different than yours, and you can't possibly work in the codebase until all the opening-curly-braces conform to the same rule - then you should really consider a career in auditing.