Dillon Mulroy is a principal systems engineer at Cloudflare. He builds developer tools and publishes TypeScript libraries, with interests in functional programming and the way engineers learn from people using their products.[1][2]
Start with anti-slop →
Career
Mulroy describes joining Cloudflare in late November before the April 2026 interview and working on its Agent Experience team. His responsibilities included a dashboard agent and supporting agent infrastructure. Cloudflare’s current author page gives his title as Principal Systems Engineer. His public education record lists Mansfield University of Pennsylvania from 2011 to 2015.[2][3][5]
Contributions
Make the preferred code patterns explicit
Anti-slop turns his TypeScript and JavaScript preferences into Oxlint rules. Examples reject unsafe assertion chains, broad function contracts and code that discards known type information before asserting it back. Rules use syntax and lexical scope rather than a full TypeScript checker, so the project documents which same-file flows it can recognize and which imported definitions remain outside its analysis.[4]
Maintain a local policy instead of accepting a fixed package
The rules are intended to be copied into a repository and adapted to its standards. The installation skill configures Oxlint and records the upstream version; updates preserve local customizations. This makes the rules an explicit team policy. It does not establish that every rejected pattern is wrong in every program or that the linter proves correctness.[4]
Ideas
In his interview with Kent C. Dodds, Mulroy describes watching users work, learning from support escalations and treating observability as part of product engineering. His background includes internal insurance tools, consulting at Formidable and Vercel’s domains work. The common concern is how a tool changes the task someone must complete, including the repetitive steps that are easy for its builder to overlook.[3]
Tools, writing & talks
Tools
Start here
anti-slop
github.comVendored Oxlint rules expressing a team’s preferred TypeScript and JavaScript patterns.
Read the analysis boundaries and a few violation examples before enabling rules. Setup requires compatible Oxlint packages; copy the rules into your repository and review their policy against your own code.
Creator[4]Original source
Writing, research & talks
- Foundations, feedback, and agentskentcdodds.com
An interview about user feedback, developer tools and product engineering at Cloudflare.
Interview guest[3]