A Message To My Future Self

“I just have one question.”

The old man and a woman I took to be his wife came up to me after I had burned through my signing line at Book Bar, a lovely venue in the Berkeley neighborhood of Denver, Colorado. I was there with fellow New Mexican author Rebecca Roanhorse who was promoting her electric debut Trail of Lightning while I was promoting my own debut Implanted from Angry Robot. We had both read sections from our respective books, answered questions moderated by J.L. Forrest who runs the Denver Science Fiction and Fantasy reading series, and then made ourselves available to sign books and chat with audience members afterwards. Forrest provides a nice recap of the evening here.

Reading-Series_Teffeau_Roanhorse_8x10

It was only my forth public appearance for Implanted, and I was still trying to figure out how to strike that careful balance between being approachable and authorly, all the while keeping imposter syndrome at bay. No mean feat when you’re sitting next to the zeitgeist. My mouth was tired from trying to smile for the last two hours lest my resting bitch face slip through. I still hadn’t found a position on my barstool that both presented my pear-shaped frame to best advantage and didn’t aggravate my lower back. I was regretting my choice of outfit and rethinking my answer to one of the questions put to us earlier in the evening. And oh god was I hungry, having put off dinner since there hadn’t been time to eat beforehand.

But I smiled at the couple and said, “Sure!”

He had his hands clasped behind his back. His wife stood mute beside him, a half-smile pasted to her face. An impressive white beard reached down to his breastbone. He paused and pursed his lips, and suddenly I realized this wouldn’t be like the other people I’d spoken with that evening. The ones who said they were excited to read Implanted after hearing me speak, the woman who was grateful to have found a cyberpunk novel not imbued with the male gaze, or the nervous young man desperate for writing advice. Somehow, this would be different.

This gentleman pointed out that both excerpts Rebecca and I had read that night depicted women hunting men for hurting another woman. After a moment of reflection, I realized it was true. Rebecca read from Chapter 2 of Trail of Lightning where her main character Maggie is chasing down a man-shaped monster who has stolen away a young woman to feast on—a powerful, unsettling scene. My selection, the opening chapter of Implanted, the main character Emery is hunting a young man who’s in the process of stalking a different young woman. When the coast is clear, he attacks in an attempt to steal her neural implant. Emery stops him, but she leaves the scene of the crime before the police arrive, setting her on a journey the rest of the book follows.

“Would your character go to such an effort to protect a man in the same situation?” the old man asked me, an unpleasant intensity to his voice.

Rebecca was engaged with some enthusiastic fans beside me, so she luckily didn’t have to face his quiet disbelief when I said, “Yes, of course.”

I then nattered on about how that wasn’t really the point of the scene though, that my main character was protecting someone from a similar attack she survived before the events of the book, that as the author, I got to pick what elements best served my story, and in this case, upending reader expectations and exploring female rage, was my goal. After all, I named the person Emery is following Breck Warner, echoing the name of that of apex scumbag Brock Turner. Subtle, I am not. Of course it would be a young woman Emery’s trying to protect from a repeat of her own past, a past she hasn’t quite figured out how to escape at the start of the book. I said something glib about sisterhood too, but the details at this point are fuzzy.

But I well remember the way he shook his head, disappointed, and left. His wife followed him, having never said a word. Oh, and in case you were wondering, he didn’t buy either my or Rebecca’s book.

I’ve thought a lot about that interaction since. I know it doesn’t hold a candle to uncomfortable interactions other authors have had with members of the public over the years. But I try to analyze moments like this when they pop up to better prepare me for the next one. I’m a classic staircase wit where I’m nothing better than a deer in headlights in the moment. It’s only after I’ve retired from the hum and buzz of a public interaction that any cleverness returns, far too late for a rescue.

As a publishing professional trying to drum up support for a debut, I’m always fearful that any negative interaction could affect my ability to get another project published—not true of course, but the little voice in my head doesn’t know that. After reviewing that conversation, however, I don’t think there was anything I could have said to salvage that interaction—to make the sale, as it were. He was being provocative at best, trying to set me down at worst, for having the temerity to center the female experience in my story.

So much of writing—writing for publication, that is—is getting enough people to decide, “hey, this is great,” and getting even more people to read it, preferably giving up their cold hard cash for the opportunity to do so. The business side of writing leads to this mindset that we must go after every potential reader and find a way to convince them we’re worth their time and money. That each missed opportunity is why our numbers suck, that if we could only convince this one other person we’d all be bestsellers and shortlisted for all the awards. A bruising cycle that only ends when you either quit writing or pick out a penname to start over.

It’s not worth it. Even for someone like me where my little book could use all the help it can get. But if someone is going to approach my book from such a perspective, there’s something freeing in deciding: my dude, my work is not for you.

These aren’t the droids you’re looking for.

You can find such sentiment online, often in pithy tweets that read like affirmations in our current political climate made by women stronger and/or more experienced than me in navigating the intersection of art and economics in a broken world. Sometimes it feels a little like settling, knowing your work can never have the reach you’ve dreamed of. Or maybe I should feel driven to succeed despite that dude and all the others like him, even if it feels like crawling uphill over shards of glass. I don’t know. Of course, I’m still writing, but my wide-eyed naiveté has taken a critical hit, and I’m not sure I can afford that, not when that naiveté is what allowed me to pursue writing in the first place.

It’s just one guy, right? Why am I even letting myself get caught up in all this? Maybe it’s the people-pleaser in me. Maybe it’s a way for me to give other writers out there a head’s up about the world we’re so desperate to be a part of, a toolkit for deciding how and when to cut your losses.

And maybe, like Emery, I’m trying to protect my future self from another no-win situation, where the best choice is to walk away and keep writing, no matter what.

Invisibility of Progress

Improvements in writing ability are often hard to detect. So much of what is “good” is contextual—dictated by a particular project, the audience you’re writing for, or even market trends.

I’ve talked before about How Do You Know if you are ready for publication. Although it’s related, that’s not exactly what I want to talk about today.
Instead I want to focus on all the invisible things writers do in the hopes of bettering their craft, expanding their professional network, and positioning themselves for success to the best of their ability.
Image courtesy of Penywise of Morgue Files
Objective measures of success in this field are pretty self-explanatory. You’re either published or you’re not (however you choose to define it). When you’re “not” published, chances are you’re doing a bunch of things other than writing in the hopes they will pay off in some small way in the future.
For example, I haven’t sold any short stories since last fall. If you are looking at my output objectively—well, there isn’t any by that definition. Instead, so much of what I’m doing these days is invisible. And I’m still trying to figure out what that means.
These invisible activities include:
Reading slush for Masque Books – Beyond occasional mentions here on the blog, it’s something I do to strengthen my ability to evaluate projects, diagnose writing problems, and gain insights into the editorial process. I won’t be able to learn these things overnight—this requires a commitment of months if not years to see the benefit from this type of activity.
Joining an invitation-only critique group – The meetings are intense and panic-inducing. I’m learning tons, making good connections, but as with any critique group, feedback is only as good as the projects I bring to them. Workshopping novels (and short stories to a lesser extent) can be a long process outside of development time.
Submitting to higher-tier markets – I have three in rotation right now that I truly believe in. And I’ve been aiming high. My sales last year gave me the confidence to target higher-tier markets. Personal rejections? Check. Second-round bumps? Check. Agonizing ‘You just missed the cut’ notices? Oh yeah. And the worst part is, all this means longer response times.
When non-writers ask me about my writing these days, it’s hard to explain how all these invisible activities fill up my time and contribute to my work. But they do mean something. They are valuable. They just go largely unseen because they don’t conform to objective measures of success.
I just have to believe they’ll add up to something that cannot be ignored one day.

What aspect of your writing life is invisible?

var gaJsHost = ((“https:” == document.location.protocol) ? “https://ssl.” : “http://www.”); document.write(unescape(“%3Cscript src='” + gaJsHost + “google-analytics.com/ga.js’ type=’text/javascript’%3E%3C/script%3E”)); try { var pageTracker = _gat._getTracker(“UA-15029142-1”); pageTracker._trackPageview(); } catch(err) {}

Immaturity in Writing

In January, I started reading slush for Masque Books, a digital imprint of Prime Books. And so far it’s been a fascinating peek behind the publishing curtain.

I’ve seen my fair share of crazy fonts and strange formatting, but not nearly as much as I expected to based on the horror stories of the slush pile that get bandied about. What’s surprised me the most is the overall care that’s gone into the submissions. This doesn’t mean they’ve knocked my socks off, but rather that the average submission is much higher in quality than I expected—they’ve been literate, proofread if not perfect, and largely followed the submission guidelines.

That kind of attention to detail is encouraging to see, which is why it’s so heartbreaking to get to the actual story and know within two paragraphs, sometimes sooner, that it’s a no-go. And more often than not, the culprit is immature writing.

What do I mean by that? Well, it’s a catch-all phrase that I use when I see a manuscript that has either sentence-level issues or a lack of sophistication with elements of craft (or both).

Sentence-Level Issues

This can be as simple as a poor grasp of grammar—improper punctuation, run-on sentences, etc. A mistake or two won’t make or break a submission. But they can add up, and when the errors are egregious, it’s that much harder to take a story seriously.

There are also more subtle signs of sentence-level issues. Things like wordiness, filtering, awkward phrasing. I’ve trained myself to write tight, to weed out inefficiencies in my text, to catch mistakes and edit out the awkwardness. When I see project where these kinds of things aren’t addressed, it makes me wonder just how far along the writer is in their journey. Is this their first project and they haven’t quite figured everything out? Or have they just not taken the time to refine their writing to make it the best it can be? I usually go with the former interpretation, and have to hope they won’t give up when they get their rejection, that they’ll keep writing, keep striving until they get their stories out into the world.

Bottom line, every word in your story subconsciously signals your ability as a storyteller to a reader. Sentence-level issues are the one thing you as a writer can control in a highly capricious business, so there’s no excuse not to learn them. And if you haven’t learned them, when I read your submission I assume that you are too immature a writer to competently tell me a story I’m interested in.

Elements of Craft Lack Sophistication

This is even more subjective, but in some ways more detrimental to a submission. Say an author has great descriptive powers, but cannot orchestrate an action scene to save their life. Or the voice of the protagonist is largely spot on, but infodumps and unrealistic dialogue grounds a story before it even gets started. Essentially, there is some aspect (or aspects) of the writer’s craft that screams inexperience, by virtue of it being poorly handled or weaker relative to other aspects of the work.

This isn’t always a fatal flaw—after all, a good editor will work with a writer to improve all aspects of a story. But the problems with craft must be surmountable. For example, a story where every paragraph tells the reader what to think instead of showing them or a clumsy inner monologue that sidelines action in every scene are too insidious to tackle. Other things like a lack of specificity or an overabundance of specificity could be fixable, but the story would have to be worth the effort.

This is where beta readers and critique partners and groups come in, because writers can be blind to their shortcomings.

Bottom line, you cannot afford to ignore the weaker parts of your craft and hope the rest will be strong enough to carry your story. If I see a big imbalance in your abilities as a writer or if the way you handle certain aspects of craft show your inexperience or lack of awareness of what’s acceptable, then I’m going to assume you haven’t matured as a writer and that your story isn’t ready for publication.

Harsh? Yes. Necessary? Also yes. I’ve only recommended two stories since I’ve started slushing, and those were both with big reservations.

So at the end of the day, remember: Writing stories is hard. Rejecting stories is easy.

It’s all too easy to find a reason to reject a story. You’re goal as a writer is to minimize those reasons for “easy” rejections (following guidelines, fine-tuning your prose, making strides with your craft). You want to make it difficult for me to say no. You want me to keep hoping if I turn the page, it will be worth it.

I want it to be worth it. And you can prove that to me by maturing as a writer. It won’t happen overnight. But if you keep writing, keep working, keep striving, you’ll get there. We all will. One day. var gaJsHost = ((“https:” == document.location.protocol) ? “https://ssl.” : “http://www.”); document.write(unescape(“%3Cscript src='” + gaJsHost + “google-analytics.com/ga.js’ type=’text/javascript’%3E%3C/script%3E”)); try { var pageTracker = _gat._getTracker(“UA-15029142-1”); pageTracker._trackPageview(); } catch(err) {}

Assumptions, part deux

Last week, I talked about reader assumptions and how the writer can use them to their advantage in their stories. They’re great for worldbuilding shorthand and reveals and revelations, so long as you don’t thoroughly confuse your reader in the process. And I should also say, it can take time to get a bead on what readers think as they progress through a story. Experience will help guide your intuition, along with really awesome trusted readers.
But today, I want to talk about a different kind of assumption. The assumptions we writers make every time we sit down and, well, write.
Think back on when you first started writing. Did you think it would be easy? Did you think if your story had a beginning, middle, and end, it was bound to be good?
As you continued to write, did you assume that if you never stopped, that would somehow translate into success? What about if you wrote a good story/book and assumed it would sell even if there wasn’t a ready market for it? After all, we are told to write the book of our hearts, regardless of what the market demands… Did you ever assume you could get away with breaking the rules because you are you?
Alas, in writing there is no easy button.
Now, some of these assumptions may smack of naiveté now, but I guarantee you those assumptions were helping you to do one of two things: 1) Stay motivated – those dreams of making it big fuel us all at one time or another, and 2) Finish the story – after all, if you don’t make it to the end, it doesn’t matter how well you can write.
In the post Different Stages, Different Questions awhile back, I talked about how writers operate at different stages of writing experience, and the questions that guide their efforts. I also think the assumptions we carry with us at different points in our lives also have a formative effect on our work.
After all, if you don’t know any better, those assumptions are all you have to navigate the writing process. And they can be useful, except when you reach a point where they stop being helpful and start being a hindrance.
I want to point you to a series of posts on The Cockeyed Caravan blog by screenwriter Matt Bird (and if you haven’t visited this blog, you are missing out). In the series, he talks about the more detrimental assumptions we writers make about process, craft, and careers, and discusses the actual reality we face. I know it’s a lot of links to click through, but I think you’ll agree that he’s spot on.
Happy writing! (And retooling your own assumptions about writing!)

var gaJsHost = ((“https:” == document.location.protocol) ? “https://ssl.” : “http://www.”); document.write(unescape(“%3Cscript src='” + gaJsHost + “google-analytics.com/ga.js’ type=’text/javascript’%3E%3C/script%3E”)); try { var pageTracker = _gat._getTracker(“UA-15029142-1”); pageTracker._trackPageview(); } catch(err) {}

You Know What Happens When You Assume Things…

Assumptions sometimes get a bad rap. A lot of times they make an ass out of you and me, but that’s often only in hindsight. In fact, I’d posit assumptions are essential to living, and, along with that, writing.
After all, an assumption is made based on the information you have on hand or experiences you’ve acquired and can extrapolate from. For example, deciding what to wear based on a glance out the window—I assume I won’t need a rain jacket because the sun is out. Or I assume I can make cream of cauliflower soup because I’ve made cream of broccoli soup in the past.
The assumptions we make are based on our accrued knowledge. So we accrue knowledge to survive, but that doesn’t mean that knowledge is always enough to navigate our world. Mistakes do happen, and that’s actually a good thing for writers.
As people read our stories and novels, they are interpreting our words and trying to make sense of the world we’ve presented them with. To do this, they must make assumptions. For example, if I don’t point out that the sky is green in my story and people get around by walking on their hands, my readers will assume the sky is blue and people walk like normal.
So if on page 30 I suddenly point out that the sky in my world is actually green, that forces the reader to stop and reevaluate what I’ve told them. This can be a bad thing when it throws the reader out of the story. But for some story elements, particularly reveals, this can be a neat trick and make your reader even more invested in figuring out your story as they try to fit the pieces together into a cohesive whole.
“But what does it all mean?”
I like to do this particularly at the opening of a story, where I’m trying to hook a reader’s interest by slowly dealing out world details. Readers will make assumptions based on what is mentioned and/or described, along with what isn’t. And depending on how those details complement one another or how they disrupt one another, my reader will make assumptions about the larger story world that can potentially make the worldbuilding easier on me.
As writers, we should all be relying on a reader’s assumption about genre conventions when crafting our stories except when those conventions interfere with the story we’re writing. In other words, we should be using these assumptions as world building shorthand except when they get in the way. Big deviations, ones that will just cause more confusion than not, however, should probably be addressed as soon as possible so you don’t disorient the reader.
But for me, I like to use reader assumptions and turn them on their head sometimes. As James Killick discusses in Reveals and Revelations,
If you break it down, there are only really two types of revelation that can be made within a story – revelations about the story and revelations about character. The differences should be fairly self-explanatory – a revelation about the story is when something is revealed outside of character – who the murderer is, who is sleeping with the heroine’s husband. Character revelation is when something is revealed about character – a hidden trait, an unrealised dream, a hitherto misinterpreted desire.
And both of these (when successful) work because the author has leveraged the reader’s assumptions about the story. The trick is setting them up (which is another post entirely :P).
As readers, we make all kinds of assumptions based on what’s presented to us by the author, as well as unconsciously, based on our own personal and cultural biases. Remember the social media explosion when peoplewere surprised that Rue was black in the movie version of The Hunger Games? That was attributed to a tendency of assumed whiteness where readers assume literary characters are white unless told otherwise. In fact, as The Hunger Games demonstrated, those details stating otherwise can be easily overlooked in a culture of assumed whiteness (and it must be said, poor literacy skills).
So what does that mean for the writer? Well, I think in some ways it’s our duty to engage with these assumptions and draw attention to them by disrupting them in unique ways without sacrificing story. Particularly the more insidious ones related to gender and race and power (and Juliette Wade has a great post on this subject).
But ultimately playing with readers’ assumptions is just another tool in your toolbox. So use it wisely.

var gaJsHost = ((“https:” == document.location.protocol) ? “https://ssl.” : “http://www.”); document.write(unescape(“%3Cscript src='” + gaJsHost + “google-analytics.com/ga.js’ type=’text/javascript’%3E%3C/script%3E”)); try { var pageTracker = _gat._getTracker(“UA-15029142-1”); pageTracker._trackPageview(); } catch(err) {}