Subscribe for posts about software engineering, architecture, and functional programming.
I write about code that works and the craft of building maintainable systems. Expect technical deep dives, pragmatic reflections, and the occasional observation about web development's absurdities.
Get updates via RSS or email. Unsubscribe anytime (no hard feelings).
Remember when I said the book was almost done? It’s done. The first full draft, anyway 😅. Every chapter written, every code sample compiling, every paragraph existing in some form that I’m not immediately embarrassed by. I think.
I sat with it for a few d...
A lot of people are reaching for Effect-TS.
Every few months you’ll be three functions deep in some TypeScript service, squinting at a try/catch that swallows four different kinds of failure into one catch (err), and you’ll think: “Effect would fix this.” Then you look at the API surface, ...
It’s Friday, and I just signed a petition asking the Node.js TSC to vote no on allowing AI-generated code in Node.js core.
Someone opened a 19,000-line pull request to rewrite Node.js internals, with the disclaimer that “a significant amount of Claude Code tokens” ...
Two days ago I published a post about parsing instead of validating in TypeScript. I hand-rolled branded types with unique symbol, wrote Parsed<T> result types, and stitched together parsers with early returns. It worked. It was also kind of ugly, and...
I’ve been thinking about Alexis King’s Parse, don’t validate again. I do this quite regularly, actually, usually after staring at a TypeScript codebase that’s been quietly accumulating if (user.email) checks like barnacles. The post is from 2019, and ...