I Have Not Forgotten You...

Assuming, of course, that anyone besides Patrick and me is reading these!

The rest of my life intruded over the weekend, via an annoyingly bad cold. So I lacked the time and energy necessary to craft the next installment in the Brief History. Or indeed, the mental faculties to recall the Brief History.

Unless you wanted to see an installment that read, "And then I said some stuff and Patrick said some stuff and some stuff happened and we made a comic."

Wait, let me guess -- you wouldn't have noticed a difference?

Actually, I'm going to take this opportunity to ask for a shout out from those of you who are reading -- could you drop by and say hello in the comments section?

And I'll be back with a real post in a day or so. Thanks for your understanding!

A Brief History of Cold Iron Badge, Part 4

Once upon a time, before Professor Stephen Hawking wrote his book, it was possible to write a brief history of something and call is something other than 'A Brief History of Something'.

Not afterwards.

At first it was a joke, an increasingly obvious and un-clever go-to reference. But then it stopped being a reference and, because of its ubiquity, simply became the natural way to refer to a not-very-long written narrative detailing the origin and development of something.

(There were other Brief Histories before Hawking's, of course. But he put the phrase on the popular cultural map in a way that it hadn't been before -- or, to use a more elegant and apt turn of phrase, he put it into IdeaSpace.)

Not to expend too much effort justifying my own lack of creativity in blog post titles, but it never occurred to me to call this series anything other than 'A Brief History of Cold Iron Badge'. And I'd be willing to wager that none of you saw that title and thought that I was referencing Hawking particularly, whether cleverly or (more likely) not.

A Brief History of Blah-de-blah has become a trope.

This is not the only evolutionary path that a trope can follow, but it's an important one for storytelling -- for fiction. Because, occupying a level of universality that lies beyond references, homages, rip-offs and cliches, tropes are fundamental concepts that don't need to be explained for the audience.

Whether something is really a trope, or merely a reference/cliche/et cetera of course depends on who the audience is. There are tropes that are common to every culture, every demographic, every sub-culture, even every clique, that someone from outside those particular groups wouldn't get on the same subconscious level... and there are tropes that are common to all of humanity.

Cold Iron Badge was deliberately designed to be very, very tropey.

I touched on this in my last post, but it bears repeating and exploring in more detail: There are a number of points where Cold Iron Badge pretty blatantly uses tropes -- touchstones, storytelling conventions -- from either fantasy literature, cop shows, or both. And this was entirely intentional on my part.

A story that is fundamentally -- as I also noted last time out -- a genre mashup absolutely depends on honouring the key tropes of the genres that it's drawing from (and sometimes on subverting them). It's important on many levels, but one of the most important is the most basic. Because tropes, especially genre tropes, tell the audience what sort of expectations to have of the story. And when those expectations are either entertainingly fulfilled, or entertainingly subverted, the audience is generally happy. Which makes the writer happy.

This is true of all genres, but genre mashups are particularly fun for this, because an audience familiar with the tropes of all the genres involved will understand when there's conflict between the tropes of the underlying genres. Which creates dramatic tension, interest, and lots of opportunity for expectations to be fulfilled or subverted in a most entertaining manner.

And this, more than anything else, is what pushed the evolution of the collection of characters and other loose concepts that I've been talking about to become Cold Iron Badge.

What, for instance, would cause an interesting dynamic between Christine and Delric, while also forcing them to work together? Why would people like Ray and Bunny -- with their, to be tactful, questionable degree of competence -- be front-line law-enforcement personnel? What would cops as we understand them have to do with Fairyland at all?

The answer came to me, as many do, on the subway. I couldn't tell you what inspired it -- well, the whole process I've been discussing in these posts inspired it, but I don't remember what specifically led to the, "Eureka!" moment.

But there it was: After a mysterious event opens the doors between Earth and Fairyland, people who are themselves strange and marginal enough to be able to cope with all the weirdness are tasked to watch the new border between the two worlds. To enforce the laws, prevent incursions and excursions in either direction, and to keep a fragile peace.

I liked it. It made sense to me, it made sense for the characters. It gave both fantasy and cop show tropes free rein and it provided a roomy stage that would fit all kinds of stories and ideas.

It worked for me, and a couple of emails later, I knew that it worked for Patrick too. We didn't have a plot yet, but the core of what was now definitely called Cold Iron Badge was all there.

Next step: Go from characters and concept to an actual story. More on that next time...

A Brief History of Cold Iron Badge, Part 3

So Patrick was in a "super" mood -- eager to work on a story with superheroic or supernatural elements.

I can get behind a good superhero story, but I wasn't in the mood to write one.

(An idea that Patrick and I had talked about working on a couple of years previously had been a superhero story -- it got as far as being outlined, having the script for the first issue written and all the key characters designed. Then, between our schedules at the time, and someone else independently coming up with another version of the same idea, it fell by the wayside. I may talk more about this project another time, as I still have a great deal of affection for it.)

That left the supernatural.

As you've probably already inferred from some of our previous posts, though -- as well as the comic that we eventually cooked up -- we were both of a mind to create an action-adventurey kind of supernatural tale, rather than one that focused on, say, horror.

(Actually, I pitched Patrick a teenagers-getting-disembowelled story that I had on the shelf, in the form of a mostly-finished screenplay. It wouldn't have been difficult to turn into a comics script, but it wasn't Patrick's cup of tea.)

So we were looking at at least some of our protagonists being tough and competent.

But despite that, "Bunny Mayhem" was the first character to be imported into Cold Iron Badge.

Imported?

Yes. A lot our our characters existed in some capacity previously to Cold Iron Badge. Not precisely, of course... not in the final forms they appear in now. But Patrick and I -- entirely separately -- had character concepts or sometimes just names, from years of ideas that were waiting for the right venue.

Patrick had been looking for a story to use Christine McCall in for years. Ray Donovan was a character name I'd made up as a teenager meshed with a character concept that was much more recent. And Delric... well, Delric's origins are dorkily embarrassing.

But Bunny was the first. Bunny was one of mine, but I think Patrick suggested using her. And because she was the first, Bunny ended up defining a great deal of what came afterwards.

Because of her name, you see.

Because in the time between me coming up with the name "Bunny Mayhem", there was another supernatural action-adventure story that achieved some degree of success, featuring a title character with an ever-so-slightly similar name.

Bunny.

Buffy.

Bunny. Buffy.

Buffy. Bunny.

You see the problem?

I felt, very strongly, that I needed to deal with this similarity -- which really was a coincidence -- by crafting a story that would not otherwise invite comparison with Buffy the Vampire Slayer. But was still a supernatural action-adventure story.

Well, this happened to dovetail with some other things I'd been thinking about. I tend to enjoy genre mashups, and I like procedurals a lot -- they provide story hooks that are immediately understandable to the reader and don't require a lot of complicated backstory to understand: The heroes are involved in the story because it's their job. This balances nicely with the need for fantastical stories to establish and explore a world that is clearly different from our own. So fantasy and procedural seemed like a good fit.

But what sort of procedural?

As I suggested in an earlier post ('Does Fantasy Have To Be Anti-Democratic?'), inspired by both the fiction and the criticism of Ursula K. LeGuin, I think a lot about ethics and fantasy. Much fantasy seems to be seriously at odds with contemporary ethics, and one ethical issue that bothers me a lot in many supernatural action-adventure stories is secrecy, a distrust of the public, and a lack of accountability.

The illustrious Vampire Slayer, for instance, operates in secrecy, aided by a few friends. An attempt by the U. S. military to get involved in battling the supernatural was a major plot point in one season, and interestingly, was treated as being at best horribly misguided, at worst an immoral conspiracy that became a tool of the forces of evil.

The irony of this wasn't lost on me, and neither was the opportunity to resolve my own ethical issues with some of the elements of my chosen genre while also clearly differentating my story from Joss Whedon's.

My heroes wouldn't be secretive vigilantes, but cops, protecting a public that was fully aware of both their existence and that of the supernatural menace...

Um, which was going to be what, exactly?

More on how we solved that problem next time.

A Brief History of Cold Iron Badge, Part 2

So Patrick and I had agreed that we should work together on a comic without actually knowing what the project was going to be.

Now, I had a bunch of ideas that I thought were pretty solid. Some of them, I'd been waiting to use for years.

None of them was Cold Iron Badge.

They were good ideas. They would have made good comics. I suspect that some of them would have lent themselves better than Cold Iron Badge to monetizing and merchandising.

But they weren't ideas that worked for both of us. No matter how good they were, I couldn't be married to them. We found -- had to find, through a lot of discussion and a lot of give-and-take -- a story that we could both get excited about.

There are a few reasons for this; one is philosophical. I'm not a proponent of applying auteur theory to comics -- even though it's actually possible in comics to be an auteur (unlike, say, film).

But just because something is possible doesn't mean that it's always a good idea. Collaboration is an incredibly powerful creative tool, and a lot of my own best writing has been collaborative. Comics is a medium that lends itself to collaboration. Particularly in my case, since I can't draw, and I am pretty much utterly dependent on having a creative partner in the form of an artist if I want to make comics.

(And even in comics, there are few genuine auteurs. My friend Mark Oakley is one. But even Dave Sim had Gerhard.)

Another reason is practical. In any comics project, the artist is going to be spending a lot more time drawing it than the writer spent writing it, so if there's no money on the table, it damn well better be something they actually want to draw.

(I believe it was Warren Ellis who said that he begins every new collaboration asking the artist he's working with questions like, "What do you love to draw? What do you hate to draw? What have you always wanted to draw and never gotten the chance?" That thought was never far from my mind while Cold Iron Badge was coming together.)

And besides: Patrick is talented. He has good ideas. Why wouldn't I want him involved in creating the story?

This isn't unprecedented for me -- Xeno's Arrow was developed in very much the same way, with Greg Beettam and me discussing the kind of story we wanted to tell, building our characters and world outwards from the initial desire to collaborate. It wasn't the first idea we kicked around, either -- just the best. It beat out, by the way, an idea that we did give a lot of thought too, that even got to the scripting and plotting stage before we decided that we weren't really into it, and which -- conceived, keep in mind, in early 1993 -- was eerily similar in many ways to Harry Potter.

That's a whole 'nother story, but I will say that it's enough to make me wonder if Alan Moore is right about IdeaSpace.

So: Patrick and I were kicking ideas around, mostly by email. And the germ of what became Cold Iron Badge was contained in a phrase he wrote, about being in a "super" mood -- wanting to tell a story that was superheroic, or supernatural. I immediately gravitated to the latter.

More on how that evolved into Cold Iron Badge next time.

A Brief History of Cold Iron Badge, Part 1

I'm going to leave my impressions of the rest of the first edition of The Hobbit -- from Chapter Six on -- for another time, for a couple of reasons.

I haven't actually finished it yet, for one thing -- I've been reading other things, books that I can actually read while on public transit without fear of damaging an heirloom. A lot of science fiction (one of my other loves, and which I also write) by John Scalzi and Charles Stross, both terrific writers.

The other thing is that first edition of The Hobbit, after the radically-different Chapter Five, the variation between versions in the chapters that follow is pretty minor. Barely noticeable, and not the sort of thing that makes for very interesting analysis.

So, if I'm not going to bore you with that, what do I intend to bore you with?

Well, Patrick has been wowing everyone with his posts about process, so you've learned quite a bit about the whys and hows of his creative choices. But you haven't heard much about the writing side of that particular coin.

So: How was Cold Iron Badge conceived? How did that translate into the story you've been following and, I hope, enjoying the hell out of?

It emerged, first and foremost, from a desire to work together.

Patrick and I have been friends for a long time, and at various times in the past we had talked about doing a comic of some sort. Nothing that had gotten beyond an interesting conversation or two and some character designs.

About a year and a half ago, I was frustrated. My attempts at breaking into screenwriting had long since fallen by the wayside (the details are a long story for another time). I had also recently had reason to remind myself why I've always avoided writing short stories or a novel: I'm just not very good at prose. What I'm good at is scripting.

Especially in the wake of attending the 2007 Toronto Comics Art Festival, I missed comics. But it was clear to me that, in terms of creative outlets that were fun, didn't have many related expenses, gatekeepers or bars to entry, but still held out the possibility of being of high quality and maybe even profitable someday, webcomics were where the action was.

The problem was, I can't do a webcomic by myself. Because I can't draw. It pisses me off. It's the one talent I don't have that I really, really wish I did. But I can't draw for beans.

At that point, I didn't have many contacts in comics anymore. My "career" (and I use the self-deprecating quotes advisedly) was about as cold as my "career" in film. The artists I was still in touch with were all busy with their own lives and projects.

So, Patrick and I were talking, and I was bemoaning my situation. "The problem is," I whinged, "That I don't know any artists who want to work with me!"

"Ahem," he replied.

"Oh! I thought you were busy!" I said.

So, that was where it all began.

That left wide open the question of what we were actually going to work on. More on that next time.

The Riddle of Riddles in the Dark

On to Chapter Five: 'Riddles in the Dark'. Bilbo, lost and alone in forgotten caves beneath the Misty Mountains, finds a Ring, finds Gollum and finds his way out. And some riddles are exchanged.

That much is the same.

There's so much that fascinates me about the changes between Chapter Five of the first edition of The Hobbit and the revised version, released after the success of The Lord of the Rings, that most of us are more familiar with.

(I'm going to stop at this point to somewhat belatedly acknowledge that what follows is going to contain rather a lot of spoilers. Although if you don't already know what happens in The Hobbit, why the heck are you here? Go read it. Now. Come back later.)

Obviously, Tolkien's big ret-con* is the centrepiece. Over the course of writing The Lord of the Rings, his conception of what the seemingly innocuous ring of invisibility that Bilbo found deep under the Misty Mountains actually was changed so dramatically, that Chapter Five of the original version of The Hobbit simply made no sense at all anymore. So Tolkien came up with the brilliant idea that the story as originally written was a lie that Bilbo told, and wrote in his memoirs, because he wanted his claim to the Ring to be indisputable, and was ashamed at the thought that he'd stolen it.

Tolkien had a little bit of fun at his own expense, as well, when Frodo and Gandalf discuss Bilbo in The Fellowship of the Ring and Frodo describes the "true" version of the story as "much more likely."

And then, of course, Tolkien rewrote The Hobbit, emending many minor details (as discussed in one of my previous posts) and altering Chapter Five extensively, making it reflect the "truth" as described in The Lord of the Rings.

But that vital change was made up of countless other changes, major and minor. One of them in particular is surprising to me: Gollum barely matters to the story at all.

The Hobbit was written by a man who had studied, and who understood, myths, folklore and fairy-tales right down to the core of his being, so it's no surprise that The Hobbit shares at least some of the classic characteristics of the Hero's Journey as articulated by Joseph Campbell. Campbell suggests that the Hero's Journey consists of a call to adventure, a journey out, a series of tests, some sort of ultimate trial (usually a confrontation with death) and if the hero succeeds, a journey back, with a reward.

Of course these criteria are sufficiently general that they can be applied to a very broad range of stories. But I don't think that it's entirely a coincidence that the subtitle of The Hobbit is There And Back Again.

The point of this digression is that The Hobbit is a story about a journey, a going and a returning. It's also an episodic story, well-suited to being read aloud a chapter a night at bedtime. Bilbo goes from one point to another in his travels, meeting new characters and having fairly discrete adventures along the way.

But the interesting thing is that virtually every character that Bilbo encounters returns at some point. Every character becomes important again later on, either at the climactic Battle of Five Armies or during Bilbo's return home at the very end of the story. Elrond, the Goblins and Wargs, Beorn, the Elven-King. Even the trolls, indirectly, when Bilbo and Gandalf pick up their treasure on the way back.

Except Gollum. Gollum, after Bilbo leaves the Misty Mountains, never matters again in the story. He was a mechanism for getting Bilbo the Ring and getting him out of the caves.
Gollum, who is arguably the pivotal character of The Lord of the Rings -- key to the theme, the unfolding action and the resolution, the tragically fallen counterpart to Frodo -- doesn't matter.

He's also a rather more pathetic figure, who apologizes to Bilbo for losing the Ring that he apparently genuinely intended to give him for winning the riddle contest, and tries to make up for it by leading him to safety. He's clearly not a very nice person (the reference to him eating Goblins, when he can, is present in both versions) but he's not the treacherous, debased, tragic, obsessive figure we know from The Lord of the Rings. His last words to Bilbo are directions: "It musst squeeze in and sneak down. We dursn't go with it, my preciouss, no we dursn't, gollum!"

Compare that to the blood-curdling accusation and threat, "Thief, thief, thief! Baggins! We hates it, we hates it, we hates it for ever!" that echoes in Bilbo's ears, and across the pages of The Lord of the Rings right through to the conclusion.

Gollum was a minor, almost a throwaway character.

That Tolkien had the chutzpah to change things so dramatically is frankly astounding.

It's also inspiring, and illustrative.

It's a reminder that tales can, and sometimes should, grow in the telling. That I -- that we -- can grow creatively, and that the process of creative growth never really ends. That earlier works can be reinterpreted in the light of later ones. That characters too, can grow and become more than they were.

That these changes, sometimes even retroactive ones, are not something to be feared, but opportunities to be explored.

Tolkien was good enough, and wise enough, to grow with his work as his work grew with him, and he was smart enough to use that growth as a solution to the story problem it created.

None of which means that I'm about to rewrite the past to support the revelation that Christine is actually a spider elemental, or that Delric is really a giant who only looks like an elf because he's been merged with a magic sword.

But the reason not to do those things isn't because they'd be ret-cons, but because they'd be stupid. I think that's my take-away from all this, and a new mantra: Embrace change, but avoid stupidity.

After all, Tolkien managed it.

Next: 'Out of the Frying-Pan Into the Fire'. Yes, that's what Tolkien actually called Chapter Six of The Hobbit.
__

* That's geek-speak that means a retroactive change to continuity.

From An Unexpected Party to Riddles In The Dark

So, we were speaking of The Hobbit.

As I mentioned, I decided to finally -- I've had the book for about three and a half years -- read the first-edition copy of The Hobbit that my wife gave me.

So far, in the limited amount of time I have to read for pleasure (other than on the subway, which is not something I'm going to subject a seventy-year-old rare book to) I've covered just over a hundred pages -- from the start of the story to just past the ending of Chapter Five.

Chapter Five, 'Riddles In The Dark', is of course the chapter that's radically different from the version of The Hobbit that most of us are familiar with, the chapter that Tolkien felt he had to ret-con in order for Lord Of The Rings to work. More on that another time. The four chapters that precede it, in comparison, are not altered as dramatically. Minor changes at most -- a word here or a sentence or two there, that's about it.

And the overall difference is almost shocking.

It's not that the book isn't outstanding. It's just strikingly different. And, to anyone familiar with Lord Of The Rings, sometimes bizarrely so. The idea that one of Bilbo's Tookish ancestors had married a fairy is followed by a paranthesis noting that less friendly people suggested it had been a goblin. And Elrond refers to his High Elven kindred as "gnomes".

But it goes deeper than that.

The Hobbit, in the version that most of us are familiar with, is full of anachronisms and things that strike a tone that's not entirely consistent with Lord Of The Rings. But anachronisms and inconsistencies of tone are a huge part of what Tolkien cut -- so those elements are even more pronounced in the original.

The overall effect, for me, was that the story reached, and then crossed, some sort of tipping point. That tipping point was in Chapter 2, 'Roast Mutton', on page 43 in this edition.
The Dwarves are discussing the dubious character of the region they and Bilbo are crossing (as they do in both versions). The italics are mine, for emphasis: "These parts are none too well known, and are too near the mountains. Policemen never come so far, and the map-makers have not reached this country yet."

Policemen? In Middle-Earth?

In the long-abandoned wild lands between Bree and Rivendell? What policemen? Whose? How?

Policemen?

And with that, the balance of the familiar and the fantastic, that Tolkien was such a master of, was thrown irrecoverably off.

Again, none of this makes the first edition of The Hobbit a bad book, or a poorly-crafted one. It's a great book, wonderfully written. But it clearly doesn't take place in Middle-Earth, not really. It takes place in a world much more like our own, that uses the languages, and history, and some of the characters of Middle-Earth to enrich a fine and very engaging story.

Fantasy fiction depends on striking that balance -- what and where it lies depends on the story -- between the familiar and the fantastical. And what I've realized, in reading The Hobbit as it was originally written, is how small and subtle the choices that balance rests on can be. A single word, a single idea that doesn't quite fit, can make all the difference.

Fantasists, it is sometimes said, are playing God, freely creating entire worlds to tell their stories in. Well, this is a reminder of the tremendous responsiblity that accompanies that freedom. The existence of an imaginary world is always provisional; it depends on the reader continuing to believe in it. And the smallest inconsistency or wrong note -- a single word! -- can tip the balance from belief to unbelief. And then poof. A whole world gone, like that.

As a writer of fantasy, I haven't decided yet whether the fact that even Tolkien struggled to find and maintain that balance takes the pressure off me... or just makes me feel doomed.

Next time: Riddles In The Dark.

In A Hole In The Ground There Lived A Hobbit...

For me, it all begins with Tolkien. And that means that it begins with The Hobbit.

The Hobbit, besides being a genuinely great book, is a very interesting one from a writer's standpoint. It's the reason that The Lord of the Rings exists -- no Hobbit, no call for a sequel, and yet it was never intended to introduce people to Tolkien's Middle Earth.

Tolkien originally wrote The Hobbit for his children -- he wrote a great deal for his children, including annual letters from Santa that were eventually collected as The Father Christmas Letters -- and as such it was mainly intended to be an exciting, entertaining adventure. But it's also, and this was quite unusual in fantasy for children at the time, clearly set not in a generic fairy-tale setting, but in a very concrete world different from our own -- a world with a deep and meaningful and mysterious history that was only really hinted at.

Of course, Tolkien wrote The Hobbit while he was also involved in his life-long project of creating the languages and mythology of Middle Earth -- the stories that became The Silmarillion. So he went to those tales when he needed names and events from the distant past of Bilbo Baggins's world. Elrond, the legendary blades of Gondolin and the ancient battles between Elves and Goblins (they weren't called Orcs yet), these are all Tolkien bringing his secret obsession to life by putting elements of it into a story that other people would actually see.

But in doing so, and by being so unbelievably good at it, he set in motion a chain of events that would lead to him writing The Lord of the Rings, and eventually (after his death) to the publication of The Silmarillion, in a version compliled by his son Christopher Tolkien with the help of Canadian and later fantasy writer Guy Gavriel Kay.

What that means, is that what was intended to be a one-off story for children that had a few minor references to Middle Earth became most people's actual introduction to the actual Middle Earth.

So there were a number of discrepancies, in both tone and detail, between The Hobbit as originally written and Tolkien's vision of the "actual" Middle Earth. And since Tolkien was before all else an inveterate world-builder, this bothered him.

What did Tolkien do about it?

As a writer, I find what he did very interesting.

First of all, when The Hobbit was re-released in the wake of the success of Lord of the Rings, Tolkien went back and changed things, mostly minor details. Terms that that had fallen out of his evolving "translation" of the languages of Middle Earth, and words that didn't quite convey the right tone were most of it.

But there was a much bigger change along with the minor ones, and it's something Tolkien included in Lord of the Rings.

The Lord of the Rings contains an early example* of what we Big-Time Geeks call a ret-con -- a retroactive change to a story's continuity. Without giving too much away, it has to do with how Bilbo Baggins gets the Ring from Gollum. Tolkien's changing notion of what the Ring was by meant that the story as originally written didn't make sense anymore.

So Tolkien, through Gandalf and Frodo, explained that the version of the story that appeared in The Hobbit had been a lie, made up by Bilbo to justify keeping the Ring.

But the new, "true" version of the story was also incorporated into the revised edition of The Hobbit -- Tolkien rewrote that whole chapter. So the ret-con in Lord of the Rings read a bit strangely to anyone, like me, who first read the revised Hobbit. Because it was a fix for something that wasn't broken anymore.

I love that story. It's a wonderful illustration of Tolkien's brilliant, meandering and incremental creative process. But I've always wanted to read the original version, to see for myself how it differs, and to find out just what Bilbo said when he lied to the dwarves.

Yes, I'm a huge Tolkien geek.

I am also, now, the proud owner of a first edition of The Hobbit. It was an engagement present from my wife, which is a whole other story that deserves its own post.

But the funny thing is, I still haven't actually read it. There's always so little time -- and with work and family obligations, I've never had the time to read it in a place and situation where the book would be safe. A first edition of The Hobbit is genuinely rare, and when a book is genuinely rare and also one that you personally revere and that was an engagement present from your wife... well, you don't just take that book on the subway for the morning commute, you know?

But I think it's time, now, to read it. To see what Tolkien changed, and what he didn't. To read 'Riddles in the Dark' as it was originally written. And to share my impressions.

I'm looking forward to reading The Hobbit for the first time. See you in a couple of weeks with some thoughts on the subject.

--

*"Early" is a relative term, of course. A genuinely early example of a ret-con would be the idea, which seems to have been popularized in the Athenian tragedies of the Fifth Century BCE, that Helen had not actually gone to Troy, but had sat out the Trojan War in Egypt while a doppelganger was in Troy in her place. So, you know, she hadn't actually done anything wrong, and it was okay that she and her husband got back together after the war because she wasn't really responsible for the death of thousands. But I was speaking mainly about Western popular fiction.

Portrait of the Writer as a Young Nerd: Influences

In our interview (conducted by the inestimable Shaenon Garrity) just before Cold Iron Badge launched, I was asked for some of my influences as a fantasy writer. I mentioned Steven Brust, Charles De Lint, Guy Gavriel Kay, Tanya Huff, Neil Gaiman, and Joss Whedon.

Now, this was by no means an exhaustive list. As worthy as those creators are, I was focusing particularly focused on works in fantasy that were influences on Cold Iron Badge.

Brust, for instance, inspired me to explore low-fantasy, street-level characters dealing with high fantasy problems, while mixing in sensibilities from other genres (Brust adds mystery and noir; I threw police procedural into the genre blender).

De Lint was one of my keys to urban fantasy, and along with Guy Gavriel Kay's Fionavar Tapestry also to unashamedly Canadian characters and settings. I, of course, repaid the favour by having characters named in their honour horribly murdered.

But, as I said, that's a "influenced Cold Iron Badge" list more than it's the "influenced Stephen" list. Here's how incomplete it is on the latter front:

It doesn't. Mention. Tolkien.

Tolkien was my gateway drug to fantasy. Tolkien was where it all started. He's the reason that the modern fantasy genre exists in anything close to its present form. He's the reason both that there is a Dungeons & Dragons (1) and that I cared enough about the content to want to play it. The thousand and one pale imitators who followed in his wake are evidence of the enduring power, influence and excellence of his work.

I'll probably have more to say about Tolkien in the future; pending that I will note that Lord of the Rings is a profoundly deep, powerful work. It's an essential piece not only of the canon of fantasy, but of English literature in general. I both envy and sympathize with those who haven't yet read it (they've missed out on the pleasure so far, but get to read it for the first time), and I can get pretty judgemental about people who didn't like it (2).

I also owe a rather strong debt to Roger Zelazny. A warm, funny, deeply intelligent and humanistic writer, he used a seemingly effortless light and fluid style to juxtapose the heroic and the human, the perfectly immortal and the tragically mortal. He's probably best remembered for his Amber series, and that's where I first encountered him, although Lord Of Light is often considered his finest novel. I learned a lot about writing from reading Zelazny. His few, too-brief essays on writing, and anecdotes passed along by other writers who knew him, amount to a crash course in creative writing.

And there's Douglas Adams, who didn't write fantasy, but whose wit and sense of the ridiculous influenced me deeply. He's another writer, to point out what's becoming a pretty clear theme, who put ordinary people in a world ruled by the rules and tropes of genre fiction, and made them try to cope with it and get out alive and sane.

Of course, especially as a young aspiring writer, everything I've read (3) influenced me one way or another. For good or for bad, pushing me towards or away from particular approaches and ideas, giving me examples I was inspired to emulate or motivated to avoid.

(There's lots to say, for instance, about the schlocky fantasy I read as a teenager that I would now place in my personal Hall of Shame. Or, more charitably, I could characterize those books as examples that I was inspired to avoid. But that's a long, embarrassing story for another time.)

The process never stops as long as we continue to live and to learn, although it does level off. I'm older now, I have a stronger grasp of craft and of my personal voice. It's less likely that the next novel I read will be such a strong influence that it'll be a game-changer in how I view fantasy, writing or life in general.

In contemporary fantasy, for instance, there are a lot of writers I admire, whose books I love, who I still wouldn't characterize as strong influences. George R. R. Martin is one; he revitalized the genre with A Song of Ice And Fire -- read the series, but only if you can stand the pain, because he's brilliant at putting his characters through the wringer.

There's J. K. Rowling, who with Harry Potter not only found great success, but basically made reading cool again (and note that she did it, again, by mixing and matching genres, in this case the fantasy epic with the classic British "kids gang solving mysteries" adventure, as if Lord of the Rings had been written by Enid Blyton).

And Terry Pratchett, as funny as Adams but deeper, putting genre-conscious characters in a world ruled by fantasy tropes, and then letting them change that world and the world change them.

Of course, creative influences are funny -- trying to break them down into something as neat and tidy as clear genre categories is ultimately futile. Even in this short list, I've broken away from speaking exclusively of fantasy writers to include Douglas Adams. Everything I've read really has gone into who I am as a human being and as a creator, not just the books with dragons and swords. Maybe I'm ignoring the early impact of the Hardy Boys on my writerly development. Or the significance of the fact that I stand alone with Steve Bochcho in having thought that Cop Rock was a totally awesome show.

And yet.

There must be something inside me that drew me, not just to fantasy, but to the writers I've cited here. Some reaction, some spark that made me choose fantasy as a vehicle for my storytelling (4). The common threads, the seeds of inspiration, are so clear, the connection must be real. And I also think -- I believe -- that it's a connection that is important and meaningful.

In the end, of course, it's readers (and, in the case of the truly great, which I'm not, literary biographers and university professors and the like) who truly and most clearly see the connection between writers, following the thread of influences. And they in turn are influenced by me (5) and it all begins again.

Which is humbling, and a little daunting. I thought I was just writing a fun adventure story about a cop who teams up with an elf. Now I'm part of the endless cycle of influences that ripple through our culture, affecting people, changing the world.

No pressure, huh?

---

(1) Yes, I've read about the history of D&D, and I know that Gary Gygax always claimed not to have been particularly influenced by Tolkien; however, it's because of the appeal of Tolkien, and the Tolkien-related hooks in D&D, that it found an audience. D&D may have been rooted in wargamers developing rules for small-unit tactical skirmishing with fantasy elements derived from Moorcock, Lieber and Vance, but that's not what made D&D a phenomenon.

(2) In this viewpoint I may be unkind, but I'm at least in good company; see Ursula K. LeGuin's wonderful essay, 'Why Are Americans Afraid Of Dragons?' You can find it in The Language of the Night, a collection of her short non-fiction.

(3) And seen, and heard, and experienced, but this is supposed to be a blog post on fantasy, not my autobiography, and I'm trying to stay on point.

(4) This also, of course, completely ignores the fact that Cold Iron Badge is a work of collaboration; Patrick and I developed the story and characters together, and he has his own experiences and influences that he brought to the process.

(5) "This Geigen-Miller clown is a hack! I can do better than this!"