Showing posts with label writing. Show all posts
Showing posts with label writing. Show all posts

Monday, August 22, 2011

Love, Revenge and Conan: What's My Motivation?

NOTE: THIS IS THE NEXT-TO-LAST POST FOR THIS LOCATION. AT THE END OF AUGUST, THIS BLOG WILL NO LONGER BE UPDATED. MY BLOG WILL BE FOUND AT MY NEWLY-REVAMPED WEBSITE, ALEX BLEDSOE.COM.

So there's a new Conan movie. And, if the previews are any indication, Conan spends the movie on a quest for revenge against the villain(s) who destroyed his village and murdered his family.

I won't go into how many ways this deviates from the original Robert E. Howard character (short answer: a lot). Instead, it got me thinking about screenwriters and how they think.

Consider the idea of "motivation." In movies, heroes are usually motivated by either love or revenge. And they must have a definite, solid, entirely personal reason for doing anything. I first became conscious of this trope watching The Skeleton Key, eighty percent of a great horror movie. Caroline, played by Kate Hudson, talks about how she became a geriatrics nurse after watching an elderly relative slowly die from Alzheimer's.


"Ah-HA! My motivation! Now I can act!"

Really? So she couldn't be a person who looked at possible careers and chose one that sounded good, or wanted to have a job with security, or any of the reasons most of us choose our jobs? No, there had to be a hyper-dramatic, entirely personal reason so that the audience will "sympathize" with her.

Giving Caroline such a background smacks of a "Screenwriting for Dummies" lesson. Sure, characters need motivation. But screenwriters seem unable to accept that "earning a paycheck," "providing for my family" or most crucially "the satisfaction of a job well done" are acceptable motivations. If the line "this time it's personal" doesn't apply, then it isn't valid.

Except that it is.

Here are two examples from the work of Oscar-winning director/screenwriter William Friedkin. In his 1986 film To Live and Die in L.A., FBI agent Richard Chance (CSI's William Petersen) sets out to bring down villain Rick Masters (Willem Dafoe) after Masters kills his partner. He even blatantly states, "I'm gonna bag Masters, and I don't give a shit how I do it." It's a textbook--well, a screenwriting textbook--character motivation. This time it's personal, and it encompasses both love (of the bromance kind) and revenge. It keeps an otherwise excellent movie from being truly great.



Conversely, in Friedkin's 1971 film The French Connection, New York cop Popeye Doyle (Gene Hackman) stays tenaciously on the villain's tail because, simply, it's his job. He needs no ulterior motive, nothing that says "this time it's personal." Through the course of the story it becomes personal, but only because the villain's success reflects badly on his professionalism. His ego is tied to his job, and he simply can't let the bad guys win. There's no hint that a childhood trauma caused this, or that a gangster (or Frenchman) once killed his family, or any sort of trite justification. It's realistic, and it's one of the elements that helps make the film a classic.



There are many useful things novelists can learn from screenwriters: get to the point, keep the action moving, craft witty dialogue and so forth. But this is one lesson they should skip. So make sure that you take away the right lessons, and stay grounded in reality where there are many other motivations besides love and revenge.

But....

As I read over the above, I realized my perspective is entirely one-sided. So for another point of view, I asked writer and USC film graduate Melissa Olson to comment on what I'd written so far. She responded:

"When I was at USC, nobody dreamed of being the next Michael Bay (well, maybe in the directing track(:). Everyone dreamed of telling the story they wanted to tell, to make the statement they wanted to make. But once you get out of school, the film industry is a tough business.

"Screenwriting is complicated, and in many ways it’s much more restrictive than novels. Maybe the screenwriters of
Conan (there were three) didn’t want the movie to be about motivation; they wanted to get that out of the way and tell a different story. Shortcuts aren’t terrible things, they’re just easy ways out. Sometimes you gotta take one to get to where you want to go."

So there's two sides to this. What do you, the reader/filmgoer, think?

Monday, August 1, 2011

Genre respect and the NYT

It's an ongoing issue that genre fiction--mystery, science fiction, fantasy, romance, horror--is somehow less important than so-called "literary" fiction. That involves forgetting that in many cases the disposable genre fiction of yesterday (Jules Verne, HG Wells, Edgar Allen Poe, HP Lovecraft, Louis L'Amour, Jack London, Dashiell Hammett, Raymond Chandler) has become the acknowledged classics of today.

Still, it's frustrating to still see this play out right in front of me, as it did last month in the New York Times. I won't use the authors' names here, because it's not important; it's not hard to figure out if you feel the need, but it's utterly beside the point. To me, what's important is how this "corps of impudent snobs who characterize themselves as intellectuals" (props to Spiro Agnew) pronounces and supports its judgment.

Here are two excerpts from the literary novel's review:

"So does the new novel deliver? I’m not so sure...the author seems a bit lost, adrift in unfamiliar waters, and the book feels less like a second novel than it does another try at a first."

"There is only so much we can read this way before we are overwhelmed by the desire to drop the pretense."


And here are two from the review of the genre novel:

"[The author's] novel has the stylized quality of books by Angela Carter like The Infernal Desire Machines of Doctor Hoffman, and it displays similar pyrotechnics."

"Yet in a highwire act of her own, [the author] still raises the novel above the ordinary through her ability to convey the richness of the [characters’] emotional lives, coupled with impressive writing."


Clearly the first review was less than positive, while the second was close to a rave. Now, the kicker: which book got the three-page excerpt also published in the New York Times? That's right, after their reviewer says "There is only so much we can read this way before we are overwhelmed by the desire to drop the pretense," the Times decides to put that to the test.

As I said, I mean no disrespect to either writer. I do mean disrespect to this constant shafting of the genre in which I work, in which a lot of people do great work that readers actually want to read. How do I know? You don't get David Foster Wallace conventions; you do get Terry Pratchett ones.

But perversely I also enjoy this lack of respect. Like Superman and Lex Luthor, or Batman and the Joker, your hero is measured against the strength and cunning of the villain opposing him/her. And when you get right down to it, the Literary Establishment is actually a lot like Lex Luthor: powerful, entrenched, sophisticated, and--most delightfully--fundamentally threatened by those aliens in their brightly colored costumes.

Now if you'll excuse me, I have to go put on my cape and long underwear.

Monday, July 25, 2011

Age ain't nothin' but a...problem

In a recent Wall Street Journal, Alexandra Alter talked about the dangers of having your literary characters, especially detectives, age in real time. She cites several examples of authors allowing their characters to develop the infirmities and declines that come with advancing years, as well as those who freeze their heroes in time so that while the world changes, they don't.

The original detective heroes like the Continental Op and Philip Marlowe didn't face this worry. Their series were relatively short compared to what we now consider a successful run: seven novels and some short stories for Marlowe, compared to 21 for John Sandford's "Prey" series; Agatha Christie's Miss Marple racked up 12 novels, against 40 for Robert B. Parker's Spenser. Sam Spade, the quintessential tough-guy detective, exists in only a single novel, The Maltese Falcon.

The appetite for series now requires at least a book a year, and authors with contemporary settings have to face the fact that the world changes around their heroes. Do the heroes change with it? Some do. James Lee Burke's Dave Robicheaux, once young enough to be played in a movie by Alec Baldwin, is now 73. Michael Connelly's 60-year-old Harry Bosch has to deal with the vagaries of contemporary retirement. But some, like Spenser or Kay Scarpetta, don't. In fact, the biggest surprise in the article was how many authors began with their heroes aging, and then arbitrarily froze them in time when the series became successful.

It made me think about Eddie LaCrosse's age, and how that affects his ongoing adventures. I created his prototype character when I was 18, but I wanted him to be worldly and sophisticated, so I made him roughly 35, which is his age in The Sword-Edged Blonde. At the time I thought that was mature enough to give him the perspective I wanted. However, by the time the book actually came out I was over 40, which meant I was now writing about a character a decade younger than me. Further, and strange as it seems, I'm continuing to age. So I'm faced with the dilemma of what age Eddie should be in each book.

Luckily I'm freed from the worries of the modern world, since Eddie's world is fantasy and only changes when I change it. But I still want him to be believable, and part of that is aging. I don't have a set time frame, like Stephanie Plum (Kinsey Millhone ages one year for every 2 1/2 books, so she'll be about 40 when the series concludes). But he does progress. In the framing story of Dark Jenny I think he's about thirty-eight, settled into his relationship with Liz and established in Neceda. In the next book, Wake of the Bloody Angel, he's about the same age. Which works out to real-time again, one year per book, by default. But it's not deliberate, therefore I can't be held to it. Ultimately, Eddie's as old as I say he is.

Wednesday, July 20, 2011

A free market of idiots

I'm enough of an ex-journalist that I've read with interest about Britain's scandal-plagued scandal sheet News of the World. Short version: to feed its tabloid readership, the paper hacked into the e-mails, phones and private records of politicians and celebrities, to great financial success. So far so good, but then they broke into the voice mail of a murdered teenage girl, even deleting some of her messages so that her parents believed (falsely) that she was alive. That was the line, and they crossed it.

This has been roundly condemned, as it should be, and it's brought a lot of attention to the nature of British media, also as it should be. Those on the left are trying mightily to attach the scandal to Rupert Murdoch, head of News Corp and owner of News of the World (and of course Fox News here in the US). He's, of course, denying any knowledge of these actions.

But I don't think Murdoch is utlimately to blame. I think the blame lies here:



Let me be clear: it's not the magazines. It's the person buying them.

Murdoch and his kind do nothing more than obey the first rule of business: give the people what they want. From gossip to innuendo to outright lies, his various media outlets have one thing in common: success. If nobody cared about celebrities, he wouldn't be in the gossip business. If people turned off news that was repeatedly shown to be biased, and with occasional outright fabrications, his news shows would either straighten up or go dark. And if there wasn't a ravenous appetite for sordid details, the phone of a dead girl would not have been hacked.



Every person who buys a magazine with a Kardashian on the cover, or watches the Octomom on TV, or reads Perez Hilton online is as responsible, if not more so, than Rupert Murdoch for the state of media and so-called "news." These consumers have created the environment that promises economic rewards for hacking the phone of a dead girl. The defense is that these magazines are "harmless," that celebrity gossip is "just for fun," but now we've learned that "fun" might extend to the private e-mails, voice mails and medical records of 9/11 families (the FBI is investigating that). Is that "harmless?" Because once you've exhausted celebrity culture (and please, God, I hope we're close), the only things left are private citizens with the bad luck to suffer public tragedy. And that could be any of us. Our worst nightmare could be marketed as "just for fun."

So, let me be plain: supporting this crap with your money and time makes you the problem, not the people who produce it. Stop buying it, and they'll go away. That's how an intelligent free market works. But a free market of idiots leads to this:

Wednesday, July 13, 2011

Interview: Genevieve Valentine, author of Mechanique



Recently I reviewed the debut novel by Genevieve Valentine, Mechanique: A Tale of the Circus Tresaulti. I thought it a brilliant and intriguing book, and as a writer, I wondered about the thought process behind some of the concepts. Genevieve was kind enough to answer some questions for me.

The bones (in the story, circus aerialists have their human bones replaces with light, hollow copper one) represent different things to each character who receives them. What inspired them, and what did they represent for you, the author?

Appropriately enough, bird skeletons were a large part of the influence on the bones. I was looking them up for something unrelated, but the physiology was really interesting and stuck with me as I started writing about what exactly made the performers in the Circus Tresaulti so different. For me, the bones were always a tangible symbol of the sacrifices you make for something you love, though the self-destructive aspect of it often goes hand-in-hand, depending on the character.

The narrative jumps among several voices and points of view. Why did you choose that form?

When I sat down to begin I just started writing, and the scenes I wanted to get down first came first, in the perspective I thought made the most sense. By the time I had the breathing space to sit back and worry if it was going to work, I loved how it was coming together too much to think about stopping.

The story doesn't have a specific setting, either geographically or in time. Why did you decide on that?

I approached it with the idea that the deep aftermath of a war takes on this air of inevitability and surreality, as if it both defined and took place outside of the world now. With a war as big as the one that's implied here, that devastates natural resources and completely shifts the practice of government, old nations and eras slowly cease to matter. It doesn't help that the Circus operates in this landscape as they themselves are a bit unstuck in time by the magic that holds the Circus together.

How well did the artwork by Kiri Moth capture your sense of the story?

SO WELL. Sorry for the caps, but it's awesome. The cover alone is so detailed and evocative that no one could ask for more, but for me, some of the interior art pieces truly hit home. My two favorites are probably the griffin, which is so perfect it's become an emblem for the Circus in earnest, and Elena on the trapeze. The grace and introspection and loneliness of that moment is exactly how I had pictured it when I was writing, and seeing the recreation in my inbox the first time, I clutched my pearls like a dowager.

Thanks to Genevieve for answering my questions. You can find Mechanique: A Tale of the Circus Tresaulti at all the usual outlets.

Monday, July 4, 2011

Look back in chagrin

Recently I've been revising an old manuscript that I originally wrote over a decade ago, and haven't touched in at least seven years. It's an interesting window into the past of my own creative process, and some lessons I've since learned are vividly displayed in all their teeth-gnashing glory. Here are some examples.

1) A little description goes a long way. I described the physical settings in great detail, thinking at the time that the action wouldn't work without it. I try to always make my action scenes use the specific geography I've set up, so that the reader gets the sense that these events could happen nowhere else. I now know that back then, I seriously underestimated the reader's ability to comprehend. For example, I had this as a description of a creek:

"The creek occupied an open ribbon of ground fifty feet wide, and the grass beyond it grew high enough to hide anything."

I thought that readers needed to know that the width of open ground would accommodate the events about to occur. However, in revision I realized this was didactic overkill. Whatever image of a "creek" the reader conjures will work quite well, and has the virtue of getting the reader to contribute to the story's reality.

I also tended to give exact measurements when they weren't necessary. For example, "[it] landed hard on its belly ten yards away." In context of the scene, knowing the precise distance is pedantic and unnecessary.

2) There's a fine line between ambiguity and confusing lack of information, and I often have trouble seeing this line until someone points it out to me. In this story, the plot was set in motion by a man wandering out of the desert and promptly dropping dead. We never found out who he was, where he came from, or why he carried the McGuffin he brought. In re-reading I realized this was a huge dangling plot point that might--and probably should--annoy the reader. So while I liked the ambiguity and wanted to keep as much as possible, I filled in some more detail and implication, so there's at least some sort of explanation.

3) Elmore Leonard, a man who should know, advises, "Never use a verb other than 'said' to carry dialogue." I had clearly not grasped that concept. If the tone of the dialogue isn't clear from the dialogue itself, then in most cases you need to back up and rethink the words. Certainly I did.

4) My chapters have gotten shorter. The first five chapters of this book averaged 17-18 manuscript pages, while my more recent ones are between 13-15. This is an observation, not a value judgment, since in one sense a chapter is as long as it needs to be. But evidently mine need to be shorter than they used to.

And finally,

5) The chapters may be longer, but this book was short. Really short. 350 manuscript pages, when my average for the Eddie LaCrosse series is between 400-420 (and even that's short compared to most fantasy novels). As I revise, I've found places to legitimately add more detail and incident, but I internalized too much journalism to tolerate any padding. And that's another important lesson: like a chapter, a story is as long as it is. Some stories might need multiple volumes of a thousand pages each; then again, some might just take 400 or so pages. Maybe less.

Yes, a lot of these lessons caused me to wince, clench my teeth and look away in both disgust and horror. The urge to think, "I can't believe I wrote something so bad" is pretty strong. But it's also incorrect. I wrote this story the best that I could at the time. I improve with each story I write, with each comment and suggestion I get from my editor, and with each book I read. The process doesn't end. So if you're an aspiring writer out there, and you resurrect an old manuscript that makes you want to give up writing forever, remember two things: a) it was the best you could do at the time, and b) you're better now.

And that should always be true.

Wednesday, June 29, 2011

Interview with Teresa Frohock, author of Miserere

Teresa Frohock is both a friend and the author of Miserere: an Autumn Tale, a book I enjoyed so much that I gave her the following blurb:

"Miserere is about redemption, and the triumph of our best impulses over our worst. It's also about swords, monsters, chases, ghosts, magic, court intrigues and battles to the death. It's also (and this is the important part) really, really good."

You can read my full review here.



Teresa graciously agreed to answer some questions for me about the book.

You and I have both recently written books that include people of genuine, true religious faith (my book is The Hum and the Shiver, out this fall). The pitfalls of this are enormous: the danger of sanctimoniousness, of preachiness (literal and figurative), of simply alienating readers who don't share whatever faith the characters embody. How much did you worry about this, and how did you overcome it?

Thanks so much for having me here, Alex, I really appreciate the opportunity to talk about some of this.

Truth be told, I’m still worried about some of those things. Although I think people who read speculative fiction are open-minded and much more amenable to experimentation than other genres, I still worry that some may suffer contempt prior to investigation. I hope not.

It helps that I have no agenda here. I’m not out to push a viewpoint, Christian or otherwise. I just wanted to tell a story, and as I constructed Woerld, I realized the focus would be on Lucian, who happened to belong to the Christian bastion. From that point forward, I had to educate myself about Christianity and I was really surprised by the facts I found.

The version of Christianity that I present on Woerld is gleaned not just from Biblical sources, but also from the Pseudepigrapha and Apocrypa. I wanted to see what Christianity might have been like before the Schism of 1054 when Rome split from the Byzantine Church. I approached all the religions on Woerld strictly from a scholarly angle at first, then I eased the spiritual elements inherent to the practices of the religion into the story.

I focused entirely on the growth of the individual character and not the dogma of the religion. And that was hard, showing how the adherents struggle with their faith from personal viewpoints. When we speak of Muslims, Jews, Christians, Buddhists, Hindus, we tend to think in terms of groups, not individuals. I wanted to put the focus on the individual and show that
personal growth doesn’t come from automatically joining a group, but comes through the internal work of the individual.

If you read most religious texts closely, they emphasize a personal contact with a higher power, not group-think. So I did very much what you’ve done with Reverend Craig in The Hum and the Shiver—I simply had Lucian live his life in accordance with the dictates of his beliefs. I’ve always loved Emerson and Thoreau’s writings and their emphasis on the individual’s responsibility to contact the divine within and bring that light into the world through action. That is a concept inherent to all religions and I wanted to illustrate that philosophy in Miserere.

You incorporate a young woman, Lindsay, who must learn both to be a warrior (a common fantasy trope) and to truly believe in God (not so common). What did she represent for you?

Lindsay represents our twenty-first century’s society secular thinking about religion, our preconceptions and our misconceptions. Her exposure to religion comes primarily through the media, meaning she understands the various religions through the extremes of the worst possible examples of the adherents: politicians who mouth their version of Christianity while they actively engage in immoral behavior; a Catholic Church hiding child-molesting priests; jihadists that believe their way to paradise is paved with the bodies they leave behind; Hindus and Muslims and Christians and Jews constantly fighting one another either in rhetoric or with guns.

This is what Lindsay is exposed to day after day, then she is taken to the obligatory church service, plunked in a pew, and told God is love. Needless to say, she’s a tad cynical over the whole thing. Kind of like the rest of us.

So I like having her as the voice of the reader, to question Lucian and the adults in Woerld about how things work. That way I can gently ease my readers into Woerld yet not make the picture too rosy. It’s not. There are serious conflicts among the bastions and the governments in Woerld—it was never my intent to present a Utopian society.

Children aren’t afraid to question the status quo, and they see things very clearly, more clearly than adults want to admit. Lindsay is the perfect lens to view Woerld and its imperfections.

Your novel is definitely a fantasy, and many fantasies create their own religions. You chose to use actual existing world religions. What was your thought process behind that?

I thought about Tolkien and Lewis and wondered what The Lord of the Rings would have looked like if Tolkien had written it as a Catholic story instead of embedding the religious tenets beneath Middle Earth’s mythology, or what Narnia would have looked like if, instead of a lion, Aslan was the Christ. Not being as much of a fan of Tolkien as I am of Lewis, I really started reading Lewis’ works; he had a talent for rooting out the spirituality of Christianity and getting to the essence of its beliefs without sanctimony.

I checked out some other current fantasy titles that used fallen angels, and while they addressed the fallen part of the situation, very few showed it from a Christian angle. I think God’s Demon by Wayne Barlowe was the closest novel to presenting hell from a Christian viewpoint, and I love what Barlowe did with that story. The language he used, the characterization, and his perception of hell as an actual, physical place just knocked me for a loop.

Barlowe took the war in heaven and showed how the fallen angels fought. I’ve always been fascinated by the war in heaven and often wondered: what if it’s still going on? I’m sacrilegious like that.

In the end, I fell in love with the absolute challenge of it. This is my own ego talking now, but I wanted to prove you could write a fantasy with Christians in it without the story becoming insipid or preachy. I began constructing Woerld and realized that all religions have some form of hell or purgatory, so realistically, it wouldn’t be just Christians. I mean why would heaven only use a fraction of its forces to combat evil?

So the other religions started seeping in and with that there must be a hierarchy, and the structure of Woerld evolved until it became what it is in Miserere. The more I worked on it, the more detail seeped in, and again, I just loved the challenge of using real religions.

You have a male hero torn between and among a group of women: his sister, his former lover, and his new protégé. Was there a deliberate thought process behind the gender roles for these characters?

I wanted to step outside of a few of the standard fantasy tropes and twist them. The most common trope from the fairy tales of my youth was that of the beautiful princess who was captured by the evil warlord or witch and rescued by a handsome prince. I wanted to turn that trope upside down and show the handsome prince who was captured by the wicked queen and rescued by the beautiful princess. Only in Miserere, the prince takes a real beating from the wicked queen, the beautiful princess is mauled and half-mad, and the wicked queen isn’t strung too tight either.

That was my primary thinking, then everything sort of got away from me. Most people are conditioned to see men in one of two roles: protector or aggressor. Lucian sees himself as the protector, even though it is Lindsay and Rachael who end up saving him more often than he saves them. He is determined not to abandon them, though, and that’s important, that desire to be a part of someone’s life even if it means constraints on his existence.

Nor did I want the women to be perfect. Rachael had her part in her own downfall; Catarina is a grand case of self-will run riot; and Lindsay thinks they’re all being horribly unfair to Lucian while she downplays his crimes in her own mind.

When I got the cover art for Miserere (by the wonderful Michael C. Hayes), I just cried, it was better than anything I could have imagined. I had been dreading what an artist’s conception of Miserere would be, but more than anything, I feared chain mail bikinis on the women and Lucian standing with Catarina and Rachael kneeling or the women pictured lower in the foreground.



Instead, Michael got exactly what I was doing and busted the tropes with me: they’re all standing with their backs to one another; Rachael and Catarina are wearing the armor they would probably choose; Lucian is on his knees between them; and the walls of the Citadel rise behind them. Catarina’s face is cunning, Rachael is distrustfully looking at Lucian, and Lucian—my
poor Lucian—looks to Heaven, because when you’re trapped between those two women, your only salvation is from above.

Thanks to Teresa Frohock for answering my questions. Miserere: an Autumn Tale is available now from Night Shade Books.

Monday, March 28, 2011

The Wicked Day: the weight of legend

It's no secret that my new Eddie LaCrosse novel Dark Jenny (which hits stores tomorrow, March 29) draws its inspiration from Arthurian sources. So on the eve of its release I'd like to write about the straight Arthurian novel that's so good, I wish I'd written it: Mary Stewart's The Wicked Day.



Stewart's first three Arthurian novels (The Crystal Cave, The Hollow Hills, The Last Enchantment) were about Merlin, who I find the least interesting of the major characters. There's something ineffably smug about him as he toys with destinies and then fails so spectacularly he takes Camelot down with him. In a sense he's the Karl Rove or James Carville of the Arthurian world (or maybe Lee Atwater, if you want to stretch a point), and a novel with that approach might be fun. As it is, and despite Stewart's skill, after three books I was ready to seal Merlin in a cave myself.

But Stewart switches gears entirely for The Wicked Day. This novel is about Mordred, Arthur's bastard son by his half-sister Morgause. Unlike the first-person narration of the prior books, this one is in third person, so all the characters we've previously seen through Merlin's eyes are now shown from a different perspective. Stewart makes Mordred a complex, driven but honest young man who both fights his destiny and embraces it. His relationship with his father is fascinating, since both know of Merlin's prophecy that Mordred will bring down Arthur's kingdom, and yet they forge a close friendship.

The first time I read the book, I admit I was disappointed in the ending. Not that it was a surprise: it's the ending that the Arthurian legend must have, one way or another. But up until then Stewart had fleshed out the characters and situations so well that the inexplicable events actually came to make sense. And then comes the final battle at Camlann, where Arthur and Mordred meet, and die. Instead of giving us their final confrontation, held in a futile attempt to make peace, she retreats and falls back on:

None of those watching was ever destined to know what Arthur and Mordred spoke of.
(first edition, p. 302)

This sudden distance from the climactic moment is jarring, and when I first read it, it well and truly pissed me off. I felt cheated, all the more so because I loved the rest of the book. For years I called it "99.9 percent of a good book."

But as time passed (and I made my own run at Arthurian-ish characters) I realized her choice made sense. No matter what she came up with for this climactic scene, it pales next to the weight of a thousand years of legend. By leaving this moment to the reader's imagination, she gives the story the sense of inevitability and tragedy that a more literal depiction could never have done. Ultimately it doesn't matter what they said, because the end of the story was written by Fate long before either Mordred or Arthur came along.

So I've come to fully love The Wicked Day, to the point that I'll probably never attempt a straight Arthurian novel. And besides, Dark Jenny covers all the bases I wanted to touch. It's my Camelot, skewed and tweaked to fit in the world of Eddie LaCrosse, sword jockey.

Monday, March 21, 2011

Review: Alice Hoffman's The Red Garden


If Alice Hoffman was a painter, her brush strokes would barely touch the canvas, yet her pictures would be as vivid as Monet's. She crafts delicate stories that always seem on the verge of wafting away until they come back to earth with some devastating, perfect detail.

The Red Garden is something new from her: a book pitched somewhere between a short story collection and a novel. The individual tales stand more or less on their own, but the cumulative effect is much more novelistic. The continuing character is Blackwell, a Massachusetts town that she tracks from its settling in 1750 through the present day. Founded by a woman so tough and determined that she milks a bear to keep the settlers alive, the town remains home to strong-willed women who either choose duty over love, or find love's solace fleeting. The men are often confused, aimless, seeking a direction in life that many of them find in the wilderness of the nearby mountain. Bears are a recurring motif, as are bees and eels in the river. The titular garden grows plants that inevitably turn red for reasons that the reader knows, but not the inhabitants.

And there are elements of overt magic, specifically in the story "The Fisherman's Wife." But for the most part, the supernatural elements remain subtle, hidden, easily explained to the characters with more mundane explanations. Only the reader, with the perspective of history, sees them for what they truly are. And it's that gentle, cobweb-light push/pull of magic and reality that defines the book's tone.

Stylistically, Hoffman goes for something equally subtle. Characters weave in and out of the stories, and Hoffman plays with narrative voice when it suits her ("The Truth About My Mother," for example, is told in first person). There's a sense that the penultimate story, "The Red Garden," resolves threads left from the very first tale, "The Bear's House." But then there's a final story, "King of the Bees," that thematically says no story ever ends, not even when we think we understand it. Blackwell's tales go on, just as life continues past our own moments of epiphany.

As a reader, I try to expose myself to things vastly different from what I write. The Red Garden has virtually nothing in common with my own stories, but I hope it teaches me to be a hair more subtle, or to risk a moment of delicacy amongst the swordplay and carnage.

Tuesday, March 15, 2011

The Rio Bravo approach to world-building

I’m often asked about “world building,” the term for creating the environment for fantasy novels. Most tend to be much more elaborate than mine, which may be one reason why my books are so much shorter. I usually respond with some variation of, “I’m more interested in people building,” which is true but can understandably sound a bit facile.

Still, I can't deny I’m far more interested in the details of character than in aspects of society that don’t impinge on the story. So I cast about for another example of that approach, and found it in one of my favorite movies, Howard Hawks’ classic western Rio Bravo starring John Wayne, Dean Martin and Ricky Nelson.



The setting is as generic a Western town as you can imagine: it's nameless (although it's assumed to be "Rio Bravo," no one ever actually says so), isolated, and the only institutions shown are the jail, the hotel and the saloon. Contrast this to the unique, incredibly detailed sets of The Wild Bunch or the specific geographical settings of The Searchers. At the time (1959) television was filled with Western series the way we now have reality shows, and nothing about Rio Bravo's setting is substantially different from the backlot towns people saw every week for free on Bonanza, Gunsmoke and Have Gun, Will Travel. So what did the movie have to make them pay to see it?



Characters. Archetypal to be sure, but developed with detail and skill, played by actors at the top of their games and laced through with humor. In other words, the exact opposite of world-building. People-building. And if I have to err, that's the direction I'd rather go. I can live with an underdeveloped or generic setting, as long as it's populated by compelling and interesting characters.

What do you think? How much setting is enough, and how much is too much?


Admit it: this picture really makes you want to see the movie, doesn't it?

Wednesday, March 9, 2011

Monday, March 7, 2011

Reality...what a (necessary) concept

Reality may seem a strange concern for a writer who focuses on fantasy and horror. After all, how can you claim anything is "real" in tales of faux-medieval warriors, disco-era vampires and supernatural hillbillies? Yet it's an overwhelming concern to me, and one that leads me repeatedly back to the films of John Cassavetes.

His work--among them Shadows, Faces, the seminal A Woman Under the Influence, my current favorite Opening Night--created the American independent film movement. Their sometimes ragged natures are often perceived as the result of improvisation, in the same vein as the films of Christopher Guest or Henry Jaglom, but that's a misperception: Cassavetes may have based his screenplays on rehearsal improvisations, but the final films are the result of tightly scripted and deliberately constructed performances. Within them, of course, are moments of invention, but not so many as you might think.

This approach is made clear in A Constant Forge, a lengthy (140 minutes) documentary by Charles Kiselyak. Cassavetes died in 1989, so the majority of the interviews are with people who worked with him, along with excerpts from print interviews read by Sean Penn. It's also obvious in Cassavetes Directs, a fly-on-the-wall account of the filming of his last movie, Love Streams, in 1984.

So what's the point of this approach? Simply, it allows an almost total breakdown of the line between performance and documentary realism. There are moments in A Woman Under the Influence that feel so real, so uncomfortably genuine, that even with famous actors like Peter Falk and Gena Rowlands onscreen, you can forget you're watching a movie and feel like you're spying on real people. For an audience used to dramatic signposts (THIS is a serious scene, THIS is a humorous line, you should feel TERROR here), a movie like this can be a hugely uncomfortable experience.

So what can a prose writer get from this? I hope it serves as a reminder that no matter what's happening in the story, whether your hero is facing a dragon or a vampire is learning that sunlight will not destroy her, the reality of the moment lies in reactions that are unanticipated but undeniably genuine. In Cassavetes' work, he strove to get beneath the surface responses people give, the "performances" that get us through real life, in order to present something original that the audience nevertheless responds to as genuine. As writers, we should do the same. As writers of fantasy, horror and science fiction, it should be a priority.

Here's a clip of Cassavetes in action, talking about the release of Opening Night but finally going off on some interesting tangents.

Monday, February 28, 2011

Hundreds of little people living under his skin.*

Coming up with character names is, as the master Charles Dickens probably knew, one of the most fun aspects of writing. Unlike real life, where you're named long before your identity is formed, you have the chance to give someone a handle that reflects their personality. Villains can be named "Uriah Heep"; plucky young urchins can be "Pip" or "The Artful Dodger"; Doomed girls can be "Little Nell." For a current master of this sort of thing, check out the films of Larry Blamire (for example, in The Lost Skeleton of Cadavra his alien couple is named "Kro-Bar" and "Lattis.").

But sometimes naming gets...tricky. As I've said elsewhere, I first invented my Eddie LaCrosse character in high school, except back then I named him "Devaraux LaCrosse." It was my attempt to play the high-fantasy, high-falutin' name game so prevalent in the genre of the time. My villain, who ultimately bore the much more reasonable monicker "Andrew Reese," was then known as "Kakorian Shay." Now, there's nothing inherently wrong with these ten-dollar names, I suppose, and perhaps a better writer could've made them work. But my bad guy certainly benefitted from a more normal name, and my hero never truly came alive for me until he started answering to the much less grandiose "Eddie."

In another, so far unfinished work, I used a placeholder name for the heroine, simply because I didn't want to stop writing long enough to think of the right one. "Bailey Nichols" was a play off a character from WKRP in Cincinatti, Bailey Quarters (Quarters/Nichols, quarters/nickles, get it?). There was no reason for this association within my story, which is a Southern Grand Guignol set during the eighties; consciously at least, it was entirely arbitrary. But as I worked on it, the name "Bailey Nichols" suddenly seemed to fit. I can't say for sure if it was merely the familiarity of repetition, but I was no longer able to think of her under any other name. So Bailey Nichols she remains.

Sometimes names present themselves, and there's no question they're right. Fauvette, the heroine of Blood Groove, was named after the song of the same name by Duncan Browne, whose music accompanied my writing process. She never had another name. The same with Bronwyn, protagonist of my upcoming novel The Hum and the Shiver. However, the names of the vampire sisters in The Girls with Games of Blood, Prudence and Patience, were arrived at by a deliberate process of pairing up names in search of ones that looked, sounded and felt right.

I started thinking about these issues after reading about another writer, Chelsea Main, whose critique group recommended she change the name of her protagonist. It turns out my response to "Bailey Nichols" wasn't unique. Chelsea said, "To me, names are not arbitrary labels for my characters. Names carry meaning and symbolism. The feel of a name says a lot about a character's personality to me. Choosing the correct name is a big deal - and letting go of one I've become attached to is not easy."

So what are your favorite character names, both from other's work and, if applicable, your own? Everyone who replies here will have a shot at my last remaining ARC of Dark Jenny.

*Full quote: "Every human being has hundreds of little people living under his skin. The talent of a writer is his ability to give them their separate names.” (Mel Brooks)

Monday, February 21, 2011

Bad Influences from Good Sources

As writers, we all own up (or should) to the things that influence us in a positive way. For example, I acknowledge the debt I owe to Robert B. Parker for my understanding of how to make a first-person narrative entertaining. But what about negative influences? What about the things that we tried to incorporate into our own writing that turned out to be huge, big mistakes?

I have two examples from my own career. One is Joe R. Lansdale's Drive In novels, particularly The Drive-In 2: Not Just One of Them Sequels. I read this one in the late 80s, when I was trying to develop my own voice and style, and it completely threw me off course for what turned out to be several years. It wasn't just that I liked the style, which I did up to a point; it was that it was so different from my own work, I took it as a sign that I was doing everything wrong. Clearly sincerity and forthrightness weren't what people wanted; they wanted irony and robust humor (I was half right, as the subsequent rise of uber-ironic Joss Whedon proved). What I missed was the meta-level of Lansdale's work, which was far more important than either the irony or the farting tyrannosaurs. So I spent years--no kidding, years--trying to work in a style for which I was entirely unsuited, and which I completely misunderstood. It was probably 1994 before I regrouped, found my own voice and began producing things that, whatever their overall merit, at least sounded like me.

The second example is the Martin Scorsese film The Color of Money, with a screenplay by novelist Richard Price. At the climax, veteran pool shark Fast Eddie Felson (Paul Newman) finds himself about to shoot a game against his own protege, Vincent Lauria (Tom Cruise). The whole film seems to have come down to this game, and the audience is breathless to see who will win. That is, until this exchange of dialogue:

Vincent: Eddie, what are you gonna do when I kick your ass?
Eddie: Pick myself up and let you kick me again.
Vincent: Oh, yeah?
Eddie: Yeah. Just don't put the money in the bank, kid, 'cause if I don't whip you now, I'm gonna whip you next month in Dallas...And if not then, then the month after that in New Orleans.
Vincent: Oh, yeah? What makes you so sure?
Eddie: Hey--I'm back! (shoots the break, screen fades to black)

This final minute of film completely realigns the story we've just watched. What seemed to be a standard, if well-done sports drama about the fall of the old and rise of the new becomes, in that moment, a story of the reclaimed self-awareness of Fast Eddie Felson. It's significant that we never even see the results of the break Eddie shoots, because in that moment the game of nine-ball, the whole impetus of the story thus far, becomes immaterial. Much like the first Rocky, it no longer matters who wins the game, because that's never been the real story. Only unlike Rocky, Scorsese and Price manage to hide that from us until literally the last minute.

I saw this as a challenge. I resolved to make every story I wrote hinge on this sort of twist, which is a whole lot trickier than it first appears. I think I only succeeded once, in a so-far-unpublished short story about jaguar hunters in South America. My other stories from this period left readers with a sense of "Huh? What?" Luckily I came to realize that the film's ending worked so well because it was unexpected, unusual, and rare. The moment people start expecting a twist at the end, whatever you come up with lost its potency (this was also later proved true by the flame-out of twist-meister M. Night Shyamalan). So I went back to writing stories that ended appropriately for themselves, which often meant just as the reader expects. That's not always a bad thing.

So let's hear from some other writers. Who influenced you in what turned out to be a bad way?

Monday, February 7, 2011

Return of the REAL King


There are many books on Elvis, from treatises on his sociopolitical influence to muckraking autobiographies by those on his payroll, but it's rare to find one that understands his impact, yet takes the time to delve into the human being behind it. Gillian Gaar's Return of the King does just that, using as her sources mainly interviews with musicians and others who worked with Elvis from just prior to his 1968 comeback TV show through his death in 1977. This is not a book that tells how a simple boy from Tupelo turned into a sex symbol and superstar; instead, this explains how the acknowledged King of Rock and Roll briefly took back his career and showed a jaded Sixties audience just why he was the King.

The arc of Elvis' career is well known: hillbilly cat, Army service, movie star, Vegas act, bloated corpse on the bathroom floor. It's in that gap between "movie star" and "Vegas Act" that Gaar begins, detailing Elvis' dissatisfaction with his career and the music he was forced to record. Elvis was the very embodiment of the saying, "Wham, Bam, Thank You Ma'am," combining unsettling sexuality with Southern politeness, and it was the latter quality that kept him from breaking free of people like Colonel Tom Parker, the manager who had guided his rise but had no interest in insuring his continued growth as a performer and artist. But eventually even Elvis had enough, and he supported TV auteur Steve Binder in the creation of a TV show that was much more than the Colonel's intended simple "Christmas special."



Gaar devotes her pages exclusively to what other biographers deal with only in passing: the creation of the music. There are riveting accounts of recording sessions from the musicians who played them, revealing the disheartening reality of Elvis' career. This makes his moments of triumph all the more powerful, because he had to overcome the very machinery that supposedly created him in the first place. What comes through is both Elvis' humanity, his kindness and decency to the players he worked with, and the loneliness that a man surrounded only by payroll sycophants can truly feel.



(One non-musical highlight is the account of Elvis' meeting with then-president Richard Nixon, as related by members of Nixon's staff and Elvis' inner circle. What is often depicted as a possibly drug-addled adventure becomes clearly a moment of utter showing-off by the King, for a surprising reason.)

I've read a lot of books about Elvis, and this is one of the few that makes no apologies for either his accomplishments or his failures. Gaar does not pass judgment, and although she does imbue her tale with authorial sympathy, she doesn't gloss over failures both musical and personal. If you've ever wondered why Elvis mattered, you'll understand after reading Gaar's book.

Monday, January 24, 2011

Low Road: Donald Goines and urban tragedy


I discovered the novels of Donald Goines when I worked for a book distributor that sold collections to libraries. Often this meant orders for all the books by a particular author, as was the case with Goines, whose novels bore vivid titles like Whoreson, Black Gangster, Swamp Man and White Man's Justice, Black Man's Grief. Goines' first novel appeared in 1971, and he died in 1974 at age 37 after writing sixteen books, a meteoric career by any standards. And they're all still in print today.

Low Road: The Life and Legacy of Donald Goines is an attempt to put his life and accomplishments into the context of their specific times. Occasionally it seems like author Eddie B. Allen, Jr. is more interested in the context than the man, but ultimately his approach pays off. Allen describes the Detroit in which Goines grew up, as well as the racial situation throughout the country. Goines, son of a successful middle-class black family, faked his way into the air force at fifteen, served in Korea and returned at seventeen a veteran and heroin addict. He tried careers as pimp and hustler, served time in prison and then, inspired by former pimp turned literary darling Iceberg Slim, decided to pursue writing. He wrote what he knew, but he wrote with a blinding honesty and the kind of grit you can't fake. His street hustlers weren't glamorous or admirable, and even when they tried to do the right thing, they still had past sins that needed atonement. But it was more than a transcription of his own experience; these were stories, crafted and polished, by a man who too late discovered his true calling.

It isn't until the penultimate chapter, "Prodigal Son," that Allen goes in depth into Goines' work, connecting characters and situations among the books, and with Goines' own life. Here he presents an analysis of what Goines tried to accomplish, his motivations and why he connected with readers. The first Goines novel I read, Swamp Man, turns out to be an anomaly, set in Mississippi and dealing with a brother's revenge for his sister's degradation at the hands of repulsive rednecks. The rest of Goines' output is urban and concerned mainly with survival, although a little vengeance gets had as well.

Oddly Allen, also a Detroit native like his subject, seems unable to fully accept that Goines, untrained and unschooled, could have simply imagined the stories, going into great depths to find real-life sources and qualifying observations with statements like, "[Goines] might not have intended it, but the symbolism in the story is conspicuous." Or, "Whether Donnie did it consciously or without thought, he gave several different characters in his books identical names." This skepticism seems strange in a book about a man who, we assume, fascinated Allen enough to write about him.

(I think this is the profound lesson of Goines' work to other writers: the fact that you don't need formal training, no MFA or fancy residency in Iowa. You can simply decide be a writer. The technical skills will come with practice and help, but the core drive requires nothing but the desire to tell a story uniquely your own [and figuring out that part can be harder than it sounds]. Goines had that desire, which is why we still remember him.)

Still, Allen does a good job of presenting Goines' ouvre in detail, qualified or not. In the epilogue, he explains his own connection to Goines, his attempts to solve the writer's 1974 murder (no one was ever arrested or charged), and thoughts on Goines' legacy from academics.

There is, ultimately, a lot of Allen in the book. Whether this detracts from the reading experience is something for each reader to decide. It didn't bother me; it was like having a tour guide, and given the areas that the book explores, it was handy to have someone along who knew the territory. Ultimately Low Road gives as much insight into Goines as we're likely to get at this late date, and if the man remains an enigma to the reader, it's probably because he was one to himself as well.

Friday, January 7, 2011

The Finn Substitution

Some have brewed a ha-ha about a new edition of Mark Twain's The Adventures of Huckleberry Finn that removes what is euphemistically called "the N word" and replaces it with the word, "slave." This has brought all kinds of interesting trivia to light ("the N word" is used 219 times in Finn, "slave" is not actually a synonym for it, Finn is the fourth most-banned book in the country, etc.). But as I read the ever-increasing attempts to be the most offended by this, I can only think: what's the big deal? It was done twenty years ago, too, and no one thought anything about it. In fact, it's been done multiple times.

The one with which I'm most familiar is part of the Great Illustrated Classics series that takes well-known (and public domain) novels and repackages them for young readers, simplifying the stories and adding illustrations on every facing page. We have a shelf of them, and I've enjoyed reading them aloud to my kids (my oldest son's favorite is Journey to the Center of the Earth). And we've read both Finn and Tom Sawyer. Finn was published in 1990, and to my knowledge has never stirred the least bit of ire.



Now I admit, in reading Sawyer, it annoyed me that villainous Injun Joe was now "Crazy Joe." I understood the impulse to change it, but I disagreed with it. Similarly, in their version of Finn there's no "N word," and the dialogue has been rewritten so that no one-for-one substitution is needed. Jim is a slave, and that's enough.

So why all the outrage about this new edition that boldly goes where...well, many have gone before?

Probably for two reasons. First, the recent release of The Autobiography of Mark Twain, a volume he stipulated could only be published a century after his death. It's both a best seller and a critical darling, so Twain is back in the public eye.

And two...well, now there's the internet, and people on the internet love to be offended. Any time there's an issue like this, people rush to show how outraged they are, in a pile-on usually as distasteful as whatever the original offense might've been.* You can see some of it here and here. Even Roger Ebert, who should really know better, chimed in with a particularly crass and tasteless tweet.

Yes, rewriting Finn bugs me, but I'll respond in the proper adult fashion: by not buying this edition. That's all any of us need to do, to register our disapproval. I won't rant and rave about the greater social ills its existence reveals, or try to show how much more it offends me than it does anyone else.

I'm not defending this editorial bowdlerizing by any means; I disapprove of it, and think the concepts behind it are both shallow and wrong. But it's not real censorship as long as the original text is available. And I'm pretty sure it still is.

*(And yes, I recognize the potential hypocrisy in saying this in the context of a post that could be interpreted as doing exactly that. If you think so, please disregard anything I say.)

Sunday, December 26, 2010

Saved by Darkness

In 1978, I was as hardcore a geek/nerd/dweeb as a boy could be. Star Wars had come upon the world, legitimizing those of us who read books with spaceships and monsters on the covers (and got beaten up by our cousins for it, but that's another blog post). Starlog magazine was hot. TV had The Six Million Dollar Man, The Bionic Woman and the original Battlestar Galactica. Even music was jumping on the star wagon: Styx had spaceships at the climax of "Come Sail Away" and a Tolkein tribute song on their album Pieces of Eight. Heck, the entire British progressive rock scene owed as much to fantasy literature as it did to rock and roll. The time was right for me to undergo the final metamorphosis into the kind of genre fan and writer who lives, breathes and dreams about spaceships and dragons, lost in a world of imagination and whimsy.

But I was saved at the last minute from this darkness, by Darkness.



Bruce Springsteen's fourth album appeared in 1978. Prior to this, I knew him primarily from FM radio, which had introduced him via "Rosalita (Come Out Tonight)." But now I was right there for the new album, and because of it, nothing would be the same.

The music on Darkness is solid and muscular, made up of snarling guitars and surging keyboards. But the lyrics are what make it special, and what made me connect with it. The romantic escape of his prior work is gone, burned out and swept away. Every song is about people trapped in small-town lives, in soul-crushing ennui where dreams no longer matter. Yet in each song is a kernel of something that might be hope.

What really spoke to me were the songs about fathers and sons. By its very title, "Adam Raised a Cain" states its purpose, and musically recreates all those arguments between every dad and every son. "Factory," which at first seems so slight it might be filler, actually described my own father's life in painful detail. In fact, for the first time I realized it was possible to make music--and by extension, any kind of art--from someone's own life. Not in the literal autobiographical sense, but through feelings that everyone understood and experienced, emotions other than the "love/escape/party" music on the radio. Or the "heroic destiny/good vs evil/love conquers all" tropes at the heart of what I read, listened to and watched.

Because of this music, I stayed connected to the world in a way I otherwise might not have, and often against my will. No matter how much I wanted to disappear into the Federation, the Rebellion, Pern or Shannara, the Boss would drag me back. Because I became a long-term Springsteen fan, I couldn't ignore or escape the real world. And when I began to synthesize the things I loved (horror and fantasy) with this real-world connection, I found my voice as a writer.

This is all fresh in my mind due to the release of The Promise, an exhaustive 3 CD/3 DVD set chronicling the making of the album. But I'd steer anyone interested simply to the album itself. Everything I talk about is there. And if you're a fan of my books, then you'll be able to share the moment when I turned onto the path that eventually led to the stories you enjoy.

Friday, November 5, 2010

The Loving Dead: zombies with one thing on their minds


When it comes to the living dead, I'm strictly vanilla. I want my zombies slow, shambling, mindless and prolific. I have no time for zombies that run, or speak, or suffer from a virus and aren't really zombies. So I began reading Amelia Beamer's The Loving Dead with a bit of trepidation, since her zombies are not only virus-spawned (and thus not technically dead), the virus is an STD. These zombies are both hungry, and horny.

But there's more at work here. For while the book breaks a lot of my zombie preference rules, it does include one thing I believe is essential for every good horror story: a level of metaphor. The Loving Dead may be about individual characters, but it's also about a specific class of people: disaffected urban twentysomethings so unused to having anything truly matter that, when the first zombies appear, their initial reaction is to pop in a DVD of Night of the Living Dead. Not to get survival hints, mind you, but just because of the association.

Michael and Kate are platonic housemates and co-workers at a San Francisco Trader Joe's. They throw a costume party the night the zombie apocalypse begins, and initially think it's all part of the game. When they realize it's not, but can find no corroborative evidence on TV or the internet, they're completely at a loss. Separated for most of the story, the twin narratives draw them together at the safest place they can imagine: the island of Alcatraz.

The book reminded me most of a fairly obscure Japanese SF film called Matango, or in America, Attack of the Mushroom People. In it, a shipwreck maroons a bunch of 60s-era affluent Japanese on a strange island, where they contribute absolutely nothing to their own survival before they apathetically mutate into the titular mushroom people. In its native country it was seen as a mocking attack on middle-class complacency; recut for the States, it came across as a big helping of WTF? But The Loving Dead shares its sense of a generation so unaccustomed to anything geniune that, when real danger arrives, they can only ignore it, or relate to it through pop culture. By the end, it's an open question whether the zombies or the humans are the most adrift in their world.

The Loving Dead is published by Night Shade Books.

Monday, November 1, 2010

Helsinki Homicide: ice cold crime without "girl" in the title


Scandanavian thrillers are all the rage right now thanks to Steig Larsson, but I've been a fan of this sub-genre since Peter Hoeg's novel Smilla's Sense of Snow and the original Norwegian version of the film Insomnia. Larsson's Millenium trilogy may be the Hunger Games of its moment, but recently I discovered another Scandanavian author, from Finland, whose crime novels are much more to my taste.

Jarrko Sipila is a novelist and crime reporter whose "Helsinki Homicide" series has just begun being translated into English. The first one, Against the Wall, won the 2009 award for Best Finnish Crime Novel. It details the investigation into the murder of a young hoodlum mixed up in customs fraud, and follows parallel paths as both the criminal underworld and the police force seek the motive behind the crime.

It does something I love, best exemplified by the Michael Mann film Manhunter: it makes you hope that real cops are as smart, resourceful and tenacious as the ones in the story. The team under Lieutenant Kari Takamaki is unified by their dedication to duty, a Hawksian professionalism that needs no trite character justifications. These men and women do their job because it's their job, and they get their satisfaction from doing it to the best of their abilities. This is what separates them from the criminals, who are equally smart and resourceful but prey to disloyalty, greed and complex bonds of loyalty and revenge. The cops win by essentially maneuvering the bad guys into tripping over their own worst tendencies.

It's a bit hard to evaluate Sipila's style, since it's translated to English from Finnish; apparently the only word the two languages share is "sauna." He started as a journalist, so I imagine in his native Finnish his prose is punchy, succinct and vivid; if it's a little clunky in English, I can live with that. I had no issue with one common criticism, the complex Finnish names, except where two very similar ones (Lindstrom and Lydman) were concerned. Still, the cleverness of the plotting, the broad strokes of character and the unique milieu come through just fine. And what connects with the reader is the universality of it all: criminals have the same motives in Helsinki that they do anywhere else, and cops want to catch them for the same reasons they do in New York or LA.

Against the Wall is followed by Vengeance, which is near the top of my to-be-read pile. Hopefully more of the series will make it into English as well, because tough, honest crime novels are always welcome.

Sipila's novels in English are available directly from the Minneapolis publisher, Ice Cold Crime.