Dillon Mulroy
Principal engineer at Cloudflare as of 2026, on agents and developer tooling. Streams TypeScript, OCaml and Neovim on Twitch, and wrote the better-result library after writing the same Result type about a hundred times.
Dillon Mulroy did not write this page.
We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.
Filter All topics · Newest first
-
Their wordseveryone voting yes deeply misunderstands the power of network effects
- 6 weeks earlier
-
Their wordsmy take has always been that "discipline doesn't scale" across teams and eng orgs and is a huge reason to use effect
-
Their wordsevery time i’ve built something without effect over the past almost 3 years ive come to deeply regret it and wish i had just done it from the start
- 10 months earlier
-
Their wordsdurable workflows are scaling errors as values to your infrastructure. errors as values lead to predictable, maintainable, and scalable software.
- 8 months earlier
-
Their wordsThis is what leads to slop JS/TS software. Treating errors generically like this is a mistake. It leads to fragile software, poor telemetry/observability/debugging, and as a result worse experiences
- 8 weeks earlier
-
Their wordsthe most important typescript feature is discriminated unions and everyone should be using them more
- 6 months earlier
-
Their wordsMy hot take is that JS has the lowest bar of entry to building and being productive (a good thing) but one of the highest bars of any language and stack to building high quality, stable, and reliable software. Very few devs have the expertise to pull off the latter
- 7 months earlier
-
Their wordsOne thing that drives me crazy about the React ecosystem, and more specifically "tech influencers" and "thought leaders" in the space, is the infantilization of the developers using and working in it. I’m tired of reading takes like TypeScript generics, mapped types, etc should only be needed and used by library authors for most use cases. Or today’s discourse; Don’t use `useCallback’, ‘useMemo’, and React.memo. If you’re building anything beyond a simple CRUD app or a an incredibly focused app with few features, you _will_ need these features.