Practical write-ups on the decisions, trade-offs, and patterns behind the systems we design and operate — enterprise software, cloud, data, and security.
Handover is not a deliverable at the end of a project — it is a design constraint from the start. What we have learned building systems that outlive the team that built them.
Most cloud-cost tools help you see spend. They rarely help you reduce it. The leverage is upstream, in the architecture — and in the way teams make trade-offs.
You do not need a 40-person data platform team to benefit from data contracts. Here is a deliberately modest version that a five-engineer shop can adopt next sprint.
The enterprise zero-trust pitch assumes infinite budget and unlimited patience. Here is a staged approach a mid-sized engineering team can actually implement in a year.
Why we default to old, widely-used, aggressively unfashionable technology — and when we break our own rule.
If there is a question you wish our engineers had answered publicly, let us know. We will consider it for a future article.