Lint for the Dryer: Don’t Repeat Yourself in Reviews, Agents, or Docs

This talk is confirmed. The time of the talk will be announced soon.
The recording will be published after editing. Multipass and Full ticket holders have early access.
Bookmark
Rate this content

If you've left the same code review comment twice, it should probably become a new lint rule. And if you've written that lint rule, this is your sign that there's a component or hook you're still missing. Our team built custom ESLint rules for our React app to catch things like stale dependency arrays or hand-rolled versions of components we already have. We'll draw on those to look at how to climb that ladder, and just as importantly, when to stop.

This talk has been presented at React Summit US 2026, check out the latest edition of this React Conference.

Tucker Chapin
Tucker Chapin
Video transcription, chapters and summary will be available later.