27 essays
Software Architecture
How boundaries, contracts and dependencies shape what software can become.
Browse the shelf
Ideas recur from different directions. These shelves gather the essays by what they examine, across product, software and organisations.
One essay may sit on several shelves. Its leading topic appears first.
27 essays
How boundaries, contracts and dependencies shape what software can become.
19 essays
How the product feels in the hand, across speed, interaction and platform boundaries.
19 essays
How team boundaries, management structures and decision rights shape the work.
15 essays
How engineers review, explain and improve work while keeping responsibility close to it.
14 essays
How latency, rendering and perceived speed shape the experience people actually feel.
13 essays
How shared foundations, standards and services make safe delivery easier across products.
11 essays
How numbers reveal or distort what systems and people actually experience.
11 essays
How systems fail, recover and remain observable when traffic and change expose their assumptions.
10 essays
How local environments, repositories and feedback loops make engineering work easier or harder.
10 essays
How AI changes engineering work, architecture and the value of human judgement.
10 essays
How evidence becomes a decision, especially when the obvious answer is incomplete.
9 essays
How intent, decisions and accountability travel through meetings, messages, diagrams and engineering records.
8 essays
How changes move safely from an idea into production, and where that movement stalls.
8 essays
How one shared codebase changes organisational ownership, integration, standards and memory.
3 essays
Physical constraints, imperfect lines and old media as correctives to digital sameness.
2 essays
How engineers contribute across ownership boundaries without weakening stewardship.