Writing from the lab notebook.
Long-form essays on the engineering decisions behind systems that scale, and the SaaS economics underneath them. Two pillars, written down.
The Boring Infra Manifesto
Why your novel product needs a dull database.
// Choose well-understood, battle-tested infrastructure. Save your novelty for the product surface — the place where users actually notice it.
read note→Architecture is a Debt Schedule
Every decision is a loan against future development.
// A framework for deciding which architectural debts are worth taking on, which to refinance, and which will bankrupt you by year three.
read note→The Idempotency Tax
Every distributed system pays it eventually.
// Pay on day one with disciplined retry semantics, or pay double on day 800 when a duplicate webhook bankrupts a customer.
read note→COGS < CAC, Always
The first principle of SaaS economics.
// Why the unit-economics gap quietly defines every other decision you'll make — from pricing tiers to database choice to hiring plan.
read note→The True Cost of a Nine
From 99.9% to 99.99% uptime, in real dollars.
// Each additional nine is an order of magnitude more expensive. A working method for deciding which nines your business can afford and which it can't.
read note→Pricing the Multi-Tenant Database
When per-customer infrastructure quietly eats your margin.
// A pattern for architecting around the largest hidden COGS line in most B2B SaaS companies, before it becomes the reason you can't raise prices.
read note→Read something useful? Let's talk.
If a piece resonated — or if it provoked the opposite — that's usually the start of an interesting engagement. Either path lands in the same inbox.