Alec Nevala-Lee

Thoughts on art, creativity, and the writing life.

Posts Tagged ‘The English Patient

“Three years earlier…”

leave a comment »

"Three years earlier..."

Note: This post is the twenty-seventh installment in my author’s commentary for Eternal Empire, covering Chapter 26. You can read the previous installments here.

Of all the tidbits of writing advice I’ve picked up over the years, one I never tire of quoting comes courtesy of the legendary pulp novelist Jack Woodford. In his classic book Trial and Error—which manages to be both a useful writer’s manual and a gem of self-promotion—Woodford says:

The trouble with most first short stories is that they have their beginnings buried in their middles. Take up the thousand word short story you have written and read down until you come to the first dialogue or objective action.

Now, start reading all over again, beginning the story as though that first bit of action or dialogue were the start of the story. Read along for two or three hundred words while the action and dialogue continue, until you come to the point where you have again resorted to expository writing—that is, to telling the reader something, rather than to portraying the material in narrative or dramatic form. At this point, insert all of that material which went before the first action or dialogue. Write an additional sentence or two of transition, in between the dialogue and action section and the expository section. Retype the story, with the middle at the beginning, the beginning at the middle, and the ending where it was in the first place. Now you need no longer wail, “But I don’t know how to start a story!”

To my eye, this is what a writing tip should be: practical, immediately applicable, and just a little mechanical. Putting it into practice is a matter of copying and pasting. If it works, great; if not, it’s easy to reverse it. But what strikes me the most about it now is that although Woodford is talking about how to start a story, when you generalize it, it’s really a rule about flashbacks. I’ve always seen flashbacks as a dangerous tool: they interrupt what ought to be a continuous flow of action, whether internal or external, and offer the temptation to spend time on backstory, rather than revealing character through action. But they also have their uses. As Woodford notes, you usually want to get the story moving in the very first sentence, and a flashback can be used, paradoxically, to enable narrative momentum by placing the exposition at a point where the plot can sustain it. When you follow Woodford’s approach, you find that the flashback naturally appears during an organic pause, where the plot has to regroup to take a breather anyway. All stories, if they aren’t going to exhaust the reader, need a few stretches of relative flatness to balance out the high points, and it’s valuable real estate. If you find that you really need a flashback—if only because the backstory would be more vivid or interesting if clustered in a single unit, rather than dispersed—then it probably belongs at a moment when the story can afford to slow down.

"They regarded each other in silence..."

And like most useful writing tools, a flashback can be perform a double duty, inserting a moment of delay where it increases the suspense. Elsewhere, I’ve used the movie Snowpiercer as an example: just before the protagonist is about to reach the end of his violent quest, he pauses, lights a cigarette, and tells us a little about himself for the first time. Anywhere else, and the speech would have seemed like a misstep; here, it both postpones the climax at a point of maximum tension and reminds us of the stakes involved at just the right moment. Snowpiercer may be the most relentlessly linear action movie I’ve ever seen—it tracks the hero’s progress from one train compartment to another, so that his movement through physical space exactly parallels the structure of the story—and it cleverly places what amounts to a flashback at the only spot where it wouldn’t interrupt the plot’s forward motion. But even more loosely constructed stories can benefit from its example. Not every narrative needs to move singlemindledly from A to B, and in certain exceptional works, like The English Patient or Citizen Kane, the movement between past and present and back again can almost become a character in itself. But chronological order is the baseline from which we depart only with good reason. And those departures work best when they occur in places where the rhythm allows for a regathering.

The flashback that opens Part II of Eternal Empire is an interesting case, because it was written long after the rest of the novel was complete. My editor had suggested clarifying the relationship between Maddy and Ilya, which otherwise depends mostly on the reader’s knowledge of The Icon Thief, and I realized that she had a good point: much of the action of the novel’s second half hinges on the evolving understanding between these two characters. It also gave me a chance to revisit a piece of the story that the previous books had left unexplored. And because the novel was already so tightly structured, it made sense to stick it here. Last week, I noted that I usually start any writing project with three or four big twists in mind, and I’ll outline the book so that each of these occur at the end of a section. As a result, the beginning of the next section benefits from the residual momentum that the previous climax has generated. Inserting the flashback here put it at a point where I could trust that the reader, having come this far, would at least make it through the next few pages, and it provided a useful way of delaying the resolution of the previous scene, which ended with the hood coming down over Maddy’s head. It wasn’t part of my original conception, but once it was there, it seemed to strengthen, rather than weaken, the surrounding material. And when we catch up with Maddy again, waiting in the back of the car for whatever is coming next, we know exactly what brought her there…

Written by nevalalee

July 16, 2015 at 9:57 am

The limitations of technique

leave a comment »

Recently, as I prepare to make the last round of cuts and revisions to my third novel, I’ve been reading one of my favorite books, Charles Koppelman’s Behind the Seen. The book’s rather cumbersome subtitle is How Walter Murch Edited Cold Mountain Using Apple’s Final Cut Pro and What This Means for Cinema, and while this may not sound like a page-turner to most people, it’s one of the five or six best books on film I know. As I’ve made clear before, Walter Murch—the man whom David Thomson describes as “the scholar, gentleman, and superb craftsman of modern film,” and whom Lawrence Weschler calls, more simply, “the smartest man in America”—is one of my heroes, and for those who are interested in narrative and technical craft of any kind, this book is a treasure trove. Yet here’s the thing: I don’t much care for Cold Mountain itself. I watched it dutifully when I first read the book, and although I’ve since revisited Koppelman’s account of Murch’s editing process countless times, nothing of the actual movie has lingered in my memory. I was startled last night, for instance, to realize that Philip Seymour Hoffman plays an important supporting character: his performance, like the rest of the movie, has simply melted away.

This paradox grows all the stronger when we examine the rest of Murch’s filmography. The English Patient, as I’ve said elsewhere, is an intelligent movie of impressive texture and skill, and Murch deserved the two Oscars he won for it. But as with Cold Mountain, I can barely remember anything about it, with only a handful of images left behind even after two viewings. I couldn’t get more than halfway through Hemingway & Gellhorn, despite being fascinated by Murch’s account of his work on it at last year’s Chicago Humanities Festival. Murch has worked as a sound designer on many great movies, above all Apocalypse Now, but when it comes to his primary work as an editor, his only unqualified masterpiece remains The Conversation. (As strange as it sounds, of all the movies that he’s edited, the one I enjoy the most is probably The Godfather Part III.) I have no doubt that Murch approached all these projects with the same care, diligence, and ingenuity that shines through all of his published work and interviews, but in movie after movie, that last extra piece of inspiration, the one that might have given a film a permanent place in my imagination, just isn’t there.

Part of this may be due to the inherent limitations of an editor’s role, since even the most inventive and resourceful editor is ultimately constrained by the material at hand and the quality of his collaborators. But I prefer to think of it, in a larger sense, as a warning about the limits of technique. Movies, for the most part, are technically wonderful, and they’ve been advancing along all the dimensions of craft—cinematography, sound, art direction—since the invention of the medium. Progress in art is never linear, but with respect to craft, progress is continuous and ongoing, with each generation adding to its predecessor’s bag of tricks, and as a result, movies look and sound better now than they ever have before. Moreover, nearly without exception, professionals in film are good at their jobs. Even the directors we love to hate, like Michael Bay, arrived at their position after a fierce process of natural selection, and in the end, only the most tremendously talented and driven artists survive. (Bay, alas, has one of the greatest eyes in movies.) Not everyone can be as articulate or intelligent as Murch, but for the most part, movies these days, on a technical level, are the product of loving craftsmanship.

So why are most movies so bad? It has nothing to do with technique, and everything to do with the factors that even the greatest craftsmen can’t entirely control. When you look at a student project from any of our major film schools, the technical aspects—the lighting, the camerawork, even the acting—are generally excellent. It’s the stories that aren’t very good. For all the tricks that storytellers have accumulated and shared over a century of making movies, decent scripts are either tantalizingly elusive or destroyed along the way by the hands of studio executives—which is one role in the movie business where talent does not tend to rise to the top. And the proof is everywhere, from John Carter on down. If there’s one movie artist who rivals Murch for his intelligence, good advice, and willingness to discuss aspects of his craft, it’s screenwriter William Goldman, who hasn’t written a movie since Dreamcatcher. Technique only gets you so far; the rest is a mystery. And even Murch understands this. On the wall of his editing studio, we’re told, hangs a brass “B.” Koppelman explains what it means: “Work hard to get the best grade you can—in this world, a B is all that is humanly attainable…Getting an A? That depends on good timing and the whims of the gods.”

A year’s worth of reading

with 3 comments

These days, I’m fortunate enough to have more work than I can handle, which also means that I no longer have much time to read for my own pleasure. The past year, in particular, was all business: I had just over nine months to take City of Exiles from conception to final draft, along with a number of other projects, which meant that nearly all my free time was devoted to either writing or research. All the same, I managed to make time to read a number of books that didn’t have anything to do with my work, either in my spare moments, on vacation, or in parallel with writing the novel itself. (Like many writers, I like to read a few pages of an author I admire before starting work for the day, which means that I tend to read books in piecemeal over the course of many weeks or months.) And while I doubt I’ll ever return to being the sort of omnivorous reader I was growing up, it’s still important to me to read as much as possible, both for professional reasons and for the sake of my own sanity.

Much of this year was spent catching up on books that I’d been meaning to read for a long time. The best book I read this year, by far, was The Magic Mountain by Thomas Mann, which seems likely to stand as one of my ten favorite novels, followed close behind by Catch-22, which really does deserve its reputation as the most inventive comic novel of the twentieth century. Turning to slightly more recent books, I was able to catch up on such disparate works as The English Patient, Cloud Atlas, and The Time Traveler’s Wife, all of which I admired. Of these, the two that retain the strongest hold on my imagination are John Crowley’s Little, Big, despite my mixed feelings on reading it for the first time, and J.M. Coetzee’s Disgrace, which strikes me as one of the most perfect of all recent novels. More disappointing were London Fields, Updike’s Terrorist, and, somewhat to my surprise, A Confederacy of Dunces, which I found clumsy and only intermittently engaging, despite its reputation as a classic.

Of books published in the last few years, my reading consisted mostly of nonfiction, despite my nagging resolve to read more contemporary novels. I greatly enjoyed The Immortal Life of Henrietta Lacks by Rebecca Skloot, which is a model of both popular science and investigative journalism. Like everybody else, I bought and read Steve Jobs by Walter Isaacson, which is short on analysis but long on fascination—more a gold mine of material than a real portrait, but still an essential document. I read The New York Regional Mormon Singles Halloween Dance by Elna Baker partly as background material for my novel, but was ultimately won over by Baker’s genuine wit and candor—it’s one of the funniest books I’ve read in a long time. And although The Possessed by Elif Batuman was a little thin, like a selection of essays in search of a theme, it made me curious to see what she’ll do next, given a more substantial project.

As for the coming year, as before, I expect that most of my time will be spent on background reading and research. Still, I have a few other authors I’ve been meaning to try. I’m going to read DeLillo for the first time, probably starting with Underworld, and then the later Philip Roth, beginning with American Pastoral. If I’m feeling really ambitious, I’ll tackle Faulkner, Morrison, and Perec’s Life: A User’s Manual as well. Above all else, I’m going to make a concerted effort to read more contemporary fiction. A glance at the bookshelves in the next room—the property of my wife, who is a much better reader than I am—reveals such titles as A Visit From the Goon Squad, Swamplandia!, and The Magicians, all of which have been beckoning to me for some time now. These days, of course, even my leisure reading has something mercenary about it, as I look for tricks and techniques to borrow or steal. As the year goes on, then, I hope to have a chance to talk more about these books, and if all goes well, I’ll have a few useful things to share, too.

Fiction into film: The English Patient

with 4 comments

A few months ago, after greatly enjoying The Conversations, Michael Ondaatje’s delightful book-length interview with Walter Murch, I decided to read Ondaatje’s The English Patient for the first time. I went through it very slowly, only a handful of pages each day, in parallel with my own work on the sequel to The Icon Thief. Upon finishing it last week, I was deeply impressed, not just by the writing, which had drawn me to the book in the first place, but also by the novel’s structural ingenuity—derived, Ondaatje says, from a long process of rewriting and revision—and the richness of its research. This is one of the few novels where detailed historical background has been integrated seamlessly into the poetry of the story itself, and it reflects a real, uniquely novelistic curiosity about other times and places. It’s a great book.

Reading The English Patient also made me want to check out the movie, which I hadn’t seen in more than a decade, when I watched it as part of a special screening for a college course. I recalled admiring it, although in a rather detached way, and found that I didn’t remember much about the story, aside from a few moments and images (and the phrase “suprasternal notch”). But I sensed it would be worth revisiting, both because I’d just finished the book and because I’ve become deeply interested, over the past few years, in the career of editor Walter Murch. Murch is one of film’s last true polymaths, an enormously intelligent man who just happened to settle into editing and sound design, and The English Patient, for which he won two Oscars (including the first ever awarded for a digitally edited movie), is a landmark in his career. It was with a great deal of interest, then, that I watched the film again last night.

First, the good news. The adaptation, by director Anthony Minghella, is very intelligently done. It was probably impossible to film Ondaatje’s full story, with its impressionistic collage of lives and memories, in any kind of commercially viable way, so the decision was wisely made to focus on the central romantic episode, the doomed love affair between Almásy (Ralph Fiennes) and Katherine Clifton (Kristin Scott Thomas). Doing so involved inventing a lot of new, explicitly cinematic material, some satisfying (the car crash and sandstorm in the desert), some less so (Almásy’s melodramatic escape from the prison train). The film also makes the stakes more personal: the mission of Caravaggio (Willem Dafoe) is less about simple fact-finding, as it was in the book, than about revenge. And the new ending, with Almásy silently asking Hana (Juliette Binoche) to end his life, gives the film a sense of resolution that the book deliberately lacks.

These changes, while extensive, are smartly done, and they respect the book while acknowledging its limitations as source material. As Roger Ebert points out in his review of Apocalypse Now, another milestone in Murch’s career, movies aren’t very good at conveying abstract ideas, but they’re great for showing us “the look of a battle, the expression on a face, the mood of a country.” On this level, The English Patient sustains comparison with the works of David Lean, with a greater interest in women, and remains, as David Thomson says, “one of the most deeply textured of films.” Murch’s work, in particular, is astonishing, and the level of craft on display here is very impressive.

Yet the pieces don’t quite come together. The novel’s tentative, intellectual nature, which the adaptation doesn’t try to match, infects the movie as well. It feels like an art film that has willed itself into being an epic romance, when in fact the great epic romances need to be a little vulgar—just look at Gone With the Wind. Doomed romances may obsess their participants in real life, but in fiction, seen from the outside, they can seem silly or absurd. The English Patient understands a great deal about the craft of the romantic epic, the genre in which it has chosen to plant itself, but nothing of its absurdity. In the end, it’s just too intelligent, too beautifully made, to move us on more than an abstract level. It’s a heroic effort; I just wish it were something a little more, or a lot less.

Michael Ondaatje on first drafts

with 2 comments

There are some writers who have a plan before they sit down for those years of writing a book—they have a concept or plot that’s very certain. These are good writers, who know exactly how the story will end. I seem to have none of those assurances. I’m much more uncertain, insecure almost in the way that I’m continually being fed and diverted by the possibilities from the world around me—chance anecdotes overhead, the texture within a rumour—as much as by what my research reveals. For those four or five years, I collect such things, and they fall into a form or a shape or a situation I have established…the final stages of the war in Italy, the preparation for death by a gunfighter

I do this until I have a complete but rough first draft, by which time I’ve essentially discovered the story. I then put on a different hat…and I start eliminating the wrong notes, the repetitions, the trails that go nowhere. I start merging and tightening the work…at this stage three scenes can become one. I take this process as far as I can. There are numerous drafts…Eventually I try it out on my peers and my editor, and I try not to be too defensive about the work. I don’t always agree with them, but their responses and notes are an essential stage for me. The only way I can get that democratic, communal sense is to be not so sure about what I have done. But it is also important that I don’t show them the work until that stage is reached, until I’ve taken it as far as I can go. I don’t want their influence to come too early in the process after my discovery of the story and the form.

Michael Ondaatje, The Conversations

Written by nevalalee

March 20, 2011 at 9:49 am

What I read when I’m writing

leave a comment »

When Norman Mailer was writing The Naked and the Dead, the novel that made him famous at age twenty-five, he had a simple method for getting ready to work in the morning. Mailer says:

I had four books on my desk all the time I was writing: Anna Karenina, Of Time and the River, U.S.A., and Studs Lonigan. And whenever I wanted to get in the mood to write I’d read one of them. The atmosphere of The Naked and the Dead, the overspirit, is Tolstoyan; the rococo comes out of Dos Passos; the fundamental, slogging style from Farrell, and the occasional overrich descriptions from Wolfe.

And Mailer isn’t the only writer who kept a few favorite books on his desk. I imagine that many novelists have books that they keep at the ready for when they feel inspiration starting to flag. Sometimes it’s the same book over the course of an entire career; more often, I suspect, it varies from project to project. In my own case, I start each writing day by reading a few pages of a book that embodies the tone or voice I’m trying to achieve—as if something of the author’s talent will magically transmit itself—and return to it more than once as I continue to work. And rather to my surprise, when it comes to the novels I read while writing, I find myself sticking to a limited, strictly defined circle of books.

As I mentioned yesterday, I generally do a fast, rough draft of an entire chapter first thing in the morning, which usually takes a couple of hours. I’ve found from experience that the best books to read while I’m doing that messy initial version are rich, ripe, stylistically powerful books that encourage my own writing to be a little more florid—qualities that I pare down relentlessly in subsequent revisions, but which are often good to have in a first draft, where the point is to get as many ideas or images onto the page as possible. For me, the ideal author for this purpose is John Updike. Our styles as writers couldn’t be more different, but something in his ornate sentences just puts my brain to work. (It’s the Heist school of writing: I imagine a writer better than I am, then figure out what he would do.)

At the moment, then, I’m starting each morning with a few pages of Updike’s Terrorist. Later in the day, though, when I’m polishing what I’ve already written, I feel that it’s a mistake to read something so dense and mannered, because I run the risk of ending up with mere self-indulgence (a quality to which even Updike himself isn’t immune). For later drafts, it’s better to go with an author whose prose is a little more restrained, clean, and elegant—someone like Ian McEwan, say. While writing Kamera, I worked my way through Atonement, Amsterdam, Saturday, The Innocent, Black Dogs, and The Comfort of Strangers. Right now, since I’ve already read all the McEwan I own, I’m doing something similar with Michael Ondaatje’s The English Patient, which has the kind of spare, classical style that I’m hoping will restrain the worst of my impulses.

There’s a negative side to all this, too. While I’m writing, I avoid books that I think will noticeably infect my style, for better or worse. This includes bad books, of course, but also good novels where the author’s style clashes with mine. I also try to avoid books in translation, reasoning that it’s better to read books by great stylists who originally wrote in my own language. The problem? Since I’m always writing, my reading for the past few years has been extremely constrained. I haven’t read Cloud Atlas, for instance, because I’m afraid of being overly influenced by it, and because I don’t want to read anything in translation, I haven’t gotten around to Mario Vargas Llosa, among many others.

Obviously, this state of affairs can’t stand: as much as I like Updike and McEwan, I don’t want to be stuck with them for the rest of my life. And reading and being influenced by radically different authors is an important part of growing as a novelist. At some point, then, I’ll probably need to rethink this approach. (Although not until I finish this draft.)

%d bloggers like this: