Corporate Controlled Linters

I’ve worked for two large Fortune 500 companies and I’ve also worked for a mid-sized company.

Can someone convince me that not all linters are good? If they are commit hooking linters that are configured to nest shit into one line and densely pack 20 args/params undoing all dev attempts to make the code more readable, and there’s not much you can do because it’s a linter controlled at the sector/corporate level rather than at the individual team level (meaning you can’t configure it without going through someone who likes it the way it is)… and you’re mandated to use it because your team lead and their skips don’t want to fight up the chain… and because they’re not the ones programming either… and especially if most devs own their entire repo (so no one else except for the next hire to backfill) will read that repo.

I agree it’s a silly hill to die on, I guess I’ll just collect my paycheck then. Definitely motivates me to continue personal projects which I can control the quality of.

When linters are implemented well (and if not, then if you have the flexibility and luxury to configure the linter without running into heavy resistance), then I agree that could be good. But I would rather not have a linter if I’m going to have to deal with a shitty linter for 8+ hours/day.