February 2026
14
There is a particular kind of satisfaction in encountering a system that simply works. Not the flashy, buzzword-laden architecture diagram, but the quiet kind.
11
Every time I watch a team reach for a message queue when a cron job would suffice.
09
Useful when you need to rate-limit API calls during batch operations. Drop-in replacement for Promise.all.
05
Simon's analysis is the clearest articulation of why prompt injection is a fundamentally new class of problem.
03
The gap between "interesting to build" and "pleasant to maintain" is where most technical debt lives.
January 2026
28
A confession and a framework: when TDD helps, when it hurts, and what I do instead for exploratory code.
24
A 40-line zero-dependency .env file parser that handles variable interpolation and multi-line values.
21
The best piece of software engineering writing published this decade and I am not even slightly joking.
17
Found this photo from 2014. The blinking lights of the production rack at the old office.
14
The ordering is the lesson. Most teams try to make it fast before they have made it right.
10
If you cannot name a function in five seconds, you do not understand what it does yet.
05
A retrospective on a decade-plus with Node, from callback hell to modern async/await, and the lessons that transcend runtime choices.
02
Configurable retry with exponential backoff, jitter, and abort signal support. The version I keep copy-pasting between projects.
December 2025
29
Counterintuitive career advice: the highest-paid engineers are not the best coders. They are the best simplifiers.
24
Architecture diagram for the 2026 platform migration, sketched out with the kids' markers.
19
The best documentation is the code you did not write. The second best is a three-sentence README.