frontend

How to Actually Use Linting for Team Success

Thoughts from the intersection of code, craft, people, and progress.

It’s not about rules—it’s about reducing friction.

Linting is valuable when it removes repetitive decisions and catches useful problems before review. It becomes less valuable when the team spends an afternoon debating a rule whose main achievement is moving a comma.

Linting works when it quietly removes low-value debate and catches mistakes early. It fails when the configuration becomes a collection of unexplained preferences that everybody learns to ignore.

There is a practical tension underneath this topic: we want enough structure to move confidently, but not so much that the structure becomes the work.

Make the work easier to do well

The leadership part is rarely the grand speech. It is the ordinary environment around the work: whether people can ask an awkward question, whether priorities stay still long enough to act on them, and whether useful effort is noticed.

My practical test is simple: after a conversation, does the other person have more clarity and more agency? Good leadership should not make the leader look essential. It should help the team make sound decisions without waiting for permission at every turn.

Leadership is not having every answer. It is making better answers possible.

Trust is built in small, repeatable moments. Say what matters, make space for challenge, and follow through when somebody takes the risk of being honest.

The details will change from project to project. The underlying habit of paying attention travels well.