Category: vocabulary

I think they’re making excuses. I think sometimes Art becomes an easy shield to protect a writer from criticism. If art is highly subjective in and of itself, whether or not it’s any good is very subjective. And if any of you have ever visited the internet (surprise—you’re there now) you’ve probably encountered one or two thousand people who are more than willing to explain how and why THIS is the greatest achievement of all mankind. Don’t agree? Well then you just don’t get it.

And that’s the catch. Every tale worth telling is a careful balance between plot and story. It’s the things happening outside that my characters are actively engaging in, and how these things are actively affecting and changing my characters. Key word there—active. When I upset that balance, things stop happening. Either my character stops doing things or they stop developing. Or both.

For the record, either one of these is bad. Both is just downright awful. We want active characters who grow and change. I mean… everybody gets that, right?

The other big thing in attempts to be artistic is language. Excessively elaborate descriptions using increasingly arcane vocabulary. Labyrinthine sentence structure in which one could perhaps lose a minotaur. Like, a full-size minotaur.

There’s probably something to be said for the fact that most attempts at writing art lean toward complexity over simplicity. And again, this is one of those times when defensive writers tend to whip around and say this failure is the reader’s fault. “Do you think I should lower the quality of my writing just because you got such a pathetic education you don’t know what uxorious, mytacism, or atramentous mean?”

When I’m writing my primary goal has to be that my readers understand what I’m trying to say. If they don’t understand page one, I can’t blame them for not going to page two. There are ways to make these things work, sure, but I’ve got to accept nobody’s picking up my books hoping for a vocabulary lesson or that they’ll need a spreadsheet to keep track of my spiraling plot.

Fun note. When I went looking for the most obscure adjectives I could find, one of the first results was a list titled “100 Exquisite Adjectives” (emphasis mine) which I’d guess was about 20% rare and obscure words most readers wouldn’t know. So let me just ask you… how exquisite is sallisthorian as words go? Do you think most readers would find me pretentious for describing a character that way? Is it too on the nose? If they’ve got no idea what it means, is it their fault for not knowing or my fault for using it?

Oh, and for the record, I just made up sallisthorian while writing this. I’m saying it means “like the Man-Thing” (who was, of course, known as Ted Sallis when he was human). And if anybody wants to argue about how were we supposed to know what that means… well, that’s kinda my point, isn’t it?

Thursday’s Thanksgiving and my parents are coming into town tomorrow, so I’ve got a lot of cleaning to do. No post on Thursday. But I had a simple idea I’d been meaning to toss out to you for a while now and this seemed like a good time.

Random theory of mine, probably not all that original. I think we tend to batch-read words. We tend to look at larger text elements—the clauses and phrases and sentences, rather than the individual words that make up those elements. I mean, you’re doing it right now. You’re not picking out the individual words, you’re reading this as a whole. And that’s a good thing. It’s what we want readers to do. It means my writing has a great flow to it.

But…

By the same token, this can make us kind of blind to things in our own work. Once we’ve written a sentence, we tend to gloss over it. Especially after reading it three or four times. We get overly-familiar with it. Even when we’re re-reading it in an edit draft, a lot of the time we’re just taking in the big picture and not looking at what’s actually there on the page.  It’s how we can read a sentence a dozen times and never notice that glaring typo in the middle of it. Or not notice there’s a word missing altogether.  Or that twice on this page we refer to Stu as Ted, but we don’t think about it because we know Stu was called Ted in an earlier draft and so they’re the same person in our heads.

That kinda thing.

So here’s my quick tip for you.  Do at least one pass where you  don’t read your story. Read the words on the page. Actually look at each individual word there on your screen  and. Read. Each. One. Of. Them.

Yeah, it’s slow. And it’s tough. That sounds silly, I know, but it is super-tough to go through a story this way. Especially a story we know. You need a ton of patience and focus. But I guarantee you’ll find dozens of things that were missed on earlier passes.

In fact, here’s a tip for that tip. Before you do this pass, change the font on your whole document. If you normally write in Times, switch it over to Courier. If you normally write in Courier, switch it over to Times. If you normally write in Wingdings, what the hell’s wrong with you? Seriously, nobody’s going to be able to read that. Put it in Times, make everybody’s life easer.

Anyway… remember what I said about how we get overly-familiar with things? Well y’see Timmy, by changing the font, I’ve just made the whole document unfamiliar to me. The spacing’s different. Things will sit on each page in new ways. Which means I’ll be looking at it with fresh eyes, and things will be a little easier to catch.

And there you go. This writing tip has been brought to you by cranberry sauce. And by Nana’s special holiday rolls.

Next time… well, look. Black Friday’s coming up, and if you’ve been here for any amount of time you know what I’ll be talking about. And then there’s Cyber Monday, plus NaNoWriMo will’ve been wrapped up for a couple of days. I’m going to be blabbing about a lot of stuff for the next week or so. Check back often.

Until then, go write.

I don’t have a lot of time this week because tomorrow is the start of (cue cheering) WonderCon in Anaheim.  I’m going to be there hanging out for parts, signing some books, and Sunday I’ll be holding a two hour version of the Writer’s Coffeehouse.  Please feel free to stop by, say hi, and listen to me talk about this crazy business of writing stuff.

Speaking of which…

Spelling and vocabulary.

I’ve got to know how to spell if I want to make it as a writer.

Now I’m sure a couple folks have already rolled there own eyes and moved on to watching some cool YouTube videos.  I mean, I said this was going to be about basics, but nobody thought we’d go thisbasic, right?  We don’t need a grade school refresher.  Besides, its the 21st century.  People have spellcheckers on their phones!  Technology’s made knowing how to sell pointless.

Right?

Well…  As I’ve talked about once or thrice before, spellcheckers are pretty much idiots.  They can tell me if a word’s spelled right, but they can’t tell me if it’s the right word.  It’s the classic there, their, or they’re argument.

And that’s the vocabulary half of this.  Some of the greatest computers out there are pretty bad when it comes to understanding grammar, which means it’s doubtful they’re always going to know which word I’m trying to use.  Which means there’s a good chance it doesn’t’ actually know if this word is spelled right or not.  Did I want thereor their?  Only one of them’s correct, and if I don’t know which it’s supposed to be…

F’r example, check out this list.  I’ve done this sort of thing before.  These are all words people used in articles on fairly popular, journalistic websites (some news, some entertainment) pared up with the word they meant to use.  I’m willing to bet all those articles were spellchecked and given a good thumbs up from the computer, but the writer didn’t know the difference.  Or maybe their editor.  Or maybe both of them

lede and lead

poles and polls

borders and boarders

allude and elude

right and rite

peek and peak

serfs and surfs
reign and rein

Yeah, a couple of those are laughable, I know, but I swear I didn’t make any of these up.  They meant to use X, but they printed Y. A couple of these I’ve seen multiple tines, even.

And I’m sure you know what they all mean, right?  You wouldn’t be laughing if you didn’t know bothof the words.  If I only know one of them, well… that’s not entirely helpful, is it?  Especially as a writer.  Words are supposed to be my thing, the raw material of my trade, but I don’t know what they mean?  Would you want surgery from a doctor who knew what some of your organs did?

Now, a common defense I see for this a lot is that I don’t need to know.  Spelling’s not that important, and it’s all just an arbitrary constrict, anyway.  Readers will get my meaning from context.  If I meant polls and I wrote poles, when it’s actually in a sentence people will still understand what I’m trying to say

Yeah.  Yeah, they will.  That’s why most readers and agents and editors will excuse a mistake or two.  We’re all human.  We make typos.  We get a little tired and bleary-eyed during that 2 am line edit the day before a book’s due (not that I’ve ever done that…).

But, y’see, Timmy, if I don’t know how to spell, if I don’t know my vocabulary, if I’m just depending on the computer too do it all for me… I’m going to make more of these mistakes.  More and more, the longer my manuscript is.  Dozens, maybe hundreds of them.

And, yeah, we’ll all gloss over one or two points where we just need to get it from context.  Maybe even three or four.  But there hits a point—and it really isn’t that high—where we start to wonder if this person really knows what they’re doing.  Again, how many times do you really want to here your doctor joke “Wow, what do you think thatdoes?”

Want proof?

Well, I’ve littered half a dozen or so of these mistakes all through this little rant.  You probably noticed some and chuckled.  Hopefully all of them.  I’m tempted to say someone might even leap down halfway through reading this to comment on the irony of my post on spelling having such blatant spelling errors.  And they’d be kinda justified.  Here I am, trying to say I understand the craft, that my words are worth your time, worth reading, and yet…

I’m making a lot of really blatant, basic mistakes in just three or four pages. 

It’s understandable that they’d shake their head, scoff, and say “oh, no, good sir.  Not you.  Not today.”

To put it another way, we’d understand if I got rejected over that kind of thing.

And I don’t want to see anybody here rejected over that kind of thing.

This weekend—WonderCon!

Next time, I want to talk about what you can do.  Or, really, what your characters can do.

Until then, go write.

            First off, so very sorry post have been irregular here as of late. Believe I’ve mentioned I’m juggling a few things.  One of which is the con I’m at right now.

            But we’ll talk about that in a bit…

            This week I wanted to revisit an idea that I’ve brought up a couple of times over the past few months.  I’ve heard it called a few different things, but my preferred term has always been flow.  First heard it that way from a wonderful author and writing teacher named Drusilla Campbell, and it always stuck with me.

            The visual I’d like to put in your head for flow is traffic. Regular old automobile traffic.  I’m going to go out on a limb and guess most of you reading this can drive, and the few who don’t have still ridden in a car.  And hopefully most of you have been to a city, or at least on a highway of some kind.

            So… let’s talk about the flow of traffic.

            Living in Los Angeles (and before that San Diego, and before that the greater Boston area), I’m very used to highway traffic.  Sometimes, often late at night, the highway is clear and wide open.  There’s barely anyone on the road and you can pretty much fly.

            Of course, even if there aren’t many cars on the road, something big can still create a traffic jam.  Major construction or a big accident can condense things down to one lane, and suddenly that very open road is densely packed and moving at a crawl.

            During the day it can be even worse.  When there’s a million people on the road (no exaggeration here in LA) one small problem can slow everything down.  A large one can bring things to a crashing halt.  Hell, there’s a big hill on the 405 through the Sepulveda Pass and it always causes traffic slowdowns, both ways, up and down.  I’ve been in traffic jams so bad you could actually shut your car off, get out, and stretch your legs for a bit.

            There are places where the very structure and layout of the freeway just naturally causes traffic jams. There’s no way to avoid it the way things have been constructed.  I know a couple stretches where—for no reason—the road goes from six lanes to three.  And then back up to five.  That mile of three lanes… it’s almost always clogged.

            Traffic patterns can even get messed up when people just start looking at the wrong thing. We’ve all been in massive slowdowns that are simply caused by people staring at something on the side of the road. Or sometimes on the other side of the road.  A big accident in the northbound lane can make everybody in the southbound lane slow down to take a look.

            Sometimes it works great, though.  Those million people can be on the road and it’s fantastic.  Everything works.  I’ve had times when I’ve been looking at all the cars on the road, but then looked down to realize I’m almost doing sixty-five.  We’re all going at almost sixty-five, in perfect sync.  I was just caught up in everything and didn’t even realize what was actually going on.

            But that flow can get disrupted so easily.  Again, one car going really slow.  One closed lane.  One distraction over on the shoulder.

            What’s the point of this little visualization?

            Reading a story is a lot like traffic.  It has a flow.  When the flow’s great, we barely notice how fast things are going.  We just zoom along and suddenly realize we’ve read a hundred pages and it’s dark out and where the hell am I?  A book that you can’t put down has great flow.  A book that you should love but you just can’t get into… probably doesn’t.

            Here’s a few things that have the potential of causing a traffic jam in my story.

            A friend of mine has a book where the main character slips into sort of a fever dream.  She’s sick, she’s been medicated, and now she’s… a bit out of it.  And so the next two chapters of the book are in stage play format.  It becomes a bit more separated from reality for the reader and we understand it’s more surreal for the character as well.

            Compare this to another book I read recently when, for no reason, maybe 15-20% of a page would suddenly be in screenplay format.  Dialogue, prose, prose, slugline, dialogue, stage direction, prose, dialogue.  It jarred me out of an otherwise wonderful book every single time, and the author did it every four or five pages.  I looked for patterns and tried to figure out if there was a recurring motif, but couldn’t find anything.  I loved the story, but I kept getting knocked out if it.

            There’s nothing wrong with doing clever things.  It’s highly encouraged.  But I need to have a reason to do them, because my readers are going to assume there’s a reason I did it. That’s natural, isn’t it? I made the effort to put it in the book, so there must be a point to it.  Bruce Joel Rubin once mentioned that when we stop experiencing stories in our gut, we go into our head and start analyzing them.  That’s when the flow breaks.  When we stop reading and start drawing mental diagrams.

            I was reading this big sprawling generational family saga recently.  Not normally my kind of thing, but I’ve been trying to expand my reading umbrella lately.  And I’m overall glad I read it.

            But…

            One issue it had was that, by nature of being multigenerational, there were lots of people who were called “Dad,” and quite a few who were “Mom.”  And they were all Dad and Mom.  No “Pops” or “Papa” or “Daddy Dearest.”  No “Mum” or “Ma” or “Mother.”  Which got confusing because the book also jumped POV and timeframes a lot.  We might be in Yakko’s head for a chapter, then hop over to his granddaughter’s.  Which meant “Dad and Mom” is now referring to different people.  Some of them even had the same name, so there was a Yakko Jr. and a Yakko the III (fortunately grandpa had died)

            Anyway, what it amounted to was me going back to analyze the book every ten or fifteen pages to make sure the person behind this POV was who I thought they were.

            This is closely related to something else I’ve mentioned before—when lots of people have very similar names, especially when they all begin with the same letter.  We naturally lock on to that first letter to help keep things straight in our heads. If my story has a large cast featuring John, Jerry, Jacob, Jared, Justin, Jean, Jon, Jeri, Juan, Jenn, and Jess, people are (again) going to spend just as much time going backward to figure out who’s who as they are going forward to, well… read my story.

            We work with words.  That’s a simple fact of the job.  And nobody wants to use common words.  We want to work with amazing words.  Exciting, sexy, awe-inspiring words that people will remember years from now.  Decades from now, even.

            But here’s the thing to remember.  The words don’t really matter. The story matters. The characters matter.  The actual words are just a delivery device.  They’re how I’m telling you the story.  As a writer and a reader, I don’t want to be focused on the act of communication more than what’s being communicated.  The words should be almost invisible.

            And the truth is… the common words are going to be a lot less visible than the uncommon words. As readers—as people—we notice the uncommon. It stands out. And in many cases… it’s distracting. 

            This isn’t to say we can’t use uncommon or obscure words. There should be a reason for using them, though, and that reason shouldn’t just be me wanting to show off the obscure word I learned on Doctor Who a few months ago.  They shouldn’t be stumbling blocks for my reader.  Again, they should be adding to the story, not the delivery device.

            That’s just a few things.  I’ve mentioned some others before.  Flow is kind of tough to get too specific about because something that causes a small bump for me might be slamming you into a metaphorical wall.  Or vice versa.

            Y’see, Timmy, that’s the biggest lesson about flow.  It’s an empathy issue.  It’s about being able to put myself in someone else’s shoes—a lot of other people’s shoes—and make an honest assessment about things.  Will this reference trip people up?  Is this structure confusing?  Is it easy to keep all these characters straight?

            Because if I can’t be honest about my work, there’s a good chance I’m going to jam things up.

            And if that happens too often, to stick with our traffic metaphor… people will start looking for alternate routes.  

           Next time, I’d like to talk about that opening chapter.  You know what I mean.  The P word.  Although, fair warning, next time might not be for two weeks or so.

            Oh, and hey—I’m at Phoenix Comic Fest right now!  Are you reading this? You should come find me. I’m that guy typing on his phone. And also talking on panels and signing stuff and all that.  Come by and say hi.

            And then go write.