Adrian Goldsworthy. Historian and Novelist
Published 27 Aug 2025This should have posted earlier this morning, but for some reason did not.
This is the follow up to last week’s discussion of grand strategy, looking at the reactions and criticisms of Luttwak’s ideas, followed by some of my own thoughts.
February 23, 2026
Grand Strategy of the Roman Empire PART TWO
February 22, 2026
QotD: The shift from “motte-and-bailey” construction to stone castles
As we move to stone construction and especially full stone construction (which we’ll define as the point when at least one complete curtain wall – don’t worry, we’ll define that in a second – is in stone) in the 12th century, we’re beginning to contemplate a different kind of defense. The wooden motte and bailey, as we’ve seen, mostly served to resist both raids and “hasty” assaults, thus forcing less coordinated or numerous attackers to set in to starve the castle out or go home. But stone walls are a much larger investment in time and resources; they also require a fair bit more careful design in order to be structurally sound. For all of that expense, the builder wants quite a bit of a security, and in the design of stone castles it is hard not to notice increasing attention towards resisting a deliberate assault; stone castles of the 12th century and beyond are increasingly being designed to stand up to the best that the “small army” playbook can throw at them. Of course it is no accident that this is coming at the same time that medieval European population and wealth is beginning to increase more rapidly, leaving political authorities (read: the high nobility) with both the resources for impressive new castles (although generally the number of castles falls during this period – fewer, stronger castles) and at the same time with more resources to invest in the expertise of siegecraft (meaning that an attacker is more likely to have fancy tools like towers, catapults and better coordination to use them).
To talk about how these designs work, we need to clear some terminology. The (typically thin) wall that runs the circuit of the castle and encloses the bailey is called a “curtain wall“. In stone castles, there may be multiple curtain walls, arranged concentrically (a design that seems to emerge in the Near East and makes its way to Europe in the 13th century via the crusades); the outermost complete circuit (the primary wall, as it were) is called the enceinte. Increasingly, the keep in stone castles is moved into the bailey (that is, it sits at the center of the castle rather than off to one side), although of course stone versions of motte and bailey designs exist. In some castle design systems, with stone the keep itself drops away, since the stone walls and towers often provided themselves enough space to house the necessary peacetime functions; in Germany there often was no keep (that is, no core structure that contained the core of the fortified house), but there often was a bergfriede, a smaller but still tall “fighting tower” to serve the tactical role of the keep (an elevated, core position of last-resort in a defense-in-depth arrangement) without the peacetime role.
While the wooden palisade curtain walls of earlier motte and bailey castles often lacked many defensive features (though sometimes you’d have towers and gatehouses to provide fighting positions around the gates), stone castles tend to have lots of projecting towers which stick out from the curtain wall. The value of projecting towers is that soldiers up on those towers have clear lines of fire running down the walls, allowing them to target enemies at the base of the curtain wall (the term for this sort of fire is “enfilade” fire – when you are being hit in the side). Clearly what is being envisaged here is the ability to engage enemies doing things like undermining the base of walls or setting up ladders or other scaling devices.
The curtain walls themselves also become fighting positions. Whether on a tower or on the wall itself, the term for the fighting position at the top is a “battlement”. Battlements often have a jagged “tooth” pattern of gaps to provide firing positions; the term for the overall system is crenellation; the areas which have stone are merlons, while the gaps to fire through are crenals. The walkway behind both atop the wall is the chemin de ronde, allure or “wall-walk”. One problem with using the walls themselves as fighting positions is that it is very hard to engage enemies directly beneath the wall or along it without leaning out beyond the protection of the wall and exposing yourself to enemy fire. The older solution to this were wooden, shed-like projections from the wall called “hoarding”; these were temporary, built when a siege was expected. During the crusades, European armies encountered Near Eastern fortification design which instead used stone overhangs (with the merlons on the outside) with gaps through which one might fire (or just drop things) directly down at the base of the wall; these are called machicolations and were swiftly adopted to replace hoardings, since machicolations were safer from both literal fire (wood burns, stone does not) and catapult fire, and also permanent. All of this work on the walls and the towers is designed to allow a small number of defenders to exchange fire effectively with a large number of attackers, and in so doing to keep those attackers from being able to “set up shop” beneath the walls.
[I]t is worth noting something about the amount of fire being developed by these projecting towers: the goal is to prevent the enemy operating safely at the wall’s base, not to prohibit approaches to the wall. These defenses simply aren’t designed to support that much fire, which makes sense: castle garrisons were generally quite small, often dozens or a few hundred men. While Hollywood loves sieges where all of the walls of the castle are lined with soldiers multiple ranks deep, more often the problem for the defender was having enough soldiers just to watch the whole perimeter around the clock (recall the example at Antioch: Bohemond only needs one traitor to access Antioch because one of its defensive towers was regularly defended by only one guy at night). It is actually not hard to see that merely by looking at the battlements: notice in the images here so far often how spaced out the merlons of the crenellation are. The idea here isn’t maximizing fire for a given length of wall but protecting a relatively small number of combatants on the wall. As we’ll see, that is a significant design choice: castle design assumes the enemy will reach the walls and aims to prevent escalade once they are there; later in this series we’ll see defenses designed to prohibit effective approach itself.
As with the simpler motte and bailey, stone castles often employ a system of defense in depth to raise the cost of an attack. At minimum, generally, that system consists of a moat (either wet or dry), the main curtain walls (with their towers and gatehouses) and then a central keep. Larger castles, especially in the 13th century and beyond, adopting cues from castle design in the Levant (via the crusades) employed multiple concentric rings of walls. Generally these were set up so that the central ring was taller, either by dint of terrain (as with a castle set on a hill) or by building taller walls, than the outer ring. The idea here seems not to be stacking fire on approaching enemies, but ensuring that the inner ring could dominate the outer ring if the latter fell to attackers; defenders could fire down on attackers who would lack cover (since the merlons of the outer ring would face the other way). As an aside, the concern to be firing down is less about the energy imparted by a falling arrow (though this is more meaningful with javelins or thrown rocks) and more about a firing position that denies enemies cover by shooting down at them (think about attackers, for instance, crossing a dry moat – if your wall is the right height and the edges of the moat are carefully angled, you can set up a situation where the ditch never actually offers the attackers any usable cover, but you need to be high up to do it!).
Speaking of the moat, this is a common defensive element (essentially just a big ditch!) which often gets left out of pop culture depictions of castles and siege warfare, but it accomplishes so many things at such a low cost premium. Even assuming the moat is “dry”! For attackers on foot (say, with ladders) looking to approach the wall, the moat is an obstacle that slows them down without potentially providing any additional cover (it is also likely to disorder an attack). For sappers (attackers looking to tunnel under the walls and then collapse the tunnel to generate a breach), the depth of the ditch forces them to dig deeper, which in turn raises the demands in both labor and engineering to dig their tunnel. For any attack with siege engines (towers, rams, or covered protective housings made so that the wall can be approached safely), the moat is an obstruction that has to be filled in before those engines can move forward – a task which in turn broadcasts the intended route well in advance, giving the defenders a lot of time to prepare.
Well-built stone castles of this sort were stunningly resistant to assault, even with relatively small garrisons (dozens or a few hundred, not thousands). That said, building them was very expensive; maintaining them wasn’t cheap either. For both castles and fortified cities, one ubiquitous element in warfare of the period (and in the ancient period too, by the by) was the rush when war was in the offing to repair castle and town walls, dig out the moat and to clear buildings that during peace had been built int he firing lines of the castle or city walls.
Bret Devereaux, “Collections: Fortification, Part III: Castling”, A Collection of Unmitigated Pedantry, 2021-12-10.
February 18, 2026
Battle of Manila, 1945
Real Time History
Published 3 Oct 2025The Battle of Manila 1945 was the only urban battle in the American Pacific War comparable with Stalingrad, Berlin or other European battles. In gruelling weeks of fighting the 6th Army fought in house-to-house combat against entrenched Japanese.
(more…)
QotD: Defending the borders of the Roman Empire
As Luttwak notes, modern historians and military theorists have a tendency to sneer at linear defense lines.1 In fact, some historians of ancient Rome actually blame the decline and eventual collapse of the empire on all the “wasted” energy spent building frontier fortifications. The argument against such “cordon” defenses is that for a given quantity of military potential, spreading it out equally along a perimeter and trying to guard every spot equally dilutes your strength. This makes it easy for an attacker (who picks the time and location of the battle) to concentrate his forces, create a local advantage, and break through.
The thing is, approximately none of this logic applied in the Roman situation. First of all, as we’ve already noted, a huge fraction of the threats the Romans faced were “low-intensity”: border skirmishes, slave raids, pirates and brigands, that sort of thing. Static fortifications, walls and towers, are often more than sufficient for dealing with these problems. Paradoxically, that actually increases the mobility and responsiveness of the main forces. If they aren’t constantly running back and forth along the border dealing with bandits, that means they can respond with short notice to “high-intensity” threats (like major invasions and rebellions) that pop up, and are probably better rested and better provisioned when the emergency arrives. So, far from diluting their strength, a lightly-manned series of linear fortifications actually enabled the Romans to concentrate it.
Secondly, those linear fortifications can also be very useful when that major invasion shows up, even if they are overrun. A defense system doesn’t have to be impenetrable in order to still be very, very useful. One thing it can do is buy time, either for the main army to arrive or for some other strategic purpose. The defenses can also act to channel opposing forces into particular well-scouted avenues of attack, or change the calculus of which invasion routes are more and less appealing. Finally, in the process of setting up those defenses, you probably got to know the terrain extremely well, such that when the battle comes you have a tactical advantage.
[…]
The third, and perhaps most important, reason why the Roman frontier fortifications were actually very smart is that they were carefully designed to double as a springboard for invasions into enemy territory. Luttwak coins the term “preclusive defense” to describe this approach. The basic idea is that an army can take bigger risks — pursue a retreating foe, seize a strategic opportunity that might be an ambush, etc. — if it knows that there are strong, prepared defensive lines that it can retreat to nearby. Roman armies were constantly taking advantage of this, and moreover taking advantage of the fact that the system of border fortifications was also a system of roads, supply lines, food and equipment storage depots, and so on. The limes were not a wall that the Romans huddled behind, they were a weapon pointed outwards, magnifying the power that the legions could project, helping them to do more with less.
John Psmith, “REVIEW: The Grand Strategy of the Roman Empire by Edward Luttwak”, Mr. and Mrs. Psmith’s Bookshelf, 2023-11-13.
- I, an ignoramus, assumed this was all downstream of the Maginot line’s bad reputation, but Luttwak says it’s actually the fault of Clausewitz.
February 10, 2026
QotD: The (historical) walls of Jericho
These strategic (and operational) considerations dictate some of the tactical realities of most sieges. The attacker’s army is generally going to be larger and stronger, typically a lot larger and stronger, because if the two sides were anywhere near parity with each other the defender would risk a battle rather than submit to a siege. Thus the main problem the attacker faces is access: if the attacker can get into the settlement, that will typically be sufficient to ensure victory.
The problem standing between that attacking army and access was, of course, walls (though as we will see, walls rarely stand alone as part of a defensive system). Even very early Neolithic settlements often show concerns for defense and signs of fortification. The oldest set of city walls belong to one of the oldest excavated cities (which should tell us how short the interval between the development of large population centers and the need to fortify those population centers was), Jericho in the West Bank. The site was inhabited beginning around 10,000 BC and the initial phase of construction on what appears to be a city wall reinforced with a defensive tower was c. 8000 BC. It is striking just how substantial the fortifications are, given how early they were constructed: initially the wall was a 3.6m stone perimeter wall, supported by a 8.5m tall tower, all in stone. That setup was eventually reinforced with a defensive ditch dug 2.7m deep and 8.2m wide cutting through the bedrock (that is a ditch even Roel Konijnendijk could be proud of!), by which point the main wall was enhanced to be some 1.5-2m thick and anywhere from 3.7-5.2m high. That is a serious wall and unlikely the first defensive system protecting the site; chances are there were older fortifications, perhaps in perishable materials, which do not survive. Simply put, no one starts by building a 4m by 2m stone wall reinforced by a massive stone tower and a huge ditch through the bedrock; clearly city walls [were] something people had already been thinking about for some time.
I want to stress just how deep into the past a site like Jericho is. At 8000 BC, Jericho’s wall and tower pre-date the earliest writing anywhere (the Kish tablet, c. 3200 BC) by c. 4,800 years. The tower of Jericho was more ancient to the Great Pyramid of Giza (c. 2600 BC), than the Great Pyramid is to us. In short, the problem of walled cities – and taking walled cities – was a very old problem, one which predated writing by thousands of years. By the time the arrival of writing allows us to see even a little more clearly, Egypt, Mesopotamia and the Levant are already filled with walled cities, often with stunningly impressive stone or brick walls. Gilgamesh (r. 2900-2700 BC) brags about the walls of Uruk in the Epic of Gilgamesh (composed c. 2100) as enclosing more than three square miles and being made of superior baked bricks (rather than inferior mudbrick); there is evidence to suggest, by the by, that the historical Gilgamesh (or Bilgames) did build Uruk’s walls and that they would have lived up to the poem’s billing. Meanwhile, in Egypt, we have artwork like the Towns Palette, which appears to commemorate the successful sieges of a number of walled towns
So a would-be agrarian conqueror in Egypt, Mesopotamia or the Levant, from well before the Bronze Age would have already had to contest with the problem of how to seize fortified towns. Of course depictions like these make it difficult to reconstruct siege tactics (the animals on the Towns Palette likely represent armies, rather than a strategy of “use a giant bird as a siege weapon”), so we’re going to jump ahead to the (Neo)Assyrian Empire (911-609 BC; note that we are jumping ahead thousands of years).
Bret Devereaux, “Collections: Fortification, Part I: The Besieger’s Playbook”, A Collection of Unmitigated Pedantry, 2021-10-29.
February 9, 2026
Why This Is The Greatest Lord Of The Rings Scene Ever
The Critical Drinker
Published 6 Feb 2026Since its the 25th anniversary of the trilogy, I figured I’d reminisce about my favourite ever scene from all three movies. And explain why I’m objectively right about it.
January 31, 2026
WW1: Hell in the Trenches | EP 4
The Rest Is History
Published 4 Sept 2025What happened at the crucial, bloody, Battle of Ypres in October 1914? How did the battle come about? Why did the Germans and the British fight each other so brutally and for so long to take Ypres? What made the fighting so particularly violent? How were the British able to repel the relentless German onslaught time after time? What was the famous “Kindermord” — “the Massacre of the Innocents” — in the German army, and how true was it? And, what would be the outcome of this almighty clash?
Join Dominic and Tom as they discuss the terrible Battle of Ypres; its significance to the First World War overall, and its consequences for the rise of Hitler in Germany later on….
0:00 – Adobe Express AD
0:49 – Intro: To the Front
3:26 – The Kindermord Myth
5:02 – Race to Ypres
11:04 – The Ypres Salient
17:07 – Crisis at Gheluvelt
23:29 – Uber & Folio Society ADs
25:43 – November Slaughter
32:05 – The Langemark Legend
44:02 – Why the War Didn’t Stop
(more…)
January 25, 2026
Grand Strategy of the Roman Empire – Part ONE, the start of the debate
Adrian Goldsworthy. Historian and Novelist
Published 20 Aug 2025Following on from videos about military planning under the Republic, and about forts and garrisons, today we will begin to look at one of the big debates in the study of the Roman army and the Roman empire — did the Romans plan in a rational and informed way how to secure and defend their empire for the long term future. In short, did the Roman emperors and their advisors have a Grand Strategy which informed their decisions. This time, we will think about how this all started, and in particular Edward N. Luttwak, The Grand Strategy of the Roman Empire (1976), which really kicked off and did much to shape the debate.
January 23, 2026
WW1: 1 Million Vs 1 Million at the Marne | EP 3
The Rest Is History
Published 1 Sept 2025What extraordinary events saw the French — already on the brink of defeat — take on the formerly formidable German army in a remarkable counter-offensive on the 4th of September, in France, in a clash that would later become known as the Miracle on the Marne? Why was this such a decisive moment in the events of the First World War How did it relate to the famous Schlieffen plan? Did it really see the French charging into battle in Renault taxis? And, why did it become one of the most legendary moments in all of French history?
(more…)
January 17, 2026
QotD: The introduction of tanks on the western front did not break the trench stalemate
Where the Germans tried tactics, the British tried tools. If the problems were trenches, what was needed was a trench removal machine: the tank.
In theory, a good tank ought to be effectively immune to machine-gun fire, able to cross trenches without slowing and physically protect the infantry (who could advance huddled behind the mass of it), all while bringing its own firepower to the battle. Tracked armored vehicles had been an idea considered casually by a number of the pre-war powers but not seriously attempted. The British put the first serious effort into tank development with the Landship Committee, formed in February of 1915; the first real tanks, 49 British Mark I tanks, made their first battlefield appearance during the Battle of the Somme in 1916. Reliability proved to be a problem: of the 49 tanks that stepped off on the attack on September 15th, only 3 were operational on the 16th, mostly due to mechanical failures and breakdowns.
Nevertheless there was promise in the idea that was clearly recognized and a major effort to show what tanks could do what attempted at Cambrai in November of 1917; this time hundreds of tanks were deployed and they had a real impact, breaking through the barbed wire and scattering the initial German defenses. But then came the inevitable German counter-attacks and most of the ground taken was lost. It was obvious that tanks had great potential; the French had by 1917 already developed their own, the light Renault FT tank, which would end up being the most successful tank of the war despite its small size (it is the first tank to have its main armament in a rotating turret and so in some sense the first “real” tank). This was hardly an under-invested in technology. So did tanks break the trench stalemate?
No.
It’s understandable that many people have the impression that they did. Interwar armored doctrine, particularly German Maneuver Warfare (bewegungskrieg) and Soviet Deep Battle both aimed to use the mobility and striking power of tanks in concentrated actions to break the trench stalemate in future wars (the two doctrines are not identical, mind you, but in this they share an objective). But these were doctrines constructed around the performance capabilities of interwar tanks, particularly by two countries (Germany and the USSR) who were not saddled with large numbers of WWI era tanks (and so could premise their doctrine entirely on more advanced models). The Panzer II, with a 24.5mph top speed and an operational range of around 100 miles, depending on conditions, was actually in a position to race the train and win; the same of course true of the Soviet interwar T-26 light tank (19.3mph on roads, 81-150 mile operational range). Such tanks could have radios for coordination and communication on the move (something not done with WWI tanks or even French tanks in WWII).
By contrast, that Renault FT had a top speed of 4.3mph and an operational range of just 37 miles. The British Mark V tank, introduced in 1918, moved at only 5mph and had just 45 miles of range. Such tanks struggled to keep up with the infantry; they certainly were not going to win any race the infantry could not. It is little surprise that the French, posed with the doctrinal problem of having to make use of the many thousands of WWI tanks they had, settled on a doctrine whereby most tanks would simply be the armored gauntlet stretched over the infantry’s fist: it was all those tanks could do! The sort of tank that could do more than just dent the trench-lines (the same way a good infiltration assault with infantry could) were a decade or more away when the war ended.
Moreover, of course, the doctrine – briefly the systems of thinking and patterns of training, habit and action – to actually pull off what tanks would do in 1939 and 1940 were also years away. It seems absurd to fault World War I era commanders for not coming up with a novel tactical and operational system in 1918 for using vehicles that wouldn’t exist for another 15 years and yet more so assuming that they would get it right (since there were quite a number of different ideas post-war about how tanks ought to be used and while many of them seemed plausible, not all of them were practical or effective in the field). It is hard to see how any amount of support into R&D or doctrine was going to make tanks capable of breakthroughs even in the late 1920s or early 1930s (honestly, look at the “best” tanks of the early 1930s; they’re still not up to the task in most cases) much less by 1918.
Bret Devereaux, “Collections: No Man’s Land, Part II: Breaking the Stalemate”, A Collection of Unmitigated Pedantry, 2021-09-24.
January 16, 2026
WW1: The Slaughter Starts | EP 2
The Rest Is History
Published 28 Aug 2025What was Britain’s first military move following the outbreak of the First World War? Where did the French launch their initial attack on the Germans? Whose army was the biggest and best of all the participants in the war? And, what unfolded at the pivotal Battle of the Ardennes in August 1914, on the frontiers of France, between the Germans and the French, and what would be the consequences of the outcome for the war as a whole?
Join Dominic and Tom as they discuss, in riveting, unsparing detail, the dramatic early engagements of the First World War, and the bloody Battle of Ardennes.
00:00 Who was Aubrey Herbert? The MP offered the throne of Albania
02:24 Expectations of WW1: catastrophe foretold
04:50 Britain’s war council: should the BEF go to France?
14:12 The French: splendid uniforms uniforms, and a daring plan …
20:05 Battle of the Frontiers
26:37 Charleroi: Lanrezac’s warnings ignored, French collapse begins
30:20 The Battle of Mons
42:00 French retreat as well: Joffre forced to abandon offensives
44:44 The Battle of Le Cateau: Smith-Dorrien decides to stand and fight
47:35 Le Cateau outcome: heavy losses, but strategic British success
49:04 The Great Retreat: exhaustion, refugees, collapse of morale
51:05 Sir John French proposes pulling back behind Paris
53:12 London & Paris reactions
56:09 Paris prepares for siege
(more…)
January 10, 2026
A Short Tour of Roman London
Scenic Routes to the Past
Published 19 Sept 2025The ruins of Londinium – London’s Roman predecessor – are not spectacular. But they are extremely interesting …
0:00 Introduction
0:40 City walls
1:47 St. Magnus the Martyr
2:26 Monument to the Great Fire
3:12 Leadenhall Market
4:10 London Mithraeum
6:19 Bank of England
7:08 Guildhall Amphitheater
8:14 The Gherkin
January 8, 2026
WW1: The War Begins… | EP 1
The Rest Is History
Published 25 Aug 2025Following the declaration of war in 1914, how did the outbreak of the First World War unfold? What were the earliest military engagements of this terrible, totemic event? Who were its key political players and how did they respond? What was the attitude to the war in Germany? Were the allies unified from this early stage, or were they suspicious and frozen by indecision? And, how did the Germans, with the mightiest army in all the world, make its move on “plucky little” Belgium?
Join Dominic and Tom as they launch into one of the most consequential events of all time: the outbreak of the First World War.
00:00 – Germany: from peaceful nation to war machine
02:30 – Introduction to WWI series: scope and importance
04:16 – Was Germany uniquely responsible for the war? Historians’ debate
06:12 – Fear versus aggression: German motivations
06:46 – The July Crisis: Sarajevo, blank cheque, Kaiser’s holiday, Austrian ultimatum
08:08 – Helmuth von Moltke the Younger: personality, melancholy, moustaches
12:01 – Germany’s strategic weakness: encirclement fears, manpower and GDP
13:45 – The Schlieffen Plan explained
18:06 – Von Moltke panics
19:00 – Kaiser signs mobilization order; emotional scene in Berlin
22:53 – The problem of Belgian neutrality and Britain’s obligations
23:47 – British cabinet debates: how far into Belgium would justify war?
25:04 – German ultimatum to Belgium: demands for railways and fortresses
26:14 – Belgium rejects ultimatum; King Albert’s defiance
27:59 – “A scrap of paper”: German gaffe fuels British propaganda
28:35 – King Albert’s speech to parliament: “Determined at any cost”
29:52 – Total War Rome (Creative Assembly)
30:37 – German invasion begins
36:18 – German reprisals in Belgium
50:00 – Comparisons with Allied conduct in Ireland, colonies, and elsewhere
50:47 – The Leuven library fire: destruction of manuscripts, global outrage
52:12 – Germany’s reputation collapses: admired culture turned to “barbarism”
53:28 – Fall of Brussels: German army enters the capital
(more…)
December 14, 2025
QotD: Why are Castles?
Castles differ from that other standby of medieval fortifications — city walls — in one crucial way, and that difference sheds a lot of light on their military application.
A massive city wall, like the one shown above, has the very clear purpose of limiting access to a city or town. Close the gates, and no one can get in. Try to get in, and we’ll shoot you! The walls are meant to protect the settlement, both its inhabitants as well as its structures and physical wealth.
A castle, on the other hand, has a much smaller footprint than a city. It might only be a few buildings and a courtyard. Indeed, as we’ll see later in the series, the earliest castles (the classic “motte and bailey” design) were relatively small fortifications of earth and timber, capable of being built in a matter of days.
Image of a motte and bailey style castle. This particular one would take much longer than a few days to make, but it’s worth noting that even this “primitive” castle of timber and earth would have been a serious problem for any attacker. (Duncan Grey – Display Board of Huntingdon Hill Motte and Bailey Castle – CC BY-SA 2.0).
Especially if a lord was not in residence, a castle might only have a garrison of a few dozen, a far cry from the walls around urban centers that protected thousands or tens of thousands of lives!
So why bother?
Because, unlike a city wall which is meant to defend everything within it, a castle isn’t built in order to protect a tiny bit of land on top of a hill. Instead (say it with me, class): a castle is built to deny an enemy freedom of movement.
It’s not about what’s inside the walls. It’s about what’s outside the walls.
A castle allows you to control a disproportionately large area of land.
That control matters a great deal, because land was the source of wealth in pre-modern contexts. In societies where 80-95% of the populace were farmers, wealth and power came from controlling arable land. Capital did not derive principally from urban centers — wealthy and valuable as those were.1
Before we go further into how that impacts war and politics, I want to take a moment and dig deeper into why a castle allows its owner to control the land, because it’s something that’s usually glossed over, and understanding this dynamic will have a significant bearing on everything else we talk about here.
The Ugly Nature of Rule
As I’ve explained before, in order to actually rule an area, the ruler needs to have a monopoly on legitimate violence within that area. The emphasis here is on legitimate violence, which is significantly different than just “brute force”; force alone will always be a temporary and unstable method of rule. [You can read this explainer for more on that.] A ruler’s legitimacy allows that monopoly to continue unopposed.
One of the main reasons why a ruler needs that monopoly is that it allows for the collection of resources for use by the state. I’m going to lump all this together under the word “taxes”, but to be clear: in pre-modern societies, “taxes” could include manual labor commitments, payments in kind (in crops, in material, etc.), or in cash.
For all that, the ruler needs his agents to have unfettered access to the country he aims to rule; his tax collectors, law enforcers, merchants, judges, and certainly his lords and military all need to be able to move freely throughout the realm in order to do all the necessary business of maintaining law, order, and the collection of taxes.
Those are the most basic elements of statehood, the most basic mechanism of ordinary, everyday governing.
Castles fit into that system the same as any other governmental or administrative center: it’s a place to collect and store resources, a place for state agents to shelter, a locale for arbitration of justice, a residence for a lord … A castle can be a courthouse, police station, secret service listening post, governor’s mansion, and revenue service office all in one.
And a castle is fortified for much the same reasons that governmental buildings across history have always been fortified.
Even if the majority of a subject populace believes your rule is legitimate — a big if! — then there will still be people who chafe at the collection of taxes and who feel wronged by the administration of justice. Those outliers — if indeed they even are outliers — might try something stupid, like taking back their resources or stabbing your
thugspeace-loving tax collectors. Better to have everything locked up, right?And if the castle is large, and visibly imposing? Well that doesn’t hurt, does it?
That’s the every-day purpose of castles, at least in the sense that on any average Tuesday morning, that’s what the castle is for. That’s what people in the castle are doing. Ruling.
Eric Falden, “What Were Castles Actually For?”, Falden’s Forge, 2025-07-29.
1. There are exceptions, of course, such as thassalocratic polities. But sea-faring societies don’t built castles and are therefore WAY outside the bounds of this discussion.
December 10, 2025
The Korean War Week 77: The Korean Winter Bites Hard – December 9, 1951
The Korean War by Indy Neidell
Published 9 Dec 2025Now that they’ve agreed on a Demarcation Line, the talk this week at the Panmunjom peace talks has turned to whether there will be restrictions or not after the signing of an armistice. Also, how would inspections work to make sure the other side is complying with the armistice terms? Perhaps a group of representatives from neutral nations? Meanwhile the troops are digging in to their winter defenses, as the frozen Korean winter descends upon them.
Chapters
00:00 Intro
00:48 Recap
01:16 Two New Points
08:42 Korean Winter
11:47 Communist Defenses
13:20 Summary
13:33 Conclusion
14:28 Call to Action
(more…)





