Pickled monarch

I’m currently a little over a hundred pages into Andrew Roberts’s 700+ page The Last King of America: The Misunderstood Reign of George III. It’s excellent so far, and full of surprises. Here’s one.

This is the twenty-year old George, Prince of Wales writing to his tutor and “dearest friend,” John Stuart, 3rd Earl of Bute in 1758:

What a pretty pickle I should be in a future day if I had not your sagacious counsels.

To “be in a pickle” is not an expression I would have imagined being current in the 1730s, so it surprised to me both 1) that the expression is so old and also 2) that it’s survived to the present. Most such casual idioms go stale pretty quickly—and the more specific they are the more so. I don’t imagine much of anything written nowadays will be intelligible by the end of the century.

But notice that what I at first took to be an oddity of grammatical structure actually suggests the idiom has changed a bit: George says “what a pretty pickle I should be,” not “I should be in.” I can’t be certain that this isn’t just a twenty-year old expressing himself imprecisely (though the volume, style, and erudition of George’s letters suggests otherwise), but if not, the idiom as used by George makes himself the pickle. And in this period, the pickle could be either something soaked in brine or something served up covered in a particular salty sauce. Here’s the Online Etymology Dictionary:

The meaning “cucumber preserved in pickle” first recorded 1707, via use of the word for the salty liquid in which meat, etc. was preserved (c. 1500). Colloquial figurative sense of “a sorry plight, a state or condition of difficulty or disorder” is recorded by 1560s, from the time when the word still meant a sauce served on meat about to be eaten.

Served up garnished and ready to eat—an altogether more precarious image than even that suggested by our continued use of the phrase, and one appropriate to the situation George found himself in following the death of his father but before the death of his hostile and mean-spirited grandfather. At any rate, this figurative sense is much older than the more specific meaning of a pickled cucumber, a usage that was still pretty recent in George’s youth. Presumably, to be “in a pickle,” in which you are the hapless victim of a bad situation, is a mutation based on the baseball/tag game.

Another odd example—from the infinite and labyrinthine cellars and archival storage closets of English—of what makes even seemingly unexceptional aspects of the language fun and diverting.

I wrote about Roberts’s approach to history about a year ago. You can read that here.

Addendum: Speaking of historical oddities and surprises, here’s an offhand observation and ironic note from the very first chapter:

The Prince and Princess of Wales’s Court was a close-knit group that made its own amusements. In 1748, Lady Hervey noted that the young Prince George and the other royal children were playing ‘at baseball, a play all who are or have been schoolboys are well acquainted with.’ She added that ‘the ladies as well as the gentlemen join in this amusement.’ It was a form of rounders that later became popular in America—a game that, ironically, George III played but George Washington did not.

Poe, seashells, and measures of success

I get monthly e-mails from Clemson’s dissertation and thesis service reporting new downloads of my master’s thesis. There are a few dozen every month, which I’ve always found kind of interesting. I’ve even, out of curiosity, turned up blog reviews of that paper online. It’s gratifying to know that all that research is of interest to someone and that people are learning from it. I know I did.

But what I realized at some point in the last year is that all those downloads make my master’s thesis probably—excluding a handful of blog posts that have found their way pretty high into Google’s algorithm—the most widely read thing I’ve ever written. Downloads of that paper outstrip sales of my best-selling novel by a factor of ten.

This doesn’t bother me, by any means—I just find it curious, and even amusing. I certainly don’t think about that thesis as often as I think about my novels and plans for future ones. But it has gotten me thinking about how you measure your own success.

So I was interested to learn from The Reason for the Darkness of the Night, the Edgar Allan Poe biography I referred to last month and hope to review when I get some time, that Poe’s bestselling book in his lifetime, and his only book to get a second edition in his lifetime, was… The Conchologist’s First Book, an introductory textbook on molluscs for which he received no royalties.

If this annoyed or discouraged Poe, there’s no evidence of it. Which points to one of his strengths, even when doing hack work as a writer-for-hire—simply plugging away at the work, moving on to the next project.

While The Conchologist’s First Book has an interesting genesis (read The Reason for the Darkness of the Night for an account of how Poe came to translate/compile/write this book) and Poe actually ended up making serious contributions to the emerging field of conchology, the book is largely forgotten today. When I looked it up on Project Gutenberg I was only the 28th person to download it in the last thirty days. For comparison’s sake, the second volume of the Works of Edgar Allan Poe got nearly 8400 downloads in the same timeframe.

You might not be immediately popular for the work you care most about, but you might end up remembered for the work you do. Food for thought.

“The Tell-Tale Heart” on City of Man Podcast

I’m excited to have hosted City of Man for the Christian Humanist Radio Network’s annual Halloween crossover again. This year the shows are all covering selected stories by Edgar Allan Poe. On this episode of City of Man, David Grubbs, Mathew Block and I discuss the story that began my own lifelong love of Poe’s work, “The Tell-Tale Heart.”

We discuss Poe’s life and work overall, the tragedy that dogged him for forty years, the story itself, the immense craft put into it, how it compares to a similar story from Poe’s corpus, and whether “The Tell-Tale Heart” really deserves its lofty spot in the canon of American short fiction.

N.b.: early in the episode, when I say Poe picked a fight with Nathaniel Hawthorne, I mean Henry Wadsworth Longfellow. Poe would have my hide for that.

This was a great discussion of a great story and I’ve had a good time listening to it again. I hope y’all enjoy, and that you’ll check out some of the resources we recommend at the end.

You can listen to this episode of City of Man on iTunes, Stitcher, or other fine podcasting platforms. Give City of Man a visit at the show’s Facebook page or the Christian Humanist Radio Network’s main site. Be sure to subscribe to the show—and the other shows on the CHRN—so you can catch up on previous episodes and won’t miss future episodes. Coyle’s a hardworking guy and has made City of Man one of the best shows in my podcast feed, and I’m grateful that he asked me to host the crossover again this year.

Thanks for listening!

Dune

Paul AtreiDes (timotheé Chalamet) and Lady Jessica (Reb Ferguson) encounter a sand worm by night

Paul AtreiDes (timotheé Chalamet) and Lady Jessica (Rebecca Ferguson) encounter a sandworm by night in Denis Villeneuve’s Dune

Here’s a movie review I didn’t expect to write. I read Frank Herbert’s novel Dune a few years ago, and while I enjoyed it and it impressed me with its mass of involving detail, I honestly didn’t see what all the fuss was about. When news of Denis Villeneuve’s film adaptation arrived, I was interested—I’ve liked all of Villeneuve’s movies that I’ve seen so far, especially Sicario—but not at all eager. I’d catch it eventually.

Fortunately for me, a good friend insisted we see it at the first available opportunity, and in IMAX. That was last night. Here I am the morning after to tell you to go see it.

Dune depicts the travails of House Atreides, a noble family in a galactic empire 8,000 years from now. The Atreides have been mortal foes of House Harkonnen, a family of sybaritic grotesques who combine love of power with ruthless self-interest. As Dune begins, we learn that the Atreides, led by Duke Leto (Oscar Isaac), have just been given the planet of Arrakis in fief by the emperor, ousting the Harkonnens after generations of monopoly control of the planet and its single valuable resource—spice, a substance with medicinal and hallucinogenic properties that also enables intergalactic space flight. Leto and his wife, Lady Jessica (Rebecca Ferguson) and son Paul (Timothée Chalamet) are unhappy with the move but answer the emperor’s call.

Arrakis is an all-desert planet, hot, inhospitable, and lethal without careful and precisely calibrated technological controls in place. Not only its climate but its native life post a threat, specifically the Fremen, hostile tribal bands that have somehow found a way to eke out a living in the desert, and—towering above all in size and significance, and the source and guardian of the precious spice—the sandworms. Leto’s task now, as the newly appointed lord of Arrakis, is to harvest the spice, defend the harvesters from the sandworms, and defend everything from the attacks of the Fremen. His solution is to adapt his noble family’s traditional techniques to a new environment—rather than the air and sea power they enjoyed on their homeworld, they will develop desert power by gaining the trust of the much-abused Fremen and allying with them.

But despite their best efforts, the Atreides and their followers catch on quickly that they’ve been presented with an unmanageable situation, trying to meet quotas with outdated and poorly maintained equipment and with assassins secreted in the walls of their palace. The Harkonnens have a long reach and clearly want Arrakis back, and, worse, it appears the Emperor is on their side, having set the Atreides up to fail and provide a pretext for a Harkonnen strike. The clash that comes midway through the movie is the beginning of a breakneck series of attacks, flights, and attempts merely to survive that culminates in Paul’s duel to the death with a Fremen challenger.

Does that sound like a lot? It’s the simplest I could make it, and my summary still obscures the fact that it is Paul, the teenaged scion of House Atreides, who is the main character. There is also the forbidding all-female Bene Gesserit cult to which Lady Jessica belongs, a sort of Goddess Illuminati manipulating the noble houses of the empire according to plans of their own; a band of savage imperial mercenaries hired on by the Harkonnens; and Arrakis’s resident ecologist, who is legally obligated to remain a neutral functionary of the empire but chooses to take sides.

And more. And more. And more.

That’s the greatest accomplishment of Villeneuve’s Dune—taking a vast world of intricate politics, religion, trade, ecology, and mythology and making it comprehensible. I had to explain all of that background. In the film, most of it is shown; we pick up on it just by watching, the way movies are supposed to work. While in a few places the filmmakers do cave and have a video lecture instruct Paul directly on particular aspects of Arrakis’s zoology or culture, those places are few and far between. Furthermore, even as we’re learning about this strange, fantastical, and complicated world through the first half, the story keeps moving. This is a two-and-a-half hour movie that, despite the weight of weird information it has to convey, never slows down and goes by in a flash.

It’s also well-cast and acted, with an especially strong supporting cast. My favorites among those were Jason Momoa as Duncan Idaho, Paul’s tutor in the arts of war, and Javier Bardem as the weary but canny Fremen leader Stilgar. Stellan Skarsgard’s obese voluptuary Vladimir Harkonnen is legitimately scary and revolting, a hard combination to pull off. (Near the end I told a buddy in the theater with me that if we got one more scene with the Harkonnens I just might puke.)

Furthermore, the leads are all very good. Oscar Isaac and Rebecca Ferguson, one of my favorite actresses, are excellent as an oddly matched pair of nobles united by their love and duty toward their son. And Timothée Chalamet, an actor I’ve never, ever liked in anything I’ve seen him in (recall that he gave us a “punchable” Henry V in The King), is outstanding here—naively eager, devotedly learning from his father and tutors (when was the last time you saw a kid learning from his elders in a movie?), and rising to the occasion when the crucial moment arrives. He was very good, buoyed by a terrific supporting cast, and actually made Paul more likeable, to me, than the cipher in the book.

Dune is also technically brilliant, with a rich variety of exotic but believable sets, amazing but not impractical costumes and props, and an attention to detail, protocol, and ritual in the way the characters interact that made this feel like a real, lived-in, limitless world. Herbert’s novel accomplished this total immersion cumulatively—by the time you reach the end, the wealth of detail and brilliantly evoked locations and events make you feel like you’ve spent years in this fictional world. The film accomplishes this through texture. All of its visuals are brilliantly tactile. It all feels so real and so right that, near the end, I had grown intolerably thirsty, felt like I had grit in my clothes, and had a nagging worry about inhaling the spice that drifts sparkling through the frame whenever the characters enter the desert. I haven’t felt this physically involved in a movie’s images since Saving Private Ryan.

If I have any complaints, they’re relatively minor. The film is heavily frontloaded with exposition, but gets moving immediately and levels out in the first ten minutes. Zendaya felt out of place as Chani, the Fremen girl Paul has visions and dreams of. She works well enough as the subject of a vision or dream, staring ethereally at Paul just before he wakes, but once she arrives in the flesh her line delivery sounded stiff and forced. Hopefully she’ll be better in the sequel. Also, while the movie looks stunning and is mostly well-shot, night-time scenes near the end are entirely too gloomily lit by cinematographer Greig Fraser, with faces sometimes entirely in shadow and the iconic sandworm in one scene (see the screenshot above) hard to make out. I had a hard time even telling who was who in one crucial scene.

I’ve also heard one complaint elsewhere that I’ll push back on. The title card at the beginning of the movie reads, pointedly, Dune: Part One. The movie gets us about halfway through the book. At least one critic has complained of the abruptness of the ending, but I actually found the place and the moment in the story where the filmmakers chose to leave off appropriate and satisfying, a natural break in the story. I certainly left looking forward to part two.

There’s much more I could point out—the excellent score by Hans Zimmer; the eerie sound design; the skillful use of IMAX for particular scenes; the stunning real life locations, including Jordanian desert where parts of Lawrence of Arabia were also shot—but what I intended as a short review has gotten long enough. (Addendum: I will also point out that, if intense, Dune is refreshingly clean. This is a brand new sci-fi epic you could watch with your kids.)

Dune is a well-crafted, well-acted, thoughtful, and exciting movie that takes place in a fantastical but grounded and believable world, and takes its time to tell a story and tell it well. And not only that, but the characters, plot, and themes all have substance. That makes a film like Dune vanishingly rare nowadays, and I was heartened not only to be surprised by it, but to watch it in a theatre full of other people who also clearly enjoyed it. Whether you’re an old fan of the books or just like good movies, Dune is well worth your time.

Learning the wrong lessons from architecture

Twitter used to have an occasional trending hashtag inviting people to “confess your unpopular opinion.” Here’s one of mine, offered as a follow-up thought to yesterday’s post on traditional vs. modern architecture.

In the City Journal piece I linked to and quoted from, Catesby Leigh writes:

All three branches of the federal government are headquartered in classical buildings: the U.S. Capitol, the White House, and the Supreme Court. Apart from a three-decade interlude of eclectic Victorian confusion between the Civil War and the mid-1890s, classicism predominated from the Founding until World War II. And it has served the nation brilliantly, defining civic architecture in the public mind.

Later:

Jefferson, good lawyer that he was, was won over by the artistic significance, as authoritative precedents, of ancient buildings—especially the Pantheon, perhaps the Roman Empire’s most influential architectural landmark, and also a gorgeous Roman temple in the southern French city of Nîmes on which he modeled his Virginia Capitol in Richmond. (“Here I am, Madam, gazing whole hours at the [Nîmes temple], like a lover at his mistress,” Jefferson wrote to a Parisian lady while serving as the American minister to France.)

Architecture, and classical architecture in particular, is a language—with vocabulary, syntax, multiple styles, and even regional dialects—and language is an instrument of adornment, narration, declaration—and instruction.

Me, personally, I’m a half-timber and gothic man (with a serious soft spot for traditional Southern farmhouses), and I also love and adore classical architecture for all the reasons I laid out yesterday. But precisely on the grounds that architecture, Goethe’s “frozen music,” silently instructs, I think housing the three branches of the federal government in what we instinctually recognize as temples has been a mistake.

And it is a typically Jeffersonian and American mistake—to think you can mimic sacred architecture without the ghost of an overawing polytheism hanging around, to think you can rationalistically borrow form without keeping the meaning. We intuitively know when we’re in sacred space, and I think two centuries of Americans have learned the wrong lesson from this architecture. Witness the overtly religious rhetoric denouncing the January 6th riot. And don’t get me started on this literal temple to an all-powerful god, colossal enthroned idol and all.

A small point, but not an unimportant one.

Modern architecture—there to be demolished

From the late Sir Roger Scruton’s documentary “Why Beauty Matters,” which I wrote about last year:

When the public began to react against the brutal concrete style of the 1960s, architects simply replaced it with a new kind of junk: glass walls hung on steel frames, with absurd details that don’t match. The result is another kind of failure to fit. It is there simply to be demolished.

You can watch this illustrated with depressing simplicity in this short video on YouTube.

Two recent articles on the topic:

This longish piece by art and architecture critic Catesby Leigh takes Donald Trump’s lame duck mandate of classicism as “the preferred and default style” for federal architecture, especially in DC, as a jumping off point. Leigh then examines a flap over architectural style at the University of Virginia that, years before, prefigured the dustup over Trump’s reform. Leigh strikingly compares the self-consciously “exogenous” and “visually abrasive” modernist buildings at UVA—and many, many other places—with classical architecture, noting that while the classical “is not a ‘style’” properly speaking,

It is a visual language of enduring, objective forms wedded to a coherent syntax, a language whose flexibility has permitted stylistic variations in federal architecture ranging from Palladian classicism to art deco. Classical buildings are composed in a manner analogous to the human body, with an organic hierarchy of parts comprising a legible, resonant whole. We are instinctively drawn to such buildings. The same cannot be said of modernist architecture’s dehumanized forms.

From Scruton again (beginning at 49:27 here):

The same kind of criticism [of classical, representational art] is aimed at traditionalists in architecture. One target is Leon Krier, architect of the Prince of Wales’s model town of Poundbury. Designing modest streets, laid out in traditional ways, using the well-tried and much-loved details that have served us down the centuries, Leon Krier has created a genuine settlement. The proportions are human proportions. The details are restful to the eye. This is not great or original architecture, nor does it try to be. It is a modest attempt to get things right by following patterns and examples laid down by tradition.

Modest, well-tried, much-loved, genuine, restful, and human are, as it happens, virtual antonyms of modern architecture.

In his essay, Leigh goes on to note the roots of the preference for classical architecture in America’s early history: the inspirations from still-standing (I’ll come back to that) Greek and Roman examples, the influence of America’s first ally, France, and the values and virtues the proportion, dignity, and order of the style and its variations were meant to embody and encourage.

Nevertheless, Leigh notes, while “Architecture can have a political role—to ennoble the institutions it houses . . . it runs deeper than politics. Goethe famously referred to it as ‘frozen music.’”

Another important line of argument that Leigh develops—important in this ruthlessly and unimaginatively pragmatic age—is that of cost and return on investment.

During last year’s EO controversy, the AIA regurgitated the misleading argument that classical design “can increase the cost of a project (to up to three times as much)” in a letter to Trump. Many laypeople are taken in by this canard, but the truth is that modernism’s proclivity for abstract, unornamented surfaces and details means construction elements must be dimensioned very precisely to keep the weather out. And that is expensive. Classicism allows for greater tolerances because joints can be concealed by pilasters, belt courses, cornices, and so on. Modernist designs can also be harder to make weather-resistant because of their frequent eschewal of time-tested local usages of materials and details. “The end result when compared apples-to-apples (in terms of quality, details, and finished execution),” a gifted classical architect wrote to me not long ago, “is a modern[ist] building will be more expensive, it will have a shorter lifespan, and it will also require higher maintenance and upkeep costs.” This can and should be verified.

Modernist buildings, as Scruton, Tom Wolfe, and others have observed, do not last.

On that point, here’s the second piece that recently caught my eye. At The Critic, Andrew Hunt looks at ugly modernist buildings and their consequences—not only aesthetic and human, but environmental. Hunt:

[Modern politicians] fetishise house-building, but fail to notice that building even a two-bed house creates 80 tonnes of carbon and uses 150 tonnes of materials—the same amount of landfill as an average household creates over 300 years! By comparison, powering your house produces about 2 tonnes of CO2 per year. Even if you could build a truly net zero home tomorrow (which you can’t), it would take forty years to break even.  

A big part of the problem is modern construction materials. Producing concrete (180kg of CO2/tonne) and steel (1.85tonnes of CO2/tonne!) are two of the most ubiquitous and environmentally destructive industries on the planet.

Badly designed and built of poor materials at great cost both financially and in terms of pollution and carbon output, modernist buildings are unloved and rapidly superannuate:

Pre-stressed concrete meanwhile has a lifespan of 50-100 years, meaning many of the first concrete structures have already crumbled into carcinogenic dust. . . . [B]adly built eyesores are being torn down barely a generation after their construction: tower blocks from the 60s, council offices from the 70s and shopping centres from the 90s. That’s billions of tonnes of fossil fuels and mining degradation ending up as landfill.

Hunt links the above to this article, “The problem with reinforced concrete,” and also contrasts problems with modern building materials with the styles and building materials of the past:

sandstone has a carbon footprint of just 77kg/tonne, and wood can be CO2 negative as it locks in carbon. Those old materials last longer as well. There are stone buildings that have been knocking around for more than a millennium—Rome’s Pantheon is 1900 years old. If treated properly, wooden buildings can last almost as long. The world’s oldest inhabited house in the Faroe Islands is 900 years old and built from wood. China’s ornately carved Nanchang Temple has been welcoming Buddhists since the 8th century.

And the kicker, the most striking paragraph in the essay to me, perhaps the most ironic and certainly the bitterest:

Isn’t it odd? Our ancestors built stunning buildings that were environmentally sustainable, have lasted for centuries and are admired and cherished. Almost all of them managed it—Greeks and Romans, Ottomans and Venetians, Tudors and Georgians. Yet they had none of the technology or machinery we have today. In every other sphere of life, we are thrashing our forebears. Why is construction the odd one out? And why have we accepted it for so long?

One hopes we won’t have to for much longer. But, given the vested interests—political, cultural, ideological—noted in both pieces, I’m not holding my breath.

For a gleeful mid-1970s jaunt through modern architecture that slaughters all kinds of sacred cows, starting with the vandals at Bauhaus and continuing through Le Corbusier and accomplices, read Tom Wolfe’s short book From Bauhaus to Our House sometime. In the meantime, watch Scruton’s documentary wherever you can find it, and appreciate the fitting, the settled, and the human wherever it still stands in your neighborhood.

No Time to Die

Daniel Craig as James Bond in No Time to Die

Daniel Craig as James Bond in No Time to Die

It’s clear to me now why No Time to Die’s release was delayed so often and for so long—who, at any point last year, could have really enjoyed a movie about an invisible microscopic threat that originated in a secret lab, that spreads person to person by close contact, that could potentially infect the whole world, and that you can’t remove once it’s tainted you?

The lab, in this case, is not in Wuhan but in London, and the microscopic threat is not a virus but a nanobot technology codenamed Heracles.

The story

At the beginning of No Time to Die, as highly proficient and heavily armed agents infiltrate the lab with the aid of a turncoat scientist, Heracles is referred to only as “the weapon.” Only later does it become clear what the weapon actually is, what kind of damage it’s capable of, and, crucially, who is stealing it.

Following the breach of the lab, M (Ralph Fiennes) sends for 007—but he doesn’t mean James Bond. Bond is five years into a long overdue retirement, whiling away his days fishing and sailing out of a luxury bungalow on the Jamaican coast. He has dropped off the grid following the film’s cold open, a bifurcated tale that is one part flashback for erstwhile Bond paramour Madeleine Swann (Lea Seydoux, returning from Spectre) and one part resolution to Bond’s leftover affection for Vesper Lynd of Casino Royale. We learn some of Madeleine’s tragic backstory, and we see an attempt on Bond’s life by agents of Blofeld (Christoph Waltz) in the Italian town where Vesper is buried. Bond assumes that Madeleine had something to do with Blofeld’s men finding and almost killing him, so he puts her on a train and disappears from her life—or so they both think.

When we catch up to Bond he’s had an unexpected visit from Felix Leiter (Jeffrey Wright) and an even more unexpected visit from the new 007—Nomi (Lashana Lynch). Leiter wants Bond to help him find the missing scientist from the lab heist scene. Nomi wants Bond to stay out of it. Bond can’t resist getting involved, and so he’s off to Cuba.

In Cuba it becomes clear that much more is going on than a simple laboratory theft, and even clearer that Blofeld and SPECTRE are not behind it. Bond and his contact in Cuba, Paloma (Ana de Armas), walk into a trap, and after extricating themselves from that and swiping the scientist from Nomi, Bond and Leiter are betrayed.

From here Bond returns to London and M’s office—now wearing a “Visitor” ID badge—and applies himself to some detective work. He gains an interview with the imprisoned Blofeld but must be accompanied by Blofeld’s psychiatrist, who turns out to be Madeleine. Her discomfort at seeing Bond again after several years is not all down to failed relationship awkwardness. She has recently been approached by an ominous figure from that flashback in the cold open, Lyutsifer Safin (Rami Malek), who has a special request for her.

Events in London don’t end well, and so while Nomi tracks down a lead on a double agent, Bond is off to Norway to reconnect with Madeleine and learn more about the threat that is slowly and lethally revealing itself.

I can’t say much more about the plot without giving things away, but suffice it to say that the movie clips along brilliantly from Norway to its final destination, slowly gathering speed until the final confrontation and revelation.

The good

No Time to Die is a whole lot of movie. It’s two hours and forty-three minutes long but (mostly) keeps moving, helped along by a lot of traditional Bond globetrotting, energetic and well-staged action scenes, Hans Zimmer’s score, good performances, and a (mostly) intriguing plot.

The film is brilliant on the technical side. The costumes and sets look great, especially the concrete bunkers where Safin and Bond face each other down at the end, and the special effects and stunt work are outstanding. All of the action scenes are good, not only enjoyable but exciting. I particularly liked a fight in a foggy Norwegian forest, in which Bond is forced to improvised in much the way he did at the end of Skyfall, and the climactic sequence, set in a repurposed Cold War-era missile silo, feels like a level from GoldenEye for N64 in the best possible way. I really thrilled as the film approached the conclusion.

No Time to Die is also beautiful to look at, as it was shot on 65mm film and mostly in the real places where the film takes place—Italy, London, Jamaica, Norway, and finally the Faroe Islands standing in for “disputed islands” between Japan and Russia. The cinematographer, Linus Sandgren, makes full use of the format for Lawrence of Arabia-scale landscapes and beauty shots. The lab heist at the beginning, taking place high on a London skyscraper at sunset, is stunning.

The cast perform well from top to bottom, though I felt Ralph Fiennes could have used more screentime and Christoph Waltz needed either more or none at all. Like some others, I was worried about the direction the film would take Nomi as a “new” 007, but I was quite pleasantly surprised. Nomi’s got a big attitude, but after some genuinely enjoyable rivalry in the early going she and Bond learn to respect and work with each other. They even have some of the film’s best banter, with Bond often getting the last word. It’s also in this snipping back-and-forth with Nomi that we get the clearest glimpses of the Bond from the early Craig movies rather than the sleepwalker from Spectre.

And while I’ve seen a few people criticize Rami Malek’s Safin as a “weak” Bond villain, I disagree. I found him a real threat, and his first appearance since the cold open, in which he is masked, is genuinely menacing. What I do wish is that he had more time in the film and that his motivations regarding his ultimate plans for Heracles—moving from wiping out certain bad people to spreading it worldwide—were clearer. Is this a eugenics project? Racially motivated genocide—as his pet scientist hints he could do if he wanted? Pure nihilism? I’ve seen the movie twice and I’m still not sure about this.

The film also features some nice nods to previous films and even Fleming’s original stories. The porcelain bulldog willed to Bond by Judi Dench’s M in Skyfall shows up, for example, and Safin’s garden of poisonous plants comes straight from the novel You Only Live Twice.

The bad

I’ve hinted at a few misgivings about the movie. I’m not completely sure the plot involving Blofeld leading SPECTRE from prison makes sense. I got more of it on a second viewing—for example, how one of Blofeld’s henchmen wound up working as one of Safin’s henchmen later in the film—but I think the plot moves quickly through this to conceal its basic implausibility.

Unusually for Bond, he is also prone to speechifying in this film. Two scenes stand out—one about halfway through in which he opens his heart to Madeleine, and one in which he berates Safin as an “angry little man” who is “playing God.” Bond can care deeply about women he loves and loathe a hubristic enemy, but this has seldom been something laid out for the audience in soliloquy. This is not a big problem, but an oddity of the writing and one that doesn’t jibe with what we know of Bond. (The movie overexplains things elsewhere, too, as when the scientist, having gone rogue, says to himself what is happening, or when Q’s computer announces “Blofeld’s bionic eyeball unlocked,” a system message that deserves to become immortal.)

No Time to Die is overlong, and it is overstuffed. Its fast and well-managed pacing doesn’t fully resolve either of these problems (I’ll have a lot more to say about that below). When I write that M or Safin could use more screentime, I’m not arguing for a longer movie but a re-proportioned one, one that trims away or removes some sidestories and subplots that, while contributing to the plot, also add to the sense of bloat and diffusion.

And I think I know why this is, but I can’t examine that without giving things away. So if you’ve seen the movie, feel free to continue into the spoiler territory below.

My biggest misgiving—spoilers ahead

I need to set this complicated but ultimately rather mild criticism up with two spoilers: Bond and Madeleine have a five-year old daughter, Mathilde; and, at the end, Bond, infected with Heracles nanobots that would target and kill Madeleine and Mathilde if he so much as touches them, dies stopping Safin’s plan.

I think No Time to Die missteps by bringing Madeleine back from Spectre—and in giving her and Bond a child. The film would be shorter, tighter, and—in Bond’s death—more powerful without Madeleine.

no-time-to-die-poster-james-bond.jpg

Some of my criticism is purely practical. With the exception of Sylvia Trench, who disappeared after the first two Connery films, Bond has never had a girlfriend carry over from one movie to another. It’s out of character.

Furthermore, Madeleine being the daughter of Mr White requires the audience to recall who Mr White is and some of what he’s been responsible for if they want to understand Safin’s motivation. This is a tall order for casual fans. (My wife, for instance, was mystified by the connection.) While there have always been some continuities in the Bond series, the films mostly stand alone—for a reason.

(Also: I’m not usually the type to make internet neckbeard arguments about believability, but I did have to question the wisdom of Her Majesty’s government in clearing Madeleine to meet regularly with Blofeld, given that she’s the daughter of a known terrorist financier with ties to two other terrorist leaders. There are surely other psychiatrists in London.)

It also seems like the screenwriters never quite decided what to do with Mathilde, Bond and Madeleine’s daughter. After Safin kidnaps her, he uses Mathilde as a powerful bargaining chip, manipulating both Madeleine and, in one of the film’s tensest scenes, Bond. But when Mathilde becomes even slightly inconvenient he abandons her. Thereafter, Mathilde becomes what TV Tropes calls The Load, a helpless human cargo for the hero to heft along while also fighting the bad guy.

And that, the conclusion, with Bond facing his death, is the root of my biggest misgiving. As Bond, wounded and bleeding out and also infected with Heracles, calls in a missile strike to obliterate Safin’s stores of Heracles but that will also surely kill him, too, he has a tearful conversation with Madeleine by radio. She confirms that Mathilde is his child. He tells her he loves her. He smiles. The missiles home in and Bond dies a glorious death.

And it doesn’t quite work—at least not for me.

What the movie gets right is that Bond can’t grow old and harmless, withering into senescence in retirement. If Bond is ever to die, it must be in the line of duty, because it has always been duty—Queen and Country—that drives him, and he has always endured, with a stiff upper lip and a wry comment, as a result. Men like Bond come and go but England is forever, even with the collapse and irrelevance of the Empire. A brief exchange between Safin and Bond nails this. Called “redundant” by Safin, Bond begs to differ: “Not as long as there are men like you around.”

What the movie gets wrong is its diffusion of our investment in Bond’s sacrifice. Are we pulling for Bond to succeed and weeping at his sacrifice because he’s defeating an enemy of Britain and saving the world? That works. Are we pulling for Bond to succeed and weeping at his sacrifice because he’ll save but never again see Madeleine and Mathilde? That also works. Either of these things could have been fine, but not both together. Ironically, by bringing Madeleine back and giving her and Bond a child, presumably to give Bond a more intimate, personal stake in the plot, the screenwriters actually lower the stakes. This might have worked, because Skyfall did it—and did it better, because there the personal and the patriotic were united in the figure of M. Here, the two halves of Bond’s motivation are separate and distract from each other.

Trimming these subplots, especially replacing Madeleine with another character with no tie to the events of previous films, could have untangled some of the middle of the film’s plot complications and, in the conclusion, allowed the audience to focus solely on Bond’s confrontation with Safin.

The result, ultimately, is a fast-paced but overcomplicated plot that also doesn’t quite work tonally or in terms of Bond’s character.

Conclusion

That’s a lot of explanation about what I think doesn’t quite gel in No Time to Die, but there I’m minutely examining the difference between a B+ and a B- movie. Most of the film works, and works well. I just think it could have been even better. Even if long, slightly overcomplicated, and taking one too many missteps in the conclusion, its fast pace, excellent action, and great performances will keep the Bond name alive for a long time to come. It’s a worthy conclusion for Daniel Craig’s run as Bond.

I’m going to miss Craig as 007. For me, No Time to Die ranks below, but not too far below, the two masterpieces from his tenure—Casino Royale and Skyfall. I don’t know what will come after Craig, but I’m hopeful, and I appreciate what he brought to the character for fifteen years.

Thank you, 007. That’ll be all.

Robert E Lee: A Life

Allen Guelzo’s new biography of Robert E Lee could not have been better timed. Begun eight years ago, Guelzo worked on it from the late years of the Obama administration, through the Trump years and the Charlottesville riot, finished it during the COVID-19 epidemic and the social upheavals of the summer of 2020, and it appeared in bookstores just a few weeks after Richmond’s monumental equestrian statue of Lee and Traveller came down. The time is ripe for a well-researched, well-argued, measured look at the real man behind the many propaganda versions of Robert E Lee.

And Guelzo’s Robert E Lee: A Life almost perfectly—almost—fits the bill.

The life

Even before examining Lee’s Virginian ancestry, the standard way to begin a life of Lee, Guelzo opens with an admission: his bias. Guelzo is “a Yankee from Yankeeland” and can only, in the end, regard Lee as a traitor. This would seem to close off certain sympathies or lines of questioning from the start, but Guelzo is intellectually honest enough to work through and against his bias most of the time (about which more below), and, frankly, I can get along with someone who is upfront about his bias. Charitable but not uncritical, this is a long way from the smears and hatchet jobs—here’s the worst, a mendacious piece from The Atlantic that just will not go away—that commonly circulate today.

With this off his chest, Guelzo begins with Lee’s father, “Light Horse Harry” Lee. Light Horse Harry was an eager young cavalryman during the Revolution who impressed no less than George Washington and Nathanael Greene with his vigor, but proved an utter failure in post-war political life—not to mention his private life. He made many political enemies and just as many disastrous investments. He twice married into wealth, and the second time it was only a legal provision by his in-laws prohibiting him from having access to his wife’s money that kept the family from going completely broke. By the time Robert was born, the eighth of nine children, the family was in dire financial trouble. When Robert was six, Light Horse Harry left for the Caribbean in a scheme to recoup his losses and return in triumph. Instead he fell ill and died in Georgia on the return trip, when Robert was still only eleven.

The character and death of Robert Lee’s father, a politically inept wastrel who more or less abandoned his family, is, for Guelzo, one of the seminal moments in Lee’s life. For the rest of his life, Guelzo convincingly argues, Lee was motivated to be the man his father—and several other older male relations—failed to be: to pursue independence, scrupulous financial solvency, and personal moral perfection. The negative example of his own father was ever before him. Guelzo notes that right up until the Civil War, Lee was often identified as the son of Light Horse Harry Lee. The constant reminder, he suggests, was Lee’s hairshirt.

Guelzo spends a good amount of time on Lee’s youth, education, and early military career. Following his graduation from West Point, Lee spent decades as an army engineer, working on east coast fortifications like Fort Pulaski and Fortress Monroe or western “improvements,” like a project to redirect the Mississippi in order to prevent the port of St Louis from silting up. A chapter on Lee’s performance in the Mexican War, in which he began as an engineer on the staff of General Winfield Scott but ended up as Scott’s favored reconnaissance officer and military protégé, is especially good, as Guelzo notes what Lee learned by example from the United States’s shameful perfidy toward Mexico and Scott’s high-minded and idealistically honorable conduct of the war.

These chapters, covering approximately the first two hundred pages, are well spent and give proper proportion to the Lee’s life before the Civil War. Throughout, Guelzo takes careful note of Lee’s uprightness and strength of character—already remarked upon in his teens and twenties—and his gravitation toward older male mentors, a series of army officers culminating in General Winfield Scott. He marks also Lee’s constant fretting about money despite being, by the standards of the time, apparently well situated; his marriage and family life (which can easily go missing in military biographies); and even the development of his religious beliefs, which began as what Guelzo characterizes as a noncommittal “genteel low church Episcopalianism” that gradually, especially during the war years, grew more open and more fervent.

Guelzo also carefully examines Lee’s political ideas—what there are of them—an inherited Federalist sentiment that evolved toward a preference for the anti-populist, anti-Jacksonian Whigs over the Democrats. But, most importantly, Guelzo notes Lee’s early apolitical stance, a stance maintained with greater and greater tenacity as political strife became more and more difficult to avoid.

Crucially, Guelzo brings the reader into the first great test of Lee’s resolve on all of his goals—personal independence, care for family, financial stability. This is the death of his father-in-law, George Washington Parke Custis, a gregarious dabbler and, as lord of Arlington plantation in Alexandria, one of the largest slaveowners in northern Virginia. When Custis died in 1857, he left behind a poorly managed and run-down estate and seemingly impossible provisions in his will—generous legacies for his grandchildren, the payment of his many creditors, and the manumission of the Custis slaves within five years—and named Lee as executor. Seeing the provisions of the will carried out to the letter consumed Lee’s life into the early years of the Civil War and still caused problems in the years afterward.

When the crisis of the Union comes, Guelzo gives a thorough and detailed examination of Lee’s competing instincts and loyalties—the will to avoid politics, his loathing of slavery and secessionism, his fear of the federal government’s use of force against other Americans, and his loyalty to family and, by extension, home state. He also lays out, before, during, and after the war, the legal difficulties involved in the Constitution’s ambiguous (and, I would argue, factitious) definition of treason. (A reviewer at National Review also notes that, at the time, the oath sworn by army officers was written with “United States” grammatically plural and was only changed because of the Civil War. Guelzo includes the text of the oath but does not draw attention to this.)

The chapters on the Civil War proper, what I imagine a lot of people will read the book for, are excellent. I may not agree with all of Guelzo’s perspectives on the fighting or the personalities involved, but this offers an engaging—even exciting and moving—and authoritative tour of the conflict through Lee’s involvement as commander of the Army of Northern Virginia. Throughout, Guelzo never loses sight of Lee the man, and keeps the reader abreast not only of the campaigns but of Lee’s personal life. Lee lost not only the property bequeathed to his children during the war, but a daughter and a grandson, and one of his sons was captured and threatened with hanging by his Union captors. He also had at least two heart attacks.

The final chapters follow Lee’s postwar years as president of Washington College in Lexington. Here Guelzo gives much more thorough coverage than is typical of Lee biographies, and this attention is welcome. Much more than a famous name or a figurehead, Lee oversaw a revival and expansion of the college that helped it survive the lean years following the war.

Perhaps the highest praise I can give the book is to note my hesitation to read the final few chapters. When one reads a biography one knows the end must come, but as I sensed its approach in the onward march of Reconstruction and Lee’s steeply declining health, I read with trepidation. Guelzo’s description of Lee’s death, coming at the end of this involving and intimately personal look at the man, moved me deeply.

The value

Guelzo, despite his openly stated bias in favor of a nationalist vision of a divinely ordained and indivisible Union—a bias and vision I don’t share—does a great deal to help Lee’s reputation in this hostile age. He brings an intellectual honesty to much of his account that pokes holes in a lot of simplistic versions of Lee and simply debunks others.

He demonstrates, for example, that Lee’s regard for slavery as an “evil” was not mere rhetoric. Did Lee benefit from slavery? Yes—who didn’t in that age? Did Lee have modern attitudes toward race? No—who did in that age? Guelzo does not conceal these facts, but he also points out where Lee was exceptional in this regard. The only slaves Lee ever personally owned were a single family inherited from his mother, a family whom he liberated when he didn’t have to. He worked especially hard to see to it that all of his father-in-laws’ slaves were freed by the stipulated deadline—again, as Guelzo points out, at great inconvenience to himself and despite the chaotic early years of the war, the occupation of Arlington by the Union army, and the ready availability of Confederate judges who could have voided that provision of the will. Guelzo also shows how, after the war, Lee used his position as president of Washington College to prevent racial violence in Lexington, handing out harsh penalties or outright dismissals from the college to students who assaulted or antagonized freedmen.

Militarily, Guelzo also has insightful critiques and reassessments of Lee’s capabilities as a general. While a commonly repeated consensus is that Lee was a master tactician but a poor strategist, Guelzo makes a very good case for the accuracy of Lee’s strategic vision, that Lee understood early that the war would have to be won quickly, and virtually within sight of Washington, DC, in order to prevent the triumph of the Union through sheer scale and manpower. This was a refreshing and interesting perspective.

Guelzo also, in the book’s complex and challenging epilogue, deflates the commonly repeated cliché that Confederate monuments were put up as subtle semiotic violence toward African Americans, using the Lee monument in Charlottesville as an example. By the time Guelzo reaches latter day conflicts, the comparison with the life so meticulously laid out in the preceding 400 pages renders the present appropriately small, tawdry, and depressing. Guelzo also pushes back against some of the more unfair misrepresentations of Lee’s character popularized by Thomas Connelly in his 1977 book The Marble Man.

Overall, the portrait Guelzo presents the reader is of Lee as a flawed but good and principled man burdened with impossible personal standards, a man characterized more often than not by frustration—with the army, with newspapers, with the US government, with the Confederate government, with the slaves of his father-in-law’s plantation, with Arlington itself, the apple of his homebody wife’s eye—and a man who, from his return from Mexico onward, was deeply unhappy. I would dispute some of this. Guelzo gives us some glimpses of the deep affection Lee felt for his children, his charm and gentility toward women generally, and his sense of humor and fun, but these dimensions of his personality are often missing.

This may not be a complete portrait of the man, but it is a good portrait.

Quibbles

Nevertheless, I have quibbles, mostly relating to places where Guelzo betrays his bias. I want to point out three, with examples, so pardon the length. If you’re not here for the long haul, you can jump straight to my conclusion below. Otherwise, look at these three narrative tics and notice how they overlap.

The first is simply stylistic, relating to how Guelzo incorporates quotations, especially from letters and other primary sources, and what in fiction are called “dialogue tags.” Here are a few samples:

But [a steamboat] could carry many times the commercial load of the rafts and barges, and unlike the flatboats and keelboats it could turn around and breast the Mississippi’s current for a trip upstream, making possible a complete circuit of the entire river highway between New Orleans and Pittsburgh. “What a prospect of commerce is held out to the immense regions of the west, by the use of these boats!” drooled Niles’ Weekly Register (67).

“The rumor which has reached me of this distressing event, I could not before credit, nor can I even now realize its truth,” Lee wailed in a letter to Gratiot on December 23 (74).

The first was President Polk’s political jealousy of General Zachary Taylor, whose modest victories were already “giving great uneasiness to the administration” and leading to discussions about a presidential bid by the old planter-general. “These officers are all Whigs and violent partisans,” Polk spluttered (89).

I don’t think there’s much in these quotations to warrant the verbs drool, wail, or splutter. These are the wildest examples, but throughout—and clustering noticeably in the two early chapters I pulled these from—Guelzo overdoes it with these tags. It’s distracting and sometimes comical, and while I don’t think Guelzo intended this, but they also carry a faint air of derision wherever they appear.

Similarly, Guelzo occasionally editorializes in the middle of his narrative, often with a “it never seems to have occurred to him,” a tic I noticed early on, as here:

“I seem to think that Said opportunity is to drop in my lap like a ripe pear,” he admitted. Nevertheless, he persisted in believing that it was “remarkable that a man of my Standing should not have been Sought after by all these Companies for internal improvement.” It seems never to have occurred to Lee to go looking for those companies and opportunities on his own, or that the coastal engineering projects that had consumed his career thus far were of little interest to the infinitely more lucrative inland projects of railroads, real estate, and bridges (73).

Even Rob, at ten years old, remembered that Lee made a fetish of being “punctual” and on Sunday mornings would “appear some minutes before the rest of us,” ready to proceed to the academy chapel, and “rallying my mother for being late, and for forgetting something at the last moment.” If [Mary Lee] strained his patience, “he was off and would march along to church himself, or with any of the children who were ready.” (It never occurred to her husband that Mary Lee’s slowness might be due to some other cause than forgetfulness.) (132)

“These people [the Union army] delight to destroy the weak, and those who can make no defence,” Lee fumed, as if the wounds of Arlington and White House had been reopened by the destruction of Fredericksburg; it never occurred to him that Fredericksburg’s enslaved population might look on the arrival of the Union Army in a very different light (274).

There were other issues, too, that fueled [Lee’s] bitterness over Union conduct, which seemed to diverge so wantonly and destructively from the scrupulous pattern Winfield Scott had set long ago in Mexico. (It never seems to have occurred to him that the barbarities of slavery were worth weighing in the balance, or that those barbarities and the men who excused them were precisely what he was, objectively, protecting.) (310)

Again there is that faint whiff of derision or scorn. Some of this Guelzo just can’t know (about which more below), and some of it represents an abandonment of his quest to understand the man. The latter two examples are especially frustrating, as Guelzo otherwise devotes so much time and effort to exploring and explaining Lee’s negative view of slavery, his rigorous soldierly avoidance of political questions, and his scrupulous attempts to uphold honorable and civilized standards of warfare. But here, instead of trying to integrate all of this understanding and interpret these events or passages in light of it, he simply gives up in favor of hectoring Lee for failing to be Allen Guelzo.

Finally, there’s not much of it, but there is, crucially, more psychologizing than I prefer in a historical work. Two examples:

Mary herself maintained an informal Sunday school at Arlington for slave children, teaching them (in quiet violation of Virginia law but mostly to satisfy her own sense of a white woman’s obligation to lesser beings) to read in “a little school house” in the woods (145).

Again, how can Guelzo possibly know this? Is obligation utterly incompatible with a sincere desire to help? Is this not a species of what modern people rather cheaply call “giving back”? And this comes in the same paragraph as a description of Lee purchasing Mary a lifetime membership in the American Colonization Society and paying the way for manumitted slaves to migrate to Liberia at his own expense.

Then there’s Guelzo’s handling of the notorious Norris incident, in which three of Mary’s father’s slaves, including a man named Wesley Norris, ran away from Arlington, were returned, and whipped. A lurid denunciation of Lee, as the executor of his late father-in-law’s will, appeared shortly afterward in Horace Greeley’s anti-slavery New-York Tribune and, after the war, when Radical Republicans were looking for excuses to prosecute or hang ex-Confederates, a yet more elaborate version appeared in an explicitly abolitionist newspaper. My point here is that our sources for these details had plenty of motivation to exaggerate or fabricate. (Arlington’s official account of this incident, appropriately cautious, hedges its bets, concluding on a note invoking what one might call “emotional truth.”)

While Guelzo accepts more of the story than I tend to (I’m disinclined to think it’s a complete fabrication, but that’s a debate about historiography and sources for another time), he follows his account with this:

A week later [after the appearance of the Tribune story], he wrote to Custis Lee . . . wondering whether “you have been told that George Wesly and Mary Norris absconded some months ago, were captured in Maryland, making their way to Pennsylvania, brought back, and are now hired out in lower Virginia.” He said nothing about the whipping, except to acknowledge that “the N.Y. Tribune has attacked me for my treatment of your grandfather’s slaves.” He added, cryptically, “I shall not reply.”

But he could not bring himself actually to deny that he had done what the Tribune described, and it is difficult to avoid the conclusion that when his fury had cooled, he was sickened at himself, as much for the damage done to his own self-image as for the cruelty inflicted on the three fugitives. In that moment, he had reverted to Light Horse Harry, spiking a deserter’s head on a pole (157-8).

This is a lot to read into Lee’s refusal to write a rebuttal to a hostile newspaper, and even gets into the cheap father complex stuff that mars a more popular-level biography like Roy Blount Jr’s. This bit of psychological speculation—because it is, after all, only speculation—is especially egregious since Guelzo notes many other instances in which Lee, protective of his and his family’s honor and cognizant of how degrading political debate and newspaper mudslinging could be, refused to descend to the level of his critics—both north and South, and before, during, and after the Civil War. Even today Southerners of a certain background are raised neither to answer nor even acknowledge unfair criticism, an ideal that, as in Lee’s lifetime, is becoming harder and harder to live out. In cases like these it appears—it never occurs to him?—that Guelzo is simply unwilling to or incapable of fully understanding his subjects or allowing their actions to speak for themselves.

Or perhaps it’s simply his bias again. Just a few too many times Guelzo gives in to an impulse to hold Lee at arm’s length and superficially critique him, forgetting for a moment some of his own carefully researched insight into the man. Though he capably unpacks many of the factors that made Lee into the man he was, most especially the lifelong negative example of Lee’s own father, Guelzo never entirely overcomes cultural blindspots like this, and his picture of Lee, though strong, deeply researched, and mostly fair, never completely coheres.

Imperfections—precisely what Lee dreaded.

Nevertheless

If I have dwelt at length on these flaws—which are more nagging interpretive tics suggestive of an underlying unwillingness to comprehend than narrative-wrecking errors—it’s because Guelzo’s book is otherwise so good. Guelzo’s standards of research are extraordinary, his coverage is meticulous, his account is fair and openminded toward Lee most of the time, and his writing is excellent. I finished the 430+ page body of the work in just over a week, and not only because of my interest in the subject.

And most importantly, Guelzo’s commitment to research and to finding the human being underneath the partisan versions of Lee helps puncture a number of useful misconceptions—or outright fictions. And this in spite of a bias that can lead Guelzo to clearly lay out Lee’s understanding of his own situation, the ambiguity and uncertainty of his position, and his reasons for resigning from the US Army and going with Virginia—which had not yet seceded at the time of his resignation—and still write in the book’s conclusion what amounts to a “Meh—treason.” Again, that clearly stated bias. Nevertheless, this is the fairest shake I expect Lee to get anytime soon.

But in a way, despite the nagging issues I’ve examined, Guelzo’s bias—honestly admitted from the get-go—may prove to be a strength. This book, coming from this author with this perspective but still striving both to understand and to make Lee comprehensible, may get a hearing older biographies by previous biographers would not. And an attempt at an honest account, one that seeks however imperfectly to explain Lee on his own terms, is welcome in this day and age.

My recurring thought over the history, monument, and naming debates of the last several years has been Go read a book. For those honest and openminded enough to do so, Guelzo’s Robert E Lee: A Life may be the right book at the right time.

More if you’re interested

In the epilogue, Guelzo graciously refers to Emory Thomas’s biography of Lee as “the best and most balanced of any single-volume Lee biography,” and I think I agree. I recommend it. I also recommend William C Davis’s Crucible of Command, which is a dual biography of Lee and his opposite number, Grant. It’s one of the best books I’ve read on either man or the Civil War generally. Guelzo is mildly dismissive of Douglas Southall Freeman, author of the Pulitzer Prize-winning four-volume RE Lee, but Freeman’s research is still unparalleled and his perspective less “worshipful” than it is often accused of. (Ironically, Freeman was praised at the time for presenting a realistic and human portrait of a man long “viewed by [other] biographers through the rose-tinted glasses of romance.”) The one-volume abridgement Lee is still worth reading.

If you’re pressed for time, some good essays (a couple of which I recommended before, in a post for the sesquicentennial of Lee’s death a year ago today):

And several of y’all sent me a link to theologian Kevin DeYoung’s interview with Guelzo, which is a good one-hour introduction to the topic with, again, Guelzo being quite upfront about his biases.

Chesterton on Poe

I’ve been thinking a lot about Edgar Allan Poe for, oh, the last twenty-seven years or so, and so I was struck yesterday to catch the following in the first chapter of GK Chesterton’s Orthodoxy, a book I’ve read many times:

Poets do not go mad; but chess-players do. Mathematicians go mad, and cashiers; but creative artists very seldom. I am not, as will be seen, in any sense attacking logic: I only say that this danger does lie in logic, not in imagination. Artistic paternity is as wholesome as physical paternity. Moreover, it is worthy of remark that when a poet really was morbid it was commonly because he had some weak spot of rationality on his brain. Poe, for instance, really was morbid; not because he was poetical, but because he was specially analytical.

For comparison, here’s a really interesting review of The Reason for the Darkness of the Night, by John Tresch, a new biography that approaches Poe—who had spent time in the army at Fort Moultrie and a very short stint at West Point, which was then primarily an engineering school, and who went on to influence both science fiction and “ratiocination”-based detective stories as genres—as a frustrated scientist. Here’s the reviewer on Poe’s Eureka: A Prose Poem, published a year before his untimely death. I quote at length to make a point:

As the reviews–which were overwhelmingly savage–pointed out, it contains no actual scientific research: Poe reaches his conclusions by ‘ratiocination’, the method also favoured by his fictional detective Auguste Dupin. In its grandiose and disorientating shifts of perspective, it bears a closer resemblance to the diorama shows of New York’s entertainment palaces than it does to a scientific treatise.

Yet Tresch finds method in the madness of Eureka. Poe conceives the universe in terms of an eternal flux between the forces of attraction and repulsion. Matter and soul, time and space are all manifestations of the same essence. Attraction is the force that manifests in matter and gravity, while repulsion imbues electricity, life and spirit. The universe began in a spasm of repulsion, diffusing outwards to create multiplicity out of unity, before the forces of attraction–as described by Newton’s theory of gravity and Laplace’s nebular hypothesis–drew it back into clumps of matter. The process cycles constantly through microcosm and macrocosm, at every scale from the microbial to the galactic. It is the breath of life, the heartbeat of the universe, and will continue until a final collapse in which all life and consciousness will merge into the unity from which they arose.

Solipsistic and extravagantly overreaching, Eureka was nonetheless a sincere attempt to formulate a holistic science in opposition to the narrow specialisms that Poe saw hardening around him.

“Morbid . . . not because he was poetical, but because he was specially analytical” is tough but fair. It also fairly neatly illustrates a passage from later in the same paragraph of Orthodoxy, in which Chesterton writes that

To accept everything is an exercise, to understand everything a strain. The poet only desires exaltation and expansion, a world to stretch himself in. The poet only asks to get his head into the heavens. It is the logician who seeks to get the heavens into his head. And it is his head that splits.

This aside about Poe got me poking around looking for other places where Chesterton had written about him. While I found several offhand remarks and allusions, the longest reference, one that indicates intimate familiarity with Poe’s work, comes in chapter two of Chesterton’s literary study Robert Louis Stevenson. Here Chesterton contends with the basic artistic sensibilities of Stevenson and Poe, who were often at that time—Chesterton thinks unjustly—compared:

Now in the same manner there is at the back of every artist's mind something like a pattern or a type of architecture. The original quality in any man of imagination is imagery. It is a thing like the landscapes of his dreams; the sort of world he would wish to make or in which he would wish to wander; the strange flora and fauna of his own secret planet; the sort of thing that he likes to think about. This general atmosphere, and pattern or structure of growth, governs all his creations however varied; and because he can in this sense create a world, he is in this sense a creator; the image of God. Now everybody knows what was in this sense the atmosphere and architecture of Poe. Dark wine, dying lamps, drugging odours, a sense of being stifled in curtains of black velvet, a substance which is at once utterly black and unfathomably soft, all carried with them a sense of indefinite and infinite decay. The word infinite is not itself used indefinitely. The point of Poe is that we feel that everything is decaying, including ourselves; faces are already growing featureless like those of lepers; roof-trees are rotting from root to roof; one great grey fungus as vast as a forest is sucking up life rather than giving it forth; mirrored in stagnant pools like lakes of poison which yet fade without line or frontier into the swamp. The stars are not clean in his sight; but are rather more worlds made for worms. And this corruption is increased, by an intense imaginative genius, with the addition of a satin surface of luxury and even a terrible sort of comfort. “Purple cushions that the lamplight gloated o’er” is in the spirit of his brother Baudelaire who wrote of divans profonds commes les tombeaux [divans as deep as tombs]. This dark luxury has something almost liquid about it. Its laxity seems to be betraying more vividly how all these things are being sucked away from us, down a slow whirlpool more like a moving swamp. That is the atmosphere of Edgar Allan Poe; a sort of rich rottenness of decomposition, with something thick and narcotic in the very air. It is idle to describe what so darkly and magnificently describes itself.

When I say that Chesterton finds the comparison of Stevenson to Poe unjust, I think he finds it unjust to both men. Because while this is a vivid, meticulous, and incisive riff on “the atmosphere and architecture” of Poe’s stories and verse, I don’t read it as necessarily condemnatory. Chesterton’s whole point is the simple unlikeness of Stevenson and Poe. Where Poe is morbid, he is nevertheless good at what he does. And some of us certainly respond readily to the “dark wine, dying lamps,” and “dark luxury” of Poe’s vision.

Elsewhere in my cursory search I ran across the following from Jorge Luis Borges, from “On Chesterton” in an essay collection called Other Inquisitions, 1937-1952. After describing several fantastical scenarios from Chesterton stories, Borges writes:

These examples, which could easily be multiplied, prove that Chesterton restrained himself from being Edgar Allan Poe or Franz Kafka, but something in the makeup of his personality leaned toward the nightmarish, something secret, and blind, and central.

This consonance of Chesterton’s and Poe’s imaginations at one point had never occurred to me. Both have something high-flown, florid, and larger than life in the wild and fevered incidents of their stories. Compare the violence in any two of their stories, especially in the way the violence is conveyed by the operatic horror of observers (or narrators); and look at the frantic tone of headlong pursuit—or is it flight? who can tell?—in The Man Who Was Thursday with any number of Poe tales. And keep in mind that The Man Who Was Thursday’s subtitle is A Nightmare.

Food for thought. There’s a lot there, and I’m surprised it took me this long to connect two of my favorite writers in this way. I hope to write more on this later.

In the meantime, here’s a good short TED-Ed video on Poe.

Men of Terror

Imagining what it was like—Angus McBride’s depiction of Olaf Tryggvason’s final moments at the Battle of Svolder

Imagining what it was like—Angus McBride’s depiction of Olaf Tryggvason’s final moments at the Battle of Svolder

Old friends or longtime readers of this blog will know that one of the most important questions I bring to my historical study, and the question that bridges the gap between my academic work and my love for writing fiction, is What was it like? Instinctual and unarticulated, this question drove my earliest interests in history, and my formal study always ran parallel to my imagining being there. Then I read John Keegan and, later, Victor Davis Hanson, and their work gave substance and form to those instincts, allowing me to shape my work, from my graduate thesis onward, deliberately to pursue answers to What was it like? in addition to everything else of big-picture importance in historical research.

William R Short and Reynir A Óskarson’s Men of Terror: A Comprehensive Analysis of Viking Combat fits snugly into that important interest of mine, pursuing the same question—or set of questions—with regard to warfare in the Viking Age.

I say set of questions because Short and Óksarson don’t stop with imaginative you-are-there reconstructions or interpretations, but collect as much empirical, scientific data as possible on as wide an array of topics as possible in their research into Viking combat. This includes not only collecting archaeological evidence about, say, the build and strength of Viking Age people, but also mining the literary sources, most especially the Sagas of Icelanders but others where necessary, for information on what kinds of weapons and gear were used, and how.

men of terror cover.jpg

So, for example, based on the numerous violent incidents described in the sagas, Short and Óskarson are able to show that Viking swords were used for slashing or cutting an overwhelming majority of the time and only rarely for thrusting. Furthermore, these data correlate with the design of the thousands of surviving Viking Age swords, which almost always have cutting edges on both sides—some of which, they note, are still sharp a thousand years later—but less tapered, more spoon-shaped points that would be less suitable for stabbing. Here the archaeology and literature back each other up.

Short and Óskarson are also, however, alive to the limits of the available sources and data, and are rightly cautious in their conclusions. They frequently invoke what they call “the coin-toss problem.” Imagine flipping a quarter three times and attempting to derive reliable statistical conclusions about the results of coin tosses from those three examples. While the vast number of surviving swords make conclusions based on attacks described in literary sources more reliable, in many other areas their conclusions have to be much less certain. There is, for instance, exactly one surviving example of a Viking Age helmet, making extrapolation and sweeping conclusions about the design, use, and commonness of helmets unwise. Here one must look more closely at descriptions of helmets in literary sources—all the while keeping in mind that many of these post-date the Viking Age by centuries.

This is a delicate balancing act, but Short and Óskarson are admirably judicious in their use of all available sources and refuse to draw unwarranted conclusions. I have to say that this was enormously refreshing, especially when it comes to contentious topics like Hollywood’s favorite Viking, the “shield-maiden.”

But their willingness to embrace the difficult work of squaring what we know from often fragmentary archeological knowledge with the literary sources and all their potential flaws is not the only strength of Short and Óskarson’s book. They also bring a great deal of practical, empirical knowledge to their analysis. Through research conducted through Short’s “experimental archaeology” group Hurstwic, the authors tested their conclusions using reconstructed Viking Age weapons, armor, and clothing. This includes measuring the force of sword blows using scientific instruments, the cutting power of various Viking weapons using animal carcasses, and even much simpler experiments. The sagas recount great heroes swimming fully armed and armored. Is this possible? Short and his collaborators found out by suiting some swimmers up and dumping them in the water. Inexperienced swimmers sank almost immediately, but some Scandinavian participants accustomed to cold water swims carried on just fine. Fascinating, even exciting stuff.

After early chapters on sources, methodology, and their attempt to understand the Vikings from the inside out (about which more below), Men of Terror settles into a series of chapters exploring specific topics—the numerous kinds of weapons used throughout the Viking Age as well as armor, shields, dueling, raiding, naval combat, mass infantry battle, and grappling or “empty-hand” combat. Each chapter is lavishly illustrated with pictures of surviving archeological examples, drawings or reconstructions based on research, maps and photos of actual locations of fights and ambushes in Iceland, pictures of Hurstwic experiments and reenactments, and charts laying out all kinds of data—average blade length of surviving swords, the causes and results of duels in the sagas, the relative lethality of attacks with different kinds of weapons, and more.

These weapon by weapon and tactical chapters, with their mix of literary and archaeological research as well as real-world experiment, make up the bulk of the book. But one early chapter is perhaps the most valuable and sets the tone for all the rest: Short and Óskarson’s chapter on “the Viking mindset.”

This, too, is speaking my language. I’ve invoked Chesterton’s vision of “the inside of history” here time and time again. Short and Óskarson drive straight at this, seeking to understand the warriors of the Viking Age on their own terms rather than importing the ideals of the present day to the past. I use the phrase their own terms deliberately: Short and Óskarson work through some key Old Norse vocabulary—most especially drengskapr, manliness, and orðstirr, word-glory or fame—to establish why Vikings did what they did. They follow this up throughout the book by staying on guard for the intrusion of their own modern mindsets, always aware that what strikes them as most “efficient” or “likely” may never have occurred to a man of the Viking Age. This is a selfless, genuinely openminded approach to understanding a long-departed culture, and it’s one of the things that makes Men of Terror especially good.

I could go on much longer, but hopefully this has given you a taste for this excellent book. I highly recommend it if you have any interest in the Viking Age or medieval military history at all.

More if you’re interested

I discovered Short and his organization Hurstwic through Jackson Crawford, who has interviewed Short on his YouTube channel. These interviews are excellent resources in and of themselves. Here are Part I and Part II. If this “mindset” or “inside of history” approach resonates with you and you have an interest in the Viking Age, especially the literature thereof, let me also recommend Tom Shippey’s Laughing Shall I Die, which I read this summer.

Eaters of the Dead

13th warrior poster.jpg
 
When Eaters of the Dead was first published, this playful version of Beowulf received a rather irritable reception from reviewers . . . But Beowulf scholars all seem to enjoy it, and many have written to say so.
— Michael Crichton, "A Factual Note on Eaters of the Dead," 1992
 

I first read Eaters of the Dead in high school and didn’t know what to do with it. I sought it out primarily because it had a famous name attached to it and because many of my friends were gaga for its film adaptation, The 13th Warrior. (I hadn’t yet taken my plunge into early medieval northern Europe, a plunge I still haven’t come up from.) I got ahold of a copy with the movie tie-in cover and alternate title somewhere and started to read it.

My reaction, per Crichton’s later comments above, wasn’t so much irritable as bewildered—and slightly disturbed. What was this? A novel? A translation of a medieval manuscript? Are all these footnoted manuscripts real? Is any of it real? It couldn’t be real—I knew enough of the story already to know that—but if not then what was this thing?

Bewilderment

What’s funny is that, at the time I was reading Eaters of the Dead, I was doing much the same thing as Crichton. I just didn’t have it published. Besotted with half-formed pictures of the Middle Ages, my recent discovery of the riches of Dante, and certain artistic preoccupations that haven’t gone away (snow; almost all my books have snow in them), I was spending my free time hammering out line after line of an epic poem about the Teutonic Knights, a brutal war, and forbidden romance made the sweeter by vows faithfully kept—and liberally peppering the manuscript with footnotes, dates, alternate translations of contested terms, and excerpts of related text from other poets and chroniclers. I had discovered the fun part of scholarship, the digging and puzzle-piecing.

I finished high school and went on to college and Eaters of the Dead mostly receded from my mind. But some part of it, the part that had unconsciously jibed with my artistic and intellectual sensibilities, stayed on. While I had been confused and unimpressed with the book at first, I never hated or disdained it—a sure sign that there was something there I had missed.

Then 2020 happened, and to pass part of last summer teaching remotely and sheltering in place with family, I revisited it. Wow.

The story

Eaters of the Dead purports to be a translation of a text by Ahmad Ibn Fadlan, a real 10th century Arab courtier and diplomatic envoy. On a journey north (up the eastern side of the Caspian Sea to modern-day Russia) on behalf of the caliph in 922, Ibn Fadlan encounters a wild pagan people called the Rus or the Northmen. While staying with them he observes their customs, witnesses a chieftain’s funeral involving brutal human sacrifice, and is present for an emergency meeting following the arrival of a high-status messenger from the north.

eaters of the dead cover.png

The messenger is Wulfgar, son of King Rothgar, and he seeks the help of the local chieftain Buliwyf in dealing with a literally nameless threat. Ibn Fadlan observes the usually cheerful Northmen’s distress and foreboding and asks for an explanation, but his translators offer little and he senses it would be unwise to inquire much further. All he learns is that, in accordance with the decree of the Angel of Death, an elderly female shaman who had assisted in the sacrifice of a slave girl at the earlier funeral, he must go with Buliwyf and his warriors on their journey as a thirteenth, and foreign, member of the party.

Ibn Fadlan therefore unwillingly joins the Northmen on their long, circuitous trip northward by river. They portage between rivers, avoiding nameless threats in certain forests and riding as swiftly as possible through others, until they reach the Baltic and sail to Denmark. Finding Buliwyf’s home destroyed—again, by a threat the Northmen refuse to name or explain except to say that it comes with “the mists”—they journey on to Rothgar’s kingdom.

Everywhere in this kingdom there are signs of violent, grisly attack, and the only clues left behind by the attackers are grotesque figurines of uncertain meaning. Ibn Fadlan’s dread only grows.

Buliwyf and his men, including Ibn Fadlan, defend Rothgar’s hall against repeated attacks by a host of bearskin-clad savages that, Ibn Fadlan finally learns, are known as the wendol or “the mist monsters.” Short, ugly, stinking horribly, but powerfully built and apparently fearless, the wendol attack en masse, kill indiscriminately, and take the heads of their victims, never leaving any dead or wounded behind—until Buliwyf takes the arm of one of their number. The fighting is ugly and the losses heavy, and Ibn Fadlan is sorely tested. He also grows to admire the Northman and forms friendships with them, especially Herger, who interprets for Ibn Fadlan until the Arab can speak the language well enough to be understood. Ibn Fadlan also learns to drink and wench—a lot.

After an nighttime wendol attack in which the monsters assault the hall on horseback while carrying torches—an attack dubbed by the Northmen “the glowworm dragon Korgon”—Buliwyf and his band ride out in search of the wendol homeland across “the desert of dread,” visit a colony of dwarves living on the fringes of Northman society, and finally infiltrate the central wendol stronghold, where Buliwyf slays “the mother of the wendol” and is in turn mortally wounded by her. He holds out long enough to repulse a final, desperate wendol attack before he himself dies, and Ibn Fadlan witnesses a second, more moving funeral. The text ends abruptly as Ibn Fadlan journeys home.

The rest of the story

So much for the plot. If you’re just reading Eaters of the Dead for the story, you should finish it satisfied—it’s a real rip-snorting adventure tale, a classic quest full of exotic locales, strange customs, plenty of action, and a splash of horror.

But don’t some elements of that story sound familiar?

The movie tie-in edition I read in high school

The movie tie-in edition I read in high school

It’s Beowulf. Crichton, as he writes in “A Factual Note on Eaters of the Dead” included in some editions of the book, wrote Eaters of the Dead on a dare, as a demonstration that, viewed with fresh eyes or from a new angle, the “bores” of English literature survey classes are still exciting, dramatic, and meaningful.

To do so, Crichton took an actual text about a real journey by the real Ahmad Ibn Fadlan, deftly interwove elements of fiction into the early parts, and from the first funeral scene forward constructed an entirely new, fictitious story for the cosmopolitan Arab narrator. This story positions Ibn Fadlan as the foreign observer in a party of warriors led by a brave and charismatic nobleman responding to a crisis in a faraway kingdom beset by bloodthirsty attackers. Later, our reading of Ibn Fadlan implies, these events would become the story of Beowulf saving Hrothgar and his people from the depredations of Grendel.

All of this makes Eaters of the Dead, in addition to an adventure story:

  • a euhemeristic take on Beowulf, a “real” version of what happened “before” the development of the mythic one that has come down to us in the poem;

  • a parallel story, one retelling familiar events from a different perspective; and

  • a fictional book, a version of Ibn Fadlan that, according to the story, Crichton and previous scholars cobbled together from multiple fragmentary manuscripts in several languages.

There are plenty of other examples of all of these things, but what I notice about many others is their often po-faced ideological didacticism. Witness the recent rash of deconstructive parallel novels about “marginalized voices” (i.e. minor characters) in famous stories. What sets Eaters of the Dead apart from so many of these is how much fun it is. Not only is it, again, a rip-snorting adventure, but it’s a fun send-up of scholarship, containing as it does an introduction, information on the provenance of Ibn Fadlan manuscripts, parodically pedantic footnotes (some of them much longer than the passages they seek to illuminate), explanations of variant readings, a bibliography, and an appendix on the “predictable debate” surrounding the wendol.

Jazzing around

Crichton is—as John Gardner, author of another parallel novel about Beowulf, put it in one of his books on writing—“jazzing around.” And it’s a hoot.

It’s even more of a hoot if you know the period or something about history and anthropology generally. Crichton tucks away lots of “Easter eggs” as bonuses for those in the know to enjoy. He has Buliwyf’s party visit the ring fortress of Trelleborg, which Ibn Fadlan describes in unmistakable detail, and of course the wendol are relict headhunting Neanderthals who worship bears and shamanic fertility goddesses, as evidenced by the instantly recognizable figurines they leave behind.

This is an anachronism stew—whatever historical events lie behind Beowulf probably occurred in the 6th century and Trelleborg wasn’t built until at least sixty years after Ibn Fadlan’s real journey, and that’s not even to address the survival of Neanderthals—and Crichton admits as much in his “Factual Note.” What makes all of these things fun is the little thrill of recognition you get when they come along, a bit of authorial irony that stays fun by never coming at the characters’ expense. Crichton knows and enjoys this stuff and wants us to play along.

Again—jazzing around.

What was most remarkable to me about Eaters of the Dead, as I reread it last year and listened to the audiobook this week, is how many levels it works on. It’s a satisfying historical action adventure. It’s a genuinely creepy horror story, with a carefully structured buildup and wonderful atmosphere and tension. It’s an engaging, vividly imagined, and just-barely-realistic-enough science-fiction story—the kind of book Crichton would become famous for—pitting Vikings against prehistoric headhunters. It’s a fun—and sometimes hilarious—pastiche of modern scholarship. And it is, in the end, a great celebration of Beowulf, definitive proof of Crichton’s assertion that great literature isn’t boring.

It took me twenty years to grow into, to see what Crichton was doing and to enjoy it, but I’m thankful that I did. Check out Eaters of the Dead sometime soon and see what level it works on for you.

More if you’re interested

There is, of course, the film adaptation, The 13th Warrior, which I haven’t watched since high school and can’t really comment on except to say that it has one of the best cinematic attempts to tackle the language barrier I’ve seen. I intend to rewatch it soon.

You can read the real Ibn Fadlan’s account of his travels among the Rus in a recent translation for Penguin Classics, Ibn Fadlan and the Land of Darkness: Arab Travellers in the Far North. Jackson Crawford has an excellent short video on the “Viking funeral” witnessed by Ibn Fadlan, described in his writings, and dramatized in both Eaters of the Dead and its film adaptation, The 13th Warrior. You can watch that here.

I reread Eaters of the Dead for the first time since high school last year. As I mentioned above, I just revisited it again in the form of Simon Vance’s excellent audiobook performance. Vance narrates Ibn Fadlan with a slight accent, which actually sounds more Indian than Arab but that helps differentiate Ibn Fadlan’s narration from the footnotes. I didn’t know how well this work work going into it, but I greatly enjoyed it.

Likelihood: an addendum

Yesterday I started reading David Horspool’s entry in the Penguin Monarchs series, Cromwell: The Protector. So far it’s excellent. Considering my recent meditation here about “likelihood” and imagination in historical interpretation and writing, I found this aside (emphasis mine below) particularly striking:

Cromwell’s early biographers, permanently on the lookout for signs of future greatness, seized on the story of a childhood encounter between the young Oliver and the future Charles I, James’s son, on one of these royal visits to Hinchingbrooke. Naturally, the toddler-prince and his slightly older nemesis are meant to have fought at this play-date pregnant with historical significance, and Oliver is meant to have won. If the tale is too good to be true (which is no argument against its being true), then it is still a reminder that, as a guest in his uncle’s house, the young Oliver is likely to have been in the presence of royalty. Despite the gulf in upbringing and expectation that separated Prince Charles and Oliver Cromwell, they did not occupy entirely different worlds.

This is an eminently sensible approach.

I don’t know if it’s the postmodern or literary turn of historical interpretation, deconstructionism, or the generalized hermeneutic of suspicion pervading everything today, but the common assumption about textual evidence seems to be that if a source draws a didactic lesson from an incident, or if an incident conforms to a literary pattern, or has parallels to a commonly known story from the time the source was written down, the incident can and must be treated as invented.

I think that approach is wrong, not only for the reasons of enjoyability and interest—or pure oddity and surprise—that I’ve already written about, but for implicit human reasons: this is not how we experience our own lives. We constantly tell others about odd or surprising things that have happened to us, and we very often enlist shared stories for comparison’s sake. (There was a time in my life when everything that happened to a friend and I was fitted into an incident from “The Office.”) And of course we revisit our memories—finding foreshadowing after the fact in light of later events or drawing lessons from the things that have happened since—all the time. Identifying every instance of these natural human traits as fiction or lies not only betrays and demeans our ancestors, it leaves us with very little to work with.

But then again, based on the way history is used and abused these days, that’s probably the point.