Insights

Writing from the trenches

Notes we write because they're useful to other engineers, not to chase a keyword.

#distributed-systems

Idempotency is a feature, not a fix

Why we treat idempotency keys as part of the contract, and the patterns that make retries safe by construction.

2026-01-09

#legacy-migration

SLOs without error budgets are just dashboards

A practical guide to defining service level objectives your business actually cares about, and enforcing them.

2026-01-30

#modernization

When a rewrite is the wrong answer

Why we usually improve the system you have before reaching for a from-scratch rewrite.

2026-02-20

#distributed-systems

Why we lean on boring technology

Our default stack is Node, Postgres, and friends. Here is why we rarely reach for the shiny thing.

2026-03-13

#legacy-migration

Reading a codebase you didn't write

The first week of any engagement is mostly reading. Here is how we get oriented without breaking anything.

2026-04-03

#api-design

APIs should be boring on purpose

Good APIs are predictable, versioned, and dull. Here is the bar we hold ourselves to.

2026-04-24

#platform-engineering

Shipping on Fridays (and why we don't fear it)

Calm deployments come from good habits, not from avoiding risky days. Here is our default setup.

2026-05-15

#distributed-systems

The database is part of the system, not a detail

Postgres is where your real constraints live. Treat it like a first-class part of the design.

2026-06-05

#legacy-migration

Talking to non-engineers about technical debt

Technical debt sounds like an excuse. Here is how we explain it so stakeholders actually get it.

2026-06-26

Tell us what you're building.

No sales call, no deck. Just an engineer who'll read your message and reply honestly.

Start a conversation