Field notes

Thinking in systems.

Concise observations on architecture, reliability, delivery, and the organisations around the software.

Aug 03, 202612 min read

Treat architectural significance as a gradient: spend design effort where reversal, evidence, and accumulated coupling make change costly.

Jul 28, 20268 min read

The useful output of architecture work is not a diagram. It is a set of decisions a team can act on, challenge, test, and revisit.

Jul 14, 20268 min read

A struggling programme usually has capable people trapped inside a broken decision and delivery system. Start there.

Jun 30, 20269 min read

Reliable systems come from architecture, operations, incentives, product decisions, and incident learning working as one system.