> There’s a lint rule about naming the error parameter in catch “error”, not “err” or “e”. Who cares about this shit???

That is certainly in the less important end of the linting rules spectrum. Nonetheless, conventions like these add up in larger codebases in my experience. The more consistency you have with things that repeat a lot across the code improve readability quite much because the brain is able to do more chunking over time.

Of course this doesn't matter that much when you are learning a language or a framework and only have a couple of files.