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.
I don’t usually read mystery novels, but I enjoyed Goats’s comic novel Incomplete Worksso 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.
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.
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.
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.
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.
Miira tells the story of Miira Tahn, a dying woman who enters a virtual world where she can live in a perfectly realistic simulation of health and youth. However, the medical team tasked with performing the procedures necessary to prepare her for this are not all to be trusted, nor is the corporation overseeing it innocent of unsavory business practices.
The first half of the book tells of Miira’s preparation to enter Innerscape, her psychological distress at leaving the physical world behind, and fear at the procedures necessary to prepare her for it.
I should warn readers: I actually found some the descriptions of the surgeries unsettling to read. They were actually more disturbing to me than many books I’ve read that depict actual violence—I’m not sure why this is, as obviously there is no harm or peril intended in these scenes, but that was my reaction. That’s not a criticism, though; indeed, it shows how well-written these scenes are.
The second half of the book deals with Miira adjusting to the new world of Innerscape, all while dealing with the machinations of the various staff members assigned to help her adjust. At times, in the whirlwind of all the tests they need to run to ensure that all Miira’s senses are functioning properly, it seemed like a sex comedy set in a cyberpunk world. Again, that’s not a bad thing. I’m all for genre-mixing.
I admit, I thought the last quarter or so of Miira felt a bit rushed. Throughout the book, there are also several sub-plots and hints of a dystopian real world outside the virtual Innerscape. These are never fully explored, and the ending felt rather abrupt. But then, this is only book 1 of a trilogy—it’s clear that there are many questions to be answered in subsequent books.
And, make no mistake, I love the premise here—virtual worlds are a neat idea, especially to a gamer such as myself. It was fun to read this after just recently re-reading Ben Trube’s Surreality earlier in the summer. Both books, while very different in style and tone, examine how virtual reality grants a chance at an “idealized” new life, and how it brings out different facets of different people.
Miira is a fast-paced read with a compelling premise. I’m curious to see how the plot and characters introduced in it are developed in subsequent books.
One year ago today, I began work on a sci-fi novel. The day before, I had gone to interview for a job I really wanted. I resolved that I’d either get the job or write a novel, and I figured I’d have about a week to start on the novel before I got a call back.
At the start, I called the file for my novel “SFN” for “Science-Fiction Novel”, because I had no clue what the title ought to be. I’d been wanting to write a science fiction adventure with a space elevator in it since I was 12 years old, and had tried several times before, but never got anywhere with it. And at first, it didn’t seem like this time would work out any better. I remember sitting at my computer, wondering how I was ever going to do this, when inspiration struck.
As a junior in college, I’d had an idea for a completely unrelated story about a soldier named Theresa Gannon. It was set in the present day, and followed Gannon as she tried to cope with some sort of traumatic battle in her past. But again, I never got much beyond an outline of the story and a sketch of the main character. I hadn’t thought about it in years.
And as I sat there, staring at the blank page, I decided to put Gannon in the space elevator story. (Previous drafts had been written from various perspectives, including that of the character who would eventually become Chairman Wilson, as well as various denizens of the space station connected to the elevator.)
Making Gannon the protagonist turned out to be the spark I needed: after that, the story came together relatively quickly. I finished the first draft by early October, and from there started revising based on beta readers’ and editors’ comments. There were a few moments of frustration, but for the most part, it was exhilarating. During those few times when I felt the creeping shadow of discouragement, I reminded myself that Chris Avellone had written Planescape: Torment when he was my age. If he could manage that, surely I could do this.
The end result was The Directorate. That it took pulling together multiple threads of story ideas from my past makes me all the prouder of it. And the fact that I’ve met so many wonderful authors along the way has just made it even sweeter. Thanks to all of you wonderful folks who read the book, follow my work, and provide such terrific feedback and support. I’ve said it before, and I’ll say it again: you guys are the best!
Oh… and that job I mentioned interviewing for? I didn’t get it. But I’m not sorry–in fact, I’m glad, because if I had, I would not have finished the book. And you know what? My 12-year-old self would not be remotely impressed if he knew that I got some slightly higher-paying office job. But if I could go back and tell him that yes, we finally did write that story about the space elevator, he’d be absolutely thrilled.
To hear me read an excerpt from The Directorate, click here.
To read reviews of The Directorate on GoodReads, click here.
Before I begin, let me give a special shout-out to my blogger friend and loyal reader, Pat Prescott: yes, Pat; it’s finally happened! I don’t know how many years it’s been since you first told me about this series, but I finally have gotten around to reading it. Many thanks to Pat for the suggestion, and for all his support over the years.
Also, for those of you who don’t want to wade all the way through my long-winded review, I made a short video review for your convenience. (And also just for my own amusement.)
Casca begins with military doctors in war-torn Vietnam finding an American soldier named Casey suffering what should be a mortal wound that miraculously begins to heal. As the doctor examines him, he feels himself drawn into a vivid recollection of the man’s past: a flashback to his time as a Roman soldier, Casca Rufio Longinus, a legionnaire assigned to the province of Judea.
During his time in Judea, Casca torments a prisoner about to be crucified–Jesus of Nazareth, who curses him to an eternity as a soldier of fortune, until the Last Judgment. (Note that in the above video, I mistakenly said Casca stabs him on the way to the crucifixion. I meant to say he guards him on the way, and then stabs him.)
Casca dismisses the curse as the raving of a mad prisoner, but as he fights and receives wounds and does not die, he begins to realize that it truly is his doom to live forever, always moving from one battle to the next.
He is sent into slavery for a time, where he is mentored for by a kindly Chinese man who teaches him martial arts as well as philosophy. Eventually, he makes his way into the gladiatorial arena and battles his way to freedom. Ultimately he rejoins the Legion, centuries after he originally knew it, when Rome has seen many emperors rise and fall, and the once-mighty empire verges on collapse.
The book flashes forward again to the hospital in Vietnam–Casey having gone, and the doctors shaken by the experience. In the final chapter, the action moves to Egypt, where young Israeli soldiers fight alongside a grizzled mercenary–Casey again, who recalls fighting in the same desert many centuries before.
The writing is straightforward with no frills, so the book is a quick read. The description is limited, with most heavily-described parts being those relating to battles and Roman tactics.
There is a lot of violence, naturally, and quite a bit of sex as well. Actually one of the things that bothered me about the book was the sexism–women are described exclusively in sexual terms, and rape is commonplace. The worst part is, this probably is an accurate depiction of attitudes during the time period. There was also one section during Casca’s time as a gladiator about his rivalry with a cruel Numidian (African) gladiator that was dripping with racism (and sexism, in terms of how the man is depicted preying upon women) that rivaled Lovecraft in terms of appalling the modern reader. I could have done without that.
Maybe I shouldn’t be surprised by this from a book written in the 1970s by a man who grew up in pre-Civil Rights America. All in all, Sadler had a strange life–maybe one that would have been worthy of a novel in its own right. His military career was cut short when, to quote Wikipedia, “he was severely wounded in the knee by a feces-covered punji stick“. Before writing Casca, he wrote and performed the patriotic song “The Ballad of the Green Berets”. Later on, he shot and killed a romantic rival, for which he served 28 days in jail. Years later, he himself would be shot–whether accidentally by his own hand or by a would-be killer is unclear.
Honestly, people who don’t like to learn the biographical details of authors are missing out on a lot.
What I liked most about the book was the concept: the idea of a man condemned to live forever is an ancient one. Or, as Harlan Ellison wrote for an episode of The Outer Limits:
“Through all the legends of ancient peoples — Assyrian, Babylonian, Sumerian, Semitic — runs the saga of the Eternal Man, the one who never dies, called by various names in various times, but historically known as Gilgamesh, the man who has never tasted death … the hero who strides through the centuries …”
This idea of an immortal condemned to live through endless cycles of fruitless quests is a great one. It’s the premise for the legendary video game Planescape: Torment, as well as Stephen King’s Dark Tower series. (I’ve also heard some claim that King’s protagonist Roland was influenced by the soldier-of-fortune character “Roland the Headless Thompson Gunner“, from the song by Warren Zevon, which features the line “the eternal Thompson gunner”.) It’s a great premise for exploring themes like the futility of war, “man’s inhumanity to man”, etc.
Because the concept is so fruitful, the Casca series currently spans 47 books and counting, following Casca’s adventures across pretty much every war in recorded history. It surprises me the series was never made into a movie. I could see it very easily being adapted into one of those over-the-top, hacking and slashing and/or guns-blazing action films like they made in the 1980s. Or maybe that’s the problem: the teenage boys who would probably have been the perfect audience for these books in past eras are now spending their leisure time watching action movies and playing online first-person shooting games, and don’t even know about them.
The other day I went to look up the quote about angel food cake from the end of To Kill a Mockingbird. In the search results, I saw a bunch of study-aid/cliffs-notes style sites addressing the question, “What does the angel food cake symbolize?”
The passage in question is this, when the sheriff is explaining to Atticus why he won’t tell the town what Boo Radley did:
I never heard tell that it’s against the law for a citizen to do his utmost to prevent a crime from being committed, which is exactly what he did, but maybe you’ll say it’s my duty to tell the town all about it and not hush it up. Know what’d happen then? All the ladies in Maycomb includin’ my wife’d be knocking on his door bringing angel food cakes.
This isn’t technically wrong, but it’s way too fancy for my taste. Saying that’s “symbolism” is really over-thinking matters. It’s no more a symbol than any other gift is.
I always hated this “what does [x] symbolize?” question, and I think that nine times out of ten, it’s just a subtle way of asking “Did you actually read the book?”
Well, in English Lit class, that’s something the teachers have to establish, so it’s hard to blame them for asking it. But I wish they could find a different way to do it, because symbolism is an actual thing in literature–but it’s not near as commonplace as English classes would lead you to believe.
True symbolism is subtle, and you have to be alert to notice it. The angel food cake in Mockingbird doesn’t “symbolize” compassion, it’s just an instance of it. Any five-year-old kid could tell you that bringing somebody a cake means you want to show your appreciation for them.
Actually, this is not a bad test for deciding whether something is literary symbolism. If a kid could immediately tell you what something “symbolizes” out of context, then it’s not really a symbol.
In Richard Armour’s hilarious satire of literary analysis, The Classics Reclassified, there’s a note on symbolism in Moby Dick (I’m paraphrasing from memory): “The book is full of symbols and allegories. The whale stands for something. The sea stands for something. The reader has to stand for quite a bit, too.” I think this nicely sums up the way most readers feel about books that rely too heavily on symbolism.
Based on this, you’re probably thinking that I hate symbolism. I don’t. I’ve written stories that used symbolism. I just object to the lazy style of literary analysis where everything is a symbol, and a symbol of the most obvious things to boot.
I think we need a better term than “symbolism”. My suggestion is “reinforcement”.
In my opinion, the best use of symbolism in a story is to reinforce the core thematic elements of that story. For example: say you have a story about a guy who goes insane. You might reinforce this by having him look in a cracked mirror that distorts his reflection. It represents his figurative “cracking up” by having him (well, his reflection) literally “crack up”.
That’s just one example. You can use all sorts of things to reinforce a theme—if you write romance, have a rose bush that blooms when the lovers are together and dies when they’re apart. (Yes, I know that’s awfully hackneyed. Now you see why I don’t write romance.)
The point is, all this sort of stuff gets called “symbolism” by authors, literary critics, and academics. But that name is misleading, because it starts artists off thinking about the wrong problem—i.e. “What symbols can I create?”, instead of “How can I reinforce my theme?”
This can lead to pretentious, incoherent art where lots of stuff symbolizes other stuff, but none of it makes much sense or seems meaningful. So instead of asking “What does this symbolize”, lit critics and academics ought to be asking “How does this reinforce the theme?”