One Week To Go!

Did you know there’s only one week to go before Implanted is loosed upon the world?

Implanted-glitch (faster)

 

Things are rolling along–make that steamrolling–and I wanted to briefly check in before I head to Austin for ArmadilloCon later this week.

♦♦♦

I had a great time at RWA Nationals in Denver. It was intense, inspiring, and I left with lots of new contacts and things to think about. This is me (furthest on the right) and my New Mexico chaptermates having a blast:

♦♦♦

When I got back to town, the amazing Fran Wilde put together a worldbuilding roundtable with a group of awe-inspiring SF authors, including me, Mike Chen, Malka Older, Peng Shepard, and Tade Thompson. Check it out at Tor.com.

Tor.com_WorldbuilingRoundtable

♦♦♦

I also got interviewed by the great team at Unreliable Narrators, where we talk about Implanted, the path to publication, and some of my influences. I had a lot of fun with their thoughtful questions.

UnreliableNarratorsLogo

♦♦♦

Finally, early reviews have been trickling in, which is gratifying to see. Even more so since people seem to like Implanted! Special thanks to all the reviewers who took a chance on a debut author.

Rainy Book Reviews | The Everlasting Library | Brian’s Book Blog | Elle Loughran | Splattergeist | The Literary License Podcast

Hopefully one of those convinced you to preorder the book, if you haven’t already!

Book Deal with Angry Robot!

I’m thrilled to share the news that Angry Robot will be publishing my debut novel Implanted, out this August. I’m certain the next few months will be an amazing whirlwind in the lead up to the release.

AngryRobotLogo

You can read more about announcement at the Angry Robot homepage. You can also check out the cover and read a little more about my story world over at SFF World. And if you are really interested, Christopher Cornell on the Unreliable Narrators podcast teased a few questions out of me a few weeks ago while I was on there promoting the release of the Abandoned Places anthology from Shohola press.

You can even add the book to your To-Read list on Goodreads if that’s your thing.

All that said, it is an exciting time and I’m looking forward to the next stage on this journey. Accordingly, there will be some changes around here, so I hope you’ll stick around!

The Story Behind The Story: Forge and Fledge

Yesterday, the Runaway issue of Crossed Genres Magazine went live, which includes stories by Rachael Acks, Angela Rega, and yours truly!

cg-logo

If you haven’t yet, you should go read “Forge and Fledge,” a young adult science fiction story about an orphan of Titan desperate to escape life on a hydrocarbon mining rig. No worries, I’ll wait.

I’m so thankful to publishers Kay T. Holt and Bart Leib, as well as editor Kelly Jennings, for selecting my story for inclusion in the issue. Recently, Crossed Genres became a SFWA-qualifying market, and they are running a Kickstarter to keep publishing diverse stories and paying pro rates. If you love speculative fiction that bucks the norm, consider subscribing to the magazine and/or donating to the campaign.

Story spoilers follow:

A while back, I started researching Titan, a moon of Saturn, thinking it would be a great story setting. Originally, I wanted to use it for a novel, but the unique characteristics of Titan, that it’s mostly ice and covered in hydrocarbons, made it difficult to write the story I had already plotted out in my head. I eventually turned to Mars and wrote my novel, but in the back of my mind I kept thinking about Titan.

It’s considered a candidate for human colonization, but there are a lot of technical hurdles to overcome, not least of which is just getting there. Subzero temperatures, a thick atmosphere that exerts a pressure one and a half times that of Earth, and a gravity that’s slightly less that of the Moon’s. But it has plenty of water, nitrogen, and methane, so, as long as you get the engineering right, people could theoretically live there. (This is essentially the TL;DR version of the Wikipedia article: Colonization of Titan.)

And what would be the attraction to colonizing Titan? Why the hydrocarbons, of course (or perhaps the water depending on which post-apocalyptic future scenario you subscribe to). But even if it were possible, I couldn’t see people jumping up and down to live on a frozen iceball. Hence the corporate mining facility and the penal labor force in my story. And my main character Zhen wants nothing more than to get away by any means possible.

Remember the low grav and high atmospheric pressure? Well, it’s been theorized that humans could strap on wings and fly on Titan so long as they didn’t freeze to death first. In fact, this concept was recently featured on io9—propulsion is still an issue, but Zhen’s dive off the rig’s platform, where it hovers over Titan’s surface, would hopefully provide enough momentum for flight. At least that’s my story, and I’m sticking to it.

patentedFlyingApparatus

Image courtesy of stans_pat_pix of Flickr

 As to submission stats, I only sent this to three markets and lucked out on the third one. I’m so happy it found a home. I hope you enjoy it as well!

 

 

The Art of Layering in Our Fragmentary World

Infodumps are evil. Readers hit them, and their eyes glaze over. We’re lucky if they skip over them and keep going. Unlucky if they decide then and there to set the story or book aside.
We writers know infodumps are bad even if we can’t always avoid them in actual practice. Most advice tells us to break up the details and pepper them in the best we can.
Which is a helpful, but I’d argue an incompletesuggestion.
I’ve talked before about my writing process, and how my stories often begin as a skeletal first draft of dialogue and action, then I have to layer in everything else. In this case, layer refers to the iterative passes where I add in setting detail, character blocking, internal thoughts, and other expository “flesh” to the story.
Picture Source

Today I want to focus on the layering in of specific types of information: Description and Backstory.
But first, a digression (because it’s my blog and I can do what I want). Readers have a choice in how they spend their time. Books are in competition with video games, TV and movies, the black hole that is the internet, on top of demands of work and family. This isn’t new. With advances in technology and changes in how people spend their free time, people’s attention spans become increasingly fragmentary.
I have to wonder if this is related to readers’ intolerance with infodumps. They don’t have the patience to wade through them when in the back of their mind, they’re wondering why they’re wasting their time on a boring book when they could be doing X, Y, or Z…
In other words, you need to make your book worth the opportunity cost of other activities.
And that means conveying information in an entertaining way (however defined) all the time. So. Back to layering in details. We’re told to break them up and add them in as necessary, but it should go further than that. Here’s what I strive to do with my words, but your mileage may vary.
Description
Lush description can be wonderful, but so often, such passages have no movement, no underlying action, no impetus forward. It’s a hard balance to strike: having enough detail the reader can visualize your world, but not so much it slows down pacing.
Don’t explain/describe everything at once—Readers can tolerate a certain amount of uncertainty and that can even be a driving motivation to keep them reading. Just be careful to not have too much uncertainty because then curiosity will morph into frustration (and frustration means no more reading).
Readers are on a need-to-know basis—Some grounding details are necessary, but don’t overwhelm or bore them with things that aren’t quite important yet. Granted, there are things you’ll want to sow in to foreshadow or set up subsequent scenes, but you want to strive for natural inclusion, else those details will draw attention to themselves.
Rely on archetypes—Think of these as writerly shorthand. Use them when you want to get across a basic concept: Tree, house, cow, [insert your own noun here]. Most readers will have a mental image of these concepts in their brain. The key is to prime the reader by relying on that mental image, then gradually introducing details that confirm or disrupt that image as you move from a universal concept to a more specific one.
Think telling details—These are details that are evocative and appropriate and important for describing something accurately or setting the tone or establishing voice. But don’t waste words (and your reader’s time) on the obvious. Let the archetype do the heavy lifting, and include telling details as necessary. And sometimes, a tree is just a tree.
Backstory
Also something you’re better off peppering in as needed, this one is particularly insidious for writers because they spend so much time trying to figure out who their characters are and how they came to be that way, that it’s hard for them to decide what is and is not relevant for the reader.
So how do you determine what’s relevant? When the information:
Is key to understanding a character’s reaction/state-of-mind/worldview—This helps the reader identify where a character is coming from and may help to explain why they react in the way they do in the story. A character who has a history of abuse will probably react differently than a character who doesn’t, for example. Think of this type of information as an extension of character development. But extension is an important distinction—character development should be grounded in the story itself, the backstory just provides occasional context. 
Disrupts a character or reader’s assumptions for dramatic effect—Remember telling details? Backstory can function in the same manner, either confirming or clarifying character, or disrupting expectations for a dramatic twist. Look at the way JK Rowling handles Snape’s character in the Harry Potter series for how the judicious application of backstory can be used to increase tension, conflict, drama, and, interestingly, catharsis.
Obviously the worst thing a writer can do is bring a story to a screeching halt in order to convey whatever details are needed. But almost always the reader doesn’t need as much as the author thinks they do to understand what is going on. (This is where trusted readers are worth their weight in gold.)
Character archetypes can also come in handy here (hooker with the heart of gold, sad sack detective, fresh faced apprentice on hero’s journey, etc.) to help the reader tap into unconscious understanding of character—just don’t forget to round them out so they become more than just a caricature as you move from universal archetypes to specific characters only you can create.

***
So remember, less is almost always more, unless it confuses the reader. Strive for clarity above all, and to a lesser extent, Donald Maas’s microtension—those unexpected but revealing details that describe your story world or provide a provocative hint at your character’s past. Such details create curiosity in your reader and serve as minihooks to help your story compete in a media-rich and fragmentary world.

Happy 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) {}