thekitchenbrigade_ecoverI admit to suffering from dystopia fatigue. I love the classics of the genre, like Nineteen Eighty-Four, but the last decade has seen so many bleak future/post-apocalyptic/totalitarian government-type stories that it takes a lot for me to pick one up. But after reading Lydia Schoch’s interview of Laurie Boris, I had to give The Kitchen Brigade a shot. And within pages, it won me over.

The Kitchen Brigade is set in 2049, in the remnants of a United States torn by civil war and occupied by Russian forces. Valerie, the daughter of the former U.S. Secretary of State, has been captured by the Russians and forced to work in a kitchen, serving a Russian general and his officers. 

All the women serving in the kitchen are assigned numbers instead of names. Valerie is Three. Gradually, she gets to know the other women, all of whom came there by different routes, and who have different perspectives on the situation; from the foul-mouthed but good-natured Four to the aggressively unpleasant Two, who resents Three and sees her as a threat to her relationship with the main chef, the tough-but-fair Svetlana.

As Valerie gains the respect of Svetlana and the brigade (with the exception of Two) she also begins to realize that the situation is far less stable than it appears, and soon discovers that there are multiple factions jockeying for power, among both the Americans and the Russians, and, as in any good thriller, almost everyone has a hidden agenda.

The prose is clean and the dialogue witty—especially Four, who I think deserves her own spin-off story. Her scenes were a real highlight.

I also loved how Boris gradually tells us the backstory of how the United States collapsed—it’s done in bits and pieces; scraps of information picked up here and there, but at a certain point, it becomes very clear not only what happened, but just how disturbingly plausible the seemingly-unthinkable scenario really is. It’s an all-too-believable vision of how a cyberwar could work.

A few minor gripes: there were a few times when it was hard for me to keep track of where all the characters were during the climactic sequence. It was effective, don’t get me wrong, but I still felt a little confused. It’s a not a big flaw, though; and it could just be that I haven’t read enough thrillers to get the hang of it.

Also–and I’ll be vague here rather than risk giving too much away–there’s one scene where people are oddly reluctant to kill a particularly vile character. Boris did a really good job making this character unlikable, and provided realistic motivation for why the character behaves the way that they do, so major props for that. But this person is so unrelentingly hostile, it’s hard to feel any sympathy, although some characters do anyway.

All in all, this was a very well-crafted dystopia. And Boris has a real knack for describing the elegant dishes the brigade prepares over the course of the book. I probably haven’t given the food preparation scenes their due in this review, because I’m not much of a gourmet myself, but even I could tell they were well-done. (No pun intended.)

Earlier this year, I reviewed the novella Number Seven and the Life Left Behind, by Mayumi Hirtzel. This is another tale of espionage, intrigue, nefarious Russian agents, and people with numbers instead of names. As a fan of old Cold War spy stories like Secret Agent, it’s pretty exciting to me that people are telling stories like this again. If you liked Number Seven, I predict you will also enjoy the Kitchen Brigade. And if, like I was, you’re reluctant to check out another dystopian story, just know that this doesn’t feel like a random tyrant has been inexplicably installed, as is so often the case in dystopian fiction, but is carefully thought-out and well-described. Give it a try.

A big problem in my fiction is that my endings are too rushed. I used to think this might be part and parcel of the No Description problem, but I realize now it’s a separate issue. A number of readers raised this complaint with all my early stories, and while I tried to improve in The Directorate, it still came up.

It’s also proven to be a problem with the novel I’m working on now. Several beta readers have said the same thing, and I agree with them. The ending is, once again, too rushed.

At this point, you might be thinking, “So add more stuff then, stupid!”

The problem with that is I can think of nothing else to add. The ending comes along when it does because all the pieces are in position, and it seems natural to tip the first domino and set things in motion. If I add extraneous material, readers will notice that I’m just killing time.

I hate when authors drag things out. The best example I can think of is Stephen King’s 11/22/63. While I liked some parts, there were also times when I wanted to yell, “Just get on with it already!” Since the book hinges on an event which happened in the past and which the reader is anticipating, the way King stalled with one “the past is obdurate” setback after another was annoying to read.

In general, I’d rather something be too short than too long. If a reader thinks it’s too short, it implies they want to read more. Whereas if it bores them by being too long, they’re unlikely to read anything by the author again.

But, better than being too short or too long is being exactly the right length. I have reached a paradoxical point where the book isn’t as long as it needs to be, yet making it any longer would feel too long. Which is another way of saying that something is missing, but I don’t know what it is.

*The title isn’t mine. It’s the title of a Let’sPlay of Knights of the Old Republic II, my favorite video game of all time, which is also notorious for its allegedly rushed ending.

Devil and WolfHow to describe The Devil and the Wolf? I could tell you that it deals with questions like whether humans are innately good or evil, what it means to have a soul, and that it deconstructs and reimagines many classic aspects of mythology and religion.

But that makes it sound like pretty heavy stuff. Like Paradise Lost or something; one of those great works of classic literature that hardly anybody reads because it’s so intimidatingly hard to understand. The Devil and the Wolf isn’t like that. It’s a lighthearted romp—a divine comedy, one might say. Heaven and its angels and Hell and its demons have large roles to play in the story. Besides Mephistopheles, the title devil, Belial, Beelzebub, Lucifer, Lilith and other classic hellish figures appear in the story, as do angels like Gabriel, Raphael and so on. 

There are humans in the story as well, including a team of aspiring young paranormal researchers, and a truly unpleasant couple, one-half of which is the resentful employee of Mephistopheles, though despite her hatred for her boss, she doesn’t realize he’s actually an ancient prince of hell.

And then there is the other title character: JR Wolfe, a wolf transformed into a human by the powerful magic of the devil, as part of his plan to put an end to a millennia-old test devised by the forces of Heaven and Hell to evaluate human souls. This test is part of a larger cosmology that Pastore has constructed, and which I absolutely loved. It reminds me of the religions and spiritual hierarchies and planes of existence as imagined in RPGs—yes, even including the legendary Planescape: Torment.

How does Pastore manage to make a plot work with such a disparate blend of characters? Marvelously. I would never have imagined it could be done, and yet he has done it, in a manner that was incredibly organic and natural—so smooth in fact that I didn’t even see the gears of the plot moving towards the climax until it had almost arrived.

The characters are an absolute delight, from the hilarious banter between JR and Mephistopheles, to the political machinations of Hell’s denizens, to the stuffy formality of the angels. The dialogues are full of clever insults and comebacks, and JR’s unrelenting destructiveness is unfailingly hilarious.

But beyond that, there is some real meat to this story—questions of morality, humanity, and mortality are all in play here, but in a way that’s entertaining and fun to read. That’s why I wouldn’t describe it as a philosophical novel, even though it undoubtedly is. It would give you the wrong idea.

In telling someone about this book, I called it The Master and Margarita meets A Confederacy of Dunces. The parallels aren’t exact, but that’s the best I can do. If you’re not familiar with those titles, know that both are (a) extremely weird and (b) widely considered to be some of the greatest literary works of the 20th century.

It’s probably not a coincidence that great things are also a bit strange. We don’t normally think of “strange” or “weird” as compliments. But then again, it’s hard to imagine praising something by saying “It’s so normal,” either. 

The Devil and the Wolf is such a strange, outlandish comic fantasy, and yet every character feels so real. They all have discernible goals, motivations, and beliefs, which makes the whole world Pastore created seem immediate and alive. There might be an occasional line which falls flat, but as a whole, it all works together delightfully well. My only complaint, and it’s a minor one, is that I would have liked to learn a bit more about the young paranormal investigators. They are very promising characters.

The usual caveat about typos that comes with most indie books (including my own) applies here, although given its length, I was impressed by just how few there were.

How to describe The Devil and the Wolf? I still don’t know—this review doesn’t do it justice. All I know is, it’s weird, thought-provoking and a Hell (and Heaven) of a lot of fun.

unpublishablesThe first thing to know about The Unpublishables is that when you open it in the Kindle reader, you need to make sure and scroll back to see the epigraph. At least for me, Kindle wants to launch right into Chapter 1 without showing this important front matter. But you don’t want to miss this epigraph; it really sets the tone.

Now then…

The Unpublishables is narrated by a man named Daniel, who is the only person in America immune to a virus sweeping the country. This virus attacks the mind, and causes its victims to become obsessed with writing novels.

Everywhere Daniel goes, people ask him, “What’s your novel about?” He gradually learns that the best way of deflecting this question is to ask them about theirs—which of course they’re only too happy to tell him about. 

But one day, Daniel meets a young woman named Abigail at lunch, and the two of them instantly connect over their shared love of books—reading them, rather than writing them. In a desperate effort to impress Abigail—and if nothing else, have a reason to talk to her again despite her pretentious, arrogant boyfriend, Chadwick—Daniel realizes he must write a novel. On the spur of the moment, he chooses  life among the homeless of San Francisco as his subject

The best way to write about the homeless, Daniel soon decides, is to become one of them. And so he becomes a vagrant, living with nothing but the clothes on his back and begging for food and money. And in doing so, he encounters a wide variety of strange characters, from a woman who resembles a witch to a sinister figure known simply as “The Knifeman,” who has a penchant for telling gruesome historical stories with a curious sci-fi twist.

The Unpublishables is, of course, a comic novel, and as in his previous efforts, Goats shows first-rate skill at writing lines that make you laugh out loud. Early dialogues are Wodehousian, in more ways than one. The descriptions are vivid and memorable. And the books–oh, the books! The way he writes about books is beautiful. I’ll talk more about this later, but if you’re in a hurry and have to make a purchase decision by the end of this paragraph, know that you can buy The Unpublishables for the descriptions of books alone and you’ll be a happy customer. 

And although it’s mainly comic, The Unpublishables has some emotionally powerful moments that are not played for laughs. Some of the passages about the homeless are truly moving. In particular, one section where Daniel ponders why so many homeless people talk to themselves. It’s a moment of genuine compassion and empathy, as well as being a really surprising idea that I had never considered before. But you’ll have to read the book to see what I mean.

The descriptions of life on the street are properly gritty. Goats is never afraid to go into detail to describe every facet of what it means to live without money, food, or shelter; no matter how unpleasant it may be. It’s raw and tough to read at times, but the grit balances the wit, and it makes the whole thing feel real, instead of just a simple comedic puppet show.

Does Daniel succeed in his quest to write a novel and win Abigail away from her obnoxious partner? Well, I wouldn’t dream of spoiling that! This book is hot off the presses (figuratively speaking; it’s on Kindle) and hardly anyone has had a chance to write about it yet. I know I typically spoil things, with appropriate warnings, but in this case I’m just not going to talk about the ending. It’s one thing to spoil a Hollywood film or a novel by a famous author—when I do that, I know that there are probably dozens if not hundreds of spoiler-free reviews out there that people could read instead. But as of this writing, if you want to read about The Unpublishables, you pretty much have to read this review.  In fact… well, never mind, I’ll come back to that.

The book is, by the author’s own admission, a bit weird. If you’ve read this blog before, you probably know that “weird” is not considered a bad thing here. In fact, as often as not, it’s a compliment. So yes, the book is decidedly weird; but in all the right ways. 

Also, there are a handful of typos—but way fewer than in many indie books. And their existence is even lampshaded by the narrator, who asks us to “pretend” they are stylistic choices, and not simply the result of him being a sloppy writer.   This is one of the things I love about the Daniel character; he’s a bit of an unreliable narrator, but he tells you so up front.  This sums him up pretty well. Oh, and one other technical note: there’s a formatting issue in the form of a completely blank page between two chapters. (This might be a result of reading in landscape mode, which seems to do odd things to the ereader.)

All right, now let’s get to the heart of things.  I promised on Twitter that I was going to break one of my own rules of writing reviews. What did I mean by that? 

Once in a while, when you read about fiction, you’ll see something referred to as “significant” or “important.”  For instance, Wikipedia informs us that James Joyce’s Ulysses is one of the “most important works of modernist literature.”

Anytime I see words like “important” or “significant” used in regards to fiction, it sends up a major red flag. Why, I ask, are people describing this thing as “important” when the word “good” is shorter to write and easier to say? If somebody wants me to read a book, they had better tell me “It’s good,” and if instead they come and tell me, “Read this book, it’s important,” it seems to me like they are hiding something. They may be trying to induce me to read a book that is not good for some nefarious reason. Thus, I try never to say something is “important” when “good” will do just as well.

But that isn’t to say that a book can’t be both “important” and “good.” In my opinion, To Kill a Mockingbird is both important, due to its relationship to the Civil Rights movement in the United States, and also just generally good as a story that is enjoyable to read. (In my opinion, if it had been bad, it would never have been widely-read enough to become important.)

So, first and foremost I want, to make it very clear that The Unpublishables is a good book. It’s a fun story, with memorable characters and witty descriptions. That’s really all a book needs to be to be good, in my opinion.

But I also feel that it is an important book as well—and not because of its depiction of homelessness, even though that is another very strong element of the novel.

As I said above, throughout his travels, Daniel meets all kinds of odd characters, all of whom have written or are writing a book. Each of them is an example of some aspect of indie publishing. The Unpublishables is a fine title, but the book might as easily have been called The People You Meet in Indie Publishing; because so many different quirks of the world of independent writers are covered, from ham-fisted author-insertion to blatant plagiarism. At one point, Daniel comments that more people are writing books than have read one.

Daniel finds fragments of manuscripts of historical fiction, hears summaries of wild science fiction and fantasy adventures, and meets shameless self-promoters.  Some of the aspiring writers he meets are ground into despair after all the rejections, while others are still brimming with optimism. One of them even hides his own novel in the shelves at a used bookstore, in the hopes someone will find it and read it.

The book pokes a lot of fun at indie authors, and at times, Daniel makes some biting commentaries about the whole process of writing and publishing. I was quite amused by it, and at the same time, as Jack Point from The Yeomen of the Guard would say, “My laughter had an echo that was grim,” because, like the targets of Point’s jokes, I recognized a little of myself in the figure being roasted.

Now, you might say, “How could he make fun of indie authors?!? What a rotten thing to do; kicking a person when they’re down like that!” Well, that’s the thing: Goats isn’t laughing at us; he’s laughing at himself—obviously; because he’s an indie author, too. And it is so abundantly clear that all of the jokes in this book are born of affection, rather than malice, that it’s impossible to be offended by them. 

Paul Graham once wrote that “To have a sense of humor is to be strong.”  The humor of The Unpublishables is the humor of strength, the humor that comes from people who can laugh at themselves because, to be blunt, they know they’re doing something important. After all, Goats wrote a whole book that made fun of the process of writing books. One assumes he must have really believed in what he was doing to essentially be half-laughing at himself while doing it.

And that’s what I mean when I say The Unpublishables is an “important” book: it’s important to the indie author community.  To us. I say “us” because I am an indie author, and I know that nearly everyone who reads this blog is as well. 

The appreciation Daniel (and by extension, Goats) has for books is evident throughout The Unpublishables–both books in physical form and as a medium for telling stories, for capturing some part of a person’s life. Underlying all the friendly ribbing about the oddities of the indie author world is a deep love for the written word. Plenty of all-time great authors and books are referenced throughout, and indeed, one of them is used as the catalyst for bringing the hero and the heroine together at the beginning.

That’s what I ultimately got out of The Unpublishables: at its core, it’s about the power of books—reading them, discussing them, and writing them—to bring people together; to let people share a bit of themselves with someone else. A book is a hard thing to create, but when it is done out of love, something magical happens. 

And this is where you come in. Again, I know most of you reading this are indie authors, and many of you have blogs of your own. I highly encourage you to read this book, and to write about it. Partially, I’m doing this for selfish reasons: there are things in here I want to talk about with other people—including some alternate interpretations of certain elements, as well as how different parts all tie into the theme. But it’s hard to talk about that when I don’t know anyone else who has read the book.

But apart from my own self-interested reasons, I think this book is important for indie authors. Because it’s by an indie author, and it’s about an indie author, and in some sense, it tells the story of all indie authors. 

Ah, I am a very Narcissus!

I was going to do this as a Twitter thread, but then I realized it’s too meandering for that. It started with this:

Then I realized that the references to Tennyson’s poem come in the scenes I blogged about here–scenes that already had bothered me with their similarity, until I realized the one in The Directorate is way, way better than the one in Majestic World.

I have to be honest with you guys: I look back at The Start of the Majestic World and it seems pretty amateurish to me. There are elements I like (obviously) but the book as a whole I think isn’t nearly as good as I could do now. I toyed with the idea of doing a revised version last year, but I couldn’t figure out a way to coherently “revise” it–it was easier to just start from scratch and make up a new story with a similar vibe. (It’s called 1NG4.)

I’m greatly improved as a writer since Majestic World, which on balance makes me happy-it feels good to know that you’re improving at something. But this leaves me conflicted about whether to even keep it up for sale. Part of me feels self-conscious about leaving something that’s not really my “A” game out there for sale. (It was my 2014 self’s “A” game, but not up to 2019’s standard.)

But I’m also sentimental about it. It was my first real attempt at long fiction, and some of the ideas in it have proven useful for future books. And I really, really appreciate all the encouragement and constructive criticism I got from readers. If not for you folks, none of my subsequent books would have happened. Without Majestic World, there is no Directorate.

I hadn’t re-read The Directorate since about the time I published it, but the other day, I flipped through it to check something about the word count, for comparison to the project on which I’m currently working. I was a little nervous, since the first time I re-read Majestic World after letting some time pass, I was underwhelmed by my earlier work.

Re-reading parts of The Directorate, I found myself thinking, “Wow, this is good! No wonder I worked so hard on it.”

I’m not saying that to brag; I’m saying it to say that the way to improve as an author is to write, publish, and get feedback from readers. Including–especially!–negative feedback. There may be some things that you look back on and wince a little, but it’s worth it.

 

boat classic clouds cruise
Photo by Inge Wallumrød on Pexels.com

I love ship names. I don’t know why, but I get a real kick out of it when writers name their fictional ships. My favorite example is in Robert W. Chambers’s The Repairer of Reputations, when the characters all go out for a walk and see the ships in the harbor of fictional future New York, and Louis rattles off the names of the vessels. I loved that.

I think the reason I’m so fascinated is that every ship name has a story behind it. You see a ship name, and you automatically wonder why it was given that particular name. It’s an implied story all in itself.

This goes for spaceships in science fiction too, by the way. In fact, I might even enjoy those more, because there’s more room for unusual names. I’m working on a story now that has a spaceship in it, and I’ve been struggling to come up with just the right name. It’s an important consideration–the story that the name suggests to the reader will color their perception of the characters who fly it.

Some fictional ship names I like:

  • Alert–from H.P. Lovecraft’s Call of Cthulhu 
  • Nostromo–Ripley’s ship in Alien
  • Invisible Hand–General Grievous’s flagship in Star Wars: Episode III
  • Tempest–Pathfinder Ryder’s ship in Mass Effect Andromeda
  • PRCS Wall Cloud–a ship carrying a virus in Deus Ex
  • Pillar of Autumn–one of the first ships in Halo

Wikipedia has a list of more fictional ships. Frankly, from skimming it, I think writers aren’t being bold enough with names. The U.S. Navy names ships after famous battles–we need more of that in fiction. Also, more named after obscure historical figures, please.

41JZ1SRtsjL

I got the idea for this story not too long ago, and once I had the outline down, I raced to get it all finished as fast as I could. This tale, which I’m calling a “long short story” (hat tip to Mark Paxson for that idea) is the result.

As I think most readers know, I love conspiracy stories with weird and mysterious elements–Deus Ex, The X-Files, The Mothman Prophecies etc. fascinate me. I’ve tried writing something in this vein before, but that novella left some readers (understandably) unsatisfied. I think I was much more successful with this story–it’s way shorter than Majestic World, but I think it packs just as much conspiracy weirdness into a much tighter package. But that’s ultimately your call to make.

Some other notes:

  • It’s approximately 15,734 words. I say “approximately” because I made a few edits after converting it from a Word document, and I don’t know how to see word count in the Kindle file format.
  • There is some bad language and violence, but nothing too horrible. I think it would probably be rated PG-13 if it were a movie, but these days, who knows?
  • This is easily the fastest turnaround time I’ve ever had between thinking up an idea for a story and actually completing it. Whether that is good or bad is, again, up to you to determine.

That’s all the relevant info I can think of. It’s available on Kindle for 99 cents, and free on Kindle Unlimited.

 

51PDEHPzjpLI don’t usually read mystery novels, but I enjoyed Goats’s comic novel Incomplete Works so much that I gave Houses on the Sand a try in spite of the different genre. And it turned out to be just as good—indeed, maybe even a bit better, because it has as much wit as Incomplete Works, but also some gorgeous descriptions of the desert landscapes in which the story is set. Interludes about the winding canyons, or the beauty of the night sky, are interspersed with the fast-paced development of the plot, and it all works extremely well.

The book also has a greater emotional range than I was expecting. The protagonist, Quincy Logan, has come to the small town of Harper’s Knob to bury his grandfather, with whom he was not terribly close. There are some poignant moments when he thinks back on awkward boyhood visits to his grandfather, when he was too young to appreciate the old man’s ranch or surrounding desert. These passages, though brief, injected some real emotion into the tale.

Now, lest I scare off anybody who doesn’t care about landscapes or pathos-filled backstories, I want to be clear: this book is a tightly-written mystery, and it can be enjoyed as that alone. I admired how Goats was able to succinctly introduce these literary elements without killing the pace and tension of his central plot. And all of it was filtered through Quincy’s witty, often sardonic narration. 

I don’t want to spoil the mystery, but I will say that it kept me guessing right up until the identity of the perpetrator was revealed. Maybe experienced mystery readers will solve it faster than I did, but I found it to be a very enjoyable ride.

kreia
Kreia, from Chris Avellone’s “Knights of the Old Republic II”. Possibly my favorite fictional character, and a great example of a well-written female character.

A.C. Flory wrote a brought up a good point about Theresa Gannon, the protagonist of my book, The Directorate:

“I couldn’t relate to the main character… I simply don’t see her as female… to me, Gannon could be a he just as easily as a she.”

I know exactly what she means. Honestly, I’m surprised more readers don’t mention this, because I feel the same way. There was never much of anything distinctively female about Gannon.

“Well, you’re the one who wrote it!” you are no doubt thinking. “Why didn’t you fix that, dummy?”

Good question. As a male, writing a good female character is something I find difficult, for a number of reasons.

Stereotypes

The lazy, quick-fix approach to make a character seem distinctively gendered is to resort to stereotypes. I could have made Gannon interested in things like clothes, or shoes, or something like that. That would be stereotypically feminine.

But I hate stereotypes. It’s not that there isn’t any truth to them; most people are stereotypical in one way or another. That’s why stereotypes exist, after all. But the point of writing fiction is to give people something new and surprising. Stereotypes are, by their nature, not new and surprising but old and familiar. So in general, I think it’s good to avoid them whenever possible when you’re writing stories.

This is another way of saying that it would just feel ham-handed and rather disrespectful to have my space soldier run off to go shoe shopping. Other, more skilled writers probably could pull that off, but I couldn’t.

Writing From A Female Perspective

You don’t have to resort to stereotypes to write plausibly feminine characters, though. You can write plausible, relatable, well-rounded characters who are also distinctly women.

The big problem I see in a lot of female characters written by men is that they tend to be distinctly women first, and characters second. Usually this manifests itself in female characters being preoccupied with sex in one way or another, or else being described largely in sexual terms. I’ve read way too many female characters who seem to exist solely as sexual beings, and it gets tiresome. With Gannon, I consciously strove to avoid this. In doing so, I think I made her too non-sexual, and that makes it hard to relate to her.

The Miranda Lawson Problem

Making a character sexy is a risky proposition. If done right, it can make a character that much more memorable. But more often than not, I feel like the risk outweighs the reward, and you can end ruining a character by trying to sex them up.

Miranda Lawson is one of my favorite characters in the Mass Effect video game series. Part of it is Yvonne Strahovski’s performance (I love Australian accents, OK?), but she’s also a pretty well-written character. She’s been genetically engineered to be the “perfect woman”, and as a result, she feels a lot of pressure to be the best–pressure that sometimes makes her do morally questionable things. All in all, a really good character.

But! There’ s a major “but” here (pun not intended): for some reason, BioWare designed many of the game’s dialogue and cinematic scenes to focus, ridiculously, on her backside. Miranda wears a white catsuit, and the animators missed no opportunity to show her from the back, the most egregious example being a dialogue scene where the view “pauses” there for as long as the player wants until they choose to advance in the conversation.

BioWare defended this by saying it’s part of Miranda’s “character” that she’s genetically-engineered to be beautiful, and supposedly all this was to underscore just how sexualized she was, and how that impacts her personality.

Maybe that was the idea, but it totally didn’t come across that way. It became a running joke by Mass Effect 3 that if Miranda was around, the “camera” had to be positioned behind her. It made her seem less like a character and more like a sex object–which was too bad, because she actually is a good character, and it’s a shame she became the butt of jokes instead.

This is something that’s always bothered me, and what I took away from how Miranda is perceived is that making a character sexy is a very dangerous thing to attempt. It can very easily turn your well-crafted character into a ridiculous figure. I think this is especially true for men writing women.

Mary Sues vs. Competent Men

There’s another common criticism that I’m surprised no one has yet leveled at Gannon, but which I fully expect I’ll hear someday: that she’s a “Mary Sue”. “Mary Sues” are “idealized and seemingly perfect” characters, as Wikipedia puts it. Characters who exhibit preternatural skill in a variety of areas. Such characters seem too good to be true, and as such are hard to relate to.

The term “Mary Sue” comes from a parody of Star Trek fan fiction, so this is an issue for sci-fi writers especially. And the original Mary Sue was even a lieutenant, just like Gannon is! So, I probably am guilty of this.

Here’s my defense: there’s another stock character in fiction, referred to as the “Competent Man“. This character archetype is strongly associated with the work of science fiction author Robert Heinlein, who wrote a passage extolling the virtues of having many skills, concluding with the famous phrase, “Specialization is for insects.His heroes tend to have a wide variety of skills.

And indeed, having many skills is rather key to becoming a hero. Incompetent characters would not be terribly effective at having heroic adventures.

As a few readers noticed, many elements of The Directorate are intended as an homage to exactly the kind of military science fiction that Heinlein pioneered. I think such stories lend themselves to having competent protagonists–after all, usually people who are or have been in military service possess a lot of training in a wide variety of skills.

Have Female Editors

One piece of advice for any men who are writing female characters: make sure you have female editors and/or beta readers. I would never have attempted to publish a novel with a female protagonist if I hadn’t known women who could critique it first. And am I ever glad they did, because their feedback improved Gannon tremendously from the first draft to the one I ultimately published.

That said, there were still times when I would overrule their objections and refuse to modify something. Because, first and foremost, Gannon had to be somebody I understood. If I didn’t do that, I would have no chance of writing her plausibly. So when somebody suggested changing the character in a way that didn’t sit right with me, I would stick with the way I wanted her. I feel it had to be this way, but it’s quite possible this made her less-relatable to everyone else.

“Everywoman”

As I’ve discussed before, my early writing has been rightly criticized for having too little description. I tried to correct this in The Directorate, and not just in describing the setting–which is essential in sci-fi–but also in how I described the appearance of the characters.

The exception is Gannon. I was deliberately vague about how she looked, because I wanted the reader to project their own image of Gannon. For most of the book, she is the proxy for the reader, and they experience the world through her eyes. My idea was that by leaving her description largely to the reader, they could create their own image of a character they found relatable. (This is something I picked up writing horror: what the reader imagines for themselves is usually way better than whatever you as the author create.)

It’s possible I made her too vaguely-defined, however; and this could make her difficult to relate to.

Conclusion

Creating convincing female characters is one of the biggest challenges of writing fiction for me. I try to avoid obvious pitfalls that I’ve seen a lot of male writers fall into–lengthy descriptions of their anatomy, character traits that are nothing more than clichéd stereotypes–but I’m still not entirely satisfied with what I’ve done so far. The good news is that I can tell I’m improving, and the more I write, the more I feel emboldened to experiment with characterizations, which hopefully will lead to better and more relatable characters.