One long-form post
The piece our engineers argued about most this month — a production decision, an architecture trade-off, a thing we changed our minds on. Always with a name on it.
The post that did the most work in our drafts that month, the one production note worth your time, and what we shipped. No sponsor slots, no newsletter swap, no growth hacking. Unsubscribe in one click.
A short letter, sent on the second Wednesday of the month. Plain text where it matters, code blocks where it helps. Most issues read in under six minutes.
The piece our engineers argued about most this month — a production decision, an architecture trade-off, a thing we changed our minds on. Always with a name on it.
Something small and useful: a config that saved a week, a regulator question we hadn’t seen before, a pattern we’re trying. Two paragraphs, one link.
Three lines on what went into production at clients last month — anonymised where it has to be, named where the client agreed. No vanity metrics.
No first name, no company, no job title. We don’t segment, we don’t score, and we don’t enrich the list. One email field, one button, one confirmation.
A few archive picks so you can decide before you subscribe.
The whole deal, written down. No legalese.
Skip the letter and book a 30-minute session with a principal. Same engineering perspective, two-way.