Using linters on a codebase is a way of automating quality control. It frees up time for engineers by shifting the meticulous checking for minor details to the linter instead of code reviewers. It also helps the engineer writing the code to get faster feedback directly in their text editor.
- Convenience is king—it’s easy to do the right thing if the right thing is encoded into linters.
- Closing the gap between previous technical decisions and the current quality bar is an essential part of engineering leadership and ratcheting linters to close the gaps is very effective.
- It seems possible to apply a similar strategy for improving organizational quality. Perhaps starting with improving quality of written communication.