Yesterday, I wrote about how your code base should look like one person wrote it, even when you have a team.
A big part of that is having a code style guide that documents team norms around authoring code. But in larger code bases, manually reviewing and enforcing that can become a big time suck.
That’s where tooling can be useful! My favorite tool for this is ESLint.
ESLint’s primary role is as a code linter to catch bugs.
You’d be surprised what you can accomplish purely through a robust PR review process and a clear standards document.
That said, tools to enforce and autocorrect basic syntax stuff can be quite helpful.
Absolutely but it can reduce a lot of work if as many things as possible are enforced before you get to that stage.