Wednesday, August 27, 2014

Patrick McLaw and the Terror of Words

This story crossed my feeds today and scared the living crap out of me. Short version: author Patrick McLaw also works as a middle school teacher. He wrote two books set in the United States two hundred years in the future, dealing with a pair of school shootings. When school board officials found out about this, Mr. McLaw was put on administrative leave and taken in by the police for an emergency psychiatric evaluation, while the police searched the school for bombs and guns and came up empty. He's also been banned from county and school district properties.

Another story. In high school I wrote a short story for my school's literary magazine. The story involved two friends blowing up a chihuahua-focused dog show. It was a dumb comedy, really a rip off of Mark Twain's story Tom Quartz, in which a cat gets blown up in a mine shaft. I don't know where the chihuahuas came from. I expect if I read it now I'd be happy with the voice and nothing else.

The story was published without incident, and a few months later the Columbine shooting happened. A few days after that, I was called in to see my guidance counselor, who asked me a few questions about the story and myself to make sure I wasn't planning to shoot up the school. Luckily I was an AP student with no history of misbehavior, and that was the end of it. (Nobody really knew I played video games, including Doom II, all the time at home.)

Now, all that happened to me was I got talked to for a few minutes, and it was still one of the scariest experiences of my high school career. I was worried I could be suspended, maybe even expelled.

Today, that would be the least of my concerns. I would be immediately escorted off school property, temporarily if I were lucky, and handed over to the police. I'd be charged with issuing threats and almost certainly end up in court, with the full weight of the local legal system gunning for me. Saying that I was ripping off a story from the 1800s to practice my writing and had no intention of doing anything wrong would be no defense. I would be doomed and damned, my education cut short and quite possibly locked away for years.

Patrick McLaw wrote two books and self-published them. He did not write a manifesto, or a lunatic chatroom screed. He wrote two pieces of fiction and sought to sell them for money. So far as anyone knows that's the extent of his crime. He was nominated for Teacher of the Year and helped a student self-publish his work on Amazon. There is no hint in the stories I've read that he had a truly violent impulse in his body. Yet he's been banished from his workplace and detained, while police stand by in his district's schools to make sure he doesn't come back.

I understand the need to prevent school shootings. I don't see how throwing a respectable teacher onto the street does that. I'm relieved, and sick, to think of what could have happened to me. And I'm terrified to think of what could happen to my son in a few years, in an environment where even pointing a finger and saying "Bang" can get you suspended or expelled.

Mr. McLaw's book, The Insurrectionist, is still available on Amazon. It wouldn't be a terrible idea to give it a look; at the moment I have no idea what else can be done to help the man. But I wish him better luck than he's had so far.

Correction: Police searched the school, not Mr. McLaw's home. This post has been corrected.

Correction again: As of yesterday afternoon police have searched Mr. McLaw's home.

Monday, August 11, 2014

On Female Superheroes and Wonder Woman

I went on a lengthy stream of consciousness rant last night on female superheroes and Wonder Woman. I'm not sure what the hell I was thinking. I'm not solving anything. But there is some stuff I'd like to see in there, a few insights that might be worth something if they were developed, and what I think is a valid point about the way Diana Prince has been handled for the past few decades.

So, enjoy! Or not. As you will.

Image courtesy of

Tuesday, July 29, 2014

The Best Laid Plans

"No plan survives contact with the enemy." Alexander of Macedonia said that, right before he was killed by Ebola-laced elephants.

I propose a variant truth: "No plan survives contact with an infant."

I have determined, after incurring a brand new car bill, various medical expenses, repeated housing repair expenses, and numerous oversized grocery bills (not to mention how ridiculously expensive crabs are this year), that I would like to start making actual money with my writing. Which means writing for publication, in addition to endlessly tweaking the epic fantasy novel squatting in my brain meat.

In preparation, I've been reading Six Figure Freelancing, by Kelly James-Enger. It's a first edition copy, which means it's a bit dated (written in the days where the Internet was only a research tool and Word hadn't devoured every feature of word processing), but it still has some valuable insights on the level of persistence and organization a writer needs to freelance successfully.

I took the book to heart and declared that I would get organized. I set myself a goal for my first week, namely that I would take half an hour a night to sit and write without doing anything else. To hell with the dishes, laundry, and dog! I would set aside all my chores at 10 p.m. for a half an hour and just write.

I told my wife about my declaration, because that's how they work, and she did everything she could to help me cut down on my chores for the night, God bless her. All I had to do was put Ben to bed at his usual time, between 9 and 9:30, and I'd be set to get started.

So naturally Ben developed a mild cough and wet himself three times in a row, then refused to stay asleep when I put him in his crib, then passed out, then woke up again, then sucked down his third bottle of the night and drowsily threw himself upside-down in my lap in some non-Euclidean baby sleeping position that led to me half-lowering, half-plonking him into his crib, whereupon he tossed a bit before he gave up and passed out at the stroke of 10:30.

Now it's 10:45, and I'm finishing up this post to tell you, Dear Reader, that it is never wise to leave an infant out of your calculations, especially when he is sleeping on your chest.

Fifteen minutes to go. Onward! Upward! And stay asleep little buddy!

Tuesday, July 8, 2014

On Trying New Writing Things Forever

This blog post is procrastination. I am supposed to be writing a novel; specifically I am supposed to be writing the second draft of a novel. To do that I am supposed to be reviewing and revising the first draft to see what bits I can keep, going over my character, location and plot notes to flesh things out, and sketching out background, timeline and geography notes to try and make everything fit together. To do that I am supposed to be collecting notes and snippets strewn across three different formats of writing project into one cohesive whole I can look at without going stark raving mad.

This blog post accomplishes none of those things. But I need to confess. I'm a sinner!

I started the current novel... dear God, is it a year and a half ago? For NaNoWriMo, getting an idea down that had floated in and out of my head for awhile. I succeeded in that and finished a first draft. So far all well and good.

But editing, man, like, whoa. It's staring into the maw of insanity and knowing you created utter chaos, and furthermore that you won't get your dessert until you clean this shit up. And dessert is sopaipillas. That's a dessert worth eating.

I had a first draft, but I didn't have a fucking novel. So I had to fill things in. Character. Notes. Backstory. Cut the shit plot, add new plot. I lost two months trying to sort out geography because I had a plot that demanded my main character walk from one side of this forest-covered island to the other, and I didn't know if he would make it or how long it would take him. Two months.

Fucking mountains, how do they work?
And then, inevitably, I fucked up. You know, more.

I listen to Writing Excuses, which is normally a great source of inspiration and comfort to the writer. Not this time, though. This time the topic was story bibles. Howard Tayler and Brandon Sanderson swear by maintaining a wiki as a story bible. These are writers who write a super-long-running webcomic and a ridiculous amount of epic fantasies, respectively.

I'm writing an epic fantasy. First in a trilogy. And I'm currently up shit creek in my revision precisely because I do not know the details that are necessary to make this book hold together. Clearly I need my own story bible!

Now, all evidence to the contrary, I'm not a complete idiot. I'd done the first draft in Scrivener and I was creating a fairly competent note pool in that project. But I was running into a couple of problems with that, the first being that keeping a story bible in the same project as the actual story would fuck my reuse for the next two planned books. The second being that I'd been importing images into the faux bible like mad and it had bloated the project files to unmanageable levels.

A wiki sounded like the special sauce I needed. I would update it as needed and have a handy reference ready anytime I had to look for some valuable information. What could go wrong?

For starters, I work cross platform. I need wiki software that just works no matter what I'm writing on. That means an online solution 9 times out of 10, but because wikis are supposed to be collaborative, most of the ones freely available are public and can't be set to private. That's not suitable for a story bible for maybe a thousand different reasons.

Wikispaces was an ideal solution because it was free and it didn't require you to make your first wiki public. So I settled on that and took the time to import my story bible into the wiki. Cue: massive amounts of reformatting, because wikis don't generally do WYSIWYG cutting and pasting from a Rich Text document. But I did it, I got the story bible uploaded and I got to work and I actually made some progress...

...annnd I lost access to the wiki.

Eventually I got access back but I was all like "Screw that! Local storage for life!" And cross-platform wikis that work locally are not easy to come by, let me tell you. But there is one, and it is called TiddlyWiki and it is a pretty neat little bit of HTML and Javascript running a one file wiki, which I urge you to check out for the sheer geek factor.

I didn't like the interface, but my options were severely limited at this point so I gave it a go. And I imported all my stuff into TiddlyWiki and out of Wikispaces, and I got everything nice and neat, and...

I froze.

Why? Because I'd just burned I don't know how many weeks fiddling with this bullshit and I didn't know what to do now. Any momentum I had in the main text was long gone and I hadn't written any significant new background material. And the TiddlyWiki interface was really getting to me. Cool factor aside, my brain locked up any time I opened the damn wiki to add something to it.

Also, fun fact? Wikis demand a lot of cross-linking. Great way to waste valuable writing time.

Eventually I just started jotting down all my notes long hand, vowing to type them up into Da Bible later. Then I even dropped that pretense, and popped the notes into - you guessed it - Scrivener whenever I felt it necessary. After awhile I looked at the TiddlyWiki again, checked for an update, and found out the devs had done a complete overhaul that would blow my wiki away if I tried to use it.

Finding out that I'd locked myself into an obsolete piece of software that hurt my brain and took way too much time to use was the final straw. The final hay bale, really. I started a new Scrivener project, dumped the notes I thought were important into it, and moved on. Or so I thought.

I am now at a point where I want to review my new notes and my old notes, my original draft and the new text. And I can't wrap my ahead around the different places that stuff is stored now. Online wiki, local wiki, two or more Scrivener projects and probably a few Word documents haunting my workspace.

I know I need to take time and get everything lined up so I can look at. And what does that mean? More time not writing.

It's a little hard not to be demoralized. But! The book continues to demand release and I'm not giving up on it anytime soon, even if I have to wade through a mountain of discarded Moleskines and Post-It notes.

So what have I learned? First, don't chase fads, at least not for a major project. A wiki might work for Tayler and Sanderson, and it was worth trying, but not on an already-troubled novel. Just, no.

Second, don't chase fads, period. There's always some new tool or software that will make your writing go so much easier ohmyGOSH! It won't. Which is to say it might, but you can't make that determination in less than a year and you have other things to work on. Try stuff out, but don't waste a lot of your time on anything less than brilliant.

Third, for the love of God practice prewriting and organizing and the other things that NaNoWriMo overlooks. Especially the organizing piece. Get yourself a comfortable project layout and workflow, one that won't bother you when you're banging your head against a desk working on the actual book. The less extraneous things stressing you out the better.

And now I have to go pass out so I can tackle these damn notes in the morning. Again.

Tuesday, June 17, 2014

In Reluctant Defense of Ubisoft

I really don't want to write this blog post.

I don't like Ubisoft all that much. uPlay annoys me. The last Assassin's Creed game I played was III, and I didn't finish it. Didn't finish Far Cry 3, either, though that was solely because my wife and I spawned a tiny Overlord and I dawdled on side quests. I'm not likely to play anything they put out in the next few years unless they make a massive push on the 3DS.

And Ubisoft fucked up. No question there. But my day job is developing software and, God help me, I'm sympathetic by nature to a coder on a deadline getting yelled at for leaving out That One Feature. So brace yourselves, here we go...

In case you're not familiar, it came out during E3 that Ubisoft had left playable women out of the multiplayer modes for both of their upcoming big franchise games, Assassin's Creed and Far Cry. They wanted to include women in the games - Scout's honor! - but didn't have the resources to pull it off in time. This excuse has understandably pissed a lot of people off, much moreso with Assassin's Creed because the last few games have included multiplayer modes that did have multiple female characters.

And I get it, and I'd jump on the bandwagon except I see a lot of people saying that the developers are being "lazy", or that they just don't care about female gamers. Which is not, I think, the reason to be pissed off.

Beyond Good and Evil 2 is apparently a reason to be pissed off.
 Let's be clear right off the bat: both multiplayer features at issue here are cooperative, meaning they're part of the single player experience. (Assassin's Creed's earlier, female-friendly multiplayer deathmatches got dropped entirely.) A friend, or three, can jump into your game, or you can jump into their game, and help out with single player missions that tie directly into the main storyline of the game. And all the avatars involved are, at this moment, male, and Ubisoft is being raked over the coals for not letting players play a female.

I'm seeing a lot of angry comments in the form of "This is bullshit, it's super easy to turn a male model into a female model, Ubisoft are fucking liars." And that would be true if all the new model had to do was run around killing people. But in a properly implemented coop game that's not the case anymore, because Bioshock Infinite is a thing that happened.

You can't top this!
Your buddy has to support you, has to be able to team-kill with you, has to hand off items and witty repartee as you mow down the enemy A.I.s. If Plot happens, your buddy is no longer allowed to vanish, they have to contribute to the Plot, have to have lines, make a meaningful impact on events, or at least not fuck up verisimilitude by disappearing into the Aether.

And if you want your buddy to be male or female, that really does double the workload. You have to hire an extra voice actor, you have to write and record new dialogue, you have to animate new body language, new facial expressions. And all of that shit has to be added to the test cases, along with what happens if maybe you have two different buddies at different times who want to play different genders. How many ways, at how many different points, can that completely break the million-dollar title that's due out in a few months? Because they add up.

Oh God, take off the turban! Take off the turban!
"Bioware does this all the time", you say. Yes, they do, with blank-slate characters that represent the player and her choices. They don't do it with characters that have distinct personalities that make their own impact on the plot. Ask Bioware if you can pick the genders of every member of your supporting cast as well, and see how long it takes them to descent into apoplexy.

I am ready to be corrected on this point, but I cannot think of a game that implements a plot-relevant gender-swappable coop character with a distinct personality. The closest I can come to what people are demanding is Gears of War 3, and that isn't close at all - you could only choose a female character when the plot made them available, and if everyone wanted to play a woman, tough shit. Or there's the latest Resident Evil games, where you choose between a well-developed male or female character, but your buddy had to be the other gender and nobody got to customize anything.

Not an option, sadly.
And yes, I'm crediting Ubisoft that they're implementing cooperative gameplay that's closely tied into the story. That's because these are next-generation games adding cooperative gameplay to game storylines that are traditionally strongly character-focused: no blank slates. If Ubisoft is just doing another implementation of the Amazing Disappearing Coop Buddy who fucks off whenever anything storyline relevant happens, then the resource excuse really does not hold up at all.

See, I'm not trying to exonerate Ubisoft as a company here, because if they delayed the game or management had made gender diversity a priority from day one they could have gotten this done. I just don't like seeing people blaming the dev team for this fuckup. They're coders and artists under the deadline gun for a multimillion dollar title running on a brand new engine on brand new hardware and working in an industry where employees are routinely getting laid off en masse. For Assassin's Creed, you just have to look at the Clone Quadruplet Assassins they did put in to see that something went badly wrong during development that limited them to one playable character model for the entire game. And on top of all that, every interview I've seen with the developers suggests that they loved the idea and they're genuinely disappointed they couldn't get the job done.

Which is another thing: Ubisoft hasn't been great at having female protagonists, but they've been pretty consistent in including strong female characters in their games. Compared to Call of Duty's complete lack of women, or characters like Quiet and whoever the hell this Zelda villain is, Assassin's Creed has been downright progressive for years. So I'm a bit disappointed that Ubisoft's catching more hell for trying to do the right thing and failing than companies that didn't bother to try and address the issue at all.

You know what you did, Team Ninja.
With all that said... I'm not going to say lay off Ubisoft. At a minimum they've mis-prioritized a feature gamers obviously wanted (and not just female gamers, I like playing as a woman sometimes myself), shitcanned it rather than delay the game just long enough to get it right, and committed a massive P.R. fuckup all around. Even if they're telling the absolute truth, it's moronic to say that you were five minutes away from putting in a feature and just didn't quite make it. Jim Sterling skewers them heavily here, to the point where I can't believe Ubisoft is lying about what happened - they'd have been far better off just saying nothing at all.

So please, scream and yell and tweet and write letters demanding playable women, because it's a thing that should happen and if it's not in the next Assassin's Creed and Far Cry games then Ubisoft deserves everything it has coming.

Just give the devs in the trenches a bit of a break, mmkay? Or at least the benefit of the doubt.