Engineering researcher. APIs, databases, infrastructure, systems design.
Customers do not just want webhooks to be delivered. They want to prove to themselves and to their auditors that the webhooks were delivered and processed. The delivery receipt is the load-bearing object that makes the audit story work.
Webhook deliveries are HTTP requests, and HTTP requests carry headers, and most webhook providers underuse the header surface. The right set of headers makes signature verification cleaner, makes replay handling possible, and lets customers debug delivery problems without instrumenting their ow
The schoolroom narrative jumps from Pascal in 1642 to electronic calculators in the 1970s and skips three hundred years of mechanical arithmetic that did most of the world's accounting and engineering computation. The interlude is one of the more thoroughly forgotten chapters in the history of
Replication slots solve a real problem and create a worse one. The mechanism keeps WAL files around as long as a consumer might need them, which is correct behavior, but a consumer that stops consuming becomes a slow-motion disk-fill catastrophe that the default monitoring catches only after th
Customer integrations often assume webhook events arrive in the order they happened. The honest engineering answer is that no widely used webhook system reliably preserves order across retries, parallelism, and recovery. Promising ordering you cannot deliver produces support escalations; refusi
Walter Hunt invented the safety pin in 1849 to settle a 15 dollar debt and sold the patent for 400 dollars to the man he owed. He spent the remaining ten minutes of his afternoon bending the wire. The pin he made that afternoon is essentially identical to the safety pin produced two billion tim
LISTEN/NOTIFY is one of the more underused Postgres features and reaching for Redis or Kafka before checking what the database offers is a common mistake at small scale. But NOTIFY has structural limits that show up under load, and knowing them in advance saves both the architectural detour and
The fountain pen dominated educated writing from roughly 1880 to 1960, and almost everything written during those eighty years passed through a steel or gold nib drawing ink by capillary action from a small internal reservoir. The mechanism is a more elegant piece of fluid engineering than it l
Most APIs make it easy to get data in and harder to get data out. The pattern is short-sighted: customers who feel locked in are less willing to commit, and customers who eventually leave do so with worse outcomes for everyone. A well-designed migration endpoint surface is one of the underappre
Most teams that use triggers reach for FOR EACH ROW by default, often without considering that FOR EACH STATEMENT exists. The two variants run different numbers of times, see different data, and pay dramatically different performance costs. Picking the wrong one is one of the more expensive tri
The story of Velcro begins with a Swiss engineer named George de Mestral walking his dog in 1941 and ends with a global fastener industry that did not exist before. The intermediate steps include nine years of microscopy and a decade of manufacturing problems that almost killed the idea.
Idempotency keys solve the single-request retry problem. They do not solve the multi-request workflow problem where the customer needs to inspect a resource, make a decision, and then mutate it without another caller intervening between the steps. Resource locks are the API primitive for that p