Writing from an engineering
team that ships.
The Gaussford Library collects essays, technical writing, research notes and case studies from our engineering team. It's how we think in public — and how we teach the discipline we practice.
Browse by discipline.
Recent writing.
Business engineering as a discipline.
Why treating a company as a system — and applying engineering rigour to its design — is the highest-leverage decision founders can make.
Designing for the decade, not the demo.
Notes from ten years of building software that had to keep working long after the launch announcement fell off the front page.
SLOs, error budgets and the engineering of trust.
How we translate uptime commitments into release cadence, on-call structure and architectural pressure — without pretending reliability is free.
Threat modelling for teams that don't have a security team.
A practical, engineering-first approach to threat modelling that fits into a normal product cadence.
Evaluating AI features you actually ship.
Why offline benchmarks aren't enough, and how we build evaluation harnesses that live in the same repo as the product.
Re-engineering a legacy quoting platform.
How a nine-day quoting cycle became a four-hour one — and what the architecture underneath actually looked like.
Get new writing when it publishes.
Occasional, engineering-only notes. No newsletter theatre.