An Accident of Stars is out today in the US! The UK release should follow on August 4th, and the Australian release sometime in the next two weeks, but as of today, it’s officially out in the wild. I really hope you enjoy it!
I’ve been comparatively quiet on the SFFnal blogging front of late, partly because I’ve been busy with every other aspect of my life, but mostly because I’ve been feeling burned out on the same endless cycle of arguments. Back in high school, I once spent a frantic evening completing a history assignment I’d technically had months to complete: we were meant to cut out daily articles in the newspaper pertaining to the Israel-Palestine conflict and explain how each current event was informed by the history we’d learned. The relevant clippings in hand, I found myself writing paragraph after paragraph explaining the exact same thing in slightly different words. It was an exercise in creative repetition, but it did win me that year’s history prize, so it wasn’t a total loss.
Without wanting to compare the current discourse in SFF to the Israel-Palestine conflict, I’ve started to feel much the same way about engaging with it as I did when writing that history assignment. By this point, surely, all the salient points have already been made by all the key parties, multiple times and in myriad different ways. We know why the debate started, and we know why it’s ongoing. The problem is that, no matter how eloquently we make these same points over again, new offences stemming from the original conflict continue to occur, and merely pointing out why that’s happening isn’t getting us any closer to solving it. Which isn’t to say that making those breakdowns isn’t still important or useful: it is. I just don’t always have the strength for it right now.
Enter the announcement of programming for World Fantasy Con 2016.
There’s a good breakdown of what’s happened here, courtesy of Sarah Pinsker, while the program itself can be found here, but in a nutshell, the issue is this: there are more references to H.P. Lovecraft in the program than to women or POC; there’s a use of offensive language; and there’s little to no acknowledgement of any recent writing in the genre.
This last point is the one I want to address.
By Sarah Pinsker’s count, of the thirty-two separate works cited in the program, only four were written in the last twenty years. Four. Pinsker, who saw an early draft of the proposed programming, raised this particular issue prior to publication with the head of programming, Darrell Schweitzer, in relation to a specific example. Here is Pinsker’s account of that exchange:
The Animal Fantasy panel with the “recent” example of Watership Down? I pointed out that was written before I was born. Kij Johnson and Ursula Vernon have written amazing award-winning animal fantasy in the last few years. He said “Watership Down is recent compared to Aesop and Chaucer.” AESOP AND CHAUCER. The modern field doesn’t stand a chance.
And here, according to the program, is current, full description of the Animal Fantasy panel:
19. Animal Fantasy. The form has been around since ancient times, and in recent years Watership Down, Walter Wagnerin’s The Book of the Dun Cow, Kij Johnson’s The Fox Woman et al. and several other such books did very well. Is this sort of fantasy still being written? What is its appeal?
To break this down, Watership Down was first published in 1972 – which is to say, 44 years ago. Wagnerin’s The Book of the Dun Cow came out in 1978, which is 38 years ago. The Fox Woman, by contrast, came out in 1999, a mere 17 years ago, but whether viewed individually or as a collective, referring to all these works as the product of “recent years” is blindingly inaccurate. It’s also, quite tellingly, an elision highlighted by the very next question: if the works you’re describing as successful are truly “recent”, asking if they’re “still being written” ought to be redundant.
To truly appreciate the ridiculousness of this, imagine if a major gaming con, like PAX, announced the following panel description in the year 2016:
19. First Person Shooters. This type of game has been around since gaming began, and in recent years Doom, id Software’s Wolfenstein 3D, Rare’s GoldenEye 007 et al. and several other such games did very well. Are these sorts of games still being made? What is their appeal?
The only way someone could write such a panel description in good faith is if they know so little about the topic they’re proposing as to be unaware of the genre’s development, which in turn suggests they’re ill-equipped to investigate its output. Can you imagine a bunch of panellists trying to talk intelligently about what’s happening with FPS now – the types of title being released, the reasons people play them, the developments in the industry – while admitting themselves to be largely ignorant and/or dismissive of anything that happened after Quake? Can you imagine a panel about modern FPS whose members looked confused and frustrated when the audience asked about Overwatch, or who didn’t think Counter-Strike had that big an impact on the genre? That’s how out of touch the Animal Fantasy panel – and, indeed, the bulk of WFC’s programming – looks to me.
Of course, I don’t yet know who the panellists are, which is clearly going to inform how the Animal Fantasy panel (among others) is handled: whether the conversation sticks to the era suggested in the outline, or if newer works and developments are actually mentioned. But on the basis of what I saw at WFC in Brighton in 2013, which had a similarly retro bias in the programming, this is a con that’s more than capable of fielding myriad panellists whose genre knowledge doesn’t extend much past the mid-eighties. Indeed, it’s a con whose programming seems increasingly tailored to just that set while simultaneously claiming to be a modern, relevant industry con.
To borrow the gaming example again, the objection isn’t to the presence of panels discussing classic or older games, which can be a lot of fun and very informative for younger congoers wanting a better sense of their history: it’s behaving as if it’s not history at all – as if the genre still only really consists of Pacman, Return to Zork and the original Tomb Raider – while waving a vaguely disparaging hand at everything that’s happened since. Even if you don’t like the newer developments, you need to be able to acknowledge that they’ve happened, and to have some understanding of how they worked and what they did, in order to compare them to your preferences. But acting as though they’re invisible, as though they never really happened at all? That’s not only insulting to the audience, it’s just plain wrong.
And lest anyone take umbrage with the comparison of animal fantasy to FPS, the latter accounting for far more works in its field that the former: I chose that example precisely because FPS is well-known enough for the dissonance to be jarring. But animal fantasy, while a smaller subgenre, has nonetheless developed a lot since the 70s. To take the blindingly obvious example that somehow isn’t mentioned in the programming, I grew up reading Brian Jacques’s Redwall series, which began in 1986 – the year I was born – and only ended with his death, the final book released in 2011. The Duncton Wood series, published between 1980 and 1993, were another big influence, as was the TV show The Animals of Farthing Wood, aired between 1992 and 1995, which was an adaptation of the books of the same name, originally written in the late seventies. There’s also Elyne Mitchell’s Silver Brumby series – a staple of Australian literature – whose publication runs from 1958 to 1999, with both a live action film and an animated TV show produced in 1993 and 1994, respectively. None of which is exactly recent (while still managing to be more recent than the panel description), but which contextualises the crucial shift in the genre.
As Pinsker pointed out, Kij Johnson has written multiple works that fall into this category, all more recent than the 1999 example given in the programming, as has Ursula Vernon, notably her award-winning comic, Digger. There’s also Daniel Polansky’s The Builders, released last year with Tor. But in “recent years”, the majority of animal fantasy stories aren’t novels – they’re animated films and shows. Disney’s Zootopia, released in 2016, was an unparalleled critical success, but hardly arrived in a vacuum: all those cartoon adaptations mentioned above – Redwall had one too, along with The Animals of Farthing Wood and The Silver Bumby, to say nothing of the classic Watership Down film – helped to pave the way for it, as did countless others. I could sit here all day listing animal-centric animated films from the last thirty years, both literary adaptations and originals (The Secret of Nimh, Happy Feet, Kung-Fu Panda, Cats Don’t Dance, An American Tail, A Bug’s Life, Ice Age), and while I won’t, the fact that I can is exactly the point: unless you want to outlaw 90% of the discussion, you can’t have a sensible panel about animal fantasy as a subgenre without mentioning animation. You literally can’t, because that’s where the bulk of that particular subgenre exists, and that’s where it’s been thriving for twenty years.
Talking about animal fantasy purely in terms of novels makes as much sense as, well, applying the same restriction to a discussion of superheroes: yes, those books exist, and yes, they’re worth mentioning, but you’re kind of missing the main event. But I can already pretty much guarantee that, barring some major behind the scenes changes, you’re not going to get a WFC panel which addresses that fact. Many of you can probably guess why. For those who can’t, however, let’s run with this theme a little longer.
Elsewhere in her Twitter thread on the WFC programming, Sarah Pinsker mentions that seminal author Shirley Jackson, whose centenary this is, rates only a single programming mention compared to H. P. Lovecraft’s ten. On its own, that might not bother you, but compare it to the programming in 2013, which marked what would have been Arthur Machen’s 150’s birthday. An entire programming stream was made in Machen’s honour – Machen @ 150 – celebrating his works, his life and his influences on the genre, which amounted to eight separate panels explicitly invoking him in their premise. Similarly, in 2014, Robert Aickman’s centennial earned him seven different events commemorating his work. But Shirley Jackson’s centennial merits only a single event and a single mention – even though the program itself describes her as having written “much of the greatest and most distinctive horror of the 20th century”.
It’s not a coincidence that Shirley Jackson’s centenary merits only a single panel compared to what was organised for Aicken and Machen, just as it’s not a coincidence that the animal fantasy panel mysteriously makes no reference to the medium in which the bulk of those stories are produced. It’s not just that the programming is manifestly disinterested in the genre’s progress in the last twenty years – it’s that all those earlier, apparently more “definitive” works are only a curated selection of what’s considered classic and acceptable, which definition skews heavily towards male and “serious” and away from anything female, youthful or “frivolous”, like animation or YA.
If the position was, really and truly, that recent works are garbage, and that the only things worth discussing in SFF happened prior to 1996 (or 1986, for preference) then Shirley Jackson would merit at least as many programming items as Aicken or Machen – but she doesn’t, because she’s a woman. If the position was, really and truly, that there hasn’t really been any notable animal fantasy since 1999, then Brian Jacques, Elyne Mitchell and the wealth of early cartoon adaptations should at least rate an acknowledgement in the panel description – but they don’t, because kids’ animation isn’t respectable fantasy, Jacques wrote middle grade books, and Mitchell, assuming the programming team have even heard of her, is a woman. It’s the same logic which said that including a favourite in-joke of Schweitzer’s was more important than not using a racist slur in the programming titles (“Spicy Oriental Zeppelin”, though this, at least, seems to have been changed): they simply didn’t see the offence as a problem.
It’s not that I think Darrell Schweitzer and friends sat down at a table and asked, “Okay, how best can we exclude and minimise the contributions of women, people of colour, queer writers and anyone under fifty in our programming?”, though they could hardly have done a better job of achieving that outcome if they had. It’s that bias is an insidious, often subconscious thing, and where you’ve learned to only view particular things as worthy or important, regardless of the actual worth or importance of what’s on offer, you need to make an active effort to look at the whole picture. If your argument is that genre is an unbiased meritocracy – if that’s what you truly aspire for conventions and awards ceremonies alike to look like, the best works and writers rising to the top regardless of any other consideration – then the presence of homogeneity in your lineup should concern you, because it’s a sign that someone, somewhere is putting their hand on the scales.
Here’s the thing about awards lists and panel slots: they’re exclusive by definition, which means that someone, somewhere is always going to be miss out, whether personally or in terms of their preferences. Unless you’re handing out trophies for participation, then you’re always going to have arguments about how it was a travesty that so-and-so didn’t make the cut, and there’s always going to be both a political and a promotional aspect to whose names get bandied about. There’s no such thing as a perfect, absolutely objective nomination or adjudication process, because those decisions are ultimately based on individual preferences, and everyone has subjective reasons for liking what they like. That’s the nature of the beast, and it applies across the board, whether you’re talking about the Oscars, Crufts or a local primary school science prize. But when there is a massive, visible dissonance between what’s being created and what’s being praised – when that dissonance just so happens to map to wider social bigotry against particular groups and people – then it’s not unreasonable to advocate for a fairer process. There is, after all, a world of difference between the top prize going to the kid with the most awesome baking soda volcano you’ve ever seen, even if you thought the girl with the string beans was better, and watching some grinning lug who turned in a pile of horseshit take the trophy away from both of them.
The WFC 2016 program is frustrating, not just because it’s so manifestly disinterested in the ongoing development of SFF, but because it can’t even pretend with any degree of subtlety that its objections to those developments are anything other than a deep-seated preference for the opinions of straight white men. I’ve harped on the animal fantasy panel because Schweitzer’s response to Pinsker about it perfectly encapsulates the dissonance in his attitude, but it’s the same thing wherever you look. For god’s sake, there are more references to men born in the 1800s than to any women, living or dead. How can that possibly make sense at a convention where people are meant to go to discuss the genre’s future? How can such a convention even have a future, when it’s so hellbent on dismissing the reality of its inheritors?
Which, in a wider sense, is what’s happening right now with the Sad Puppy campaign and the Hugo Awards. Asked to share the playground equally with the other children, the Puppies lasted five minutes before deciding it was better to smash the swings and shit on the slide than let anyone use the shared equipment for games not of their orchestration. My toddler has more reasoned emotional responses, and he’s three.
But we know all that. We’ve said it before. What else is there to say?
So, remember that thing where Mark Oshiro and I are co-editing the Speculative Fiction 2015 anthology? The fabulous cover and even more fabulous TOC are here! Feast your eyes on the magnificence!
And here’s the TOC:
SpecFic’ 15 will be released in the summer and all profits from sales will be donated to Room to Read. We really hope you enjoy it!
Yesterday, after tangentially mentioning Baen Publishing in a Twitter conversation about queer representation in SFF, several Baen aficionados took this as an invitation to harangue both myself and the person to whom I was was speaking about the evils of left-wing politics, both in genre and more generally. Mostly, this involved yelling about how socialism is evil and feminism is cancer, which was equal parts hilarious and horrifying, with a bonus discussion of Christianity in the context of various political systems. My personal highlight: the unironic claim, made by a Christian participant, that Christ was apolitical, which. Um. Yeah. About that:
While the thread eventually devolved in much the way you’d expect, the actual opening salvo by Patrick Richardson – made in response to the observation that Lois McMaster Bujold’s work, politically speaking, is somewhat at variance with the bulk of Baen’s catalogue – was as follows: “It seems to be only the lefties that care about politics before story.” Which view was quickly seconded by the same woman who later claimed that Christ was apolitical: “Of course! If the story is crap but the author is a nifty socialist, that’s totes awesome!”
Twitter, as anyone who routinely uses it can tell you, is good for many things, but nuanced, lengthy dialogue is seldom one of them. And so, in addition to yesterday’s back and forth, I’m commenting here – because for all their brevity, these two statements perfectly encapsulate the fundamental misunderstanding at the heart of most anti-diversity arguments.
I’ll deal with the second claim first, as it’s always struck me as being the most wilfully obtuse permutation of the stance. The idea that pro-diversity voices are wasting time, money and effort promoting books we don’t actually like is almost cartoonishly absurd; as though diversity is a naked emperor and we the masters of his empty wardrobe. Listen: I have a toddler, a husband, an active social life, a packed writing schedule, multiple online streaming accounts and a TBR pile that stretches into infinity. If you really think I’m going to waste valuable energy advocating for stories that don’t give me pleasure, then either you’re projecting – which, given the willingness of certain Puppies to thusly waste their own time, is a disturbingly real possibility – or you’re grossly overestimating your knowledge of human nature.
Having already discussed, at length, the dissonance between how recommendations made on the basis of diversity can appear to others and what they actually mean, I won’t revisit the details here. The salient point, however, is this: once you acknowledge that a book recommended on whatever basis is, by virtue of being recommended, a book enjoyed, then it’s virtually impossible to claim that diversity advocates are wilfully dismissive of quality. Nor is the intention to treat “diverse books” as a distinct subgenre, one elevated above its fellows without any regard for category or content otherwise. This is, in fact, exactly the kind of ghettoisation the pro-diversity camp is actively trying to avoid – all the diverse books on one niche shelf at the back, instead of being a normal, integrated part of genre. This accusation likewise ignores the fact that, actually, it’s quite common to group and recommend narratives on the basis of their tropes (friends to lovers, the Chosen One) or thematic elements (classic quest, mythological underpinnings), particularly when we’re speaking to personal preference.
The problem is that, when talking to someone who doesn’t value diversity in narrative – often because they’ve simply never considered it to be a noteworthy factor in their enjoyment of a book, and not because they inherently object to its presence – it can be difficult to explain why it matters at all. Taste is always a murky thing to navigate in such arguments, but it’s an inescapable factor: popularity and obscurity are both unreliable yardsticks where quality is concerned, and given the breadth of the human experience, there’s always going to be entrenched disagreement about what a good story is or should be; whether reading should challenge our comfort zones or confirm them; whether it’s better to read a book that shows us our own experience or a different one. Nobody wants to be told what to like or how to like it, just as we all reserve the right to entertain ourselves on our own terms, and yet, to borrow a phrase, no man is an island. Taken collectively, our individual preferences can and do have an impact at the macro/cultural level that transcends their micro/personal origins, even though the one is invariably a product of the other.
This is why the promotion of diversity is often discussed in moral/representational terms, particularly in connection with children: stories are our first and greatest window into the possible, and if those early adventures consistently exclude a large portion of their audience, or if certain groups are portrayed more complexly than others, then not everyone is learning the same lesson. Even so, the idea is never that diversity should take precedence over quality, as some seem to fear, but rather, that we should aim to create stories – stories in the plural, not the singular, though still bearing in mind the interrelationship between the individual and the collective – which are both diverse and good.
So what, then, of stories that are good, but not diverse? Where do they fit in? Because, on the basis of everything I’ve said here, there’s an argument to be made – and some, indeed, have made it – that you cannot have quality without diversity at all.
While this is a useful shorthand claim to make when looking at the collective end of things as they currently stand – which is to say, when acknowledging the historical lack of diversity and the ongoing need to remedy the imbalance – as a dictum removed from context, it not only ignores the rights of the individual, both as audience and creator, but opens up the question of whether a diverse story is diverse enough. It’s a difficult problem to navigate, and one that gives me a frequent headache. On the one hand, it’s undeniable that white liberal feminism (for instance) has a long and ugly history of ignoring the various racial and homophobic aspects of misogyny as experienced by women of colour and the queer community – that there is, as Kimberle Crenshaw said, an intersectional component to oppression. As such, praising a novel for its diversity doesn’t mean those aspects of the story are automatically exempt from criticism; far from it, in fact, which is one more reason why I find the accusation that pro-diversity equals anti-quality so laughable. The advocates of diversity are simultaneously its sharpest critics, and always have been, because we’re the ones who care about getting it, by whatever definition, right.
But on the other hand, it’s an inescapable fact that stories are finite: no matter how much detail a given setting might contain, the author can’t focus on everything, or they’ll have no focus at all. By the same token, nothing and no one is perfect, least of all because ‘perfect’ means something different to everyone: the fact that an author drops the ball in one area doesn’t preclude them succeeding in another, and while the function of criticism is to discuss such contrasts – and while every individual reader is perfectly entitled to decide for themselves how such lines are drawn; to make their own decisions about content and execution – declaring imperfection the antithesis of success does all creative efforts a disservice.
Which brings me back to that mercurial element, taste, and the fear, as expressed by Richardson, that even acknowledging diversity as a factor means putting “politics before story”. It’s a telling phrase: by its very construction, it implies that politics are external to stories, instead of being a material component and/or a relevant lens through which to view them. Which, I would contend, they are. It’s not just that the personal is political: it’s that the political is seldom anything else. The only impersonal politics are those which affect other people; which is to say, they’re only ever impersonal to some, not objectively so. The conflation of political questions with abstract concerns can only occur when the decision-makers don’t meaningfully overlap with those their decisions impact. Political apathy is the sole province of the ignorant and the unaffected: everyone else, of necessity, is invested.
Speaking personally, then, and setting aside any other salient, stylistic factors, the point at which my preference for diversity will likely see me jolted from an otherwise good book, such that I may well question its claim to goodness, is the point at which the narrative becomes complicit in dehumanisation, particularly my own. What this means is always going to shift according to context, but broadly speaking, if an author leans on offensive, simple stereotyping in lieu of characterisation, or if groups that might be realistically present or active within a given context are mysteriously absent, then I’m going to count that a negative. Note that a story which is, in some active sense, about dehumanisation – a misogynist culture; a slave-owning family – is not automatically the same as being complicit in that dehumanisation. This is an important distinction to make: whereas a story about dehumanisation will, by virtue of the attempt, acknowledge what’s going on, even if the characters never question the setting – say, by portraying complex female characters within a restrictive patriarchal system – a complicit story will render these elements as wallpaper: a meaningless background detail, like the number of moons or the price of fish, without ever acknowledging the implications.
It’s not just that, overwhelmingly, complicit stories tend to be dismissive of people like me, though that certainly doesn’t help; it’s that, at the level of worldbuilding and construction, I find them boring. One of my favourite things about genre novels is learning the rules of a new time and place – the customs, language, history and traditions that make up the setting – and as such, I don’t enjoy seeing them treated as irrelevant. For instance: if I’m told that the army of Fictional Country A has always accepted female soldiers, but that women are the legal subjects of their husbands, with no effort made to reconcile the apparent contradiction, then I’m going to consider that a faulty piece of worldbuilding and be jerked out of the story. Doubly so if this is just one of a number of similar elisions, all of which centre on women in a narrative whose complexities are otherwise lovingly considered; triply so if there are no central female characters, or if the ones that do appear are stereotyped in turn. (And yes, I can think of multiple books offhand to which this particular criticism applies.)
Call it the Sex/Hexchequer Test: if an elaborate, invented system of magic or governance is portrayed with greater internal consistency than the gender roles, then the story is probably sexist. Which doesn’t, I hasten to add, mean that it has nothing else to offer and should be shunned at all costs – imperfection, as stated above, is not the antithesis of success. But if someone wants to avoid the book on those grounds, then that’s entirely their business, and at the very least, I’ll likely be cranky about it.
And thus my preference for good diverse stories, which tend not to have this problem. It’s not a question of putting politics ahead of the story: it’s about acknowledging that all stories, regardless of authorial intention, contain politics, because people are political, and people wrote them. In real life, politics only ever seem impersonal if they impact someone else; in fiction, however, that’s what makes them visible. Stories aren’t apolitical just because we happen to agree with them or find them unobjectionable: it just means we’re confusing our own moral, cultural and political preferences with a neutral default. Which doesn’t mean we’re obliged to seek out stories that take us out of our comfort zone this way, or like them if we do: it just means that we can’t gauge their quality on the sole basis that this has, in fact, happened.
And yet, far too often, this is exactly what diversity advocates are criticised for doing: as though acknowledging the political dimensions of narrative and exploring them, in whatever way, deliberately, is somehow intrinsically bad; as though nobody sympathetic to certain dominant groups or ideologies has ever done likewise. Well, they have: you just didn’t think it mattered overmuch, because you agreed.
It’s not about quality, Mr Richardson; it never was. It’s about visibility – who lives, who dies, who tells your story – and whether or not you noticed.
Trigger warning: discussion of rape/sexual assault, spoilers for Uprooted.
Recently, I contributed to a tumblr thread about our unfortunate cultural habit of romanticising abusive behaviour in stories meant primarily for teenage girls, and how this can have a very real, very negative impact on their ability to accurately identify abuse in other contexts. I highly recommend reading the other responses in the thread, as many women shared their own, similar experiences of being confused on this point as teens, while Cora Buhlert also wrote an excellent follow-up post about the conversation. It’s something I’ve been thinking about a lot in the past year or so, not only because I’m interested in feminism within SFF, but also because of my own personal history.
As a teenager, I didn’t understand consent the way I do now, because nobody ever explained it to me in anything beyond the most basic, Rape-Is-A-Masked-Man-In-The-Bushes way. I watched a lot of TV shows where young women were raped and murdered by men who were, overwhelmingly, strangers, and I read a lot of books – quite a horrifying number, in hindsight – where the abuse and coercion of women was incorporated as a normative aspect of fantasy worldbuilding, but very seldom interrogated. It’s not as if I was consciously expecting these stories to provide me with guidance about my then-fledgling sex life, but at the same time, it’s not as if there was a surplus of knowledgeable, approachable, non-judgemental adults lining up to advise me, either. My brain was a sponge: I learned without meaning to learn, in a vacuum of intention to either teach or critique. Sex ed at school meant a basic knowledge of STDs and contraceptives, a basic knowledge of anatomy, and some truly horrendous Behold Yon Horrible Consequences videos filmed in the 1980s about the dangers of teen pregnancy. I don’t think the word consent was ever used, even when we talked about rape: the binary question, rather, was whether you should say yes or no at a given time, and why drinking at parties was a bad idea because you’d be more likely to say yes and regret it later.
The idea that anyone who coaxed that drunken yes from you might be guilty of rape or assault was never mentioned. If it had been, I might have made some very different choices as a teenager. Or maybe I’d have done the exact same thing, but understood immediately what it meant, instead of locking up for an hour nearly fourteen years later, covered in cold sweat at the belated realisation: oh. Oh. Naively, I’d thought I was done with such bleak epiphanies the first time I backdated my earliest forays into internet chatrooms and realised that actually, yes: those men were, in all probability, paedophiles. The teacher in his thirties who praised my thirteen-year-old “maturity” was not just an adult wanting to be my friend, and the men aged eighteen and over who’d ask for cybersex certainly weren’t.
Culturally, we have a lot of sexist baggage about women turning thirty and what it’s supposed to mean, but nowhere in all that baggage have I ever seen mentioned the likelihood of looking back on my early sexual experiences and realising, all too late, like a brutal, cascading suckerpunch, how fucked-up most of them were. That I would, at twenty-nine, rediscover a poem I wrote at sixteen – a poem I’d read multiple times since then, had showed to multiple adults since then, had always held up internally as an example of my early skill – and almost fucking vomit to realise how clearly it described a sexual assault. I was crying when I wrote it, raw and blank in the aftermath of the event itself, and – I remember this vividly – utterly confused, because I didn’t know what had happened. How can you be nearly thirty before you understand a thing like that?
I am, I’ve come to understand, a peculiarly repressive person. I hide things from myself. For all my ferocious introspection, I can be singularly self-deceptive. I wonder at the trait: was I always that way? Is it learned or innate? What quirk of blood or history encapsulates this appalling, unuseful talent? It feels like such an incongruous thing, especially given the strength of my memories. But perhaps that’s the problem: at the time, the things that appal me now weren’t appalling at all. They might have been unpleasant, even ugly or frightening, but they were also, in the context, normal, and as such, I didn’t question them. I remembered them as acceptable, as things that just happened, and even when the feelings underlying those verdicts were – are – turbulent, a second, more intelligent ruling is nonetheless hard to make. I was depressed as a teenager, and inasmuch as a facet of that depression was situational, I thought I understood the whole, both then and afterwards. Instead, that sadness – that very real, rooted sadness, both temporal and ephemeral – acted as a masking agent for other, more particular injuries. At the time, there was no need to wonder why sex could leave me heartsick; I felt that way often enough as it was to see nothing extraordinary in the confluence.
(Oh, young thing, no. Don’t boast of the bruises you didn’t want. Your loneliness ached, I know, but less than their acquisition.)
The past, as they say, is a foreign country. I did things differently there.
Tonight, I started reading Naomi Novik’s Uprooted. It was a novel about which I’d heard only good things from people I trust; a novel I was hoping would break me out of my current reading slump, wherein I’ve started a great many books, but am struggling to finish any of them. To borrow the parlance of memes, cannot tell if too depressed to read or just fed up with exclusionary, derivative bullshit – or, alternatively, if reading so much fanfiction has utterly wrecked my internal yardstick for length, structure and content. Yesterday – partly to test this hypothesis, and partly because I just wanted to – I embarked on my third reading of Katherine Addision’s The Goblin Emperor, a novel which, both stylistically and structurally, is utterly removed from fanfic’s conventions, but which is similarly subversive of genre.
Given that I devoured it, thrilled and rapturous, in a single sitting, I’m inclined to think the problem is other people.
I hate not finishing books, but lately, I’m all out of fucks to give for stories that don’t include me in the narrative. After struggling with Ken Liu’s The Grace of Kings, I started reading Guy Gavriel Kay’s River of Stars in parallel, hoping to find enough thematic points to compare and contrast that the one might jumpstart my interest in the other. And part of me wants, really wants, to read them both – not just dutifully, but because I don’t feel fully entitled to discuss them otherwise. But god, god, where are the rest of the women, and why are the few we see surrounded by men? Where is the queerness hiding, and why do I have to sift for it like some unlucky prospector stranded at the ass end of the gold rush? Why, Mr Kay, are you taking me away from your (thus far) single female POV character to show me what her would-be assassin thinks of his attempt on her life, even and especially when he dies at the end of the chapter? All his exposition did was silence hers, and as she’s apparently The Kind Of Woman Other Women Hate, I’m holding out little hope that the next fucktillionty pages are any better.
And thus, Uprooted. I wanted to root for it. (Heh.) Every ten years, Agnieszka’s village has to give a girl to the Dragon, the wizard who protects their valley. After a decade in his service, the girls come back, unharmed but changed, only to be replaced by new apprentice. And this year, everyone thinks that Kasia, Agnieszka’s beautiful, clever best friend, is the one he’ll choose – only for Agnieszka herself to be taken instead. The writing is lovely, the pacing fluid, and we’ve already been reassured that the Dragon doesn’t assault the girls he takes, that he leaves them dowered and educated and self-possessed, and oh, I was so ready for this to be a story I loved –
But it’s not. It can’t be. The Dragon is an abuser – is grossly, violatingly abusive – and yet the narrative blooms with cues that he’s meant to be Agnieszka’s love interest, burning touches and flashing eyes, and of course, of course he’s centuries old and handsome in a young man’s body (you’re so mature for your age!) and no, this is not what I wanted – is, in fact, the exact fucking opposite of what I wanted – but what if I’m the problem? What if the novel is going to interrogate these tropes, this awful problematic idea of abuse as a prelude to romance, and I bow out too early?
I went to the internet, source of my current wisdom and early folly. Internet, I said, speaking as if to a magic mirror (wireless, wireless in the wall, who’s the truthiest of all?) – internet, does Agnieszka end up with the Dragon?
And lo, did the internet answer: pretty much, yeah. Sorry.
Now, I love Naomi Novik, and YA, and romances, though it took me a good long while to really admit the latter, and thanks to the aforementioned years of narrative conditioning, I have a pretty high tolerance for Partner A initially treating Parter B terribly Because Misunderstanding or some other reason, even though it sets my teeth on edge. By which I mean, I hate it intellectually, but there’s still a firmly-established emotional bedrock for pushing through regardless, on the offchance that we eventually get to a half-decent explanation. It’s actually not as weirdly hypocritical as it sounds: a lot of us have grown up feeling conflicted about the toxic tropes of our youth, as compelled by their unhealthy hold on our formative memories as we are repulsed by our subsequent understanding of them, and as such, it’s not uncommon to see them being… de-escalated, seems the best word for it. We know they’re fucked up, but we kinda want to use them anyway, because all the intellectualism in the world can’t make us rip out even the most diseased aortal tissue wholesale; it hurts too much, for one thing, and for another, it won’t grow back. And so, instead, we try our best to manage their perpetuation carefully: to sand off the worst, most unforgivable elements and mitigate the rest through lovingly tailored contexts. You can just about graph it, sometimes, the way those old tropes change from book to book, as newer authors learn their lore from newer permutations. It’s a form of literary evolution not unlike the Belyaev fox experiment: each new generation of readers learns to love the least-aggressive tropes from a litter of mixed novels until, one day, a thing that once bit savagely will whine and roll over for belly rubs.
Uprooted, though – Uprooted retains its teeth. And even knowing why, by this selfsame logic, other readers were able to skritch it happily behind the ears and carry on, I don’t think I can be one of them.
When the Dragon brings Agnieszka to his castle, he doesn’t tell her why he picked her. For the first few days, he barely speaks to her at all. When he touches her, he grabs her, hard. He insults her, viciously and constantly, berating her as stupid and ugly and useless, though he doesn’t stop to explain what it is he wants from her, or why she needs to learn. He forces her to dress in clothes she finds uncomfortable, expects her to cook his meals for him, but insults her efforts. And Agnieszka, right from the outset, is frightened that he’ll rape her – in fact, she doubts the safety of the girls in his care from the very first page:
He doesn’t devour them really; it only feels that way. He takes a girl to his tower, and ten years later he lets her go, but by then she’s someone different. Her clothes are too fine and she talks like a courtier and she’s been living alone with a man for ten years, so of course she’s ruined, even though the girls all say he never puts a hand on them. What else could they say?
We see her doubts again, on page sixteen:
Kasia had always said she believed the women who came back, that the Dragon didn’t put a hand on them. “He’s taken girls for a hundred years now,” she said firmly. “One of them would have admitted it, and word would have got out.”
But a few weeks ago, she’d asked my mother, privately, to tell her how it happened when a girl was married – to tell her what her own mother would have, the night before she was wed. I’d overheard them through the window, while I was coming back from the woods, and I’d stood there next to the window and listened in with hot tears running down my face, angry, so angry for Kasia’s sake.
Now that was going to be me. And I wasn’t brave – I didn’t think that I could take deep breaths, and keep from clenching up tight, like my mother had told Kasia to do so it wouldn’t hurt. I found myself imagining for one terrible moment the Dragon’s face so close to mine, even closer than when he’d inspected me at the choosing – his black eyes cold and glittering like stone, those iron-hard fingers, so strangely warm, drawing my dress away from my skin, while he smiled that sleek satisfied smile down at me. What if all of him was fever-hot like that, so I’d feel him almost glowing like an ember, all over my body, while he lay upon me and –
I shuddered away from my thoughts and stood up.
This isn’t just a vague fear, but one the narrative makes explicit: Agnieszka is, very graphically and very, very literally, afraid of being raped. And contextually, she has every reason to be! The fact that the Dragon doesn’t take her to bed the second they get to his tower is hardly proof that he has no intention of doing so later; and certainly, it’s within his power to make her do whatever he wants.
As this scene, on page twenty-eight, makes clear:
I froze in surprise and stopped reading, my mouth hanging open. He was furiously angry: his eyes were glittering and terrible…
He gaped at me and grew even more wildly angry; he stormed across the tiny chamber, while I belatedly tried to scramble up and back, but there was nowhere for me to go. He was on me in an instant, thrusting me flat down against my pillows.
“So,” he said, silkily, his hand pressed down upon my collarbone, pinning me easily to the bed. It felt as though my heart was thumping back and forth between my breastbone and my back…
“Agnieszka,” he murmured, bending low towards me, and I realised he meant to kiss me. I was terrified, and yet half-wanting him to do it and have it over with, so I wouldn’t have to be so afraid, and then he didn’t at all. “Tell me, dear Agnieszka, where are you really from? Did the Falcon send you? Or perhaps even the king himself?”
Listen: at this point, I don’t give a flying fuck that, for whatever reason, the Dragon seems to think Agnieszka is a spy. It doesn’t excuse his behaviour, because whoever she really is, she’s still a girl he’s got pinned to a bed, and he’s still making her feel sexually afraid of him in order to try and intimidate her into answering. The idea that his incredibly intimate rape threat is somehow justified by her potential treachery is, frankly, sickening. Never mind that, after she runs and accidentally spills a potion over herself, he leaves her frozen in stone for half a day without any explanation or apology; never mind that he physically makes her crawl around him, belittling her competence all the while. Agnieszka is so miserable and terrified that she wants to kill the Dragon, even contemplating suicide when she can’t go through with her plan. It’s a blink-and-you’ll-miss it moment, but to me, it felt like a slap in the face:
…I saw the tray discarded on the floor, the knife lying bare and gleaming. Oh. Oh, what a fool I’d been, even to think about it. He was my lord: if by some horrible chance I had killed him, I would surely be put to death for it, and like as not my parents along with me. Murder was no escape at all; better to just throw myself out the window.
I even turned and looked out the window, miserably…
So, to reiterate: the Dragon is treating Agnieszka in such a monstrous, abusive, bullying fashion that murder and suicide have both crossed her mind as options; she’s frightened he’ll rape her still, and he’s used that fear to try and make her comply with his wishes.
And then Prince Marek arrives, and actually tries to rape her.
To make this even more horrible, up until his assault, Agnieszka had been contemplating going to Marek for help, only keeping quiet because she’s afraid he won’t believe her. She’s heard stories of his exploits, thinks of him as a hero, and apart from anything else, he’s the only other person she’s even seen since the Dragon took her away.
Here is what happens (TW for assault):
He laughed again and kissed my throat. “Don’t worry, he can’t object,” he said, as though that was my only reason to protest…
It’s not that he was taking pleasure in overcoming me. I was still mute and my resistance was more confused batting at him, half-wondering: surely he couldn’t, Prince Marek couldn’t, the hero; surely he couldn’t even really want me. I didn’t scream, I didn’t plead, and I think he scarcely imagined that I would resist. I supposed in an ordinary noble house, some more-than-willing scullery maid would already have crept into his bedchamber and saved him the trouble of going looking. For that matter, I’d probably have been willing myself, if he’d asked me outright and given me enough time to get over my surprise and answer him: I struggled more by reflex than because I wanted to reject him.
But he did overcome me. Then I began to be really afraid, wanting only to get away; I pushed at his hands, and said, “Prince, I don’t, please, wait,” in disjointed bursts. And though he might not have wanted resistance, when he met it, he cared nothing: he only grew impatient.
“There, there; all right,” he said, as though I were a horse to be reined in and made calm, while he pinned my hand by my side. My homespun dress was tied up with a sash in a simple bow; he already had it loose, and then he dragged up my skirts.
I was trying to thrust my skirts back down, push him away, drag myself free: useless. He held me with such casual strength.
At this point, Agnieszka uses one of the few magic spells the Dragon has taught her – a spell to create clothes, the better to look pretty for him – to recover herself. Marek is so stunned that she has a chance to bash him over the head with the abandoned dinner tray, and he goes down hard, unconscious. Agnieszka, not unsurprisingly, is both frightened at the prospect of having killed a prince and shaken at having been nearly raped. So when the Dragon enters and discovers the scene, does he treat her kindly, even dispassionately, while he tries to heal the Prince? Or does he behave like a cruel, abusive, victim-blaming asshat?
Oh, yeah. Welcome to door number three.
I stood hovering anxiously over the bed, over both of them, and finally I blurted, “Will he -“
“No thanks to you,” the Dragon said, but that was good enough: I let myself sink to the ground in my heap of cream velvet, and buried my head on the bed in my arms sheathed in embroidered golden lace.
“And now you’re going to blubber, I suppose,” the Dragon said over my head. “What were you thinking? Why did you put yourself in that ludicrous dress if you didn’t want to seduce him?”
“It was better than staying in the one he tore off me!” I cried, lifting my head: not in tears at all; I had spent all my tears by then, and all I had left was anger. “I didn’t choose to be in this -“
I stopped, a heavy fold of silk caught up in my hands, staring at it. The Dragon had been nowhere near; he hadn’t worked any magic, cast any spell. “What have you done to me?” I whispered. “He said – he called me a witch. You’ve made me a witch.”
The Dragon snorted. “If I could make witches, I certainly wouldn’t choose a half-wit peasant girl as my material. I haven’t done anything to you but try and drum a few miserable cantrips into your nearly impenetrable skull.” He levered himself up off the bed with a hiss of weariness, struggling, not unlike the way I’d struggled in those terrible weeks while he –
While he taught me magic. Still on my knees, I stared up at him, bewildered and yet unwillingly beginning to believe. “But then why would you teach me?”
“I would have been delighted to leave you moldering in your coin-sized village, but my options were painfully limited.” To my blank look, he scowled. “Those with the gift must be taught: the king’s law requires it. In any case, it would’ve been idiotic of me to leave you sitting there like a ripe plum until something came along out of the Wood and ate you, and made itself into a truly remarkable horror.”
While I flinched away appalled from this idea, he turned his scowl on the prince…
“Here,” said the Dragon. “Kalikual. It’s better than beating paramours into insensibility.”
So, to be clear: not only does the Dragon neglect, at any point, to ask if Agnieszka is all right – not only does he belittle her for defending herself, and continue to bully her intelligence – but he blames the assault on her choice of clothes, and then refers to the prince, not as her assailant or rapist, but as her paramour, a consensual term that utterly minimises what just took place. Their subsequent conversation reveals his belief that Marek, who assumes the Dragon takes women “to force them to whore for me”, would have seen bedding Agnieszka as “cuckolding” him, and therefore a sort of petty revenge. Again, this is desperately minimizing language, even in context: at no point is the attempted rape named as such, and despite the fact that Agnieszka has spent literal weeks in fear of being raped, the rest of the conversation – and, indeed, the events of the following chapter – appear to show her experiencing no emotional consequences at having that fear made manifest. Instead, the Dragon continues to bully her, and badly, when she fails to make her magic work:
He roared at me furiously for ten minutes after he finally managed to put out the sulky and determined fire, calling me a witless muttonheaded spawn of pig farmers – “My father’s a woodcutter,” I said – “Of axe-swinging lummocks!” he snarled. But even so, I wasn’t afraid anymore. He only spluttered himself into exhaustion and then sent me away, and I didn’t mind his shouting at all, now that I knew there were no teeth in it to rend me.
I was almost sorry not to be better, for now I could tell his frustration was that of the lover of beauty and perfection. He hadn’t wanted a student, but, having been saddled with me, he wanted to make a great and skillful witch of me, to teach me his art…
It maddened him to no end, not without some justice. I know I was being foolish.
At this point, it was all I could do not to fling the book at the wall. It’s Agnieszka who’s been sexually assaulted and belittled, but the sympathy here – and worse, given in her voice! – is all for the Dragon: language that tries to excuse his abuse as the understandable frustration of a perfectionist, Agnieszka blaming herself for not being good enough, for daring to have interests and talents beyond what he expects of her, even though he’s done literally nothing to show her kindness at all. Are we meant to find it a sign of progress, that she doesn’t mind his shouting? Are we meant to feel well-disposed towards such a vile abuser, or ought we to be rooting for her escape?
My instincts were telling me one thing, and the narrative another. Which is why I went on Twitter and asked if their relationship becomes a romantic one. Universally, the response came back: they get together, it’s implied they’re still together at the end, and the Dragon’s early mistreatment of Agnieszka is never satisfactorily addressed.
And I just – no. No. I do not want to read nearly four hundred more pages only for this level of vicious cruelty to never be called what it is. I do not want to read about a sexual assault victim falling in love with an abusive rape-apologist and think about how romantic I would’ve found it all, when I was Agnieszka’s age; how romantic some other girl might find it now, who won’t know any better until she’s nearly thirty, too. I do not want to soldier on for the sake of those amazing feminist virtues I’ve been told the rest of the novel somehow, separately, embodies, because if I’m going to read a book that deals with rape and sexual assault, I would like it, please and thank you, to actually call it those things, or at least to behave as though belittling a victim of same in their immediate fucking aftermath isn’t an acceptable gateway to romance.
Fucking hell. I just want to read a book that doesn’t make me feel like I’m being either punched for existing, or treated as though I don’t. We’re SFF writers; we literally make up shit for a living. Why does everything have to be so brutally fucking difficult?
Earlier this week, Chuck Wendig posted a piece on his blog – I Smell Your Rookie Moves, New Writers – which, as the title suggests, is a takedown of particular errors he feels newbie authors make. It’s been doing the rounds on my tumblr, Facebook and Twitter feeds, because quite a lot of people I follow seem to share his sentiments; but as often as I’ve agreed with Wendig’s rants in this past, this isn’t one of those times. In fact, my abiding reaction to the early sections in particular has been one of teeth-grinding fury.
Before we get started, let me make two things clear up front: firstly, that I have an inherent dislike of writing advice that lays down specific mandates regardless of where it comes from; and secondly, that I have enormous respect for Wendig himself as a writer. His prose is punchy, sharp and bruisingly beautiful, quite like getting mugged by a street poet, and I have zero qualms about his ability to offer good advice otherwise. This isn’t me quibbling with Wendig’s technique, nor am I taking issue with the fact that he, specifically, is the one who’s spoken – it’s just that, on this occasion, he’s said a few things I think are fucking stupid, and I’d rather like to address them.
Straight up, there’s a need to compare what Wendig says in his very first paragraph to what he says in the fourth (bolding mine):
I am occasionally in a place where I read work by new writers. Sometimes this is at cons or conferences. Sometimes it’s in the sample of work that’s free online or a fragment from a self-published work…
What I’m trying to say is, your rookie efforts are not automatically worth putting out into the world, especially if those efforts cost readers money to access them. The mere existence of a story is not justification for its publication. Don’t make people give you cash for your inferior efforts. Get it right before you ask money to reward you for getting it wrong.
Oh my fucking GOD, I will flip a table. Where do I even begin with this bullshit? If someone is publishing their work free online, THEY AREN’T ASKING FOR CASH – and what’s more, no one is fucking asking you to read it. There are myriad online communities that exist precisely so that new writers can ‘publish’ their work and share it with each other, up to and including specific fandom and fanwriter sites, and I reject utterly the implication that there’s no point to those venues or those communities – that such new stories aren’t “worth putting out into the world” – just because they’re not up to Wendig’s standards. I’d take less issue with the sentiment of an established writer selflessly offering help to rookies if that’s what Wendig was actually doing; instead, his piece reads like a successful author castigating first-timers for daring to aspire to his level before he thinks they’re ready.
Listen: I am all for writers improving themselves, and in the event that I fork over money for a book, I am all in favour of that book not sucking! But look at the wording, here: “don’t make people give you cash for your inferior efforts” – don’t MAKE them, as though the author is standing behind the consumer with a loaded gun, forcing them to buy their latest Kindle release. The entire point of the goddamn marketplace is that consumers take risks on products and then share their opinions about what they bought, thereby potentially attracting or deterring others from purchasing likewise. Wanting to engage in this process in good faith is not a fucking crime, okay? This whole section reads like a form of literary class policing: know your place, and know that it isn’t good enough.
I also think it’s telling – and grossly hypocritical, given that Wendig himself started as a self-published writer – that he explicitly mentions writers who self-publish, who are unpublished or who write for free, but not rookie authors published via traditional means. (The only nod to traditional publishing is when he talks about “tested authors,” though even then, he could just as easily mean writers who’ve released multiple stories in other formats.) Because, let me tell you: I have read my share of traditionally published works that were fucking shit, and I guarantee I paid more for each of them than I ever have for any self-published release. Never mind that “inferior efforts” is a monumental and incredibly subjective value judgement in the first place: what traditionally published authors have that their unpaid or self-supporting brethren don’t – or not usually, at any rate – is the help of professional editors. Which doesn’t mean that their first drafts are somehow magically lacking the same mistakes Wendig is so angry about here; just that they’ve got an extra pair of eyes to catch them on the first pass. Does Wendig recommend his non-traditional rookies use editors or beta readers, which is an unequivocally useful piece of advice? No, he does not – which means, in essence, that he’s holding such writers to a higher standard than their traditionally published counterparts: be so good the first time that you don’t need an editor.
And look. Okay. Wendig never mentions fanwriters by name, but speaking as someone who’s pretty heavily invested in fan culture at this point, applied in that context, his advice here is the exact fucking OPPOSITE of useful. I mean, I have my own issues with the idea in some fanwriting circles that unsolicited criticism of any kind, even concrit, is verboten, because at the end of the day, if you’re putting something online where people not your friends can read it, you’ve got to be prepared for some degree of feedback. The internet is not your perfect, criticism-free bubble, and there’s no rule saying you get to enjoy the advantages of having an audience minus that audience having its own opinions just because you’d rather not deal with them. But when people share their writing for pleasure ahead of profit – when the content you’re reading is produced for free – that rightly changes the nature of how any feedback should be offered, assuming you care about not being an asshole. A person writing for free is not necessarily interested in improvement, or in anything other than having fun as part of an online community – in which case, telling them to stop posting until they suck less is rather like running up to a bunch of kids playing ball at the park and yelling that they need to run more drills before they do that shit in public, otherwise they’re never going to get scouted. I know it’s hard for published writers to remember this, but some people do write for pleasure alone, and the internet makes that easier than ever.
More to the point, though: writing shouldn’t begin as a woodshed exercise for every single person who wants to try it for money, and part of what makes new authors better – especially if they’re the type of rookie who can’t afford an editor and has no access to reliable betas – is getting feedback on their work. I mean, let’s be real: Wendig is acting like charging money for crap books is a crime, instead of just part of the literary-commercial ecosystem. Crap books – and we won’t always agree on what they are, because it’s a judgement call – are always going to be published, and some people are always going to regret buying them, but that doesn’t mean they should never have been written or published in the first place.
Except 50 Shades of Gray, maybe. That is some abusive, rape-apologist bullshit right there.
But I digress.
Here’s my point: so long as you continue to write, your writing style will change. Maybe you’ll get better, maybe you’ll get worse, and maybe you’ll just get different – write for long enough, and you’ll probably do all three. But if you really want to succeed as a writer, hesitating to publish through fear of your own inadequacies is going to get you vastly fewer places than publishing in confidence, but learning to accept criticism. That being so, I’m not angry that Wendig wants new writers to improve; that’s fair enough. I’m angry because a statement like “don’t make people give you cash for your inferior efforts” isn’t going stop an uncritical egotist who already thinks they’re the next John Green, but it’s sure as hell going to stop the kind of self-doubting beginner whose problem isn’t accepting criticism, but finding the necessary confidence to parse it intelligently.
Which brings me to the topic of Wendig’s actual advice, and the reason I’m always sceptical whenever I see anyone lay down hard rules about what to do, or not do, in the course of writing: it’s because, 90% of the time, that sort of advice doesn’t account for differences in individual style any more than it accounts for differences in individual taste, and therefore has the effect of teaching someone, not how to write well, where well is a universal, but how to write like the person giving the advice.
It is compelling, I know, to figure out every single thing that is happening all the time always in your story. Characters smile and laugh. Okay. They fidget. Fine. They drink a cup of tea with their pinky out. Sure, why not? But if you’re writing out every hiccup, burp, fart, wince, flinch, sip, and gobble, you got problems. A character turns on a lamp? Super, you don’t need to describe how they turn it on. I don’t need to see John Q. Dicknoggin unzipping his fly before he pisses, and frankly, I may not need to see that he pisses unless it’s telling us something about his character.
On the surface, this is a reasonable thing to say. The problem is that it’s only contextually reasonable, in that some people will be helped by taking this advice, and others hindered. Mervyn Peake’s Gormenghast, for instance -widely regarded as a genre classic – could never have been written if Peake wrote to Wendig’s specifications, and regardless of whether his work is your cup of tea, you can’t deny that many people are extremely fond of it, even though – or especially because, depending on your perspective – it contains passages like this:
The speed of the door as it swung on its hinges was extraordinary, but what was just as dramatic was the silence – a silence so complete that Bellgrove, with his head turned towards his staff and his hand still groping in the air for the bell-pull, could not grasp the reason for the peculiar behaviour of his colleagues. When a man is about to make a speech, however modest, he is glad to have the attention of his audience. To see on every face that stared in his direction an expression of intense interest, but an interest that obviously had nothing to do with him, was more than disturbing. What had happened to them? Why were all those eyes so out of focus – or if they were in focus why should they skim his own as though there were something absorbing about the woodwork of the high green door behind him? And why was Throd standing on tiptoe in order to look through him?
Bellgrove was about to turn – not because he thought there could be anything to see but because he was experiencing that sensation that causes men to turn their heads on deserted roads in order to make sure they are alone. But before he could turn of his own free will he received two sharp yet deferential knuckle-taps on his left shoulder-blade – and leaping about as though at the touch of a ghost he found himself face to face with the tall Christmas-cracker of a butler.
Intense, tight, detailed description of settings, people and actions is a valid stylistic choice. That doesn’t mean it can’t be executed badly – just that doing so is not synonymous with executing it at all.
Enter Wendig’s second objection:
We tell stories because they are interesting. We offer narrative because narrative is a bone-breaker: it snaps the femur of the status quo. It is in fact the sharp, gunshot-loud fracture-break of the expected story is what perks our attention. Guy goes to work, works, comes home, has dinner, goes to bed? Not interesting. Guy goes to work, has the same troubles with his boss, endures the standard problems of the day (“where are my goddamn staples?”), goes home, eats an unsatisfying dinner, goes to bed and sleeps restlessly until the next day of the same thing? Still not interesting. Guy goes to work and gets fired? Okay, maybe, depending on if he does something unexpected with it. Guy goes to work and gets fired out of a cannon into a warehouse full of ninjas? I’M LISTENING.
Well, of course you are, Chuck: you write SFF, and are therefore highly likely to prefer ninjas to the minutiae of daily office life. But this doesn’t change the fact that there’s an entire literary tradition based around slice-of-life realism: stories where the big emotional tension really does hinge on the fact that someone was fired after struggling with their boss, and what this means for their family. Hell, you basically just described the first third of American Beauty. What you’re really railing at here is the idea that domesticity is fundamentally uninteresting – which, don’t even get me started on the gendered implications of that logic when applied in wider contexts, aka The Reason Why So Many Goddamn Fantasy Stories Focus On Big Dudes With Swords Because What Women Do In The Castle Is Girly And Unimportant – in conjunction with a dislike of stories that privilege a character’s emotions and internality above external conflict. Which is to say: this paragraph tells us a great deal about what Chuck Wendig looks for in a novel, but conflates this preference with what good novels look like, period.
Description is the same way. You don’t need to tell me what everything looks like because I already know –
Not if I’m describing something that’s purely fictional, you don’t. Which is to say: the fact that I don’t need to tell you what everything looks like doesn’t mean I shouldn’t tell you what anything looks like.
– and most things aren’t that interesting. Leaves on a tree are leaves on a tree. For the impact of story, how many points each leaf has or how they move in the wind is not compelling.
AUGH. Look: I get that this is meant to be a random example illustrating why we shouldn’t include information that’s totally irrelevant to the plot, but it’s a really shitty example, because even ignoring the fact that sometimes, it’s just nice to set the scene, I can think of a dozen reasons off the top of my head why detailing leaves specifically might be relevant. A ranger describes a particular plant which, in addition to its historical significance, can be used as life-saving medicine. The king’s poisoner tends their herb garden, teaching their protégé the various uses of each. A paleobotanist suddenly encounters plants she thought extinct, and promptly goes into raptures. But Foz! I hear you cry, Aren’t you being unfairly specific? When would that ever happen, really?
Reader, I just described to you actual canonically important scenes from The Lord of the Rings, Robin Hobb’s Assassin series and Jurassic Park. The devil is in the motherfucking details, dudes. Sometimes you can do without them, but sometimes you really can’t.
Trim, tighten, slice, dice. Pare it all down. Render. Render!…
Whatever it is you’re writing, it’s too long. Cut it by a third or more. Do it now. I don’t care if you think you should do it, just do it. Try it. You can go back to it if you don’t like it. Consider it an intellectual challenge — can you utterly obliterate 33% of your story? Can you do it mercilessly and yet still tell the story you want to tell? I bet you jolly well fucking can.
Merciful fucking Christ, if I never see another piece of writing advice that involves the phrase “pare it all down” it’ll be too soon. I mean, look: I love a stylistically wham, bam, thank-you ma’am novel as much as the next person, but sometimes I want to indulge myself. Really settle in with the slow-burn detail, rolling around in lush descriptions of bright new worlds. Sometimes you want a bit of junk in the literary trunk, you know? Every single novel does not have to whip its metaphorical dick out on the first page and then spend the next thirty chapters furiously jacking itself to climax like a pornstar trying to hit his mark for a neatly-timed cumshot. Your novel won’t implicitly suck if you slow down and take your time teasing the reader.
Plus and also? I know we have a cultural stereotype that says rookie writers consistently produce pages and pages of unnecessary drivel, but a lot of newbies underwrite, too – in which case, telling them to pare back an already barren story isn’t going to help. There’s a reason why so many early creative writing exercises teach students how to describe, how to build: you need to get to the point of creating excess before you can learn how to cut it back, such that assuming the presence of excess as a default is a bad way to go.
The story begins on page one.
Repeat: the story begins on page one.
It doesn’t begin on page ten. It doesn’t start in chapter five.
It starts on page one.
Get to the point. Get to the story. Intro characters and their problem and the stakes to those problems as immediately as you are able. You think you’re doing some clever shit by denying this? You think you need to invest us in your luscious prose and the rich loamy soil of the worldbuilding and the deep nature of these characters — ha ha ha, no. We’re here for a reason. We’re here for a story. If by the end of the first page there isn’t the sign of a story starting up? Then we’re pulling the ripcord and ejecting. We’ll parachute out of your airless atmosphere and land on the ground where things are actually happening.
This is one way to tell a story, certainly. But it’s not the only way, and it’s not always a good one. I have had my absolute fill of – to pick a single example – first-person YA fantasy novels that start with the character in the middle of a battle for precisely this reason, but which never slow down sufficiently to explain why the fight unfolded that way in the first place, because the author never bothered to figure it out. Listen: I’m aware that there’s a debate about the utility of prologues in SFF, and some people hate them for exactly the reasons Wendig has outlined above. The story should start when it starts; if you can’t communicate that earlier information in the first chapter, then it doesn’t deserve a prologue. And in some cases, that’s correct.
But prologues also constitute an important stylistic break. In a story that’s otherwise written entirely in the first person, for instance, having a prologue in the third, containing information the viewpoint character couldn’t possibly know, but which is materially relevant to interpreting their actions, can be an extremely clever move. Think about every film you’ve ever seen that starts in one place before the opening credits roll, then cuts to the protagonist once they’ve finished. That, right there? That’s setting the scene, and even though it’s not always obvious how that first scene relates to the subsequent ones, that doesn’t mean it shouldn’t ever have been there in the first place.
Despite his presumptuous use of the royal ‘we’, Chuck Wendig is not speaking for everyone when he says that readers aren’t interested in stories that take longer than a fucking page to establish worldbuilding or character. Good novels can be slow. Not to bring up Tolkien again, because I get hives when people hold him up as the be-all, end-all of the genre, but Christ: do you even remember how The Fellowship of the Ring starts? It’s with a prologue entitled Concerning Hobbits that goes on for pages before Frodo Baggins is ever even mentioned by name, and that doesn’t stop people loving it. Writing books is not a goddamn race, is my point, and I’m sick and tired of seeing brevity held up as an unequivocal literary virtue when it’s just as liable to produce dross as gold when used inexpertly.
Dialogue, for instance, is one of those things that has rules. And for some reason, it’s one of the most common things I see get utterly fucked.
On this point, I agree with Wendig. But then, he’s not discussing style here so much as the basic rules of grammar – and even then, if you’re doing it intelligently, with purpose, as opposed to because you’re unaware of the conventions, even these can be fluid. Tim Winton’s Cloudstreet eschews all quotation marks, and it’s a gorgeous novel: yes, it’s an exception to the norm, but I mention it because Wendig’s decision to situate adherence to actual grammatical/formatting rules as identical to meeting his personal narrative preferences makes me bristle. Generally speaking, electing to fuck with the standard protocols is not something you’d do with a first novel, but that doesn’t mean it hasn’t ever been done successfully. Returning to an earlier point, it’s the kind of problem that, for a traditionally published author, would (one hopes) be caught in editing – so if you’re not too sharp on the basic conventions and you care about getting them right, you can either look them up, ask a knowledgeable friend to beta your work, or hire an editor. This is line-edit drama, not a problem with poorly-executed style, and there’s a goddamn difference, please and thank you.
You need to let your characters talk.
Dialogue is grease that slicks the wheels of your story.
And eventually it gets tiresome. You love the characters and you think they should be allowed to go on and on all day long because you think they’re just aces. They’re not. Shut them up. Keep the dialogue trim and vital. Concise and powerful. Let them have their say in the way they need to say it — in the way that best exemplifies who those characters are and what they want — and then close their mouths. Move onto the next thing. Let’s hear from someone else or something else.
Generally speaking, I agree with this, too. Unless your character is giving a speech, monologuing to a captive audience or engaging in a soliloquy, they’re probably not going to speak uninterrupted for any length of time. The conversation will go back and forth, and eventually, it’s going to end, and you don’t always need to show every single exchange in order to get the point across. I will, however, take issue with the idea that dialogue must always be “trim and vital, concise and powerful” – because many people aren’t. Naturalistic dialogue can be a powerful tool in a writer’s arsenal, letting you establish voice, dialect, setting and any manner of other things. That doesn’t mean letting the characters talk about anything under the sun with no reference to plotting; it means that not every single exchange has to be geared towards the narrative end-game in order to make a positive contribution to the story.
Each character needs to be a shining beam — each distinct from the next. Bright and demonstrative of its own color. Not archetypes, not stereotypes, but complex and easily distinguished people. And I want a reason to care about them.
This, I agree with: absolutely, 1000%.
Right out of the gate, I want this. I need to know what they want, why they want it, and what they’re willing to do to get it. I need, in very short terms, their quest. Whether desired or a burden, I gotta know why they’re here on the page in front of me. That’s not true only of the protagonist, but of all the characters.
Who are they?
If you can’t tell me quickly, they become noise instead of operating as signal.
Aaaand we’re back to disagreeing again. Because, look, Chuck – I don’t know what your fucking deal with speed is, here, but I’m going to say it again: storytelling isn’t a race. There are times when I want to know quickly what a character’s motivation is, and times where I can stand to wait a little. Sometimes, the best characters slowly emerge from the background, insinuating themselves into the story in ways you didn’t expect at the outset. A great recent example of this was Csevet in Katherine Addison’s The Goblin Emperor. A courier who initially brings the protagonist, Maia, the news of his ascension to the throne, Csevet seems at first to be a background character, someone who’ll disappear once he’s fulfilled his immediate purpose. This isn’t because Addison fails to make him a distinct individual, but is rather a consequence of the story being told with a tight focus on Maia’s perspective: Csevet’s needs aren’t as important in the first chapters as Maia’s are, and as Csevet initially appears to deliver a specific piece of news, we’re not expecting Maia to keep him around. But he does, and so the character expands, steadily revealing more and more of himself as the narrative progresses.
You don’t need to give a physical description of every single character the second they first appear in the story, because that information might not be immediately relevant. A character can move in the background as a seeming bit player before ever coming to the fore, and even once you can see them, their motives won’t always be transparent. I don’t just mean this in the facetiously obvious sense, that some characters have hidden agendas: I mean that if you’ve got six characters in a scene, the fact that the primary focus is on two of them doesn’t mean the other four won’t come into their own later. This is even more important to remember if you’re writing in first person, where describing a character or making an observation is synonymous with the character doing those things – and while the author might want to give certain details, the character might not even pick up on them for another three chapters.
What I’m saying is this: Wendig is completely correct in saying that your characters, even the minor ones, should be real, distinct individuals. But that doesn’t mean you have to give their quest away up front, or make it immediately obvious that a seemingly minor character is going to come into greater prominence later. I dislike working from the assumption that your audience is impatient, easily bored and allergic to surprises – especially as I’m not that sort of reader myself.
It’s very hard to manage a lot of characters.
I do it in some books and the way that I do it is by introducing them piecemeal — not in one big dump like I’m emptying a bag of apples onto the counter (where they promptly all roll away from me), but one or two at a time.
Which is kind of what I’m getting at, but from the opposite perspective: it’s okay to empty your bag of apples, provided you subsequently gather them all back up again. Otherwise, you’re permanently restricting yourself to writing early scenes where only one or two characters are present, which… personally? I find that boring; or at least, I wouldn’t want it as a staple. I like stories that challenge me by throwing me in the deep end, asking that I figure out a bunch of characters and navigate their relationships on the fly by way of teaching me the setting. Elizabeth Bear does this wonderfully, as do Kate Elliott and Alaya Dawn Johnson, which is a big part of why I love their books. Particularly in SFF, the social roles the characters inhabit can tell you as much about them – and the world – as their personalities and motives, and the fact that there might be a tension between how a character behaves in an official capacity and who they are otherwise can lead to some extremely satisfying characterisation. Thus: you might first show me the faceless Executioner in Chapter 1, letting them appear as a background authority in Chapter 2, so that when I finally learn their name and their hatred of the Emperor they purport to serve in Chapter 3, I feel the contradiction far more strongly than if you’d simply said as much to begin with.
…if each character sounds like a replicant of the next, you’ve got a problem. It’s not just about vocal patterns. It’s about what they’re saying in addition to how they’re saying it. It’s about their ideas and vision and desires. Look at it this way: it’s not just your prose that makes you your author. It’s not just your style. It’s whatyou write. It’s the themes you express. Characters operate the same way. They have different viewpoints and needs. They have their own ways of expressing those viewpoints and needs, too. Get on that. Otherwise, they’re all just clones with different names and faces.
Stop doing stunt moves. You can do that later. Right now, assume that you have a single goal: clarity. Clarity is key. It is king. If I do not know what is going on, then I’m out… Do yourself a favor and aim to just tell the story. Get out of the way. Be clear. Be forthright. Be confident and assertive and show us what’s happening without compromise and without burying it under a lot of mud.
You don’t get points for being deliberately ambiguous.
On the surface, this is good advice: it’s just that, given the emphasis on speed in the rest of this piece, I’m inclined to think that Wendig thinks of clarity as a synonym for simplicity, as per the injunction against “trick moves”. Which, yes: if you’re a very new writer, you need to make sure you’re being understood before you can play with expression. But natively, not everyone is going to have the same style or be interested in writing the same sort of book. It’s not a “trick move” to want to have a big cast, or to tell a slow-burn story, or to be interested in description. In fact, I’d argue that writing in a sparse, clean style takes just as much skill as writing more lavishly: there’s an art to economy, and I’ve never liked the idea that it’s somehow a better, easier choice for beginners just because it uses fewer words. Ask any artist: understanding negative space and its impact on the picture takes skill and practice, just like drawing does.
I guess what I’m saying is this: Chuck Wendig has written a piece that’s enormously helpful if you want to learn to write like Chuck Wendig and/or have a natural inclination towards his style, but which is vastly less helpful if you want to learn to write like anyone else; like you, for instance. There’s some good advice there, to be sure, but the parts that aren’t – which conflate his personal preferences with universal truths; which tell new writers they’re not good enough to be worth the cost of admission, no matter how cheap – those parts can fuck right off. Not everybody needs to write books the exact same way, just as everyone doesn’t need to read and love the exact same things, and I’m sick of writing advice that’s really just one person’s taste masquerading as objective truth.