September 27, 2018 / 1 Comment

Elementary

            Many thanks to all of you who tossed some new topic ideas at me (here and on Twitter).  I think this might fill up all the slots I had for the rest of the year.  I may even take some time to rethink my upcoming plans.

            Anyway, for now, the potential Sherlock Holmes idea stuck in my head, so let me babble about that for a minute or three.

            There’s a pair of terms that have been floating around for a bit now—Watsonian and Doylist.  On the off chance you don’t get the reference, the terms come from Dr. John (or Joan) Watson, constant companion to Sherlock Holmes, and also to their creator, Sir Arthur Conan Doyle.  When we use these terms, we’re saying there’s two ways to look at any story element.  The in-story reason for this happening, and the author’s reason for this happening.  They’re often very different, but they’re both very important.

            For example…
            Why did Sherlock Holmes die in “The Final Problem,” plunging to his death at Reichenbach Falls?  Well, from Watson’s point of view, Holmes sacrificed himself because it was the only way to stop Moriarty.  The two evenly-matched men fight, and while Holmes dies, Moriarty’s now-leaderless criminal empire will crumble.  A net win for society. 
            From Doyle’s point of view, though, he was just sick of writing Sherlock Holmes stories.  He was making money off them, yeah, but he wanted to move on and start writing more serious, important stuff about, well… ghosts and fairies.  No, seriously.  So he killed Holmes off and tried (unsuccessfully) to move on.
            Yeah, don’t be the person pointing out Doyle later retconned the death.  When he wrote this story, Holmes was dead.  Toast.  Joined the choir invisible.
            Of course, this principal doesn’t just apply to Sherlock Holmes stories.  If you look at most stories, the elements break down into these two categories.
            –Whydid Han Solo get frozen in carbonite?  The Watsonian reason is that Vader wanted to test the carbon-freezing process and Boba Fett wanted to collect on Solo’s sizeable bounty.  The Doylist reason is that Harrison Ford wasn’t sure he wanted to come back to play Solo again, so George Lucas needed an ending that could explain Solo’s potential absence but also contain the possibility of bringing him back.
            –Whydid the Twelfth Doctor regenerate?  Watsonian reason—he was shot by the Cybermen and managed to hold off his regeneration briefly before transforming into the Thirteenth Doctor.  Doylist—Peter Capaldi was leaving the series, as was showrunner Stephen Moffat, and the new team decided to cast Jodie Whittaker.
            Here’s one of my own—Whydoes Ex-Patriots begin with a Fourth of July fireworks show?  Well, from a Watsonian point of view, the citizens of the Mount are celebrating.  It’s the Fourth, but it’s also one of their first major holidays since things have (for them) kinda stabilized after the zombocalypse.  So they’re partying hard.
            From a Doylist point of view, though… this opening lets me start with action.  There’s a lot going on.  It gives me a chance to re-introduce our four main heroes. It also lets be immediately bring up the idea of nations and patriotism, which are key themes in the book.  Heck, because this was one of those very rare times where I knewthere’d be another book in the series, this was also a setup for a plot thread in Ex-Communication.
            This all makes sense, yes?
            Why are we talking about it?
            I think it’s really important to remember these distinctions when we’re talking about writing.  To be more specific, when we’re talking about aspects of writing.  If we’re discussing dialogue or characters or settings, we should be clear if this is an in-world discussion or an authorial discussion.  Are we talking about things as they relate to the characters, or as they relate to the author (and the audience)?
            “Authorial”?   Ooooh, don’t I sound all clever…
            For example, once or thrice I’ve mentioned my belief that all good, successful characters have three common traits—they’re believable, they’re relatable, and they’re likable.  But I’ve seen some pushback on this.  I’ve had people online and in person argue that characters don’t need to be likable.  Characters just need to be fascinating or compelling or… well, look.  They don’t need to be likable.
            Here’s the thing.  In a Watsonian sense—I agree with this.  I mean, I’ve said this myself lots of times (pretty much every time I talk about these traits).  Likable doesn’t mean we want a character to marry into our family and they always have a kind word to say.  Within the story, there are tons of popular protagonists who aren’t remotely likable.  Who are kind of awful, really.  There’s not a version of Hannibal Lecter—books, movies, or television—that most of us would want to have a private dinner with.  We probably couldn’t count the number of books and movies that have hit men or assassins as their main characters.  And to bring us back around, most modern interpretations of Sherlock Holmes rightly point out that the guy’s an abrasive, condescending ass. 
            (…and that’s with the people he likes.)
            But in a Doylist sense, viewed from outside… we kinda like these people.  We admire Lecter’s twisted ethics.  We envy the ultra-competent man or woman of action.  And it’s kind of pleasant to watch Holmes point out what’s sitting right in front of everyone’s face.  That separation of fiction, the thin sheath that keeps us from absolutely immersing into the story, lets us enjoy these characters in ways we couldn’t in real life.
            I mean if we didn’t like them as readers, why would we keep reading about them?  Who’d torture themselves like that.  Hell, why would we keep writingabout them if we didn’t like them?  I can’t imagine sitting down and working for months on a story about a character I didn’t enjoy on some level.

            This holds for so a lot of aspects of writing.  I’ve mentioned before that realistic dialogue in fiction is different from the actual conversations we have with each other in the real world.  Other characters might not get my protagonist, but the reader should be able to relate to them.  And I’m never going to be able build any sort of tension if I don’t understand the difference between what my readers know and what my character knows.

            Y’see, Timmy, when I’m taking in advice I need to be clear if we’re talking about things in a Watsonian or Doylist sense.  And when I see advice from other writers, I should stop and think about how they mean it.  Are they talking about the actual pace of events in the timeline of the story, or the pacing in the narrative?  Are they talking about the motives of the characters or the writer?
            In the future, I’m going to try to be better about this, too.
            Next time…
            Well, thanks to some of you, I’ve got next time all planed out in advance.
            Until then… go write.
February 6, 2018 / 1 Comment

Help From the Internet

A random thought…

Well, not that random.

The other day I made a smart-ass response to a friend’s Twitter comment about different online writing aids and apps. There’s a bunch of them out there these days. Some of them highly publicized. My comment was… snarkily negative. Let’s leave it at that.

I know. Snarkiness with friends. What has the internet come to? It’s all downhill from here.

Anyway, it did get me thinking about these different sites a bit. I mean, a good writer wants to use all the tools available, right? Is this just me inching ever-closer to cranky old manhood?

I don’t think so.

Okay, first off, let’s not even talk about the information side of this. If someone wants to hand over a bunch of their intellectual property to a random website and feels completely confident they’ve read and understood every single line of the terms of service… that’s up to them. We’ll leave that discussion for others.

I want to blather on about how useful these sites are, both short-term and long-term.

So… let’s talk machines.

(I feel hundreds of fingers poised over keyboards, ready to lunge at the comments section…)

The most common computer tool we’re going to encounter is a spellchecker. Pretty much every word processor has one.  Lots of websites do, too. Blog sites like this one, Twitter, Facebook—they’ve all got some basic spellcheck capacity.

That’s the important bit. Basic. The absolute best spellcheckers are, if I had to put a number to it, correct maybe 97-98% of the time. Don’t quote figures at me—I’m saying right up front that’s just based off my own experience. These are the spellcheckers we usually find in the word processors. The online ones… I’d drop it down into the 88-90% range. Maybe even a tiny bit lower.

What does this mean? Well, there are words that have accepted alternate spellings, but a spellchecker will say they’re wrong. There are also lots of common words—especially for genre writers—that won’t be included. I was surprised to discover cyborg wasn’t included in my spellchecker’s vocabulary. Or Cthulhu. Okay, not  quite as surprised on that one, but still…

Keep in mind, spelling is a basic, quantfiable aspect of writing. We can say, no question, whether or not I’ve spelled quantifiable correctly in that last sentence (I didn’t). That’s a hard fact (and, credit where credit is due, the spellchecker kept insisting we needed to change it).

Also—a spellchecker doesn’t know what word I meant to use.  It can only tell me about the word on the page. Or the closest correctly-spelled word to that word on the page.  Maybe it’s the one I wanted, maybe not. At this point it’s up to me to know if that’s the right word or not. And if I don’t know… well, things aren’t looking good for my manuscript.

Consider all the things I just said. The gaps. The problems. The rate of accuracy. And this is with the easiest aspect of writing. Spelling is a yes or no thing. It’s right or it isn’t. This is something a computer should excel at… and the online ones are getting a B+ at best.

How accurate do you think an online grammar program is?

Grammar’s a lot more complex than spelling. Spelling’s just a basic yes or no, but grammar has a ton of conditionals. Plus, in fiction, we bend and break the rules of grammar a lot. I tend to use a lot of sentence fragments because I like the punch they give. A friend of mine uses long, complex sentences that can border on being run-ons. I know a few people who remove or add commas to help the dramatic flow of a sentence.

And hell… dialogue? Dialogue’s a mess when it comes to grammar. A big, organic mess. Fragments, mismatched tenses, mismatched numbers, so many dangly bits…  And it needs to be. That’s how we talk. Like I’ve mentioned in the past, dialogue that uses perfect grammar sounds flat and unnatural.

Think about this. I’ve talked before about Watson, the massive supercomputer that was specifically designed by MIT to understand human speech… and still had a pretty iffy success rate. Around 72% if my math is right. And it might not be–I’m not a mathematician, after all.

D’you think the people who made that grammar website put in the time and work that was put into Watson?

So, again… how accurate is that online grammar program going to be?

More to the point, how useful is it going to be as a tool? Would you pay for a DVR that only records 3/4 of the shows you tell it to? Do you want a phone that drops one out of every four calls?

Now, I’d never say there’s no use for these tools or sites. But it’s very important to understand they’re not going to do the job for me. They’re the idiot writing partner who’d really good at one thing, so I kinda need to keep both eyes on them when they’re set loose to do… well, that thing. I need to know how to spell words and what they mean. I still need to know the rules of grammar—even moreso if I plan on breaking them.

See, that’s the long-term problem. Assuming this professional writing thing is my long-term goal, at some point I need to learn spelling and grammar. If I’m going to keep depending on someone (or something) else to do the work for me… when am I going to learn how to do the work?

Y’see, Timmy, these programs and apps are kinda like alcohol. They won’t make up for a lack of knowledge. They’ll just emphasize it. I definitely don’t want to be dependent on them. At best, if I know what I’m doing and I’m careful (and use them in moderation), they might make things a little more smooth and painless.

Next, a quick screenwriting tip.

Until then, go write.

You go write. Not your computer.

Go on…  go write.

October 3, 2013 / 3 Comments

Do You Need Mechanical Assistance?

Your minds always go there first, don’t they.  You bunch of perverts…

Some of you may remember Watson, the supercomputer that played against two Jeopardy champions and beat them. Watson was specifically built to understand human language. That was the sole point of its appearance on Jeopardy—to show that a machine could be programmed to understand subtext and clues and irony well enough that it could compete against humans using their rules.

Why am I talking about a supercomputer—a fantastic and kick-ass supercomputer, granted—when I keep insisting this place is about writing?

Do you know how big Watson is? Or how long it took to build? How many people were involved? Watson was a six year project for a team of more than twenty engineers and programmers (plus a ton of students interning with IBM). It’s a collection of processors and drives as big as my first apartment in Los Angeles (which means it’s probably the size of your kitchen).

And you know what? Even with all that computing power and information, Watson still got things wrong. Several times in warm up games and even during the main event, Watson would miss obvious clues and give the most bizarre answers. If you run the numbers, Watson didn’t know how to answer a given question almost twenty percent of the time. When it did answer, it still got one out of every ten questions wrong.

Now, again, please remember what I just said how long all those people worked on this machine. A machine that was built for the specific purpose of understanding human language. That’s going to be important when I ask my next question.

How much work do you think went into your computer’s word processor?

For that matter, how much went into just its spellchecker? Or into that automated proofreader? Do you think the people programming it were IBM-level experts in their field? And in the field of writing?

I’m not going to be a hypocrite and say these things are useless tools.  I use my spellchecker.  I usually make a pass with it during my third draft.  There’s nothing wrong with using it as a tool to help me check spelling.  But I have no illusions about the fact that I still need to be the one checking the spelling.

See, I don’t blindly accept every “correction” it offers me.  And this isn’t my entire third draft.  I still go through the whole manuscript line by line, sentence by sentence.  It can take me four or five days.  Because I know the  machine can’t be trusted to do it for me.

I’ve said it before, and I’ll keep saying it until people listen.  A computer cannot write for me.  It doesn’t matter how cool someone’s system is, it won’t do the job.  That’s why, whenever you ask a real writer for advice, they’ll usually say to hire a good editor, not to upgrade your software.

If I want to be a writer—a working, paid writer–I need to know how to spell and how to use words and what those words mean.

These words, for example.

fair and fare –one of these is how you get through an experience

dual and duel—one of these refers to citizenship

vain and vein – one of these refers to similar things

tics and ticks – one of these is a twitch

mute and moot –one of these is irrelevant

reckless and wreckless—one of these means rash

vain and vane – one of these makes you think this song is about you

desert and dessert—one of these has whipped cream

shudder and shutter – one of these means to shake

soar and sore—one of these relates to diseases

vane and vein—one of these shows the flow of air or liquid

wreck and wreak—one of these means to inflict

wait and weight – seriously, it’s embarrassing I have to ask.

As in the past, these are all mistakes I’ve seen in articles or books over the past few months.  When I come across one and it makes me shudder (not shutter), I know I have to add it to the list.  Yeah, I keep a list.  You don’t think I just come up with all this stuff from scratch once a week, do you?

In the interest of fairness… Two of these are mistakes I’ve made in the recent past.  One of them even slipped past me, my proofreaders, my editor, the copyeditor, and then me again while I looked over copyedits and layouts.

Did you know all of the answers?  Did you know what the other word meant, too?  If I don’t know them both (know—not sort of recognize) there’s a good chance I’ll make a mistake at some point.  And, granted, we all make mistakes sometimes.

But some people make a lot of mistakes.  And they don’t catch any of them.  Because they’re depending on their computer to do it for them.

Next time, I want to…

Actually, before I talk about next time, I’d like to break my rule about no self-promotion and guide you to the Kaiju Rising Kickstarter.  It’s a giant monster anthology featuring stories from folks like Peter Stenson, Timothy Long, Larry Correia, and a bunch of others (including me).  It’s already fully funded (even stretch goals), but there’s still a day or two left to snag a copy for yourself, and possibly a pile of add-ons.

Anyway, that being said…

Next time, I want to talk about exceptions.

Until then, go write.

Categories