Let’s start with the first sort of risk mitigation: reducing the risk of failure. We can actually detect a lot of these strategies by looking for deviations in farming patterns from obvious efficiency. Modern farms are built for efficiency – they typically focus on a single major crop (whatever brings the best returns for the land and market situation) because focusing on a single crop lets you maximize the value of equipment and minimize other costs. They rely on other businesses to provide everything else. Such farms tend to be geographically concentrated – all the fields together – to minimize transit time.
Subsistence farmers generally do not do this. Remember, the goal is not to maximize profit, but to avoid family destruction through starvation. If you only farm one crop (the “best” one) and you get too little rain or too much, or the temperature is wrong – that crop fails and the family starves. But if you farm several different crops, that mitigates the risk of any particular crop failing due to climate conditions, or blight (for the Romans, the standard combination seems to have been a mix of wheat, barley and beans, often with grapes or olives besides; there might also be a small garden space. Orchards might double as grazing-space for a small herd of animals, like pigs). By switching up crops like this and farming a bit of everything, the family is less profitable (and less engaged with markets, more on that in a bit), but much safer because the climate conditions that cause one crop to fail may not impact the others. A good example is actually wheat and barley – wheat is more nutritious and more valuable, but barley is more resistant to bad weather and dry-spells; if the rains don’t come, the wheat might be devastated, but the barley should make it and the family survives. On the flip side, if it rains too much, well the barley is likely to be on high-ground (because it likes the drier ground up there anyway) and so survives; that’d make for a hard year for the family, but a survivable one.
Likewise – as that example implies – our small farmers want to spread out their plots. And indeed, when you look at land-use maps of villages of subsistence farmers, what you often find is that each household farms many small plots which are geographically distributed (this is somewhat less true of the Romans, by the by). Farming, especially in the Mediterranean (but more generally as well) is very much a matter of micro-climates, especially when it comes to rainfall and moisture conditions (something that is less true on the vast flat of the American Great Plains, by the by). It is frequently the case that this side of the hill is dry while that side of the hill gets plenty of rain in a year and so on. Consequently, spreading plots out so that each family has say, a little bit of the valley, a little bit of the flat ground, a little bit of the hilly area, and so on shields each family from catastrophe is one of those micro-climates should completely fail (say, the valley floods, or the rain doesn’t fall and the hills are too dry for anything to grow).
Bret Devereaux, “Collections: Bread, How Did They Make It? Part I: Farmers!”, A collection of Unmitigated Pedantry, 2020-07-24.
February 17, 2023
QotD: Risk mitigation in pre-modern farming communities
February 13, 2023
QotD: Oaths in pre-modern cultures
First, some caveats. This is really a discussion of oath-taking as it existed (and exists) around the Mediterranean and Europe. My understanding is that the basic principles are broadly cross-cultural, but I can’t claim the expertise in practices south of the Sahara or East of the Indus to make that claim with full confidence. I am mostly going to stick to what I know best: Greece, Rome and the European Middle Ages. Oath-taking in the pre-Islamic Near East seems to follow the same set of rules (note Bachvarova’s and Connolly’s articles in Horkos), but that is beyond my expertise, as is the Middle East post-Hijra.
Second, I should note that I’m drawing my definition of an oath from Alan Sommerstein’s excellent introduction in Horkos: The Oath in Greek Society (2007), edited by A. Sommerstein and J. Fletcher – one of the real “go-to” works on oath-taking in the ancient Mediterranean world. As I go, I’ll also use some medieval examples to hopefully convince you that the same basic principles apply to medieval oaths, especially the all-important oaths of fealty and homage.
(Pedantry note: now you may be saying, “wait, an introduction? Why use that?” As of when I last checked, there is no monograph (single author, single topic) treatment of oaths. Rather, Alan Sommerstein has co-authored a set of edited collections – Horkos (2007, with J. Fletcher), Oath and State (2013, with A. Bayliss) and Oaths and Swearing (2014, with I. Torrance). This can make Greek oaths a difficult topic to get a basic overview of, as opposed to a laundry list of the 101 ancient works you must read for examples. Discussions of Roman oaths are, if anything, even less welcoming to the beginner, because they intersect with the study of Roman law. I think the expectation has always been that the serious student of the classics would have read so many oaths in the process of learning Latin and Greek to develop a sort of instinct for the cultural institution. Nevertheless, Sommerstein’s introduction in Horkos presents my preferred definition of the structure of an oath.)
Alright – all of the quibbling out of the way: onward!
So what is an Oath? Is it the same as a Vow?
Ok, let’s start with definitions. In modern English, we often use oath and vow interchangeably, but they are not (usually) the same thing. Divine beings figure in both kinds of promises, but in different ways. In a vow, the god or gods in question are the recipients of the promise: you vow something to God (or a god). By contrast, an oath is made typically to a person and the role of the divine being in the whole affair is a bit more complex.
(Etymology digression: the word “oath” comes to us by way of Old English āþ (pronounced “ath” with a long ‘a’) and has close cousins in Dutch “Eed” and German “Eid”. The word vow comes from Latin (via Middle English, via French), from the word votum. A votum is specifically a gift to a god in exchange for some favor – the gift can be in the present tense or something promised in the future. By contrast, the Latin word for oath is ius (it has a few meanings) and to swear an oath is the verb iuro (thus the legal phrase “ius iurandum” – literally “the oath to be sworn”). This Latin distinction is preserved into the English usage, where “vow” retains its Latin meaning, and the word “oath” usurps the place of Latin ius (along with other words for specific kinds of oaths in Latin, e.g. sacramentum)).
In a vow, the participant promises something – either in the present or the future – to a god, typically in exchange for something. This is why we talk of an oath of fealty or homage (promises made to a human), but a monk’s vows. When a monk promises obedience, chastity and poverty, he is offering these things to God in exchange for grace, rather than to any mortal person. Those vows are not to the community (though it may be present), but to God (e.g. Benedict in his Rule notes that the vow “is done in the presence of God and his saints to impress on the novice that if he ever acts otherwise, he will surely be condemned by the one he mocks“. (RB 58.18)). Note that a physical thing given in a vow is called a votive (from that Latin root).
(More digressions: Why do we say “marriage vows” in English? Isn’t this a promise to another human being? I suspect this usage – functionally a “frozen” phrase – derives from the assumption that the vows are, in fact, not a promise to your better half, but to God to maintain. After all, the Latin Church held – and the Catholic Church still holds – that a marriage cannot be dissolved by the consent of both parties (unlike oaths, from which a person may be released with the consent of the recipient). The act of divine ratification makes God a party to the marriage, and thus the promise is to him. Thus a vow, and not an oath.)
So again, a vow is a promise to a divinity or other higher power (you can make vows to heroes and saints, for instance), whereas an oath is a promise to another human, which is somehow enforced, witnessed or guaranteed by that higher power.
An example of this important distinction being handled in a very awkward manner is the “oath” of the Night’s Watch in Game of Thrones (delivered in S1E7, but taken, short a few words, verbatim from the books). The recruits call out to … someone … (they never name who, which as we’ll see, is a problem) to “hear my words and bear witness to my vow”. Except it’s not clear to me that this is a vow, so much as an oath. The supernatural being you are vowing something to does not bear witness because they are the primary participant – they don’t witness the gift, they receive it.
I strongly suspect that Martin is riffing off of here are the religious military orders of the Middle Ages (who did frequently take vows), but if this is a vow, it raises serious questions. It is absolutely possible to vow a certain future behavior – to essentially make yourself the gift – but who are they vowing to? The tree? It may well be “the Old Gods” who are supposed to be both nameless and numerous (this is, forgive me, not how ancient paganism worked – am I going to have to write that post too?) and who witness things (such as the Pact, itself definitely an oath, through the trees), but if so, surely you would want to specify that. Societies that do votives – especially when there are many gods – are often quite concerned that gifts might go awry. You want to be very specific as to who, exactly, you are vowing something to.
This is all the more important given that (as in the books) the Night’s Watch oath may be sworn in a sept as well as to a Weirwood tree. It wouldn’t do to vow yourself to the wrong gods! More importantly, the interchangeability of the gods in question points very strongly to this being an oath. Gods tend to be very particular about the votives they will receive; one can imagine saying “swear by whatever gods you have here” but not “vow yourself to whatever gods you have here”. Who is to say the local gods take such gifts?
Moreover, while they pledge their lives, they aren’t receiving anything in return. Here I think the problem may be that we are so used to the theologically obvious request of Christian vows (salvation and the life after death) that it doesn’t occur to us that you would need to specify what you get for a vow. But the Old Gods don’t seem to be in a position to offer salvation. Votives to gods in polytheistic systems almost always follow the do ut des system (lit. “I give, that you might give”). Things are not offered just for the heck of it – something is sought in return. And if you want that thing, you need to say it. Jupiter is not going to try to figure it out on his own. If you are asking the Old Gods to protect you, or the wall, or mankind, you need to ask.
(Pliny the Elder puts it neatly declaring, “of course, either to sacrifice without prayer or to consult the gods without sacrifice is useless” (Nat. Hist. 28.3). Prayer here (Latin: precatio) really means “asking for something” – as in the sense of “I pray thee (or ‘prithee’) tell me what happened?” And to be clear, the connection of Christian religious practice to the do ut des formula of pre-Christian paganism is a complex theological question better addressed to a theologian or church historian.)
The scene makes more sense as an oath – the oath-takers are swearing to the rest of the Night’s Watch to keep these promises, with the Weirwood Trees (and through them, the Old Gods – although again, they should specify) acting as witnesses. As a vow, too much is up in the air and the idea that a military order would permit its members to vow themselves to this or that god at random is nonsense. For a vow, the recipient – the god – is paramount.
Bret Devereaux, “Collections: Oaths! How do they Work?”, A Collection of Unmitigated Pedantry, 2019-06-28.
February 9, 2023
QotD: Collecting taxes, Medieval-style
I want to begin with an observation, obvious but frequently ignored: states are complex things. The apparatus by which a state gathers revenue, raises armies (with that revenue), administers justice and tries to organize society – that apparatus requires people. Not just any people: they need to be people of the educated, literate sort to be able to record taxes, read the laws and transmit (written) royal orders and decrees.
(Note: for a more detailed primer on what this kind of apparatus can look like, check out Wayne Lee’s (@MilHist_Lee) talk “Reaping the Rewards: How the Governor, the Priest, the Taxman, and the Garrison Secure Victory in World History” here. He’s got some specific points he’s driving at, but the first half of the talk is a broad overview of the problems you face as a suddenly successful king. Also, the whole thing is fascinating.)
In a pre-modern society, this task – assembling and organizing the literate bureaucrats you need to run a state – is very difficult. Literacy is often very low, so the number of individuals with the necessary skills is minuscule. Training new literate bureaucrats is expensive, as is paying the ones you have, creating a catch-22 where the king has no money because he has no tax collectors and he has no tax collectors because he has no money. Looking at how states form is thus often a question of looking at how this low-administration equilibrium is broken. The administrators you need might be found in civic elites who are persuaded to do the job in exchange for power, or in a co-opted religious hierarchy of educated priests, for instance.
Vassalage represents another response to the problem, which is the attempt to – as much as possible – do without. Let’s specify terms: I am using “vassalage” here because it is specific in a way that the more commonly used “feudalism” is not. I am not (yet) referring to how peasants (in Westeros the “smallfolk”) interact with lords (which is better termed “manorialism” than as part of feudalism anyway), but rather how military aristocrats (knights, lords, etc) interact with each other.
So let us say you are a king who has suddenly come into a lot of land, probably by bloody conquest. You need to extract revenue from that land in order to pay for the armies you used to conquer it, but you don’t have a pile of literate bureaucrats to collect those taxes and no easy way to get some. By handing out that land to your military retainers as fiefs (they become your vassals), you can solve a bunch of problems at once. First, you pay off your military retainers for their service with something you have that is valuable (land). Second, by extracting certain promises (called “homage”) from them, you ensure that they will continue to fight for you. And third, you are partitioning your land into smaller and smaller chunks until you get them in chunks small enough to be administered directly, with only a very, very minimal bureaucratic apparatus. Your new vassals, of course, may do the same with their new land, further fragmenting the political system.
This is the system in Westeros, albeit after generations of inheritance (such that families, rather than individuals, serve as the chief political unit). The Westerosi term for a vassal is a “bannerman”. Greater military aristocrats with larger holding are lords, while lesser ones are landed knights. Landed knights often hold significant lands and a keep (fortified manner house), which would make them something more akin to European castellans or barons than, say, a 14th century English Knight Banneret (who is unlikely to have been given permission to fortify his home, known as a license to crenellate). What is missing from this system are the vast majority of knights, who would not have had any kind of fortified dwelling or castle, but would have instead been maintained as part of the household of some more senior member of the aristocracy. A handful of landless knights show up in Game of Thrones, but they should be by far the majority and make up most of the armies.
There’s one final missing ingredient here, which is castles, something Westeros has in abundance. Castles – in the absence of castle-breaking cannon – shift power downward in this system, because they allow vassals to effectively resist their lieges. That may not manifest in open rebellion so much as a refusal to go on campaign or supply troops. This is important, because it makes lieges as dependent on their vassals as vassals are on their lieges.
Bret Devereaux, “New Acquisitions: How It Wasn’t: Game of Thrones and the Middle Ages, Part III”, A Collection of Unmitigated Pedantry, 2019-06-12.
February 5, 2023
QotD: Annual cycles of plenty and scarcity in pre-modern agricultural societies
This brings us to the most fundamental fact of rural life in the pre-modern world: the grain is harvested once a year, but the family eats every day. Of course that means the grain must be stored and only slowly consumed over the entire year (with some left over to be used as seed-grain in the following planting). That creates the first cycle in agricultural life: after the harvest, food is generally plentiful and prices for it are low […] As the year goes on, food becomes scarcer and the prices for it rise as each family “eats down” their stockpile.
That has more than just economic impacts because the family unit becomes more vulnerable as that food stockpile dwindles. Malnutrition brings on a host of other threats: elevated risk of death from injury or disease most notably. Repeated malnutrition also has devastating long-term effects on young children […] Consequently, we see seasonal mortality patterns in agricultural communities which tend to follow harvest cycles; when the harvest is poor, the family starts to run low on food before the next harvest, which leads to rationing the remaining food, which leads to malnutrition. That malnutrition is not evenly distributed though: the working age adults need to be strong enough to bring in the next harvest when it comes (or to be doing additional non-farming labor to supplement the family), so the short rations are going to go to the children and the elderly. Which in turn means that “lean” years are marked by increased mortality especially among the children and the elderly, the former of which is how the rural population “regulates” to its food production in the absence of modern birth control (but, as an aside: this doesn’t lead to pure Malthusian dynamics – a lot more influences the food production ceiling than just available land. You can have low-equilibrium or high-equilibrium systems, especially when looking at the availability of certain sorts of farming capital or access to trade at distance. I cannot stress this enough: Malthus was wrong; yes, interestingly, usefully wrong – but still wrong. The big plagues sometimes pointed to as evidence of Malthusian crises have as much if not more to do with rising trade interconnectedness than declining nutritional standards). This creates yearly cycles of plenty and vulnerability […]
Next to that little cycle, we also have a “big” cycle of generations. The ratio of labor-to-food-requirements varies as generations are born, age and die; it isn’t constant. The family is at its peak labor effectiveness at the point when the youngest generation is physically mature but hasn’t yet begun having children (the exact age-range there is going to vary by nuptial patterns, see below) and at its most vulnerable when the youngest generation is immature. By way of example, let’s imagine a family (I’m going to use Roman names because they make gender very clear, but this is a completely made-up family): we have Gaius (M, 45), his wife, Cornelia (39, F), his mother Tullia (64, F) and their children Gaius (21, M), Secundus (19, M), Julia1 (16, F) and Julia2 (14, F). That family has three male laborers, three female laborers (Tullia being in her twilight years, we don’t count), all effectively adults in that sense, against 7 mouths to feed. But let’s fast-forward fifteen years. Gaius is now 60 and slowing down, Cornelia is 54; Tullia, we may assume has passed. But Gaius now 36 is married to Clodia (20, F; welcome to Roman marriage patterns), with two children Gaius (3, M) and Julia3 (1, F); Julia1 and Julia2 are married and now in different households and Secundus, recognizing that the family’s financial situation is never going to allow him to marry and set up a household has left for the Big City. So we now have the labor of two women and a man-and-a-half (since Gaius the Elder is quite old) against six mouths and the situation is likely to get worse in the following years as Gaius-the-Younger and Clodia have more children and Gaius-the-Elder gets older. The point of all of this is to note that just as risk and vulnerability peak and subside on a yearly basis in cycles, they also do this on a generational basis in cycles.
(An aside: the exact structure of these generational patterns follow on marriage patterns which differ somewhat culture to culture. In just about every subsistence farming culture I’ve seen, women marry young (by modern standards) often in their mid-to-late teens, or early twenties; that doesn’t vary much (marriage ages tend to be younger, paradoxically, for wealthier people in these societies, by the by). But marriage-ages for men vary quite a lot, from societies where men’s age at first marriage is in the early 20s to societies like Roman and Greece where it is in the late 20s to mid-thirties. At Rome during the Republic, the expectation seems to have been that a Roman man would complete the bulk of their military service – in their twenties and possibly early thirties – before starting a household; something with implications for Roman household vulnerability. Check out Rosenstein, op. cit. on this).
On top of these cycles of vulnerability, you have truly unpredictable risk. Crops can fail in so many ways. In areas without irrigated rivers, a dry spell at the wrong time is enough; for places with rivers, flooding becomes a concern because the fields have to be set close to the water-table. Pests and crop blights are also a potential risk factor, as of course is conflict.
So instead of imagining a farm with a “standard” yield, imagine a farm with a standard grain consumption. Most years, the farm’s production (bolstered by other activities like sharecropping that we’ll talk about later) exceed that consumption, with the remainder being surplus available for sale, trade or as gifts to neighbors and friends. Some years, the farm’s production falls short, creating that shortfall. Meanwhile families tend to grow to the size the farm can support, rather than to the labor needs the farm has, which tends to mean too many hands (and mouths) and not enough land. Which in turn causes the family to ride a line of fairly high risk in many cases.
All of this is to stress that these farmers are looking to manage risk through cycles of vulnerability […]
I led in with all of that risk and vulnerability because without it just about nothing these farmers do makes a lot of sense; once you understand that they are managing risk, everything falls into place.
Most modern folks think in terms of profit maximization; we take for granted that we will still be alive tomorrow and instead ask how we can maximize how much money we have then (this is, admittedly, a lot less true for the least fortunate among us). We thus tend to favor efficient systems, even if they are vulnerable. From this perspective, ancient farmers – as we’ll see – look very silly, but this is a trap, albeit one that even some very august ancient scholars have fallen into. These are not irrational, unthinking people; they are poor, not stupid – those are not the same things.
But because these households wobble on the edge of disaster continually, that changes the calculus. These small subsistence farmers generally seek to minimize risk, rather than maximize profits. After all, improving yields by 5% doesn’t mean much if everyone starves to death in the third year because of a tail-risk that wasn’t mitigated. Moreover, for most of these farmers, working harder and farming more generally doesn’t offer a route out of the small farming class – these societies typically lack that kind of mobility (and also generally lack the massive wealth-creation potential of industrial power which powers that kind of mobility). Consequently, there is little gain to taking risks and much to lose. So as we’ll see, these farmers generally sacrifice efficiency for greater margins of safety, every time.
Bret Devereaux, “Collections: Bread, How Did They Make It? Part I: Farmers!”, A collection of Unmitigated Pedantry, 2020-07-24.
January 31, 2023
QotD: Religious rituals
I want to start with a key observation, without which much of the rest of this will not make much sense: rituals are supposed to be effective. Let me explain what that means.
We tend to have an almost anthropological view of rituals, even ones we still practice: we see them in terms of their social function or psychological impact. Frank Herbert’s Children of Dune (the Sci-fi miniseries; I can’t find the quote in the text, but then it’s a lot of text) put it wonderfully, “Ritual is the whip by which men are enlightened.” That is, ritual’s primary effect is the change that takes place in our minds, rather than in the spiritual world. This is the same line of thinking whereby a Church service is justified because it “creates a sense of community” or “brings believers together”. We view rituals often like plays or concerts, experiences without any broader consequences beyond the experience of participation or viewing itself.
This is not how polytheism (ancient or modern) works (indeed, it is not how most modern Christianity works: the sacraments are supposed to be spiritually effective; that is, if properly carried out, they do things beyond just making us feel better. You can see this articulated clearly in some traditional prayers, like the Prayer of Humble Access or Luther’s Flood Prayer).
Instead, religious rituals are meant to have (and will have, so the believer believes, if everything is done properly) real effects in both the spiritual world and the physical world. That is, your ritual will first effect a change in the god (making them better disposed to you) and second that will effect a change in the physical world we inhabit (as the god’s power is deployed in your favor).
But to reiterate, because this is key: the purpose of ritual (in ancient, polytheistic religious systems) is to produce a concrete, earthly result. It is not to improve our mood or morals, but to make crops grow, rain fall, armies win battles, business deals turn out well, ships sail, winds blow. While some rituals in these religions do concern themselves with the afterlife or other seemingly purely spiritual concerns (the lines between earthly and spiritual in those cases are – as we’ll see, somewhat blurrier in these religions than we often think them to be now), the great majority of rituals are squarely focused on what is happening around us, and are performed because they do something.
This is the practical side of practical knowledge; the ritual in polytheistic religion does not (usually) alter you in some way – it alters the world (spiritual and physical) around you in some way. Consequently, ritual is employed as a tool – this problem is solved by a wrench, that problem by a hammer, and this other problem by a ritual. Some rituals are preventative maintenance (say, we regularly observe this ritual so this god is always well disposed to us, so that they do X, Y, and Z on the regular), others are a response to crisis, but they are all tools to shape the world (again, physical and spiritual) around us. If a ritual carries a moral duty, it is only because (we’ll get to this a bit more later) other people in your community are counting on you to do it; it is a moral duty the same way that, as an accountant, not embezzling money is a moral duty. Failure lets other people (not yourself and not even really the gods) down.
Bret Devereaux, “Collections: Practical Polytheism, Part II: Practice”, A Collection of Unmitigated Pedantry, 2019-11-01.
January 27, 2023
QotD: What is Strategy?
We should start by returning to our three levels of military analysis: tactics, operations and strategy. We’ve dealt with tactics (how you fight) and operations (where you fight, and how you get there). Strategy is an often misunderstood term: most “strategy” games (especially real-time strategy) are actually focused almost entirely on tactics and operations; as a rule, if “don’t have a war” isn’t an option, you are not actually doing strategy. Likewise, a lot of basic planning in business is termed “strategy” when it really is tactics; not a question of goals, but of means to achieve those goals. Because strategy is the level of analysis that concerns why we fight – and thus also why we might not fight. Let’s unpack that.
(Attentive readers who know their Clausewitz (drink!) will recognize that I am being both broader and narrower than he in how I use the term strategy. Clausewitz terms strategy as “the employment of battles to gain the end of war” which is more nearly what we today mean as operations. In contrast, strategy as it is used today in a technical sense corresponds more nearly to what Clausewitz terms policy, the third element of his “marvelous trinity”. A full exegesis of Clausewitz’ trinity is beyond the scope of this essay, but I wanted to note the differing usages, because I’m going to quote Clausewitz below. And as always, every time Clausewitz gets quoted you must take a drink; it’s the eternal military history drinking game).
At the strategic level of analysis, the first question is “what are your policy objectives?” (although I should note that grand strategy is sometimes conceived as an analytical level above strategy, in which case policy objectives may go there). There’s a compelling argument common in realist international relations theory that the basic policy of nearly all states is to survive, with the goal of survival then suggesting a policy of maximizing security, which in turn suggests a policy of maximizing the military power of the state (which ironically leads to lower the security of other states who then must further increase their military power, a reaction known as the “security dilemma” or, more colorfully, the “Red Queen effect”). I think it is also possible for states to have policy goals beyond this: ideological projects, good and bad. But survival comes first.
From there, strategy concerns itself with the best way to achieve those policy objectives. Is peace and alliances the best way to achieve security (for a small state, the answer is often “yes”)? Would security be enhanced by, say, gaining a key chunk of territory that could be fortified to forestall invasion? Those, of course, are ends, but strategy also concerns itself with means: how do you acquire that defensible land? Buy it? Take it by force? And then – and only then, finally – do you come to the question of “what sort of war – and what sort of conduct in war – will achieve that objective?”
You may note that this is not the same kind of thinking that animates tactics or operations. Military theorists have noticed that for quite some time, often suggesting a sharp separation between the fellows who do operations and tactics (generals) and those who do strategy (typically kings or politicians). As Clausewitz says (drink!), “The political object is the goal, war is the means of reaching it, and means can never be considered in isolation from their purpose … war should never be thought of as something autonomous, but always as an instrument of policy [emphasis mine].” In short, Clausewitz stresses – and leaders have long ignored to their peril – that of all of the factors in war, policy ought to guide action (although no part of the trinity may be neglected).
This creates subordination between the three levels of analysis (to get technical, this is because operations and tactics are part of a side of the Clausewitzian trinity which ought to be subordinate to policy). Operations is subordinate to strategy; an operation which achieves something that isn’t a strategic goal accomplishes nothing. And tactics is likewise subordinate to operations. Thus the thinking pattern should always proceed from the highest questions of strategy down to the prioritization of ends (still strategy), to the means to accomplish those ends (still strategy); only then to the execution of those means (operations) and then to the on-the-ground details of that execution (tactics). Of course what this tripartite division is mean in part to signal is that all three of these stages are tremendously complex; just because tactics is the subordinate element does not mean it is simple!
Bret Devereaux, “Collections: The Battle of Helm’s Deep, Part VIII: The Mind of Saruman”, A Collection of Unmitigated Pedantry, 2020-06-19.
January 23, 2023
QotD: Rice farming
There are a lot of varieties of rice out there, but the key divide we want to make early is between dry-rice and wet-rice. When we’re talking about “rice cultures” or “rice agriculture”, generally, we mean wet-rice farming, where the rice is partially submerged during its growing. Wild rice, as far as we can tell, began as a swamp-grass and thus likes to have quite a lot of water around, although precisely controlling the water availability can lead the rice to be a lot more productive than it would be in its natural habitat. While there are varieties of rice which can be (and are) farmed “dry” (that is, in unflooded fields much like wheat and barley are farmed), the vast majority of rice farming is “wet”. As with grains, this is not merely a matter of different methods of farming, but of different varieties of rice that have been adapted to that farming; varieties of dry-rice and wet-rice have been selectively bred over millennia to perform best in those environments.
Wet-rice is farmed in paddies, small fields (often very small – some Chinese agronomists write that the ideal size for an individual rice field is around 0.1 hectare, which is just 0.24 acres) surrounded by low “bunds” (small earthwork walls or dykes) to keep in the water, typically around two feet high. Because controlling the water level is crucial, rice paddies must be very precisely flat, leading to even relatively gentle slopes often being terraced to create a series of flat fields. Each of these rice paddies (and there will be many because they are so small) are then connected by irrigation canals which channel and control the water in what is often a quite complex system.
The exact timing of rice production is more complex than wheat because a single paddy often sees two crops in a year and the exact planting times vary between areas; one common cycle on the Yangtze is for a February planting (with a June harvest) followed by a June planting (with a November harvest). In other areas, paddies planted with rice during the first planting might be drained and sown with a different plant entirely (sometimes including wheat) in the intervening time.
The cycle runs thusly: after the heavy rains of the monsoons (if available), the field is tilled (or plowed, but as we’ll see, manual tillage is often more common). The seed is then sown (or transplanted) and the field is, using the irrigation system, lightly flooded, so that the young seedlings grow in standing water. Sometimes the seed is initially planted in a dedicated seed-bed and then transferred to the field, rather than being sown there directly; doing so has a positive impact on yields, but is substantially more labor intensive. The water level is raised as the plant grows; agian this is labor intensive, but increases yields. Just before the harvest the fields are drained out and allowed to dry out, before the crop is harvested and then goes into processing.
Rice is threshed much like grain (more often manually threshed and generally not threshed with flails) to release the seeds, the individual rice grains, from the plant. That is going to free the endosperm of the speed, along with a hull around it and a layer of bran between the two. Hulling was traditionally done by hand-pounding, which frees the seed from the hull, leaving just the endosperm and some of the bran; this is how you get brown rice, which is essentially “whole-grain” rice. While it is generally less tasty, the bran actually has quite a lot of nutrients not present in the calorie-rich endosperm. Whereas white rice is produced by then milling or polishing away the bran to produce a pure, white kernal of the endosperm; it is very tasty, but lacks many of the vitamins that brown rice has.
Consequently, while a diet of mostly brown rice can be healthy, a diet overwhelmingly of white rice leads to Thiamine deficiency, known colloquially as beriberi. My impression from the literature is that this wasn’t as much an issue prior to the introduction of mechanical milling processes for rice. Mechanical milling made producing white rice in quantity cheap and so it came to dominate the diet to the exclusion of brown rice, producing negative health effects for the poor who could not afford to supplement their rice-and-millet diet with other foods, or for soldiers whose ration was in rice. But prior to that mechanical milling, brown rice was all that was available for the poor, which in turn meant less Thiamine deficiency among the lower classes of society.
Bret Devereaux, “Collections: Bread, How Did They Make It? Addendum: Rice!”, A Collection of Unmitigated Pedantry, 2020-09-04.
January 19, 2023
QotD: Did Sparta achieve its strategic objectives?
The final objective we can be quite certain about is that Sparta aimed to protect the internal social and political order of Sparta, which essentially amounts to a strategic objective to be able to continue mistreating the helots and the perioikoi. In practice – given Sparta’s desperate shortness of manpower (and economic resources!) and continued unwillingness to revisit the nature of its oppressive class system, we may say with some confidence that Sparta effectively sacrificed all other objectives on the altar of this one.
And yet Sparta’s failure here was perhaps the most complete of all. The collapse of the Spartiate class did not abate after Leuktra; by the 230s, there were hardly any Spartiates left. Meanwhile, the transition of Messenia from a group of subject communities supporting Sparta economically to an active and hostile power on Sparta’s border essentially represented the end of the Spartan social order as established in the seventh century with the reduction of Messenia to helotry in the first place.
So, does Sparta achieve its strategic objectives? By and large, I think the answer here has to be “no”. Sparta – the supposed enemy of tyrants – by mismanaging its own leadership invited one foreign oppressor (Macedon) into Greece after another (Persia). As a state that seems – to me at least – to have considered itself the natural and rightful leader of all of the Greek states, Sparta, routinely and comprehensively proved itself unworthy of the position.
The one thing we may say for Spartan foreign and military policy is that it seems to have made the world safe for helotry – it preserved the brutal system of oppression which was foundational to the Spartan state. But consider just how weak an achievement that is – we might, after all, make the same claim about North Korea: it has managed only to successfully preserve its own internal systems of oppression.
Bret Devereaux, “Collections: This. Isn’t. Sparta. Part VII: Spartan Ends”, A Collection of Unmitigated Pedantry, 2019-09-27.
January 15, 2023
QotD: The uncertain “certainties” of war in space
The comments for that post were very active with suggestions for technological or strategic situations which would or would not make orbit-to-land operations (read: planetary invasions) unnecessary or obsolete, which were all quite interesting.
What I found most striking though was a relative confidence in how space battles would be waged in general, which I’ve seen both a little bit here in the comments and frequently more broadly in the hard-sci-fi community. The assumptions run very roughly that, without some form of magic-tech (like shields), space battles would be fought at extreme range, with devastating hyper-accurate weapons against which there could be no real defense, leading to relatively “thin-skinned” spacecraft. Evasion is typically dismissed as a possibility and with it smaller craft (like fighters) with potentially more favorable thrust-to-mass ratios. It’s actually handy for encapsulating this view of space combat that The Expanse essentially reproduces this model.
And, to be clear, I am not suggesting that this vision of future combat is wrong in any particular way. It may be right! But I find the relative confidence with which this model is often offered as more than a little bit misleading. The problem isn’t the model; it’s the false certainty with which it gets presented.
[…]
Coming back around to spaceships: if multiple national navies stocked with dozens of experts with decades of experience and training aren’t fully confident they know what a naval war in 2035 will look like, I find myself with sincere doubts that science fiction writers who are at best amateur engineers and military theorists have a good sense of what warfare in 2350 (much less the Grim Darkness of the Future Where There is Only War) will look like. This isn’t to trash on any given science fiction property mind you. At best, what someone right now can do is essentially game out, flow-chart style, probable fighting systems based on plausible technological systems, understanding that even small changes can radically change the picture. For just one example, consider the question “at what range can one space warship resolve an accurate target solution against another with the stealth systems and electronics warfare available?” Different answers to that question, predicated on different sensor, weapons and electronics warfare capabilities produce wildly different combat systems.
(As an aside: I am sure someone is already dashing down in the comments preparing to write “there is no stealth in space“. To a degree, that is true – the kind of Star Trek-esque cloaking device of complete invisibility is impossible in space, because a ship’s waste heat has to go somewhere and that is going to make the craft detectable. But detectable and detected are not the same: the sky is big, there are lots of sources of electromagnetic radiation in it. There are as yet undiscovered large asteroids in the solar-system; the idea of a ship designed to radiate waste heat away from enemies and pretend to be one more undocumented large rock (or escape notice entirely, since an enemy may not be able to track everything in the sky) long enough to escape detection or close to ideal range doesn’t seem outlandish to me. Likewise, once detected, the idea of a ship using something like chaff to introduce just enough noise into an opponent’s targeting system so that they can’t determine velocity and heading with enough precision to put a hit on target at 100,000 miles away doesn’t seem insane either. Or none of that might work, leading to extreme-range exchanges. Again, the question is all about the interaction of detection, targeting and counter-measure technology, which we can’t really predict at all.)
And that uncertainty attaches to almost every sort of technological interaction. Sensors and targeting against electronics warfare and stealth, but also missiles and projectiles against point-defense and CIWS, or any kind of weapon against armor (there is often an assumption, for instance, that armor is entirely useless against nuclear strikes, which is not the case) and on and on. Layered on top of that is what future technologies will even prove practical – if heat dissipation problems for lasers or capacitor limitations on railguns be solved problems, for instance. If we can’t quite be sure how known technologies will interact in an environment (our own planet’s seas) that we are intimately familiar with, we should be careful expressing confidence about how future technology will work in space. Consequently, while a science fiction setting can certainly generate a plausible model of future space combat, I think the certainty with which those models and their assumptions are sometimes presented is misplaced.
Bret Devereaux, “Fireside Friday: August 14th, 2020”, A Collection of Unmitigated Pedantry, 2020-08-14.
January 11, 2023
QotD: “Little” gods in the ancient world
When we teach ancient religion in school – be it high school or college – we are typically focused on the big gods: the sort of gods who show up in high literature, who create the world, guide heroes, mint kings. These are the sorts of gods – Jupiter, Apollo, Anu, Ishtar – that receive state cult, which is to say that there are rituals to these gods which are funded by the state, performed by magistrates or kings or high priests (or other Very Important People); the common folk are, at best, spectators to the rituals performed on their behalf by their social superiors.
That is not to say that these gods did not receive cult from the common folk. If you are a regular sailor on a merchant ship, some private devotion to Poseidon is in order; if you are a husband wishing for more children, some observance of Ishtar may help; if you are a farmer praying for rain, Jupiter may be your guy. But these are big gods, whose vast powers are unlimited in geographic scope and their right observance is, at least in part, a job for important people who act on behalf of the entire community. Such gods are necessarily somewhat distant and unapproachable; it may be difficult to get their attention for your particular issue.
Fortunately, the world is full up of smaller and more personal gods. The most pervasive of these are household gods – god associated with either the physical home, or the hearth (the fireplace), or the household/family as a social unit. The Romans had several of these, chiefly the Lares and Penates, two sets of gods who presided over the home. The Lares seem to have originally been hearth guardians associated with the family, while the Penates may have begun as the guardians of the house’s storeroom – an important place in an agricultural society! Such figures are common in other polytheisms too – the fantasy tropes of brownies, hobs, kobolds and the like began as similar household spirits, propitiated by the family for the services they provide.
(As an aside, the Lares and Penates provide an excellent example on how practice was valued more than belief or orthodoxy in ancient religion: when I say that they “seem” or “may have originally been”, that is because it was not entirely clear to the Romans, exactly what the distinction between the Lares and Penates were; ancient authors try to reconstruct exactly what the Penates are about from etymologies (e.g. Cic. De Natura Deorum 2.68) and don’t always agree! But of course, the exact origins of the Lares or the Penates didn’t matter so much as the power they held, how they ought to be appeased, and what they might do to you!)
Household gods also illuminate the distinctly communal nature of even smaller religious observances. The rituals in a Roman household for the Lares and Penates were carried out by the heads of the household (mostly the paterfamilias although the matron of the household had a significant role – at some point, we can talk about the hierarchy of Roman households, but now I just want to note that these two positions in the Roman family are not co-equal) on behalf of the entire family unit, which we should remember might well be multi-generational, including adult children with their own children – in just the same way that important magistrates (or in monarchies, the king or his delegates) might carry out rituals on behalf of the community as a whole.
There were other forms of little gods – gods of places, for instance. The distinction between a place and the god of that same place is often not strong – when Achilles enrages the god of the river Scamander (Iliad 20), the river itself rises up against him; both the river and the god share a name. The Romans cover many small gods under the idea of the genius (pronounced gen-e-us, with the “g” hard like the g in gadget); a genius might protect an individual or family […] or even a place (called a genius locus). Water spirits, governing bodies of water great and humble, are particularly common – the fifty Nereids of Greek practice, or the Germanic Nixe or Neck.
Other gods might not be particular to a place, but to a very specific activity, or even moment. Thus (these are all Roman examples) Arculus, the god of strongboxes, or Vagitanus who gives the newborn its first cry or Forculus, god of doors (distinct from Janus and Limentinus who oversaw thresholds and Cardea, who oversaw hinges). All of these are what I tend to call small gods: gods with small powers over small domains, because – just as there are hierarchies of humans, there are hierarchies of gods.
Fortunately for the practitioner, bargaining for the aid of these smaller gods was often quite a lot cheaper than the big ones. A Jupiter or Neptune might demand sacrifices in things like bulls or the dedication of grand temples – prohibitively expensive animals for any common Roman or Greek – but the Lares and Penates might be befriended with only a regular gift of grain or a libation of wine. A small treat, like a bowl of milk, is enough to propitiate a brownie. Many rituals to gods of small places amount to little more than acknowledging them and their authority, and paying the proper respect.
Bret Devereaux, “Collections: Practical Polytheism, Part IV: Little Gods and Big People”, A Collection of Unmitigated Pedantry, 2019-11-15.
January 7, 2023
QotD: The “camp followers” of a pre-modern army
It is worth keeping in mind that an army of 10,000 or 20,000 men was, by ancient or medieval standards, a mid-sized town or city moving across the landscape. Just as towns and cities created demand for goods that shaped life around them, so did armies (although they’d have to stay put to create new patterns of agriculture, though armies that did stay put did create new patterns of agriculture, e.g. the Roman limes). Thousands of soldiers demand all sorts of services and often have the money to pay for them and that’s in addition to what the army as an army needs. That in turn is going to mean that the army is followed by a host of non-combatants, be they attached to the soldiers, looking to turn a profit, or compelled to be there.
We can start with sutlers, merchants buying or selling from the soldiers themselves (the Romans called these fellows lixae, but also called other non-soldiers in the camp lixae as well, see Roth (2012), 93-4; they also call them mercatores or negotiatores, merchants). Sutlers could be dealing in a wide array of goods. Even for armies where ration distribution was regular (e.g. the Roman army), sutlers might offer for sale tastier and fancier rations: meat, better alcohol and so on. They might also sell clothing and other goods to soldiers, even military equipment: finding “custom” weapons and armor in the archaeology of military forts and camps is not uncommon. For less regularly rationed armies, sutlers might act as a supplement to irregular systems of food and pay, providing credit to soldiers who purchased rations to make up for logistics shortfalls, to collect when those soldiers were paid. By way of example, the regulations of the Army of Flanders issued in 1596 allowed for three sutlers per 200-man company of troops (Parker, op. cit.), but the actual number was often much higher and of course those sutlers might also have their own assistants, porters, wagons and so on which moved with the army’s camp. Women who performed this role in the modern period are often referred to by the French vivandière.
For some armies there would have been an additional class of sutlers: slave dealers. Enslaved captives were a major component of loot in ancient warfare and Mediterranean military operations into and through the Middle Ages. Armies would abduct locals caught in hostile lands they moved through or enemies captured in battles or sieges; naturally generals did not want to have to manage these poor folks in the long term and so it was convenient if slave-dealer “wholesalers” were present with the army to quickly buy the large numbers of enslaved persons the army might generate (and then handle their transport – which is to say traffic them – to market). In Roman armies this was a regularized process, overseen by the quaestor (an elected treasury official who handled the army’s finances) assigned to each army, who conducted regular auctions in the camp. That of course means that these slave dealers are not only following the army, but are doing so with the necessary apparatus to transport hundreds or even thousands of captives (guards, wagons, porters, etc.).
And then there is the general category of “camp follower”, which covers a wide range of individuals (mostly women) who might move with the camp. The same 1596 regulations that provided for just three sutlers per 200-man Spanish company also provided that there could be three femmes publiques (prostitutes), another “maximum” which must often have been exceeded. But prostitutes were not the only women who might be with an army as it moved; indeed the very same regulations specify that, for propriety’s sake, the femmes publiques would have to work under the “disguise of being washerwomen or something similar” which of course implies a population of actual washerwomen and such who also moved with the army. Depending on training and social norms, soldiers may or may not have been expected to mend their own clothes or cook their own food. Soldiers might also have wives or girlfriends with them (who might in turn have those soldier’s children with them); this was more common with professional long-service armies where the army was home, but must have happened with all armies to one degree or another. Roman soldiers in the imperial period were formally, legally forbidden from marrying, but the evidence for “soldier’s families” in the permanent forts and camps of the Roman Empire is overwhelming.
The tasks women attached to these armies have have performed varied by gender norms and the organization of the logistics system. Early modern gunpowder armies represent some of the broadest range of activities and some of the armies that most relied on women in the camp to do the essential work of maintaining the camp; John Lynn (op. cit., 118-163) refers to the soldiers and their women (a mix of wives, girlfriends and unattached women) collectively as “the campaign community” and it is an apt label when thinking about the army on the march. As Lynn documents, women in the camp washed and mended clothes, nursed the sick and cooked meals, all tasks that were considered at the time inappropriate for men. Those same women might also be engaged in small crafts or in small-scale trade (that is, they might also be sutlers). Finally, as Lynn notes, women who were managing food and clothing seem often to have become logistics managers for their soldiers, guarding moveable property during battles and participating in pillaging in order to scrounge enough food and loot for they and their men to survive. I want to stress that for armies that had large numbers of women in the camp, it was because they were essential to the continued function of the army.
And finally, you have the general category of “servants”. The range of individuals captured by this label is vast. Officers and high status figures often brought either their hired servants or enslaved workers with them. Captains in the aforementioned Army of Flanders seem generally to have had at least four or five servants (called mozos) with them, for instance; higher officers more. But it wasn’t just officers who did this. Indeed, the average company in the Army of Flanders, Parker notes, would have had 20-30 individual soldiers who also had mozos with them; one force of 5,300 Spanish veterans leaving Flanders brought 2,000 such mozos as they left (Parker, op. cit. 151).
Looking at the ancient world, many – possibly most – Greek hoplites in citizen armies seem to have very often brought enslaved servants with them to carry their arms and armor; such enslaved servants are a regular feature of their armies in the sources. The Romans called these enslaved servants in their armies calones; it was a common trope of good generalship to sharply restrict their number, often with limited success. At Arausio we are told there were half as many servants (calonum et lixarum) as soldiers (Liv. Per. 67, on this note Roth (2013), 105), though excessive numbers of calones et lixae was a standard marker of bad general and the Romans did lose badly at Arausio so we ought to take those figures with a grain of salt, as Livy (and his sources) may just be communicating that the generals there were bad. That said, the notion that a very badly led army might have as many non-combatants following it as soldiers is a common one in the ancient sources. And while Roman armies were considered notable in the ancient world for how few camp servants they relied on and thus how much labor and portage was instead done by the soldiers, getting Roman aristocrats to leave their vast enslaved household staff at home was notoriously difficult (e.g. Ps.Caes. BAfr. 54; Dio Cass. 50.11.6). Much like the early modern “campaign community”, our sources frequently treat these calones as part of the army they belonged to, even though they were not soldiers.
Bret Devereaux, “Collections: Logistics, How Did They Do It, Part I: The Problem”, A Collection of Unmitigated Pedantry, 2022-07-15.
January 3, 2023
QotD: Spartan dominance over the Peloponnese
Sparta initially seems to have attempted (Hdt. 1.66-8) to have extended its treatment of Messenia to other parts of the Peloponnese (namely Tegea) in the mid sixth-century – the failure of this policy led to a more measured effort to subjugate the Peloponnese more loosely into a Spartan-lead military league (the Peloponnesian League). This project was never fully completed: Argos – the next largest power in the Peloponnese proper, but a solidly second-tier power compared to Athens, Corinth, Sparta or Thebes – successfully resisted Spartan efforts to dominate it throughout the period. But on the whole, by the late 6th century, Sparta did exert a (perhaps somewhat loose – the trend in scholarship lately has been to stress the plastic and fairly loose organization of the Peloponnesian League) kind of dominance over the Peloponnese.
The core of this control lasted until 371, when Spartan defeat at the Battle of Leuktra shattered this control. Epaminondas, the Theban commander, used the opportunity to free the helots of Messenia and reform them into a polis to provide a local counter-weight to Sparta, while Arcadia and Elis split off from Sparta’s alliance to form their own defensive league against Sparta and, to top it off, a number of the perioikic communities – including the Spartans’ elite light infantry scouts, the Skiritae – along with various borderlands also formed the new polis of Megalopolis on the northern Spartan border – it promptly joined the Arcadian league (this polis would later give us the historian Polybius; his anti-Spartan stance comes out clearly in how he treats Cleomenes III). Sparta, surrounded now by hostile poleis who had once been allies, would spend the rest of Antiquity as a political non-entity, save for one brief effort to restore Spartan greatness in the 220s, crushed by the Macedonian Antigonids who were in no mood to entertain Spartan delusions of grandeur.
We might then say that Sparta is successful – though not entirely so (Argos!) – in establishing a hegemony over the Peloponnese, but only maintains it for c. 175 years. That’s not a bad run, but for the record of a larger state dominating its backyard, it is not tremendously impressive either.
Bret Devereaux, “Collections: This. Isn’t. Sparta. Part VII: Spartan Ends”, A Collection of Unmitigated Pedantry, 2019-09-27.
December 22, 2022
QotD: Sparta as the pre-eminent foe of tyranny
One of the ways that Sparta positioned itself was as the state which championed the freedom of the Greeks. Sparta had fought the Persian tyrant, had helped to oust tyrants in Athens and had later framed Athens itself as a “tyrant city”. Sparta itself had never had a tyrant (until Cleomenes III seized sole power in the 220s). On the flip side, Spartan hegemony was, apparently, little better than Athenian hegemony, given how Sparta’s own allies consistently reacted to it and Sparta would, in the end, do absolutely nothing to stop Philip II of Macedon from consolidating sole rule over Greece. When the call went out to once again resist a foreign invader in 338, Sparta was conspicuous in its absence.
It also matters exactly how tyranny is understood here. For the ancient Greeks, tyranny was a technical term, meaning a specific kind of one-man rule – a lot like how we use the word dictatorship to mean monarchies that are not kingdoms (though in Greece this word didn’t have quite so strong a negative connotation). Sparta was pretty reliable in opposing one-man rule, but that doesn’t mean it supported “free” governments. For instance, after the Peloponnesian War, Sparta foisted a brutal oligarchy – what the Athenians came to call “The Thirty Tyrants” – on Athens; their rule was so bad and harsh that it only lasted eight months (another feat of awful Spartan statecraft). Such a government was tyrannical, but not a tyranny in the technical sense.
But the Spartan reputation for fighting against tyrannies – both in the minds of the Greeks and in the popular consciousness – is predicted on fighting one very specific monarchy: the Achaemenids of Persia. […] This is the thing for which Sparta is given the most credit in popular culture, but Sparta’s record in this regard is awful. Sparta (along with Athens) leads the Greek coalition in the second Persian war and – as discussed – much of the Spartan reputation was built out of that. But Sparta had largely been a no-show during the first Persian war, and in the subsequent decades, Sparta’s commitment to opposing Persia was opportunistic at best.
During the late stages of the Peloponnesian War, Sparta essentially allied with Persia, taking funding and ships first from the Persian satrap Tissaphernes and later from Cyrus the Younger (a Persian prince and satrap). Sparta, after all, lacked the economic foundation to finance their own navy and the Spartans had – belatedly – realized that they needed a navy to defeat Athens. And of course the Persians – and any Spartan paying attention – knew that the Athenian navy was the one thing keeping Persia out of Greek affairs. So Sparta accepted Persian money to build up the fleets necessary to bring down the Athenian navy, with the consequence that the Ionian Greeks once again became subjects to the Persian Empire.
Subsequent Spartan diplomatic incompetence would lead to the Corinthian War (395-387), which turned into a nasty stalemate – due in part to the limitations of Spartan siege and naval capabilities. Unable to end the conflict on their own, the Spartans turned to Persia – again – to help them out, and the Persians brokered a pro-Spartan peace by threatening the Corinthians with Persian intervention in favor of Sparta. The subequent treaty – the “King’s Peace” (since it was imposed by the Persian Great King, Artaxerxes II) was highly favorable to Persia. All of Ionian, Cyprus, Aeolia and Carnia fell under Persian control and the treaty barred the Greeks from forming defensive leagues – meaning that it prevented the formation of any Greek coalition large enough to resist Persian influence. The treaty essentially made Sparta into Persia’s local enforcer in Greece, a role it would hold until its defeat in 371.
If Sparta held the objective of excluding Persian influence or tyranny from Greece, it failed completely and abjectly. Sparta opened not only the windows but also the doors to Persian influence in Greece – between 410 and 370, Sparta probably did more than any Greek state had ever or would ever do to push Greece into the Persian sphere of influence. Sparta would also refuse to participate in Alexander’s invasion of Persia – a point Alexander mocked them for by dedicating the spoils of his victories “from all of the Greeks, except the Spartans” (Arr. Anab. 1.16.7); for their part, the Spartans instead tried to use it as an opportunity to seize Crete and petitioned the Persians for aid in their war against Alexander, before being crushed by Alexander’s local commander, Antipater, in what Alexander termed “a clash of mice”.
Bret Devereaux, “Collections: This. Isn’t. Sparta. Part VII: Spartan Ends”, A Collection of Unmitigated Pedantry, 2019-09-27.
December 18, 2022
QotD: Citation systems and why they were developed
For this week’s musing I wanted to talk a bit about citation systems. In particular, you all have no doubt noticed that I generally cite modern works by the author’s name, their title and date of publication (e.g. G. Parker, The Army of Flanders and the Spanish Road (1972)), but ancient works get these strange almost code-like citations (Xen. Lac. 5.3; Hdt. 7.234.2; Thuc. 5.68; etc.). And you may ask, “What gives? Why two systems?” So let’s talk about that.
The first thing that needs to be noted here is that systems of citation are for the most part a modern invention. Pre-modern authors will, of course, allude to or reference other works (although ancient Greek and Roman writers have a tendency to flex on the reader by omitting the name of the author, often just alluding to a quote of “the poet” where “the poet” is usually, but not always, Homer), but they did not generally have systems of citation as we do.
Instead most modern citation systems in use for modern books go back at most to the 1800s, though these are often standardizations of systems which might go back a bit further still. Still, the Chicago Manual of Style – the standard style guide and citation system for historians working in the United States – was first published only in 1906. Consequently its citation system is built for the facts of how modern publishing works. In particular, we publish books in codices (that is, books with pages) with numbered pages which are typically kept constant in multiple printings (including being kept constant between soft-cover and hardback versions). Consequently if you can give the book, the edition (where necessary), the publisher and a page number, any reader seeing your citation can notionally go get that edition of the book and open to the very page you were looking at and see exactly what you saw.
Of course this breaks down a little with mass-market fiction books that are often printed in multiple editions with inconsistent pagination (thus the endless frustration with trying to cite anything in A Song of Ice and Fire; the fan-made chapter-based citation system for a work without numbered or uniquely named chapters is, I must say, painfully inadequate.) but in a scholarly rather than wiki-context, one can just pick a specific edition, specify it with the facts of publication and use those page numbers.
However the systems for citing ancient works or medieval manuscripts are actually older than consistent page numbers, though they do not reach back into antiquity or even really much into the Middle Ages. As originally published, ancient works couldn’t have static page numbers – had they existed yet, which they didn’t – for a multitude of reasons: for one, being copied by hand, the pagination was likely to always be inconsistent. But for ancient works the broader problem was that while they were written in books (libri) they were not written in books (codices). The book as a physical object – pages, bound together at a spine – is more technically called a codex. After all, that’s not the only way to organize a book. Think of a modern ebook for instance: it is a book, but it isn’t a codex! Well, prior to codex becoming truly common in third and fourth centuries AD, books were typically written on scrolls (the literal meaning of libri, which later came to mean any sort of book), which notably lack pages – it is one continuous scroll of text.
Of course those scrolls do not survive. Rather, ancient works were copied onto codices during Late Antiquity or the Middle Ages and those survive. When we are lucky, several different “families” of manuscripts for a given work survive (this is useful because it means we can compare those manuscripts to detect transcription errors; alas in many cases we have only one manuscript or one clearly related family of manuscripts which all share the same errors, though such errors are generally rare and small).
With the emergence of the printing press, it became possible to print lots of copies of these works, but that combined with the manuscript tradition created its own problems: which manuscript should be the authoritative text and how ought it be divided? On the first point, the response was the slow and painstaking work of creating critical editions that incorporate the different manuscript traditions: a main text on the page meant to represent the scholar’s best guess at the correct original text with notes (called an apparatus criticus) marking where other manuscripts differ. On the second point it became necessary to impose some kind of organizing structure on these works.
The good news is that most longer classical works already had a system of larger divisions: books (libri). A long work would be too long for a single scroll and so would need to be broken into several; its quite clear from an early point that authors were aware of this and took advantage of that system of divisions to divide their works into “books” that had thematic or chronological significance. Where such a standard division didn’t exist, ancient libraries, particularly in Alexandria, had imposed them and the influence of those libraries as the standard sources for originals from which to make subsequent copies made those divisions “canon”. Because those book divisions were thus structurally important, they were preserved through the transition from scrolls to codices (as generally clearly marked chapter breaks), so that the various “books” served as “super-chapters”.
But sub-divisions were clearly necessary – a single librum is pretty long! The earliest system I am aware of for this was the addition of chapter divisions into the Vulgate – the Latin-language version of the Bible – in the 13th century. Versification – breaking the chapters down into verses – in the New Testament followed in the early 16th century (though it seems necessary to note that there were much older systems of text divisions for the Tanakh though these were not always standardized).
The same work of dividing up ancient texts began around the same time as versification for the Bible. One started by preserving the divisions already present – book divisions, but also for poetry line divisions (which could be detected metrically even if they were not actually written out in individual lines). For most poetic works, that was actually sufficient, though for collections of shorter poems it became necessary to put them in a standard order and then number them. For prose works, chapter and section divisions were imposed by modern editors. Because these divisions needed to be understandable to everyone, over time each work developed its standard set of divisions that everyone uses, codified by critical texts like the Oxford Classical Texts or the Bibliotheca Teubneriana (or “Teubners”).
Thus one cited these works not by the page numbers in modern editions, but rather by these early-modern systems of divisions. In particular a citation moves from the larger divisions to the smaller ones, separating each with a period. Thus Hdt. 7.234.2 is Herodotus, Book 7, chapter 234, section 2. In an odd quirk, it is worth noting classical citations are separated by periods, but Biblical citations are separated by colons. Thus John 3:16 but Liv. 3.16. I will note that for readers who cannot access these texts in the original language, these divisions can be a bit frustrating because they are often not reproduced in modern translations for the public (and sometimes don’t translate well, where they may split the meaning of a sentence), but I’d argue that this is just a reason for publishers to be sure to include the citation divisions in their translations.
That leaves the names of authors and their works. The classical corpus is a “closed” corpus – there is a limited number of works and new ones don’t enter very often (occasionally we find something on a papyrus or lost manuscript, but by “occasionally” I mean “about once in a lifetime”) so the full details of an author’s name are rarely necessary. I don’t need to say “Titus Livius of Patavium” because if I say Livy you know I mean Livy. And in citation as in all publishing, there is a desire for maximum brevity, so given a relatively small number of known authors it was perhaps inevitable that we’d end up abbreviating all of their names. Standard abbreviations are helpful here too, because the languages we use today grew up with these author’s names and so many of them have different forms in different languages. For instance, in English we call Titus Livius “Livy” but in French they say Tite-Live, Spanish says Tito Livio (as does Italian) and the Germans say Livius. These days the most common standard abbreviation set used in English are those settled on by the Oxford Classical Dictionary; I am dreadfully inconsistent on here but I try to stick to those. The OCD says “Livy”, by the by, but “Liv.” is also a very common short-form of his name you’ll see in citations, particularly because it abbreviates all of the linguistic variations on his name.
And then there is one final complication: titles. Ancient written works rarely include big obvious titles on the front of them and often were known by informal rather than formal titles. Consequently when standardized titles for these works formed (often being systematized during the printing-press era just like the section divisions) they tended to be in Latin, even when the works were in Greek. Thus most works have common abbreviations for titles too (again the OCD is the standard list) which typically abbreviate their Latin titles, even for works not originally in Latin.
And now you know! And you can use the link above to the OCD to decode classical citations you see.
One final note here: manuscripts. Manuscripts themselves are cited by an entirely different system because providence made every part of paleography to punish paleographers for their sins. A manuscript codex consists of folia – individual leaves of parchment (so two “pages” in modern numbering on either side of the same physical page) – which are numbered. Then each folium is divided into recto and verso – front and back. Thus a manuscript is going to be cited by its catalog entry wherever it is kept (each one will have its own system, they are not standardized) followed by the folium (‘f.’) and either recto (r) or verso (v). Typically the abbreviation “MS” leads the catalog entry to indicate a manuscript. Thus this picture of two men fighting is MS Thott.290.2º f.87r (it’s in Det Kongelige Bibliotek in Copenhagen):
And there you go.
Bret Devereaux, “Fireside Friday, June 10, 2022”, A Collection of Unmitigated Pedantry, 2022-06-10.
December 14, 2022
QotD: The “tooth-to-tail ratio” in armies
The first issue is what in military parlance is called the “tooth to tail” ratio. This is the ratio of the number of actual combat troops (the “tooth”) to logistics and support personnel (the “tail”) in a fighting force. Note that these are individuals in the fighting force – the question of the supporting civilian economy is separate. The thing is, the tooth to tail ratio has tended to shift towards a longer tail over time, particular as warfare has become increasingly industrialized and technical.
The Roman legion, for instance, was essentially all tooth. While there was a designation for support troops, the immunes, so named because they were immune from having to do certain duties in camp, these fellows were still in the battle line when the legion fought. The immunes included engineers, catapult-operators, musicians, craftsmen, and other specialists. Of course legions were also followed around by civilian non-combatants – camp-followers, sutlers, etc. – but in the actual ranks, the “tail” was minimal.
You can see much the same in the organization of medieval “lances” – units formed around a single knight. The Burgundian “lance” of the late 1400s was composed of nine men, eight of which were combatants (the knight, a second horsemen, the coustillier, and then six support soldiers, three mounted and three on foot) and one, the page, was fully a non-combatant. A tooth-to-tail ratio of 8:1. That sort of “tooth-heavy” setup is common in pre-industrial armies.
The industrial revolution changes a lot, as warfare begins to revolve as much around mobilizing firepower, typically in the form of mass artillery firepower as in mobilizing men. We rarely in our fiction focus on artillery, but modern warfare – that is warfare since around 1900 – is dominated by artillery and other forms of [indirect] fires. Artillery, not tanks or machine guns, after all was the leading cause of combat death in both World Wars. Suddenly, instead of having each soldier carry perhaps 30-40kg of equipment and eat perhaps 1.5kg of food per day, the logistics concern is moving a 9-ton heavy field gun that might throw something like 14,000kg of shell per day during a barrage, for multiple days on end. Suddenly, you need a lot more personnel moving shells than you need firing artillery.
As armies motorized after WWI and especially after WWII, this got even worse, as a unit of motorized or mechanized infantry needed a small army of mechanics and logistics personnel handling spare parts in order to stay motorized. Consequently, tooth-to-tail ratios plummeted, inverted and then kept going. In the US Army in WWI, the ratio was 1:2.6 (note that we’ve flipped the pre-industrial ratio, that’s 2.6 non-combat troops for every front line combat solider), by WWII it was 1:4.3 and by 2005 it was 1:8.1. Now I should note there’s also a lot of variance here too, particularly during the Cold War, but the general trend has been for this figure to continue increasing as more complex, expensive and high-tech weaponry is added to warfare, because all of that new kit demands technicians and mechanics to maintain and supply it.
[NR: Early in WW2, British Prime Minister Winston Churchill frequently harassed his various North African generals for the disparity between the “ration strength” of their commands and the much-smaller number of combat troops deployed. If General Wavell had 250,000 drawing rations, Churchill (who last commanded troops in the field in mid-WW1) assumed that this meant close to 200,000 combat troops available to fight the Italians and (later) the Germans. This almost certainly contributed to the high wastage rate of British generals in the Western Desert.]
Bret Devereaux, “Fireside Friday, April 22, 2022”, A Collection of Unmitigated Pedantry, 2022-04-22.