Showing posts with label Dennis Lehane. Show all posts
Showing posts with label Dennis Lehane. Show all posts

Wednesday, May 15, 2013

Why Gatsby makes a lousy movie


by Sandra Parshall

Filmmakers seem to think they can make a good movie out of anything, and they aren’t deterred by past unsuccessful efforts with the the same book.


The Great Gatsby is the latest example of this triumph of ego over material. It was made into a movie in 1926, the year after the book was published, and was filmed again in 1949 and 1974, then turned into a TV movie in 2001. Did those lackluster adaptations deter Baz Luhrmann, the Australian master of gaudy spectacle? Did he study them to determine the reason why the book simply will not come to full-bodied life on the screen? Apparently not, because he went right ahead and made all the same mistakes, only more so.

Everyone is seduced by the beauty of F. Scott Fitzgerald’s narrative prose. Six passages from the novel, including the unforgettable final line, appear in Bartlett’s Familiar Quotations. But the dialogue, transferred to screenplays word for word, is virtually impossible for actors to speak convincingly. The performances in Luhrmann’s film are almost embarrassing to watch. I have never seen so much wooden acting outside of a high school drama production. Surely the director is partly to blame for the falseness of it all, the stiff delivery, but honestly, what can any actor do with Fitzgerald’s dialogue? People simply don’t talk that way.

The only time a genuine performance threatens to break free of the script’s constraints is when Leonardo DiCaprio, as Gatsby, explodes in the hotel room scene and grabs Daisy’s husband Tom, ready to kill him. Red-faced and snorting like a bull, DiCaprio is, for at least thirty seconds, mesmerizing. Alas, it doesn’t last, it can’t last, because the script must remain faithful to the book. The accident scene that follows is unaffecting because the characters haven’t become real on the screen.

Add Luhrmann’s taste for excess to the book’s inherent flaws, and you’ve got a sparkling, dazzling mess.

The novel is revered – perhaps more than it should be – not only for Fitzgerald’s lyrical narrative style but also because it captures the amoral, culturally hollow lives of a certain social set in the years before the stock market crash brought on the Great Depression. Gatsby, born poor, has done what a lot of Americans have: reinvented himself in the process of amassing a fortune. But Gatsby is not admirable. The driving force behind his ambition is his desire to reclaim a woman who is not in any way worthy of love. Daisy is selfish and shallow, willing to sacrifice anyone to preserve her own easy life, and Gatsby is a pathetic fool for loving her. That is perhaps the novel’s greatest weakness, and the reason it doesn’t translate well to film: the characters are despicable. The story is a dark tale of destruction, with no hero and no heroine. 


A gifted writer can keep readers engaged with such characters in a novel. Put those characters on screen, in the form of real, breathing human beings, make them speak dialogue that is awkward at best, and it’s hard to persuade the viewer care about them. (I couldn’t help hoping Daisy and her husband would end up penniless when the stock market crashed.)

Compare Gatsby to Mystic River, a great novel that was made into a great film. Dennis Lehane’s characters are so real that we recognize bits of ourselves in them. They may be flawed, sometimes profoundly, but they are always struggling to be better than they are, and even when they do the wrong thing we can understand and sympathize. It doesn’t hurt that Lehane writes pitch-perfect dialogue and it moves to the screen without a glitch.


Mystic River has what The Great Gatsby lacks: genuine emotion, so deep that it haunts you long after the story ends. 
********************************
Note: When Fitzgerald saw The Great Gatsby's original cover art, shown above, he liked it so much that he added the optometrist's billboard, showing a pair of eyes, to the story. The novel received mixed reviews and sold poorly. It is now a staple of American literature courses. Recently it passed out of copyright and is now in the public domain.

Friday, December 28, 2012

Sometimes There Is No Why

by Sheila Connolly


Recently the wildly successful mystery writer Lee Child wrote an op-ed piece for the New York Times, titled "A Simple Way to Create Suspense."  While what I write is hardly similar to his books, what he said made a lot of sense to me.  It can be boiled down to this:  Ask a question. Then don't answer it.

At a regional conference, Dennis Lehane recently spoke about a related idea.  As an example, he suggested beginning a book with the protagonist—call him Joe—opening the refrigerator trying to decide what to eat.  Immediately we want to know:  what did Joe decide?  If the author never tells the reader what Joe ate for lunch, we feel cheated, because we humans are hardwired to look for answers.

In both Child's and Lehane's examples, the opening question, trivial or not, creates a sense of tension.  Child takes it a step further by deliberately withholding the answer.  As he wrote,


        "Someone killed someone else:  who? You'll find out at the end of the book.  Something weird is happening:  what?  You'll find out at the end of the book.  Something has to be stopped:  how?  You'll find out at the end of the book."

Keeps you reading, doesn't it?

This is something my editor and I have been wrestling with in the edits for my next Museum Mystery, Monument to the Dead.  Someone dies in Chapter 1, but it seems to be a natural death.  Then other people are identified as having died the same way, but all were called natural deaths.  Question 1:  are these deaths natural, or is someone killing them?  There is no evidence of murder, and nobody has investigated these deaths.

But to say they were murdered, someone has to ask:  why?  Who would want these people dead? There's no obvious reason for killing them.  So my protagonist and her allies go to work trying to find links between them.  And they do find a primary connection, but that doesn't explain the "why". That's because the "why" makes sense only to the killer, and it's not obvious to anyone else.

My editor (with whom I have worked on many books) wants to make this a more typical cozy, with a body up front (got that), and a cast of likely suspects who are first to be identified and then eliminated one by one.  I don't have that. There is really only one person who would have a motive for killing these people, and it takes the whole book to identify that person (and it's my protagonist's very specific knowledge that finally points to the killer).

I read an official FBI report on serial killers that states that motive is not the first thing an investigator should look for. FBI profilers caution against working to identify motive rather than looking for the killer.  And in most cases that makes sense. Follow the evidence first.

But I'm trying to twist it around in my book, because there is very little physical evidence to be had:  the victims are long buried, the autopsies cursory, the crime scenes cleaned up.  For me, the "why" is the important question. And I do give an answer.

The tragic recent events have left everyone asking "why?"  Why would anyone decide one day to start killing innocent children he didn't even know? Why would some guy set his house on fire and start shooting at anyone who came to put the fire out? Investigators are digging for every piece of family history, where the weapons came from, et cetera, et cetera, and reporting every shred of tangible evidence to the hungry press—because people want that "why." 

But what if the "why" is never answered?  Lee Child has got it right: we want the answer.  These awful events will linger in our memories, because that missing "why" will haunt us.


Lee Child, me, and this other guy


Friday, October 19, 2012

Storytelling

by Sheila Connolly


This week I heard Dennis Lehane speak to a packed hall—of librarians, not writers, at the New England Library Association conference.  I've crossed paths with him before, at the late-lamented Kate's Mystery Books in Cambridge, and at the New England Crime Bake, but I've never heard him give a speech.  Now I know what I've missed.
 
 
Lehane admits that he was an unlikely candidate to become a writer, based on his upbringing in some of the rougher parts of Boston.  But writing does not always emerge from book-learning, although he always loved reading, even when that was scorned by his classmates.  Or more precisely, male ones; the women found it appealing that this tough kid could quote Shakespeare and actually write books. That alone was a good incentive to pursue a literary career.

 
But I don't intend to write a biographical tribute to a writer, even one I admire.  What pleased me was I can still learn something about what makes a writer, and Lehane made his case convincingly. 

 
The part of his talk that resonated most with me was Lehane's description of his (large) Irish family and how they interacted with one another.  The members of the extended family (if I heard it right, his father was one of 17 children, his mother one of 14) all spent a lot of time together when he was growing up, and they, or at least the men, were all prodigious tellers of tales.  Moreover, those tales were often repeated within the family gatherings (Lehane estimated about every five to six weeks the story cycle would begin again).  But what was noteworthy to him was that the tales changed with each telling, just a bit, as they were polished and honed with repetition.  Now, you'd think that family members who had heard the same telling dozens of times before would notice this, but the important point was, it was the telling of the story that mattered, not the truth of it.

 
And that statement says so much about Irish tradition, or at least what I know of it.  The Irish people have a long tradition of oral storytelling.  The seanchaĆ­  fulfilled a dual role as both storytellers and historians—guardians of a culture that was often imperiled by British rule. Some may have been the designated member of a given clan or family (remember, families in Ireland in the 19th century or earlier seldom strayed far from their origins, so effectively they functioned as an oral archivist); others were itinerant, and offered up entertainment, given a meal and a place to sleep as they passed from townland to townland, in exchange for their stories. 

 
Is the art—or craft?—of this storytelling an historical artifact of a dwindling culture, or it is something innate in the sons and daughters of Ireland?  Lehane didn't address that issue, nor did he wax eloquent about his literary heritage.  Instead, what he took away from all those family gatherings (and later, gatherings of like-minded strangers in friendly bars) was the love of words, of the spinning of a tale, of drawing in an audience who had heard it all before and making it new for them. I'll let you decide whether he used wisely what he learned (I'd say yes!).