April 27, 2018 / 11 Comments

Workhorses

            Very sorry for the delay. Taxes.  Jury Duty.  Making the New York Times bestsellers list with Paradox Bound.  And that’s just what I can talk about.  The past two weeks have been kind of crazy, and last Thursday was when it all caught up with me.  Well, Wednesday night, to be honest.
            But now that I’ve got my excuses out of the way…
            (did I mention the New York Times bit…?)
            I stumbled across an interview I did with author Jessica Meigs a few years back.  I said something that sounded vaguely profound.  Or, at least something I was trying to make sound profound…

            “I think people like radical new ideas, but sometimes—most of the time, honestly—they just want the basics. There’s only so many times you can go out and have a mesquite-smoked sirloin patty garnished with goat cheese and pine nuts on a croissant. It’s cool, but eventually you just want to have a cheeseburger.”
            If it sounds vaguely familiar, Stephen King’s said something similar a few times.  I think I may have been subconsciously mimicking him.  Plus, I’ve used cooking metaphorshere a few times.  Hopefully it’s not too obscure or vague as metaphors go.
            Now, I don’t watch a lot of cooking shows (used to love Kitchen Nightmares), but I’ve never heard anyone make the argument that we should all eat nothing but gourmet food.  I can imagine how much we’d all scoff at someone who campaigned to ban cheeseburgers.  And if anyone tried to tell me I’m a crappy cook because I don’t make my own pizza dough from scratch, I’d probably laugh in their face. And then not invite them over for pizza.
            But…
            Every couple of months I’ll see some new article about how aspiring writers should use better words. Better descriptions.  Better structures.  Only uneducated simpletons and talentless hacks would use verbs like said or was. You used redinstead of encarmine?  It’s cute that you’re trying to write for grade schoolers…
            None of this is true, of course.  And I can’t help but notice that the vast majority of people who make these declarations… well, they don’t tend to sell a lot of books.  In fact, I’d guess the majority of them aren’t even professional writers. Or even amateur writers.
            It keeps coming up, though. And aspiring writers keep trying to follow it.  And often they end up in this horrible downward spiral, progressing less and less as they try to make every sentence “better.”
            Possibly weird aside.  But it has a point.  Honest.
            There’s a type of riddle that often stumps people—the one with the obvious answer.  Those ones where we stop and think and think because the answer can’t be that simple.  I mean, isn’t the whole point of a riddle to trick you into giving the wrong answer?  So even if the simple answer fits all the requirements of the question, people will convince themselves it’s got to be something more complex and spend who knows how long trying to figure out what that unnecessarily complex answer must be
            When I’m telling a story, there’s going to be lots of times that call for simplicity over complexity.  It’s not uncommon for a short, straightforward sentence to have far more impact than a far more elaborately-crafted one.  A simple structure can be a faster, much more enjoyable read for my audience than a twisting, interwoven one.  And a basic character motivation is going to be much easier for my readers to grasp and relate to than one that needs thirty pages to explain.
            Let me mention two or three basic, solid writing devices that get a bad rap.
            It was/ he was/ she was—If I’m writing in third person, past tense (it’s not as dominant as it used to be, but I think it’s still the most common type of narration you’re going to stumble across), I’ll be coming across this form of “be” a lot.  If I’m leaning toward present tense—and that’s okay, a lot of the cool kids are doing it—I’ll probably see isjust as often.
            There are times was can be the sign of some needed work. Whenever I edit I tend to do a was pass and see how often I can turn things like “Wakko was running” into “Wakko ran.”  But sometimes, after all that running, I might just have “He was exhausted.”  Sure I could be a lot more descriptive and evocative, but there’s also going to be points where “He was exhausted” is quick, gets the information across, and lets me move on to other things.
            Said—The most basic dialogue descriptor there is.  Said is a classic. Quite literally.  People have been using said for almost a thousand years.  And it’s still around and still in regular use.
            I’ve talked about said a few times in the past, so I won’t go into too much here.  I just want to remind you that one of my first face-to-face interactions with an actual, book-buying, money-paying editor was him telling me to get rid of the dozens of different descriptors I was using on every page and replace 95% of them with said.  Let it do all the heavy lifting and save the special words for special occasions.
            Linear Structure—I also talked about this just a few months ago.  It’s very common for linear structure and narrative structure to run side by side.  It’s so common  because it’s the way we’re used to experiencing things.  Our brains are pretty much  programmed to accept stories this way, and if we’re given them in other ways we’ll try to mentally wrestle them into this format.
            Now, personally, I love a story that uses clever structure or devices to move the plot along.  I think most people do. That’s kind of the trick though—I’m using them to move the plot along.  If I have dozens of flashbacks that don’t really accomplish anything, or running the story backwards just because it sounded like a cool idea, I’m just making the story more complex for no reason.  And once my convoluted structure breaks the flow for the third or fourth time, well…
            Again, something like 85-90% of all fiction (numbers pulled from experienced ether) is going to have this very straightforward format.  There’s nothing wrong with it.  I shouldn’t be nervous about just… telling my story. 
            Y’see, Timmy, there’s nothing wrong with simplicity.  Nothing’s inherently good just because of overly-complex structure or incredibly obscure vocabulary.  My writing isn’t automatically better because I decided to use four syllable words rather than two syllable ones.
            And to be very clear—I’m not saying there’s anything wrong with complexity either.  Nothing at all.  There are some wonderfully complex books out there.  It’s when I insist that everything has to be one or the other that problems arise.
            Okay, that’s a lie.  Problems arise all the time.  Hell, I could shut this blog down if that was the only time problems arose…
            My point is, if I insist that everything has to be exquisitely crafted, impenetrably structured, polysyllabic sentences that run on for pages, collected in an order that would stump most cryptography software… my writing’s probably going to be very hard for most people to get into.  It’s going to be tough for it to have any kind of flow.  And it’s going to take me a very, very long time to get that first book done.
            And that means it’s going to be tough for me to have a lot of readers.
            Anyway… I’m going to go watch Infinity War now.
            Next time, enough about workhorses.  Let’s talk about cats and dogs.
            Until then… go write.
April 5, 2018 / 6 Comments

Anneal Spilling Post

            Oh, get your mind out of the gutter.  It has to do with strengthening metal and glass. Which kinda illustrates the point I wanted to make…

            Well, you know what I haven’t talked about in a while?  Spelling!  Sure, it comes up a lot in random posts, but I wanted to focus on it for a moment.
            However, I didn’t want to just shout at you not to depend on your spellchecker.  I’ve done that plenty of times.  For now, I wanted to talk specifically about misusing words–valid, correctly-spelled words and the problems this creates for my readers.
            What’s that?  How can it be a problem if I’m using wards that are spilled the write way? Wall, here’s the think.  While spell-chick well ignore these worms—because all if then art correctly smelled—a person won’t.  Their going two peck up on each won, even if there pretty close too what I indented, and they’ll stubble wile they reed.
            And, sure, it’s easy to laugh off sentences or examples like the ones above because the rhythm of the sentence is still there.  It only takes a moment for my mind to adjust and then I’m reading just as fast as I would normally.  Understanding the actual meaning, too.
            But it only takes a small slip of a finger to type closet when I meany closed, and that’s a pretty big break.  It reads different and sounds different in my head.  Like how you stumbled over meany at the start of this paragraph when it should’ve been meant. A ridiculously simple typo that spellcheckers will just wave past, but it derails the reading experience.
            Here’s a couple of misused words I’ve collected over the past few months, in no particular order. These are words that were misused by journalists, politicians, even a copyeditor.  Plus the words they meant to use.  I think.
milk-toast vs. milquetoast
effect vs. affect
affects vs. effects
horde vs. hoard
hawk vs. hock
shotty vs. shoddy
peel vs. peal
peek vs. peak
peak vs. pique
heroin vs. heroine
cite vs.  site
desert vs. dessert
            I’ve seen people make a lot of excuses for this sort of thing in their manuscripts or articles.  Readers will get it from context.  The story is strong enough to cover for things like vocabulary.  An editor will fix it when it gets published.  Heck, one person shrugged it off and said “I’m just happy someone’s reading it.”
            Reading for how long, though?  Every time I have one of these, my reader is knocked out of enjoying my story and needs to figure out what the hell I’m trying to say, and that means I’ve killed the flow. It’ll create confusion as it guides the reader’s thoughts down the wrong paths and possibly shift the tone… creating more confusion.  Look at heroin or heroine.  If I plan on having my protagonist do one of these all weekend… well, I really need to be sure which one I want to use.  Those are two verydifferent weekends, and each one’s going to make my reader view the protagonist in a certain way.
            Y’see, Timmy, this is why I need to know more than my spellchecker.  If I mess up, I’d guess 99% of the time it’s going to suggest a word.  And that suggested word will always be spelled correctly.
            But… it isn’t necessarily the word I meant to use.  Just off my own experience, I’d guess at least one out of four times it’s the wrong word. Maybe as high as one out of three.  If I’m just glazing over and automatically tapping change, I’m going to end up with a lot of mistakes. 
            And if I don’t know if the new word is a mistake or not… well…
            I probably won’t need to worry about an editor fixing it when it gets published. 
            Next time, I’d like to share this little idea I had about how active my plot and story should be.
            Until then… go rite.
June 8, 2017 / 2 Comments

If You Can’t Say Something Nice…

            I wanted to prattle on for a minute about a part of dialogue we ignore a lot. The unspoken part, so to speak.  Well, not so to speak.  Literally, the unspoken part.
            Wait… can something be literally unspoken in prose?
            Anyway, as I so often do… I’d like to tell you a little story.
            I was working on a movie once which had a pretty standard romantic subplot. Estranged husband and wife, pushed apart by work (he wants to stay small town, she wants to go national), and now brought back together again during a crisis.  Like so many of the lower-budget things I tended to be on, we ended up running short on time. The place they decided to tighten things up was in the reconciliation/we-still-love-each-other scene.  You know that scene, right? It’s in a bunch of stories and a lot of movies.
            The director and the two actors huddled together and started talking about how they could trim the page and a half scene without, y’know, ruining it. Were there phrases that could be combined? Maybe words that could be swapped out for… shorter words?
            At which point the lead actor suggested… “What if we didn’t say anything?”
            Which is what’s in the final movie.  You can watch it and see the one minute, one-shot scene. The two of the working together in the lab, falling right back into old habits, giving each other little appreciative glances…
            And never saying a word.
            Some folks are intent on picking “better” words and elaborate. meticulous phrasing. That gets spread as kind of a gospel.  We’ve all seen it—the people who’ll never use five words if it can be said in ten.  If there’s a longer, more roundabout way to talk about something, they’ll find it.
            But I don’t need to do this.  I’ve talked about the “less is more” idea a few times here.  A fair amount of the time I can do just as much (or more) with just a few words.  Subtext can get a point across so much stronger than the spoken (or shouted) word, and sometimes that subtext doesn’t even need dialogue.
            I know this sounds kinda weird and contradictory. I think I’ve said here two or three or forty-four times that dialogue is one of the key ways we show character, so it just feels unnatural to have characters not say anything.  Especially when there are so many cool lines and comebacks tingling on our fingertips.
            Let’s consider it, though.  How often can a grim silence have so much more impact than the longest, most detailed monologue?  Think about how flirty someone can be with just the right gesture or look.  There’s whole schools of comedy based around the idea of an awkward silence.
            And this is going to be harder to write.  I won’t lie to you.. Depending on unspoken subtext means I need to have my descriptions perfect—not one extra adverb or adjective cluttering them up and slowing them down.  It means I need to have a great sense of empathy—that I know exactly how this moment will be interpreted by everyone who reads it, and not just by a few of my friends.
            Y’see, Timmy, this kind of subtlety is what makes my writing soar.  It’s how I bring my story to life and raise it up to the next level.  I want to recognize the chance to say nothing–to use that delicate balance of silence and description and subtext–and take advantage of it.
            Or, as K.M.Weiland once put it—“Never miss a good opportunity to shut up.”
            Next time, I wanted to discuss some basic geometry.  We haven’t done that in a while.
            Until then… go write.
March 23, 2017

Sentence DNA

            Okay, so, a few weeks back (before the amazing ten year anniversary) I said I’d blab on a bit about words.  That time has finally come.
            Be ascared. Be very ascared.
            Anyway…
            It’s been a while, so I figured I’d bring up spelling again.  I’m sure it seems silly that I keep revisiting this topic again and again.  But there’s a reason for it.  Words are the absolute core of what we do as writers, the bare-bones building blocks.  They’re the DNA of storytelling, the atoms to my sentence molecules.
            I musthave a solid, working vocabulary if I want to be a writer. No question, no excuses.  I need to know what words mean.  I have to know how to spell them.  I have to be able to tell them apart.
            That last one’s a killer.  We’ve all seen people go on about there/they’re/their and of course about its and it’s.  But I’ve seen folks mess up corporealand corpulent. I’ve seen major websites confuse possible and posable.
            Granted, ninety-five percent of the people making these mistakes aren’t claiming to be writers.  They’re just folks trying to express their thoughts online.  This isn’t their field of specialty.  As I’ve pointed out before, I can cook, but I’m not a chef.  I can do an oil change and rotate my tires, but I’m no mechanic.  And I don’t think the folks at my garage would look down at me for not being able to tell a carburetor and a fuel pump apart on sight.
            But…
            I’d probably look down on them if they couldn’t tell the two apart.  I’d eye all their work and claims with a bit of skepticism.  Truth is, I probably wouldn’t trust them with my car anymore. It’s the kind of ignorance that calls all their work into question.
            That’s why spelling is so important for writers.  It’s one of the first benchmarks we need to pass—one of the first indicators that we know what we’re doing.  I can’t tell you how many times, as a contest reader, I would start judging a screenplay because it had two or three misspelled or misused words in the first two pages.  If I hit twenty pages and there were more than ten typos…  Well, even when I wasn’t supposed to judge on spelling, there’s simply no way that’s not going to color my thoughts when I hit another problem.
            And y’know what?  The scripts with spelling problems always had another problem. Always.
            I wasn’t alone in this, just in case you’re thinking I’m some hypercritical jerk who’s scared of newcomers taking his job or something (keep in mind, this was almost eight or nine years ago—nobody wanted my job back then).  A good number of readers—and editors and agents—are also writers.  Even when we’re not supposed to judge on spelling… we all kinda judge on spelling.
            Anybody who’s a professional in this word-making field will.
            That said… here’s a list of paired-up words.  They’re homophones or malonyms or just… well, screwups.  As always, all of these examples come from actual mistakes I’ve seen in the wild—in books, catalogs, and on various websites that try to claim a degree of professionalism.  Hell, one of these was in an article about how to be a better writer!
            Yeah, it’s just painful to think people messed up some of these…
mote vs. moot
conscious vs. conscience
defuse vs. diffuse
reign vs. rein
angle vs. angel
dual vs. duel
idle vs. idol
dyed vs. died
pique vs. peak
emulate vs. immolate
bawl vs. ball
jive vs. jibe
do vs. due
sleight vs. slight
rouge vs. rogue
marital vs. martial
hansom vs. handsome
don vs. dawn
gild vs. guild
turn style vs. turnstile
            Neat list, eh?

            Did you know what both words meant?  In every example?  Because, again, I need to know what words meanAll the words.  Not a pretty good idea, not a general sense of how it works, not pretty-sure-that’s-the-one-I’m-looking-for.  These are my basics, after all.  This is sugar vs. salt for a chef, or carburetor vs. fuel pump for a mechanic.  If I mess these up… well, I can’t be shocked when people stop treating me like a professional.

            Actually, if you don’t mind me running a bit long, I want to toss out something else here, too.  Another point I’ve mentioned before, but it still bears repeating.
            Sometimes, for storytelling reasons, maybe I want spelling mistakes in my work. Maybe it’s an epistolary story, or just a jutted-down note within the narrative, and the character in question isn’t supposed to be all that bright. Then it makes sense that they may not be good at spelling, yes?
            I need to be super-careful when I do this.  This is one of those things that can make me lose points with editors and writers.  Seriously.  I’ve seen both.
            D’you notice up above when I’d written jutted instead of jotted?  Not a huge mistake.  Understandable, even—U and Oare pretty close on the keyboard.
            Which means, of course, there’s a chance that’s an actual mistake, not one I added in for narrative effect.  If I see somebody mess up they’re and their, I’m left wondering if the character’s not too bright… or the author isn’t. There’s no real way to be sure.
            Compare that to when I used ascared up top. It’s not a word you’ll find in many dictionaries, but it’s a generally accepted colloquialism. It’s also (take notes now) a spelling that would raise flags for copy editors or even the dumbest of spellcheckers. And readers. We’d immediately question how such a blatant, easily caught error made it in, and the default assumption would be that I meant for it to be.
            Y’see, Timmy, I need to be smart about deliberate mistakes in my writing. It needs to be very clear they’re deliberate—screw-ups the character made, not me.  Because if they’re not sure, most readers are going to assume it’s my mistake.  And as I mentioned above, if I make too many mistakes…
            Well, again, I can’t be shocked by how people react.
            Next time…
            This is getting tough, because I’m thinking of making Tuesday posts a semi-regular thing, but they’ll probably be a bit broader and not quite as writing-specific. So “next time” won’t actually deal with writing, but it’ll still—
            Y’know what? Just keep checking back here.  It’ll be worth it.  Hopefully.
            Until then, go write.

Categories