> If you are writing JS/TS, I can strongly recommend trying to write your own custom liter rules. It's quite simple and it's a great way to establish "architect

> If you are writing JS/TS, I can strongly recommend trying to write your own custom liter rules. It's quite simple and it's a great way to establish "architecture assertions". Use this tool (set the parser to ESLint): https://astexplorer.net/ https://astexplorer.net/ Goland devs have been doing that since the inception of the language since the standard library ships with a Go parser. It's a no brainer for modern languages. Code reviews shouldn't be spent catching formatting errors or naming conventions and coding guideline enforcement should be fully automated on a continuous integration server.