3 ms·
This is a fantastic example of how to not write a blog post. Putting aside the ridiculous self quotes, the author has missed the point and value prop of linting
by vorpalhex 9y ago
This is a fantastic example of how to not write a blog post. Putting aside the ridiculous self quotes, the author has missed the point and value prop of linting entirely and set up a perfectly silly straw man in it's place.
Linting exists for two reasons:
1. To catch silly mistakes (unused variables)
2. To provide a standard style
In most code bases, and I imagine this is probably true for Invision, code is read much more frequently then it's written. Someone reading my code shouldn't struggle because I prefer tabs or spaces, or because I happen to appreciate an odd spacing scheme. Code should be relatively consistent, expected and non-magical.
Instead this blog post reads like a school kid mad that they have a dress code. There are valid concerns around linting:
+ linting rules can hurt good practices (what makes sense for one codebase may not make sense for all code bases)
+ they require regular review (is this pattern still the best one for the team?)
+ they may be overly designed (and require developers to spend more time fighting whitespace alignment then actually helping readability)
Of course, all of the above are fixable problems. There's no sense in throwing linting out with a ruleset. For most developers linting provides a lot of value in the form of immediate feedback, even if the rulesets used can be flawed.