Notes on API contracts,
and the teams building against them.
Practical writing about OpenAPI, contract-first delivery, and closing the gap between design, backend, frontend, and QA.
Backend for Frontend: a practical introduction
Four requests to render one screen, business logic leaking into the browser, and a mobile team blocked on an endpoint. The BFF pattern, what it fixes, and when not to reach for it.
Read the articleBFF architecture at scale: GraphQL, the edge, and governing a fleet
Eight BFFs is an architecture, not an implementation detail. Where GraphQL genuinely wins, what server components absorbed, and the contract infrastructure that keeps a fleet comprehensible.
EngineeringRunning a BFF in production: failure, versioning, and drift
The first BFF is easy. The second year is where the pattern is tested — partial failure, timeout budgets, mobile clients that never update, and the slow accretion of logic that belongs elsewhere.
ProductConnecting Figma frames to the endpoints behind them
The link between a screen and the API that feeds it usually lives in one person's head. Here is how to put it somewhere it survives.
GuidesMock servers are how frontend stops waiting on backend
The most expensive hour in delivery is the one a frontend engineer spends blocked on an endpoint that does not exist yet.
API designOperation IDs: the small decision that survives every refactor
Paths change. Versions change. Teams reorganise. The operationId is the one identifier that can outlive all of it, if you choose it well.
EngineeringContract-first delivery, in practice rather than theory
Everyone agrees contract-first is a good idea. Far fewer teams can describe what they would actually do differently on Monday morning.
API designWhy API contracts drift, and what it costs you
Every team agrees on the contract at the start. Six weeks later the document and the running service disagree, and nobody is sure which one is wrong.