Cross-section illustration of a medieval castle's concentric defences seen from above at a slight angle: moat, outer wall, gatehouse, courtyard, inner keep

The phrase survived. The definition did not.

Consider a medieval castle. It is tempting to imagine that its security rested on the thickness of its walls, and that a besieging army faced essentially one problem, repeated: get past the stone. But that is not how a defended position worked, and the people who built them knew it. A castle was arranged so that every successful advance exposed the attacker to a new disadvantage. The moat forced engineering work under fire. The wall forced escalade or breach, both slow, both loud, both costly in men. The gatehouse compressed the attackers into a killing corridor where their numbers stopped helping them. The courtyard beyond it was overlooked from every side, so that taking the gate meant standing in the open beneath defenders who had been waiting for exactly this. And the inner keep meant that even total success outside its walls bought the attacker another siege, on worse ground, with a depleted force. ...

July 21, 2026 · 10 min

Architecture reviews that approve instead of challenge

Architecture reviews exist to catch problems before they become expensive. In practice, most reviews catch a different set of problems from the ones they were designed to find, and miss a different set from the ones that will eventually cause trouble. This is not because the reviewers lack competence. It is because most architecture reviews are not designed to produce understanding. They are designed to produce alignment and distribute accountability. Once that is the function, the outcome is predictable. ...

April 2, 2026 · 5 min