Featured

Æthelred the Unready: New Book Re-examines Infamous Anglo-Saxon King’s Military Practices

After a year and a half of writing, editing, and revising (and many more years of research), it’s finally out: my new book, England’s Unlikely Commander: The Military Career of Æthelred the Unready, is available from Rounded Globe.

England’s Unlikely Commander takes a look at the military practices of late Anglo-Saxon England, using sources like The Anglo-Saxon Chronicle, Gesta Normannorum Ducum, and royal charters. Late Anglo-Saxon England, particularly during the reign of Æthelred the Unready, was plagued by recurring Viking invasions. Viking armies under Danish rulers even conquered England twice during this era — temporarily in 1013 and again in 1016.

Accordingly, the English king Æthelred has gone down in history as an inept and passive ruler who did far too little to stem the tide against the Vikings. However, when looking at the sources more closely, I found more reasons to doubt Æthelred’s “unreadiness” than to uphold it. In fact, in England’s Unlikely Commander I make the case that Æthelred was a very typical (and highly engaged) English king who enjoyed plenty of military triumphs.

This book is not the first to re-assess King Æthelred’s reign — far from it. It is deeply indebted to the work of phenomenal scholars like Simon Keynes, Ryan Lavelle, Ian Howard, Ann Williams, Levi Roach, Richard Abels, and many others. Many of these scholars also make note of Æthelred’s military career, although it is rarely the sole focus of such research. So, while many of these scholars have touched on Æthelred as a military leader (Abels and Howard in particular), I still felt that a book focused squarely on the king’s military engagements would nicely complement this existing scholarship. After all, the main sources for the reign (especially the many versions of The Anglo-Saxon Chronicle) focus on military affairs above all else. That is not to say, however, that Æthelred’s military career can be divorced from the wider reign; it cannot and should not be.

However, there is far more to the Danish Conquest than Æthelred’s failure. In this new book, I argue that England fell to the Vikings in spite of Æthelred, not because of him. The king presented in England’s Unlikely Commander is not passive and weak, but resilient, persistent, and resourceful: even when faced with setbacks and failures (and an exceptionally difficult enemy!), Æthelred always had an idea up his sleeve. Over a 38-year reign (the longest in Anglo-Saxon England), the king led armies into battle, constructed fleets to protect his shores, defended his cities, refortified his strongholds, and even managed to re-conquer his own kingdom after being overthrown just months earlier.

It is my hope that readers will find this short book an enlightening and easy-to-read guide to Æthelred’s military career. The Danish Conquest is one of the most exciting periods in early English history, and there is far more to it than the ferocity of the Vikings and the supposed cowardice of the English leaders; it was a far closer contest than most realize, thanks at least in part to the many efforts of Æthelred the Unready.

Where to find England’s Unlikely Commander:

View it online, completely free, on Rounded Globe’s website or on Academia.edu.

A paperback version is also available.

Official Synopsis:

In the realm of popular history, it’s common to hear the claim that Æthelred the Unready, King of the English, was a military failure in an age where kings had to be warriors. Due to the unflattering nickname (unraed actually means “poorly-advised”) and the Danish Conquest of England, it might seem that these critics have won the argument before it’s even started.

That isn’t the case, though, as Bender’s research has found. This book seeks to redress King Æthelred’s military reputation, arguing that he was militarily prepared and often successful against his many enemies, including the Vikings. Tracking the king’s movement and activity over his 38-year reign, this book argues that Æthelred the Unready was anything but a battle-avoider.

Early Praise for England’s Unlikely Commander:

In this exciting new book, Brandon Bender sheds considerable new light on the life and military career of one of England’s most notorious kings. Both scholarly and accessibly written, it deserves a wide audience both within and beyond the halls of modern academe.

-Dr Levi Roach, Senior Lecturer in Medieval History, University of Exeter. Author of Æthelred the Unready (Yale University Press, 2016)

This readable and engaging study of Æthelred the Unready’s military career is a welcome contribution to the current scholarly movement reconsidering the reputation of this much-maligned king. Building his argument on careful analysis of the sources, Brandon Bender offers a concise but thorough re-evaluation of Æthelred’s military policies, exploring the different political and personal factors which might have motivated the king’s decisions. Anyone interested in the military and political history of Anglo-Saxon England will find that Bender’s book provides much food for thought.

– Dr Eleanor Parker, Lecturer in Medieval English Literature, Brasenose College, Oxford. Author of Dragon Lords: The History and Legends of Viking England and A Short History of The Danish Conquest

Other Information:

Publisher: Rounded Globe

Pages (print version): 101

Cover art and design: Dasha Lebesheva

Publication dates: 16 April 2019 (online); 22 September 2019 (print)

New Publication! Æthelred the Unready and William of Malmesbury

Above: Richard Kiley portrays King Æthelred in The Ceremony of Innocence, one of the many depictions examined in the article.  

I’m very pleased to announce the publication of my first peer-reviewed journal article. The article, titled “Æthelred the Unready and William of Malmesbury: The Death of a Reputation,” appears in volume 34 of The Year’s Work in Medievalism, released August 5th, 2021.

The article surveys portrayals of Æthelred II in popular culture, the majority of which depict him negatively — he is variously a coward, drunkard, weakling, or all of the above. Most of this material can be traced back to the medieval chronicler William of Malmesbury, who was writing well after Æthelred had died. Why did William’s account become so common? How does it compare to earlier or alternate medieval views of the king? And finally, is there any hope for Æthelred in mass media, or is he doomed to play the fool forever? I explore all of these questions in the article.

The paper is open access, meaning anyone can read it in its entirety for free or download it:

Access on The Year’s Work in Medievalism

Access on Academia.edu

My First Citation

A couple milestones: my book has been cited in an academic journal for the first time; this is also the first time I’ve been mentioned in another author’s acknowledgments. Considering that 80% of academic writing in the humanities is never cited, not even once, I’m very fortunate. It’s mentioned in an article in The Archaeological Journal about English defenses against the vikings.

The paper is called “The late tenth-century defences of Oxford and the towers of St George and St Michael” and is written by archaeologist Jeremy Haslam.

Thoughts on “Swein Forkbeard’s Invasions” and “Reign of Æthelred II” by Ian Howard

Two books by Ian Howard (Swein Forkbeard’s Invasions and the Danish Conquest of England 991-1017 and The Reign of Æthelred II: King of the English, Emperor of All the Peoples of Britain) deal with similar topics, so I thought I would address them together, especially since they share an author. Both are academic works that engage with a tumultuous and confusing period of early English history, when England fell to a Danish king in 1013, was recovered by the English one in 1014, and was conquered by Danes again in 1016. Unfortunately, the Danish Conquest has been understudied to a degree that almost seems criminal, especially when considering that there are dozens, if not hundreds, of 1066 books and documentaries readily available. I can count the books focused on the Danish Conquest on one hand, so I’ll start with Swein Forkbeard’s Invasions and the Danish Conquest, a book that was helpful when I was doing my own reading on Æthelred’s reign.

Swein Forkbeard’s Invasions

Swein Forkbeard’s Invasions came out in 2003 and puts forward a few arguments that were ahead of its time. It is one of the earlier books to recognize that the English military reaction to the Danish invasions was not nearly as inept as was once thought. While this had been mentioned by numerous authors before, this book (as the title suggests) focuses primarily on military history and is better suited to address it in detail. Howard also openly acknowledges that the English comeback in 1014 was, at least partially, a military one – a point still ignored by many historians today. I think this uncomfortable view, that Æthelred led a “re-conquest” in 1014 with Scandinavian help, will become more commonplace with time, but Howard managed to see it hiding in plain sight nearly 20 years ago. Swein Forkbeard’s Invasions is also happy to use later sagas as sources, a trend that is thankfully becoming more common; however, as I’ll get to in a moment, it can be a double-edged sword. These are some of the book’s most significant strengths, and it’s rewarding to see the Scandinavian accounts of Æthelred’s re-conquest taken seriously.

However, there are a few drawbacks that distracted me. For one, the book matter-of-factly states that Swein had served Æthelred as a mercenary, a claim I’m not sure I’ve seen anywhere else. The rationale for this isn’t very clear, so I’m still not sure why Howard thinks this. Something similar happens with Olaf Tryggvason. Howard says Olaf stayed in England after his agreement with Æthelred in 994, which is a step further than most others go. Usually I hear that while many of Olaf’s soldiers became English mercenaries, Olaf himself was not directly involved. There is also a heavy emphasis on identifying the number of soldiers involved in campaigns and invasions, which makes sense since this is military history, but I’ve never been a numbers and battlefield tactics guy myself. I’m probably shell-shocked because it so often descends into armchair general territory, which Howard does not do. While that’s more of a personal preference overall, I think it can be a dangerous game to play when dealing with this murky era. Howard does have good precedent for this, though, since even Simon Keynes did this to an extent.

Also, while it’s refreshing that Howard uses sagas as historical sources, sometimes they are given precedence over earlier English ones. I’m not sure why this is, given that the English sources he uses are hundreds of years earlier (at least in written form) and are geographically closer to many of the events they describe. The most skillful authors that I’ve seen treat the sagas as supplements or counterpoints to English sources, not as ways to overrule them. This only happens a few times, though, and I would say that Howard’s use of the sagas is more of a benefit to the book than a hindrance.

The Danish Conquest portion of the book is organized by military leader (one chapter for Swein and one for Thorkell), not strictly chronologically, which can make it difficult to understand on first read. Going from the Swein chapter to the Thorkell one can feel like deja vu when many of the same events are described again and it can be jarring to read of key players like Swein and Æthelred dying more than once. It also means that when I want to go back and find something, I have no idea which of the two chapters it came from, so I’m forced to hunt through both of them.

In all, I would say that Swein Forkbeard’s Invasions is valuable for the military historian, especially one interested in medieval Scandinavian accounts of the Danish Conquest, even if I am puzzled by some of the claims about mercenaries and found the organization of later chapters somewhat confusing. It’s an important step in the study of the Danish Conquest, which remains severely understudied compared to 1066.

The Reign of Æthelred II

Seeing as I enjoyed the book reviewed above, I was eager to pick up this biography of Æthelred. Despite the high price, I wanted to see what Howard, who often approached things from more of a military history perspective, would do with Æthelred. The subtitle of the book also promised a view of Æthelred as a ruler of peoples, a king with imperial ambitions. Based on the utilitarian cover and layout (two columns of text per page with substantial back matter), I was prepared for this to be a dense read. Having read the previous biographies of the king, though, I felt more than ready for it.

Well, it was a difficult read, but for more straightforward reasons. This book is absolutely bursting with typos. First, the more minor offenses: there are tons of semicolons used incorrectly, where a dash or even a comma would have done. For the millionth time, a semicolon is not a spicy comma. Please, writers, if you’re looking for a pause, try a long dash. I had this issue with Peter Rex’s Edward the Confessor, where it was so distracting that it nearly caused me to give up on it (It was like every semicolon; was used like this; poorly.). Capitalization is not consistent, either. Pagan, court, and royal, which are not proper nouns anyway, are sometimes capitalized for a few pages only to revert back to lowercase. It gets worse. Page 15 contains the line that Æthelred was “ten year’s old.” That random apostrophe wasn’t the only thing allowed to hitchhike its way into the finished product. There were several confused words that won’t necessarily show up underlined on a word processor. For example, emphasis was confused with emphasise (this could also be emphasize in US English). Look, every book has a few typos – my finished writing sometimes has typos – but this is different. In some sections, there are several on each page, sometimes in a single paragraph. The appendices and later chapters are noticeably cleaner (although they still contain some spicy commas), suggesting those sections of the book were proofread at a different time or by someone else.

Now on to more topical issues: there are some factual errors. For example, one part implies that Edward the Martyr was less legitimate since he had been born before Edgar’s imperial coronation (973), but Æthelred and Edmund Ætheling had also been born before it, so why does this matter? Edgar ascends in 958 rather than 959, although apparently this was on purpose. Howard’s reasoning for this date is covered in a section at the end, but why not address it right away in a footnote? I went the entire book thinking it had been an error, not something Howard had purposely re-dated. Speaking of footnotes, some of them are almost circular. A staggering number of them just refer back to the prior book, Swein Forkbeard’s Invasions, without any other supplemental sources or comments propping them up. There is nothing wrong with referring to one’s own research, but you also don’t want to re-write a prior book.

The book is poorly organized at times and not always internally consistent. The chapter “A Young King” begins with a 41-line (!) paragraph addressing the end of Edgar’s reign and most of Edward’s, with virtually no awareness that the last chapter already covered both reigns in detail. This doesn’t read like a transition between topics. Instead, it’s like these are two different essays pasted together to make two chapters, where chapter 2 is a totally independent of chapter 1.

Howard believes Æthelred was militarily active and effective, which is the same basic view that I have, although there are a couple oddities. He thinks that Æthelred led military campaigns in 984 and 988 based on his followers being referred to as miles in charters, and reasons that if there were campaigns, Æthelred must have led them. I’m open to the argument that the English conducted campaigns not mentioned in the ASC (Welsh annalists mention some), but why does it logically follow that Æthelred led them? This is more of a wording issue. Had it been presented as a possibility, rather than a near-certainty, I would not have found this too objectionable. Later, Howard says that Æthelred’s earliest military experience was in these two years, but fails to mention a 986 harrying campaign that is well-documented. Howard does address the 986 campaign in other parts of the book, but downplays its severity and significance. But still, why chase after two phantom campaigns in 984 and 988 but not refer back to the 986 one, which is one of the best-attested events in the reign? The ASC mentions it, as do numerous later sources, but the earliest account comes from Æthelred himself, who mentions it in one of his charters. That charter describes it with words like “despoliation” and “plunder,” which naturally leads me to wonder why it was downplayed by Howard as a military activity. If someone with a Scandinavian name had claimed to be responsible for “despoliation” and “plunder,” we would rightly refer to this as, at the very least, a raid.

There are many other places where the book connects dots that might not warrant being connected. Howard writes that Æthelred’s mercenaries from 994, the fleet that attacked the southern coasts in 997, and the forces that defected in 1001 were the same group, which I’m not convinced of. The book repeats the claim Swein Forkbeard once served as a mercenary leader for Æthelred. There is another leap in reasoning later on when Howard bluntly states that Æthelred must have been seriously ill in 1012, three years before he is recorded as being sick, because he did not appear to lead the witan. I’m not opposed to this idea – actually, Howard might be on to something – but a few more maybes are in order here. Is it possible that Æthelred, who came from a line of sickly and short-lived kings, missed this meeting due to illness? Of course. But it’s not presented as merely plausible or possible; it’s stated as near-fact and then repeated with a tone of certainty.

I also found that there was an overemphasis on reconciling chronology, especially when trying to align sagas with English sources. The attempts to make everything fit are admirable and extremely detailed, but sometimes there is no good way to make 15 years fit into 10. I don’t want to discourage anyone from trying to reconcile disparities in medieval sources. Rather, I think the problem is not knowing when to admit that the exact chronology is unknowable. Sometimes contradictions are just that – contradictions – and it’s better to acknowledge them and move on if there is no clear way to align them. Acknowledging a contradiction does not mean the source has to be thrown away.

Now I will zoom out and address what this book doesn’t say. There is an under-emphasis on Æthelred’s role as “Emperor of All the Peoples of Britain,” which is the subtitle of the book. Despite being mentioned in the introduction and getting a spot on the front cover, this topic is only touched on a couple times. I did not feel like it was one of the major themes of the book and was left confused about why it was part of the title at all.

A few bright spots: there is some good info on Æthelwold and Dunstan in the earlier chapters, messy as they might be. Howard does a good job of recognizing and emphasizing that they weren’t always on the same team, which is overlooked a lot. Also, the reference an Æthelredian charter claiming that Edward’s election was “unanimous” is smart and useful. And again, I think Howard could be on to something about Æthelred being ill in 1012. My issue is with the wording, not the idea itself. I also enjoyed the commentary and speculation about Æthelred’s personality and character. This is a topic most historians are too cautious to comment on, although Levi Roach has also done this at times. I appreciate the willingness to “take a shot” and go for it.

Overall, due to the poor organization of the book, the abundance of typos, surprising leaps in reasoning, and a relatively high price, I can’t say I recommend this title. Despite occasional sparks of ingenuity, this is one of the least consistent books I own. It reads more like a good first draft than a finished product. This was a book desperately in need of additional editing, proofreading, and fact-checking, and it’s a disservice to the author that it was released in this state. The prior book showed what Howard could do with a solid editing team, but it feels like he was hung out to dry in this book.

Alex Smith’s OTHER Miracle Season: 2017

Cover image: Pro Football Focus highlights Smith’s status as one of the league’s best deep passers of 2017.

The fact that Alex Smith made it onto the football field in 2020, let alone started, is nothing short of a modern miracle. Following a career- and life-threatening injury in 2018, many doubted Smith would ever play pro football again. His comeback was one of the most covered stories of an otherwise depressing 2020, so I won’t go over it again here. Instead, I want to discuss Alex Smith’s other miracle season: the time he led the league in passer rating, was the NFL’s best downfield passer, and topped 4,000 passing yards. These things sound like they shouldn’t go together. Alex Smith, an elite deep passer? 4,000 yards? Even though Smith is famous for his exceptionally clean (if unexciting) brand of football, hearing that he led the league in passer rating might seem surprising.

One of these stat lines is Patrick Mahomes during his Super Bowl-winning season. The other is Alex Smith in 2017:

14 starts, 4,031 yards, 26 TD, 5 INT, 65.9% complete, 105.3 rating, 176 rushing yards.

15 starts, 4,042 yards, 26 TD, 5 INT, 67.5% complete, 104.7 rating, 355 rushing yards.

Unless you have a photographic memory for statistics, you basically have to guess which is which. This illustrates just how good Smith was in 2017 – and how shocking it is that so many fans have forgotten this season. How did a season like this happen with Smith? And why have we largely forgotten it?

(Answer: the top line is Mahomes in 2019. The bottom line is Smith in 2017.)

Smith had been the number one overall pick way back in 2005, struggling in his first several seasons as the quarterback for an unstable and dysfunctional 49ers franchise. He finally found success in the early 2010s by adopting his current mistake-free method of passing under coach Jim Harbaugh. This rejuvenated Alex Smith didn’t try to be the savior of the world, who had been hailed as a second Joe Montana or Steve Young – he just tried to be efficient and precise and not worry about what everyone else thought. Everyone thought he was a bust anyway. Harbaugh and Smith guided the 49ers to 13-3 record in 2011. 2012 saw Smith put up some of the best numbers in the league through the season’s first half, boasting a 104.1 rating and completing 70% of his passes. However, an injury derailed his season when the younger, faster, and harder-throwing Colin Kaepernick proved to be electrifying in his own right. Smith recovered his health, but not his job. After suffering through a carousel of mediocre QBs in the post-Young era, the 49ers were suddenly a team with two starters. Just like with the Montana-Young rivalry, the Niners had a choice to make. Smith was traded to the Chiefs in the offseason, two decades after Montana had been traded there after also being supplanted by a younger, faster up-and-comer. The Chiefs had gone 2-14 in 2012, so they cleaned house and brought in Andy Reid to rebuild the franchise. Smith was the quarterback Reid chose.

Stability as a Chief: 2013-16

Thus began the most stable period of Smith’s long career. Under Reid and Smith, the Chiefs jumped from 2-14 to 11-5. From 2013-16, the Chiefs had a winning record every year and posted double-digit wins in three of those four seasons, along with three playoff appearances. Smith was steady as could be. In each of those years, he threw for between 3,200 and 3,500 yards, with a QB rating that generally stayed in the low 90s. He also began using his mobility more often, peaking at 498 rushing yards in 2015. That’s getting into legitimate dual-threat territory, although as usual, few recognized this unless they were playing against or watching the Chiefs and saw it firsthand. This stability (and mobility) did earn Smith his first Pro Bowl nod in 2013, at age 29, as well as another in 2016. In the 2016-17 postseason, he also led the Chiefs to their first playoff win since the 1993-94 postseason, a 30-0 shutout of the Houston Texans. The last QB to lead the Chiefs to a playoff win had been Montana.

This solid play also reinforced some of the more negative stereotypes about Smith, though. In his late 49ers career, Smith’s cautious but efficient play gained him a reputation as a game manager: an organized but bland player whose team wins with him, but not because of him. A game manager doesn’t put the team on his back and carry them; he efficiently distributes the ball to others who put the team on their backs.

This is important because Smith’s existing reputation helps explain why few of us remember his 2017 in the first place. Most people already had a fully-formed idea of Smith: he wins a lot of games, can run a little, and does not throw deep. He’s the sort of player the casual fan rolls his eyes at. He’s certainly not elite, so any success he has is chalked up to other players on the roster or written off entirely, as though it’s just a fluke.

2017: Alex Smith’s Career Season

Enter 2017. The Chiefs had just drafted a talented but raw quarterback, Patrick Mahomes II. Although Mahomes had more pure talent than almost anyone, the Chiefs had no reason to press him into duty immediately. They were consistently one of the NFL’s better teams and a few months earlier, they had won their first playoff game in decades. They had young and talented pass catchers like Tyreek Hill and Travis Kelce. Things were looking up. But it’s also true that the Chiefs, for all their regular season success, just couldn’t seem to get over the hump with Smith at quarterback. It seemed that he was good enough to guide the Chiefs to the playoffs every year, beating up less-talented quarterbacks and teams during the regular season, but once he was faced with the Bradys and Roethlisbergers of the league, there was just no way he could keep up. 2017 began with Smith firmly entrenched as the starter, but the writing was on the wall: Mahomes was the future. Smith, a veteran who had been through nearly everything an NFL quarterback could go through, seemed like the perfect mentor for Mahomes. He was everything Mahomes was not: careful, guarded, and able to get the ball out before anyone knew what had happened.

The 2017 season began with a bang. The Chiefs had to start their year in Foxborough against the Patriots, who some pundits had already decided would go undefeated. Smith and Co. lit up the field with deep bombs, coming from behind to stun New England 42-27. Smith’s success continued the following week, defeating the eventual Super Bowl champion Eagles. And the next week over the Chargers. And again over Washington. In Week 5, Kansas City went up against Houston, the same team they defeated 30-0 in the 2016-17 playoffs. The Chiefs won again. But somehow, this 5-0 start was different than all the other strong starts in the Smith and Reid era. They were not just winning with Smith – they were winning because of him. In the Patriots game, Smith threw for some very Mahomes-like totals: 28/35 for 368 yards and 4 touchdowns with no interceptions, good for a 148.6 rating. It was a similar story against Houston: 29/37 for 324 yards and 3 touchdowns, with no interceptions and a 130.2 rating.

For a brief moment, the national media began paying attention to Smith. During the early and middle part of the 2017 season, he was viewed as a contender for league MVP. Through his first eight games, he had thrown for 2,181 yards, 16 touchdowns, and no interceptions. If Smith maintained his pace, he would end the year with 4,362 yards, 32 touchdowns and zero (!) interceptions. Smith gradually fell out of the MVP discussion, though, partly because the Chiefs took a nosedive during the middle of the season, losing six of seven games between Week 6 and Week 12. Smith continued to play at a high level during that span, but the damage was done. The conversation shifted from “Is Alex Smith the MVP?” to “Will the Chiefs even make the playoffs?”

Perhaps Smith’s most heroic effort of the 2017 season came during one of those losses, a 38-31 game against the Jets. He showed the full extent of his abilities in this game: the 33 year-old made good decisions, displayed his ability to repeatedly throw deep, and showed off his mobility in the most dramatic way possible. Smith threw for 366 yards and 4 touchdowns, with no interceptions; he also broke off a 70-yard run that saw him outrun much of the Jets defense and break several tackles. Smith had done exactly what everyone said he didn’t do: just like in the New England game in Week 1, Smith had carried the team on his back.

The Chiefs rebounded and won their next three games from Week 13 to Week 16, putting the Smith-led Chiefs at 9-6 and securing their spot in the playoffs. Even though Smith played at an elite level for the first 15 games of the season, he and many of the other Chiefs starters did not play in Week 17 because the Chiefs were already assured of their playoff spot, so they could not afford to let Smith get injured in a meaningless game. In Week 17, with Smith tucked away safely on the sidelines, Chiefs fans got their first glimpse of Mahomes in NFL action.

The next week, Kansas City’s well-rested starters were back on the field for their playoff game against Tennessee. Smith played well as usual, throwing for 264 yards with 2 touchdowns and – as you’re probably used to seeing with Smith – no interceptions. He completed 72% of his passes and put up a 116.2 rating, but the Chiefs lost a 22-21 nail-biter, partly because Titans quarterback Marcus Mariota threw a pass to himself for a touchdown. Just like during the mid-season slump, the Chiefs lost and it really wasn’t Alex’s fault.

However, it had happened again. The Smith-led Chiefs just could not advance deep into the playoffs. They were now 1-4 in the postseason during the Reid-Smith era. Most fans in Kansas City seemed to understand that after the Titans loss, Smith had played his final game as a Chief. He’d gone out with a bang in a 2017 season that saw him throw for 4,042 yards, 26 touchdowns, 5 interceptions, and a league-best 104.7 rating. He also added 355 yards on the ground. It was the first time a Chiefs quarterback had eclipsed the 4,000-yard mark since Trent Green in 2005. It was the first time a Chief had ever led the NFL in passer rating (Note: Hall of Famer Len Dawson had led the AFL in passer rating numerous times with the Chiefs in the 1960s). It was the best-ever passer rating by a Chief.

Smith was traded to Washington after the 2017 season, having thrown for 17,608 yards, 102 touchdowns, 33 interceptions, and a 94.8 rating in his Chiefs tenure. At the time of his departure, he had the best career passer rating, completion percentage (65.1), and interception percentage (1.4) in Chiefs history. All three records have since been broken by Mahomes, but Smith, whose mobility has been constantly underrated, still holds records for the most rushing yards and touchdowns by a Chiefs quarterback (1,672 and 10, respectively). These are two records that Mahomes isn’t likely to pass any time soon.

The Causes of Smith’s 2017 Season

But how did this season happen in the first place? Even though Smith had been a good quarterback for years at that point, there is no denying that 2017 is a clear outlier among his career numbers. There are several factors that contributed:

One is that Smith had an incredible cast to work with in 2017. He had Tyreek Hill and Travis Kelce as his main targets, both of whom were (and still are) legitimate superstars. Smith was willing to throw intermediate passes to Kelce, who is a big target and can catch just about anything. He was willing to throw deep because Hill could simply outrun the whole defense. Smith had thrown deep here and there in the past, but I do think this shows how passing is a two-way street. It takes a quarterback and a receiver, not just one or the other, and Smith had a lot more to work with by 2017 than he did in 2013. In 2013, there was no Kelce (he was injured for his rookie year) to throw to at tight end, only anonymous castoffs from other teams, and no legitimate deep threats at wide receiver. His main target in 2013, just for comparison, was the aging Dwayne Bowe, who had been drafted two general managers and three head coaches ago.

Stability is another contributor that I think gets overlooked a lot. From 2013-17, Smith got to work in Andy Reid’s offense for five seasons. Compare this to Smith’s early career in San Francisco, when he had to work under five offensive coordinators in five seasons.

A simpler reason that Smith heaved the ball all over the field in 2017 is that he had to. The Chiefs defense had been one of the league’s best units from 2013-15, with some decline showing in 2016. By 2017, the Chiefs’ former strength, defense, had become a weakness. Smith, for the first time in his Chiefs career, had to throw the ball a lot just to keep Kansas City in the game. A good example of that would be the Week 1 Patriots game, where the Chiefs fell behind against an elite quarterback in Tom Brady. There weren’t many options: throw deep or lose.

Finally, Smith’s overall career arc should be taken into consideration. NFL starting quarterbacks tend to last longer than players at other positions. Smith was 33 in 2017, undoubtedly on the older side, but still not among the league’s oldest starting quarterbacks. He had the benefit of years of experience while also still retaining the physical skills to be successful, including enough mobility to make things happen with his legs.

Why We Forget About Smith’s 2017 Season

As noteworthy as Smith’s 2017 campaign was in Chiefs history, it pales in comparison to what happened next. Mahomes came out of nowhere to throw for 5,097 yards, 50 touchdowns, and a rating of 113.8 the very next year. Smith had been considered as league MVP in 2017, but Mahomes actually won it in 2018. The Chiefs’ 2018 season was like an exaggerated, fun-house mirror version 2017: the superstars like Hill and Kelce were still there, but now Sammy Watkins was added to the mix. The defense that had played poorly in 2017 suffered a complete implosion in 2018, meaning that if 2017 Smith had to throw a lot to keep the Chiefs in the game, 2018 Mahomes had to throw even more. And if there was ever a quarterback well-suited to that type of team, it was Mahomes. In short, Mahomes had the benefit of an even more talented receiving corps, had to cover for an even worse defense, and had the arm talent to out-throw nearly every QB in the league. All of this meant that Smith’s 2017, which was one of the best seasons in Chiefs history, was blown out of the water just one year later.

Winning the big one also has a funny effect on people’s memories. All the things they used to cling to during less-successful eras become unimportant. When the Royals won the World Series in 2015, Kansas Citians no longer had to reminisce about that one fluke season in 2003 or how good Zack Greinke was in 2009. Likewise, Chiefs fans simply have little reason to reflect on Alex Smith’s 2017 season because the Chiefs won it all with Mahomes, not Smith. Ironically enough, Mahomes’ Super Bowl-winning season is the one I used as my example up top for comparison with Smith’s 2017.

The final reason I will offer is the most unfair, and it’s one I had alluded to earlier: People had already made up their minds about Smith anyway. Since Smith, unlike Mahomes, had been in the league for a long time when he put up his elite season, fans already knew what to expect from him: 3,500 yards, maybe 15-20 touchdowns, a 90-ish QB rating, and a single-digit turnover season – effective enough, but not all that attractive. Because this reputation had already been established well before 2017, his final season with the Chiefs is overlooked as a fluke, if it’s recognized at all.

However, Smith deserves far more credit for what he did in 2017. Whether it conforms to your pre-existing ideas about Alex or not, it did happen. It’s not just a thought exercise. For one season, in 2017, Alex Smith was the league’s highest-rated quarterback, who threw for more yards than any Chief had in over a decade.

This is why when 2020 Alex Smith threw for 390 yards on his cyborg leg, I wasn’t too shocked. He’d put up impressive numbers before. Likewise, the next time you hear someone say that the Chiefs’ reign as the league’s most terrifying offense began under Mahomes in 2018, know that they’re wrong. It began one year earlier, in 2017, under Alex Smith.

New Medievalism Publication: Camedieval

I had the pleasure of writing a piece on medievalism for an exciting new project called Camedieval. For those not familiar with the terminology, medievalism is the study of how the medieval period is portrayed or thought of in more recent times and why. Camedieval, a project associated with CALM and GEMS at Cambridge University, seeks to make medievalism relevant to the wider public. It’s still a very new project and I’m honored to be one of the first authors to contribute.

My article is about how modern political and social discourse in the UK, Ireland, and the US still relies on shorthands derived from the early medieval rulers of England. It’s called “Epithets, Legends, and Lessons: Early English Royalty and the 21st Century” and it talks about how we still use names and legends attached to kings who lived a thousand years ago — the story of Alfred and the cakes, the legend about Cnut and the waves, and the nickname “Unready.”

Be sure to stop by Camedieval and check it out, and follow them for more medievalism posts.

Book Recommendations: Anglo-Saxon England

Finding the Balance between Readable and Rigorous

When writing about medieval history, one of the trickiest feats to pull off is making your subject both enjoyable and academically sound. While there is something to be said for writing a book so thorough that its footnotes need footnotes, I would argue that it’s rarer to find something that can be read for pleasure and study alike.

Usually it’s pretty easy to spot books that are on the lightest extreme of the spectrum. The biggest giveaway is the lack of any cited sources. These can be good coffee table books, but sometimes they’re so poorly researched that they contain outright falsehoods or severe errors. They’re usually page-turners, but when that comes at the expense of accuracy, is it really worth it?

The other extreme can be just as frustrating. There have been days when I’ve cracked open a new medieval history book, hoping to find a helpful introduction to an unfamiliar topic, and then it hits me. It’s another book by experts, for experts, written exclusively in passive-voice paragraphs that go on for pages.

Thankfully, I have run across several books that, in my opinion, strike an excellent balance between scholarship and readability. This list contains only a few of them. These works take their subjects seriously, but never talk down to their audience. They’re smart without being pretentious and thorough without being obsessive. Sometimes this readability does come at the expense of tackling every little side debate and scholarly feud, but that’s okay. Maybe it’s even a benefit if it’s your first time reading about the subject. Behold, my list of Balanced Anglo-Saxon History Books:

The King’s Body: Burial and Succession in Late Anglo-Saxon England by Nicole Marafioti

I cannot stress enough what a good book this is. Marafioti has a true talent for writing and an uncanny ability to explain the most complex issues in ways that appear magically simple. Even better, the topic of this book is one the most dramatic, but universal, ones in medieval history: the ever-present cycle of royal death, struggle, and succession. Pick up The King’s Body if you’re looking for an engaging page-turner of a book with some serious academic firepower behind it. (Note: I have an electronic copy of this book, which is the only reason it does not appear in the cover image)

Alfred the Great: Asser’s Life of King Alfred and Other Contemporary Sources translated and edited by Simon Keynes and Michael Lapidge

Alfred the Great, the only translation to crack this list, is a must-have for anyone who is getting into primary sources for the Anglo-Saxon period. The crown jewel of this collection is obviously Asser’s Life of King Alfred, but also included are early annals of The Anglo-Saxon Chronicle, extracts of Alfred’s own writing, and yes, even a section on the Alfred and the Cakes legend. This Penguin Classics title is cheap, widely available, and largely avoids the stilted style than can plague translations.

Dragon Lords: The History and Legends of Viking England by Eleanor Parker

Eleanor Parker is perhaps best known for her long-running blog, A Clerk of Oxford, which has won widespread acclaim and proven that academics can indeed connect with the general public. Her book, Dragon Lords, provides exactly what the subtitle promises: a look at the history and legends of Viking England. Better yet, there’s nothing to be afraid of here: Dragon Lords earns a spot on this list because it’s written by an academic who has plenty of experience making medieval history come alive for the public, not just for other experts.

Reassessing Anglo-Saxon England by Eric John

In a sense, this book represents the culmination of John’s lifelong research, where he skips from topic to topic in chronological order, only focusing on the ones that interest him, but that’s a good thing. It helps avoid the tediousness that plagues so many other books that cover such a wide time frame and ensures that John is always fully invested in what he’s writing about. In typical Eric John fashion, Reassessing Anglo-Saxon England is sometimes flippant, sometimes funny, and sometimes reckless, but always entertaining. This is a book that you won’t always agree with, but it’s one you’ll never forget.

Athelstan: The Making of England by Tom Holland

Is that Sarah Foot biography of Athelstan looking a little intimidating? If so, start off with Athelstan by Tom Holland. As part of the Penguin Monarchs series, this book is short and easy to follow. In a recent tweet, I described this book as “concise, punchy, and gripping from start to finish: an engaging introduction to one of England’s most important, but under-appreciated, monarchs.” This book is affordable, small enough to fit in your back pocket, and brief enough to read in an afternoon. Then, once you’re comfortable with Athelstan, you can dive into that excellent Sarah Foot book without fear.

The Year 1000: What Life Was Like at the Turn of the First Millennium – An Englishman’s World by Robert Lacey and Danny Danziger

If you want to get away from Great Man History, try The Year 1000, which has become a favorite in the last couple decades. Lacey and Danziger write in a tone that is approachable and amiable. Although this book is on the lighter end of this list, if you judge by the acknowledgements, the authors consulted every expert imaginable in the making of this book. The Year 1000 focuses on everyday life in late Anglo-Saxon times, delivered in a way that even a total newcomer will feel welcomed.

St. Brice’s Day and the Danish Conquest

Cover image: a medieval illustration of Cnut the Great (right) battling Edmund Ironside (left), by Matthew Paris.

Re-evaluating a Medieval Revenge Tale

I’m writing this post on 13 November, an unlucky day in English history. Even unluckier, today is also Friday the 13th. It’s a fitting time to dive into one of Anglo-Saxon England’s most infamous events: the St. Brice’s Day Massacre. On 13 November 1002, King Æthelred II of England, after suffering years of viking incursions, commanded that all Danes in his kingdom were to be killed. The Anglo-Saxon Chronicle contains one of the earliest accounts of what happened that day:

…the king ordered all the Danish men who were among the English race to be killed on Brice’s Day, because it was made known to the king that they wanted to ensnare his life – and afterwards all of his councillors – and have his kingdom afterwards.

As the chronicler reveals, this bloody event occurred on the feast day, 13 November, of a now-obscure saint named St. Brice of Tours, thus giving the massacre its name. We have an even earlier account of the massacre, though. Amazingly, it comes from the man who ordered it:

…it will be well known that a decree was sent out by me with the counsel of my leading men and magnates, to the effect that all the Danes who had sprung up in this island, sprouting like weeds among the wheat, were to be destroyed by a most just extermination [1].

Yes, that’s a charter of King Æthelred, where the king (or more likely, someone writing on his behalf) provides several important details that line up with the ASC’s account: the decree came directly from the king; his councillors are involved in some way (either as targets of a plot, co-planners of the massacre, or both); and all Danes in England are to be killed. Over a decade later, King Sweyn (also spelled Svein, Sven, or Swein) of Denmark conquered England. After Sweyn died in 1014, Æthelred recovered his crown and drove Sweyn’s son, Cnut, out of the country. After the death of Æthelred and his successor, Edmund, Cnut finally succeeded in conquering the entire kingdom. That much is clear and always has been. Together, the conquests of Sweyn (1013) and Cnut (1016) are referred to as The Danish Conquest.

A Medieval Revenge Tale: Dead Princesses, Avenging Brothers, and Conquest?

However, accounts of the St. Brice’s Day Massacre are usually followed up by a claim that Gunnhild (there are numerous spelling variations), the sister of King Sweyn of Denmark, was among those slain in the massacre. Supposedly her husband Pallig, a Norse mercenary in Æthelred’s service, was also killed. These claims come from William of Malmesbury, writing in the 1100s, and later appeared in countless other medieval and modern sources [2]. According to this story, Sweyn swore revenge on Æthelred and launched the campaign that would eventually topple the English kingdom. It’s a noble tale, one of revenge and retribution, where King Æthelred orders an insane purge of civilians, an innocent Danish princess is killed, and her brother punishes the mad King Æthelred by stealing his crown.

This revenge story is so routinely brought up that it occurs in informal and serious work alike. Wikipedia’s St. Brice’s Day entry, the first place most people will turn when researching the massacre, has this to say about the story of Gunnhild’s death, Sweyn’s reaction, and the massacre’s link to the Danish Conquest (as of 13 November 2020):

Among those thought to have been killed is Gunhilde, who may have been the sister of Sweyn Forkbeard, the King of Denmark… Historians have generally viewed the massacre as a political act which helped to provoke Sweyn’s invasion of 1003… Audrey MacDonald sees it as leading on to the onslaught which eventually led to the accession of Cnut in 1016.

But you know your teachers told you to never trust Wikipedia. More rigorous popular sources like History Today also make the Gunnhild story part of their accounts of St. Brice’s Day: “One of those killed at Oxford, apparently, was Gunnhild, the sister of Swein Forkbeard, which inevitably sharpened the latter’s hostility.” The author’s use of apparently tells me he’s at least a little skeptical of the story, but – perhaps due to a tight word count – that’s all he says about it. Is Richard Cavendish, the author of the piece, on to something? [3] Does the Gunnhild revenge story deserve to be taken at face value, as it so often has been, or will it crumble under scrutiny?

It turns out, Cavendish is far from the only writer to express some doubt over the story. Most academics are highly skeptical that Sweyn’s sister Gunnhild (if she existed) was killed in the massacre, and even more skeptical that the massacre “led to” or “caused” the Danish Conquest, which happened over a decade after St. Brice’s Day.

Nearly all scholars who address this story point out that it doesn’t appear until much later, which is obviously a major strike against it from a historical standpoint. William of Malmesbury was writing over a century later, despite earlier sources saying nothing about Gunnhild’s death or Sweyn’s revenge [4]. Whenever a well-attested historical event grows more and more specific with each retelling, that’s a sign we’re looking at a legend rather than something more straightforward, especially when it starts messing up chronology and contradicting earlier and better sources. But we’ll get to that. This does not mean that William of Malmesbury made the story up himself, nor does it mean he’s necessarily the first person to claim Gunnhild was married to Pallig, just that he is the first to write them down. A late date alone is not insurmountable, so we’ll need to look at some more factors before we dismiss this tale.

Gunnhild and Pallig: Victims of St. Brice’s Day?

The link between St. Brice’s Day and the Danish Conquest, as told by William of Malmesbury, stands or falls based on whether we think Gunnhild and Pallig were victims of the massacre. Without their deaths, William of Malmesbury’s claim – that the conquest was largely prompted by a personal vendetta – has nothing to stand on. However, it’s unclear if Gunnhild even existed. Levi Roach, in his book on Æthelred, tellingly lists Gunnhild in his index as the “(purported) sister of Swein Forkbeard” [5]. Ann Williams, one of the foremost experts on Æthelred’s reign, lists Gunnhild as the “supposed” sister of Sweyn Forkbeard in one of her indexes and provides one of the most thorough dismissals of the tale. She says that “the St Brice’s Day massacre had by this time acquired a crop of half-truths, tales and legends, some of which surface in the writings of those keen to blacken Æthelred’s already grimy reputation.” She also points out just how unclear William of Malmesbury’s chronology is, as he seemingly conflates Sweyn’s invasion of 1003 with his conquest of 1013. Judging by William of Malmesbury’s account, it isn’t even clear whether Pallig died in the massacre of 1002 or the invasion of 1013. Beyond that, Ann Williams sees no reason to make Pallig the husband of the possibly fictional Gunnhild. Based on the ASC, Pallig seems to have escaped before the massacre anyway [6].

Roach likewise points out that no evidence for Gunnhild exists prior to this story [7]. The much earlier ASC also records a near constant litany of assassinations, exiles, ousters, and mutilations ordered by Æthelred, especially against nobles who had betrayed the king. However, Pallig is not one of them. Why would the ASC choose to omit the grisly death of this one particular traitor when it mentions the demise of so many others? The most obvious answer is that Pallig didn’t die in England in 1002 or 1013 but that, like the Chronicle’s entry of 1001 would lead us to believe, he simply rejoined his viking allies and left Æthelred’s service altogether. Pallig aside, we still must reconcile this story with an unclear and muddled sequence of events, no evidence for Gunnhild’s existence before the 12th century, and (understandably) skeptical scholars. The story is beginning to quickly unravel.

For the purposes of this post, that means all the assumptions that follow from this story – that Sweyn wanted revenge and invaded England as a result of his sister’s death – begin to crumble, too. If there is no Gunnhild who was married to Pallig (who did not die at Æthelred’s hands, either), then why should we believe that Sweyn invaded to avenge her? And just as importantly, why the ten-year gap between the invasion of 1003 and Sweyn’s actual conquest in 1013? Perhaps this is why William of Malmesbury conflates the two – he was trying to make sense of the decade-long interruption while still claiming that St. Brice’s Day led to the Danish Conquest. He could either place Æthelred’s overthrow eleven years too early (1003) or place the massacre eleven years too late (1013), neither of which is particularly easy to resolve. As Ann Williams has suggested, maybe the episode of Gunnhild and Pallig being put to death, with all the other Danes, refers to an entirely different event than the St. Brice’s Day Massacre. If we follow this route, we now have two massacres instead of one, which makes William of Malmesbury’s story even more confused. The end result is the same, though, because we’d still have Sweyn launching his conquest to avenge his sister. There are plenty of other bizarre rationalizations one could make here, but I think it would be a fruitless endeavor. At some point, we have to admit that the story is no longer tenable as serious history, and no amount of mental gymnastics can save it.

Here is where I need to pause and clarify something, though. Even if Sweyn’s conquest of 1013 was not motivated by a desire to avenge his sister, the St. Brice’s Day Massacre might have still been a motive for his raids in 1003 [8]. It’s hard to imagine that Sweyn would have shrugged off the news of Æthelred committing genocide against his kinsmen, but this would have been one of many factors that made England attractive as a target. Sweyn would have also been motivated by the possibility of plunder and tribute. He had been raiding in England since the 990s, in any case.

Did St. Brice’s Day Cause the Danish Conquest?

So no, the Gunnhild revenge story does not hold up to scrutiny, and as an after-effect, neither does William of Malmesbury’s insinuation that the Danish Conquest was caused by the St. Brice’s Day Massacre. While plenty of scholars have critiqued the Gunnhild story, when it comes to the direct link between St. Brice’s Day and the Danish Conquest, it’s even worse: most academics don’t even address it, almost certainly because once the Gunnhild story is written off, the Danish Conquest connection, as argued by William of Malmesbury and others, crumbles by default. It’s an engaging legend, but it’s time that more writers (not just academics) start treating it as just that – a legend. Save as an amusing side note or historiography, it has no real purpose in the story of the St. Brice’s Day Massacre, and neither does it have anything substantial to do with the Danish Conquest.  

Medieval Fact Check:

And finally, just for fun, let’s summarize this with a Snopes-style “medieval fact check.” Here in the States, our political fact-checkers have been busier than ever, which is probably why this idea came to me. This is simplistic, sure, but I may do more of these depending on the reception:

The St. Brice’s Day Massacre was ordered by Æthelred II in 1002: Accurate. The ASC provides a very early account that is confirmed by an even earlier charter by Æthelred. There are countless later accounts of the massacre, of course, but these two are by far the earliest and most valuable. This is as rock-solid as they come.

Sweyn had a sister named Gunnhild: Unknown. The source for this is so late that it’s hard to really know with any certainty. In Gunnhild’s favor, I’m not aware of any sources that outright contradict her identity (yes, believe it or not, this does happen with some medieval sources), which is the only thing stopping me from labeling this as “probably inaccurate.”

Pallig was killed in the St. Brice’s Day Massacre: Probably inaccurate. Pallig is mentioned by name in the ASC’s entries for 1001, where he deserts from Æthelred’s service. He reunites with his old viking pals in the entry, but there is no indication that he remained in England. The ASC does not mention him again, even though his death in the massacre (or later) would have been relevant. The ASC records Æthelred killing, ousting, or mutilating other nobles throughout the reign. It does record not him punishing Pallig. Only much later sources say that Pallig was killed in the massacre. It’s far more likely that Pallig rejoined a larger viking force following his treachery.

Gunnhild was killed in the St. Brice’s Day Massacre: Unknown. This is another case of “we don’t know.” Pallig is a bona fide historical figure whose activity is mentioned in the ASC, but Gunnhild remains a total mystery because there are no earlier sources to help verify or contradict the later story.

Sweyn’s invasion of 1003 was prompted by the massacre: Partially accurate. While Sweyn probably wasn’t avenging the death of his (possibly fictional) sister, the massacre would have been one more justification for an invasion. Sweyn’s list of reasons would have been fairly long by this point: England is rich, I could win some tribute, I could gain more prestige, Æthelred is a madman, etc.

The massacre caused or led to the Danish Conquest: Probably inaccurate. While King Sweyn did return to raid England in 1003, England’s most formidable opponent in in late 1000s and early 1010s was not Sweyn, but Thorkell the Tall. Only after Thorkell had considerably weakened England did Sweyn return and conquer it in 1013. The decade-long gap between the massacre and the conquest, with several years where Sweyn wasn’t in England at all, is probably the nail in the coffin for this. Without the Gunnhild story to link the massacre to the conquest, things appear even more farfetched.

Sources and Notes

[1] The Anglo-Saxon Chronicle, edited and translated by Michael Swanton (J.M. Dent, 1998). For this post, I have directly quoted the passage about the massacre in the 1002 annal. The charter is quoted in the footnotes for 1002.

[2] William of Malmesbury: Gesta Regum Anglorum: Volume 1: The History of the English Kings, edited and translated by R.A.B. Mynors, R.M. Thompson, and M. Winterbottom (Oxford: Claredon Press, 1998).  

[3] Richard Cavendish, “The St Brice’s Day Massacre,” History Today 52, no. 11 (2002).

[4] Simon Keynes, The Diplomas of King Æthelred ‘the Unready’: A Study in Their Use as Historical Evidence (Cambridge University Press, 1980), 205.

[5] Levi Roach, Æthelred the Unready (Yale University Press, 2016), index.

[6] Ann Williams, Æthelred the Unready: The Ill-Counseled King (Hambledon and London, 2003), 53-54, index.

[7] Roach, 200.

[8] Roach, 201.

Vice Presidents Who Became President: VP to President History and Trivia

Joseph R. Biden Jr. has just been elected as the 46th President of the United States. Although Biden served in the Senate for 36 years, he is perhaps best known as Barack Obama’s Vice President from 2009-17. Biden will become the first former VP elected to the presidency in 32 years. The last time this occurred was in the 1988 election, when George H.W. Bush became president after serving as VP under Ronald Reagan from 1981-89. Biden will also become the first challenger to defeat an incumbent president since Bill Clinton bested Bush in the 1992 election. Even though it’s been decades since a former VP was elected president, there have been many former VPs who became US president. In fact, it’s one of the most common routes to the presidency. Let’s take a look at the 15 men who became President of the United States after being Vice President.


John Adams – Adams was the first Vice President in US history, serving under George Washington from 1789-97. He was President for one full term (1797-1801). Confusingly, at this time, the runner-up of the presidential election became the new VP, meaning that Adams became VP because he was the second most popular candidate after Washington. This also meant that when Adams finally became president, his toughest opponent, Thomas Jefferson, served as his VP. If this rule were still in effect today, it would mean that Donald Trump’s VP would be Hillary Clinton. Because of this rule, Adams also became the only president to be defeated by his own VP, losing to Thomas Jefferson in the 1800 election. The 1800 election is more significant for other reasons, though: it represented the first peaceful transfer of power in US history (Washington did not seek re-election after his second term). The “runner-up rule” for VP was discarded in 1804.


Thomas Jefferson – Jefferson is the only former VP to serve two full terms as president (1801-09), and the only one to directly defeat the president he had served under. Following the precedent set by George Washington, Jefferson declined to seek a third term. He is best known for the Louisiana Purchase, which exponentially expanded the size of the nation. Jefferson didn’t just expand the size of the country, though; he also greatly expanded the power of the president despite being a small-government advocate.


Martin Van Buren – Van Buren was VP during Andrew Jackson’s second term (1833-37). By this point, VPs were no longer the runners-up of the previous election, meaning Van Buren was Jackson’s ally, not his opponent. After Jackson declined to seek a third term, Van Buren was nominated for the presidency and served one full term (1837-41); following a catastrophic economic mess that Jackson had left behind, Van Buren was defeated by William Henry Harrison in the 1840 election.


John Tyler – Tyler served the remainder of William Henry Harrison’s term (1841-45) after Harrison’s death. His 31 day term as VP is the shortest in US history, just as Harrison’s 31 day term as president is the shortest in US history. After becoming president, Tyler was ousted by his own party, the Whigs, and was not nominated for another term (turns out it’s pretty hard to get nominated when you don’t have any party affiliation). Despite his unpopularity, Tyler established the precedent that if a president dies, the VP becomes full, legitimate president – not just an “interim” or “acting” president. While this this rule is second nature to us today, when Harrison died, it was entirely unclear what would happen next. Was Tyler a fully legitimate president? Was he a placeholder? Should there be a special election? Tyler’s staunch refusal to be known as “acting president,” and his insistence on serving the rest of Harrison’s term, set the tone for all future presidential successions.


Millard Fillmore – Fillmore served the remainder of Zachary Taylor’s term (1850-53) after Taylor’s death. Fillmore was a hardworking and intelligent self-made man, but many expected that he would be a weak president. Fillmore proved everyone wrong by firing Taylor’s entire cabinet and vehemently pursuing the Compromise of 1850. Fillmore’s independent streak did not win him many supporters, though, and he was not nominated for his own term. He was the final Whig president. He would later be nominated for president by obscure, minor parties, but was never again a serious contender for the presidency. Honest and reflective to a fault, Fillmore once famously declined an honorary doctorate from the University of Oxford, claiming he didn’t deserve the degree because he couldn’t read the Latin on the diploma.

Millard Fillmore


Andrew Johnson – Johnson served the remainder of Abraham Lincoln’s term (1865-69) after Lincoln’s assassination. As VP, he held the unusual distinction of belonging to a different political party (Democratic) than his president (Republican), something that had not happened since the earliest days of the presidency. This was because Johnson had not joined the Confederacy and Lincoln wanted to present the image of unity by running with a southerner. As president, Johnson was deeply unpopular as a Democrat up against the Radical Republicans of Congress. He was impeached and was not nominated for another term.


Chester A. Arthur – A former machine politician, Arthur served the remainder of James Garfield’s term (1881-85) after Garfield’s assassination. Although many feared that Arthur’s administration would be corrupt, Arthur won widespread admiration for his efforts to end machine politics – the very system that had elevated him to power. Although Arthur had pleasantly surprised nearly everyone with his honesty, he was not viewed as a strong candidate for reelection. Arthur himself did not actively seek reelection, probably due to failing health, and was not nominated for another term. He died the following year.

Chester A. Arthur


Theodore Roosevelt – Roosevelt served the remainder of William McKinley’s term after McKinley’s assassination in 1901. At age 42, he is the youngest person to ever become president (this distinction is commonly given, inaccurately, to John F. Kennedy. Kennedy is the youngest to be elected president). In the 1904 election, TR became the first person to be nominated for another term after succeeding a president who had died in office: Tyler, Fillmore, Johnson, and Arthur had all failed to do this. He won the election, also becoming the first of that group to win a term in his own right. In all, TR served as president from 1901-09. Although Roosevelt had initially declined to seek a third term, he broke with tradition by running again in the 1912 election after being disappointed with the performance of his chosen successor, William H. Taft. Taft and Roosevelt both lost to Woodrow Wilson.


Calvin Coolidge – A poster-child for fiscally conservative, laissez-faire government, Coolidge served the remainder of Warren Harding’s term (1923-25) after Harding’s death. Like Roosevelt, Coolidge was nominated for another term and won, overseeing most of the Roaring Twenties, but from a very comfortable distance, of course. In total, Coolidge served as president from 1923-29, conveniently leaving office just before the stock market crash of 1929 that doomed his successor, Herbert Hoover.


Harry S. Truman – Truman was the third VP to serve under Franklin D. Roosevelt. Following Roosevelt’s death in 1945, Truman served the remainder of Roosevelt’s fourth term (1945-49). He was nominated for president in 1948, when he executed a historic come-from-behind victory and served his own full term from 1949-53. The 22nd Amendment was passed during Truman’s second term, which prevented any president from serving more than two full terms – a four-term presidency like FDR’s would never happen again. The amendment also stipulated that if a VP became president and served more than 2 years of his predecessor’s term, he would be eligible to run for another term, but not for a third. Confusingly, this rule did not apply to Truman; he was grandfathered in, meaning Truman actually was eligible to seek a third term. He considered running again, but ultimately decided not to. The atomic-bomb-dropping president remains an icon in my hometown, even lending his name to our major league sports complex.


Lyndon B. Johnson – Johnson became president after John F. Kennedy’s assassination in 1963, serving the remainder of Kennedy’s term (1963-65). Johnson was nominated for his own term and won, serving as president from 1963-69 in total. Because Johnson had served fewer than two years of Kennedy’s term, he was eligible for the 1968 election. Initially he tried to secure the nomination for another term, but soon withdrew, probably due to a myriad of factors: civil unrest at home, an unpopular war abroad, and declining health. Had Johnson run again and won, he would have lived through his final term by just two days.


Richard Nixon – Nixon had served as VP under Dwight Eisenhower from 1953-61, meaning he was actually VP before Johnson and could technically be placed earlier on this list. However, I’ve placed him after Johnson since he became president later. After serving for two terms as VP under Eisenhower, Nixon ran for president in the 1960 election, losing to Kennedy. Nixon finally won his bid for president in the 1968 election. The eight year gap between his vice presidency (ended 1961) and presidency (began 1969) is the longest of anyone on this list. Nixon was re-elected in a landslide in the 1972 election, but his second term was marred by the Watergate scandal. Facing possible impeachment, Nixon resigned in 1974. He is the only president to resign.


Gerald Ford – Ford is one of the most unusual cases in presidential and vice presidential history. Before Nixon resigned in 1974, his vice president, Spiro Agnew, was caught up in scandals of his own and resigned. Nixon appointed Ford to replace Agnew, which became highly significant when Nixon himself decided to resign. As VP, Ford ascended to the presidency and served the remainder of Nixon’s second term (1974-77). This means that Ford is the only person to serve as US president without being elected to the office in any capacity – not even as vice president. He was nominated for his own term in the 1976 election, but lost to Jimmy Carter. His term is the shortest in US history among presidents who did not die in office. Ford was also the third straight president who had previously served as VP, following Johnson and Nixon.


George H.W. Bush – The senior president Bush had been Ronald Reagan’s VP from 1981-89 and won his own term as president in the 1988 election. He became the first incumbent VP to succeed to the presidency by election (not by death or resignation) since Van Buren succeeded Jackson in 1837. Despite historically high popularity following the lopsided outcome of the Gulf War, Bush ultimately lost his bid for reelection to Bill Clinton. Bush’s son of the same name served as president from 2001-09.


Joe Biden – 32 years after George H.W. Bush became president, we will have a former VP as president. Biden, a long-serving senator and former VP, has just been elected the 46th president of the United States. Biden began his political career in the early 1970s and it’s been a long road to the top. He served 36 years in the Senate, making serious bids for the presidency in 1988 and 2008. He was chosen as Barack Obama’s VP, serving in that capacity from 2009-17. Although he was frequently floated as a possible candidate for president in the 2016 election, much like how Bush had succeeded Reagan, Biden decided not to run. In 2020, he defeated President Trump and is set to become the 46th president on January 20, 2021. Biden will be the oldest president at the time of his inauguration – he will be 78 years old on January 20, 2021, easily surpassing Trump (70), Reagan (69), and Harrison (68). He will also be the oldest US president in any capacity, as Reagan was 77 when he left office and Trump will be 74. Biden’s vice president-elect, Kamala Harris, will set several records in her own right. She will be the first female VP, the first African-American VP, and the first Indian-American VP in US history. She will be the first VP with significant non-European ancestry since Charles Curtis, the Native American who was Hoover’s VP and came from the Kaw Tribe in Kansas.

VP-to-President Trivia and Records:

Two of the four presidents depicted on Mt. Rushmore are former VPs (Jefferson and Theodore Roosevelt).

Longest streak of presidents who had served as VP: 3 (Johnson, Nixon, Ford, 1963-1977)

Youngest former VP to become president: Theodore Roosevelt, 42

Oldest former VP to become president: Joe Biden, 78 (Biden turns 78 on November 20, 2020 and is set to be sworn in as 46th president on January 20, 2021)

First former VP to become president: John Adams, 1797

Latest former VP to become president: Joe Biden (set for 2021), previously George H.W. Bush (1989)

Longest time between presidents who had been VP: 28 years (1809-1837, 1993-2021)

Only former VP to serve two full terms as president: Thomas Jefferson

VPs who became president due to their predecessor’s death: John Tyler, Millard Fillmore, Andrew Johnson, Chester A. Arthur, Theodore Roosevelt, Calvin Coolidge, Harry Truman, Lyndon B. Johnson

Presidents with VP experience who were not nominated for another term: John Tyler, Millard Fillmore, Andrew Johnson, Chester A. Arthur

Presidents with VP experience who won terms in their own right: John Adams, Thomas Jefferson, Martin Van Buren, Theodore Roosevelt, Calvin Coolidge, Harry Truman, Lyndon Johnson, George H.W. Bush, Joe Biden

Only VP to become president due to their predecessor’s resignation: Gerald Ford

Presidents with VP experience whose children became president: John Adams (John Quincy Adams), George H.W. Bush (George W. Bush)

Longest gap between vice presidency and presidency: Richard Nixon, 8 years

Incumbent vice presidents who were elected president: Martin Van Buren (1836 election), George H.W. Bush (1988 election)

Presidents with VP experience who were impeached: Andrew Johnson (Richard Nixon resigned before he could be impeached)

Presidents who had served as VP under the “runner-up rule”: John Adams, Thomas Jefferson

Only president to be defeated by his own VP: John Adams, defeated by Thomas Jefferson

Presidents who had been VP for a president of another party: Thomas Jefferson (a Democratic-Republican under Federalist John Adams), Andrew Johnson (a Democrat under Republican Abraham Lincoln)

Presidents with VP experience who had no political party: John Tyler (expelled from Whig Party)

Best Facial Hair Among VPs who Became President: Chester A. Arthur, and you cannot convince me otherwise.

Best Facial Hair: Chester A. Arthur

Rex Factor Interview

Image credit: Rex Factor. Æthelred the Unready appears on the Rex Factor banner (25 July 2020).

On July 25th, I appeared on Rex Factor to discuss the military career of Æthelred the Unready. Rex Factor is a long-running podcast that discusses medieval history in a light-hearted manner, assigning monarchs and consorts marks according to battleyness (military prowess), scandal (how shocking and mischievous a monarch is – the juicier, the better!), dynasty (how many children they had), longevity (years on the throne), and subjectivity (would you want to be a subject during the reign of this monarch?).

Ten years ago, Æthelred received a battleyness score of 0/20. Co-hosts Graham Duke and Ali Hood invited me onto the podcast to see if that battleyness score needed to be revised. Will I succeed in getting Æthelred the Unready on the scoreboard? And if so, what will he score? With an original score of 0/20, I clearly have my work cut out for me!

Listen to the podcast here.

The Worst U2 Album? Looking Back at 1997’s “Pop”

I’m no U2 aficionado, but like anyone with ears, I’ve absorbed my share of U2 by osmosis. It’s impossible not to. Turns out, though, there was an entire album worth of U2 songs I’d never heard before. Unless you were paying close attention in 1997, you might not have heard it, either. That album is called Pop and its disappearance from popular culture (ironic, I know) might be intentional. It’s one of the few U2 albums that was truly polarizing, with the band itself largely abandoning it after a poorly-received supporting tour and mixed album reviews. 

I recently discovered this album by accident. I was watching a highlight reel for long-forgotten NFL quarterback Chris Chandler (don’t ask) and the backing song was a trippy dance track called “Do You Feel Loved.” I was hooked. Upon looking the song up, I was stunned that it was by U2. I had to listen to the rest of the album. Was “Do You Feel Loved” a fluke, just a change-of-pace track amidst an ordinary U2 record? Or was there something more to this?

So let’s head back to 1997 and find out.

Background

For U2, Pop was part of a wider period of experimentation that spanned roughly the entire 1990s. The band had entered the decade with a chip on their shoulders after 1988’s Rattle and Hum had been widely criticized, taking more risks on 1991’s Achtung Baby and 1993’s Zooropa, both of which were well-received. Pop built upon those earlier albums and continued the band’s foray into alt rock, grunge, electronic music, and dance. 

Pop was in progress from 1995 up until its release in March 1997. It had been slated for release in late 1996, but the band needed more time. When the album rolled out in early 1997, everything that could go wrong did go wrong. Not only did U2 feel like they’d had to rush the album (and thus felt like it was an unfinished product), but that time crunch also cut into their rehearsal time. The resulting “PopMart” tour suffered, with the band struggling in early performances due to lack of practice (the tour had been scheduled before the album was finished). 

Aftermath

Several of the album’s songs were abandoned after just a few lackluster live performances, including the aforementioned “Do You Feel Loved.” U2 continued tinkering with the tracks into the 2000s, and some later releases of Pop’s songs were heavily reworked, again hinting that the band wasn’t kidding when they said they felt Pop was unfinished. A Pitchfork review of How to Dismantle an Atomic Bomb (U2’s 2004 album) went so far as to look back on Pop as a “disastrous” record.  

Today, some U2 fans regard this entire 1990s period as a dark age (with Pop as the worst of the bunch), preferring the classic 1980s U2 sound. Others feel like this was the last era in which the band took real risks, aside from that time in 2014 when they forcibly put their latest album onto your smartphone. Anyway, as for U2 in the 1990s, I don’t have much of an opinion yet. As I said above, I’m not a U2 expert by any stretch of the imagination. But enough of that — let’s move onto the album itself.

The Good

Pop comes out swinging, proving to me that “Do You Feel Loved” was not merely a change-of-pace track on a bland album. The first track and lead single is “Discothèque.” It sounds exactly like you’d imagine for a song called “Discothèque.” Très chic. It’s a groovy European dance song with some very funky — and obnoxious — vocals: “You just can’t get enough of that lovey-dovey stuff.” I’m actually good, thanks. Some of the vocals sound like Fred Schneider from the B-52s talk-singing his way through the song, so it’s kind of love it or hate it. But that guitar riff is damn catchy, and near the end, Bono starts to become recognizable as himself. 

“Do You Feel Loved” and “Mofo” are the album’s other dance tracks: the former is my favorite song on the album, featuring heavily-distorted guitar loops riding confidently atop the bassline, all wrapped up in aggressively sexual lyrics. I’m frankly just shocked this is U2. “Mofo” sounds like it could be the theme to an action movie, sounding more like Moby’s “Extreme Ways” for Jason Bourne than “Sunday Bloody Sunday” (update: turns out that two members of U2, Adam Clayton and Larry Mullen, Jr.,  were responsible for the 1996 Mission Impossible theme. That explains things). “Do You Feel Loved” and “Mofo” are one hell of a one-two punch sitting in the 2 and 3 spots, respectively.

Other highlights include “Last Night on Earth.” It’s a little grungy at times, but overall, it sounds more like traditional U2, especially when you listen closely to the philanthropic lyrics (“You gotta give it away! / You gotta give it away!”). Nothing too challenging there, but this later part still gives me goosebumps, even after several listens: “She hasn’t been to bed in a week / she’ll be dead soon / then she’ll sleep.” Say what you want about Bono, but sometimes he manages to capture a feeling that resonates with even the most cynical listener. It’s an ability he frequently overplays, but it works well on “Last Night on Earth.” 

The 60s-tinged “Staring at the Sun,” which is clearly Beatles influenced, is another highlight. Other bands playing with this sound in the late 1990s include Fastball (listen to their albums, not just the singles, to see what I’m talking about) and Oasis (no explanation needed). Another weird fact about this song: in 2005, Gorillaz achieved a bona-fide hit with “Feel Good Inc.” which — unintentionally or otherwise — borrowed the “Windmill, windmill for the land / Turn forever hand in hand” melody from this song. It’s almost identical and has accordingly spawned numerous crappy YouTube mashups. This quick, no-frills comparison is helpful, though. I had no idea “Feel Good Inc.” had anything in common with an old U2 song, but there you go.

The piano and falsetto-laden “Gone” is another good one, as is “Please.” In fact, I would be willing to put “Please” up against “Do You Feel Loved” as the best song of the album, but for entirely different reasons. Whereas “Do You Feel Loved” is catchy, punchy, and lyrically aggressive, with “Please,” the sense of desperation sells it. Like “Sunday Bloody Sunday,” it’s pretty obviously about The Troubles. As easy as it would be to think U2 was trying to capitalize off something that helped make them famous, this song is so genuine, so earnest, that I can’t help but feel it’s sincere. I know that writers often use that word, earnest, as a backhanded compliment for sappy songs, but I don’t mean it that way at all. It’s not sappy. It’s really well done:

You had to win.

You couldn’t just pass.

The smartest ass

at the top of the class.

Your flying colors,

your family tree,

and all your lessons in history.

“Please” by U2

The Not-so-Good

But before you think this is all going to be positive, there are misses. The weird spoken-word/drum loop combo in “Miami” doesn’t work. It’s just grating. If you’re willing to suffer through the first four minutes, there’s a surprise near the end, though. Ever wanted to hear Bono scream like a hair metal rocker? No? Well, if you change your mind, listen to the end of “Miami” on the Pop album. 

“The Playboy Mansion” might be even worse. There are snarky references to plastic surgery, Big Macs, Michael Jackson, and O.J. Simpson. It’s a product of its time if there ever was one. It’s like a parody of a Don Henley song. It hasn’t aged well. 

“If God Will Send His Angels” is more boring than outright bad — there’s talk of Jesus, Christmas, and country songs (actually, you know what? That does sound pretty bad when I write it out). It’s a clear outlier in an otherwise risky album, almost like it was carefully calculated to be released as a single and climb the charts just before Christmas. As a matter of fact, it was released as a single in December 1997. Hmm… 

The Verdict

Even though Pop is a black sheep, there are still a few hints that this is a U2 album: The Troubles, a wistful Christmas song, and religious metaphors that are as frequent as they are heavy-handed. You can almost see the smirk on Bono’s face as he writes some of these lines. 

But there are a lot of risks here, and overall, Pop lands more punches than it misses. The one thing I don’t get is the title. Pop? This is a bizarre fusion of dance, electronica, grunge, and traditional U2. So don’t be fooled by the title. There’s a lot more going on here than in your regular, generic pop album. 

So does Pop deserve its ridicule and obscurity? In my mind, not really. This is an expensive, gutsy, and complicated record full of ups, downs, and everything in between. It doesn’t always work, but it’s rarely uninteresting, and there are plenty of gems buried in this forgotten release.  

Album breakdown

1-3: The Dance Tracks

4: A Christmas Song

5-7: Some Good Stuff

8-9: Stinkers

10-12: More Good Stuff