git commit -m "That is some pretty pedantic nonsense, linter."
^^ You know it's been one of those sorts of mornings when you're anthropomorphizing particular pieces of software and hate his guts.
^^ You know it's been one of those sorts of mornings when you're anthropomorphizing particular pieces of software and hate his guts.
Linter wants me to put a complete sentence with enclosing HTML tags all on one line but I want to put it indented to match style elsewhere but linter says "Haha but *this* sentence is short so you could fit it all in 80 columns; one line it is!"
But as vexing as having this argument with a machine is it is FAR FAR SUPERIOR to having arguments like this with other engineers at the company, which is the inevitable consequence of not having a linter. I would seriously avoid sitting with a human linter at lunch.
One of best cultural hacks I've ever heard of for pull reviews is that you're allowed to make stylistic arguments ONLY by PRs against the linter; style that passes the linter is Officially Good Company Style. Style that doesn't breaks the build. Neither requires comments on PRs.
I also think that any language ever developed in the future which doesn't ship with the equivalent of "go fmt" is missing one of the smartest innovations in the history of programming management.
You can write "go fmt" in any language but the genius of "go fmt" is that it creates a Schelling point for the community: "Good go code is unmodified by go fmt; you should expect *functionally no* code samples, OSS code, or libraries to disagree with The One True Nitpicker."
(The other genius is that it is fast enough to run on basically every keystroke.)
