October 14, 2021 / 2 Comments

Supporting Spaghetti

Oh, back again so soon? Well, I guess that’s as much on me as it is on you. But I did have another thought I wanted to bounce off you.

This is something I’ve seen several times in books and in bad B-movies, but it only recently struck me what was actually going on. How the storytellers were twisting things in a really unnatural way to solve a problem. So this may make you (and me) look back at some older posts I’ve done in a slightly different light..

But first, let’s talk about pasta.

I got into cooking during the pandemic. Started watching lots of cooking videos. Trying some things that were kind of new and daring for me. Maybe some of you did too. I’ve found all the prep and cooking kept my mind off other things but still working in creative ways. And now I can make really good stir-fried noodles.

Speaking of noodles, you’ve probably heard of the spaghetti test. When it’s cooked properly and ready to eat, you can throw a strand of spaghetti at the wall and the moisture and starches and, I don’t know, pasta epoxy will make it stick. If it isn’t done cooking yet, it just falls off or does a slow downward tumble like one of those Wacky Wall Walkers.

There’s another phrase you may have heard which grew out of this spaghetti test. “Let’s throw it at the wall and see what sticks.” It shows up a lot in the development stages of all sorts of things. We’ve got thirty ideas and we don’t know which one’s going to work? Well, let’s just do allof them. We throw all the spaghetti at the wall—the whole pot—and everything that sticks is good and ready to go and whatever doesn’t… isn’t. Sound familiar?

I think most of us have tried this sort of blunt, brute force approach on something. I know I’ve rewritten conversations severaltimes to see if it works better with Yakko taking the lead, or Dot, or Wakko, or Phoebe, or… who’s that guy? Let’s see what happens if he takes the lead in this. Same thing with names. Holy crap, Murdoch in Terminus went through sooooo many different names. Sometimes for whole drafts, sometimes just for a page or three. But then I found Murdoch and it was perfect.

Thing is, there’s a weird sort of flipside to this. Or maybe an inverse? Freaky mutant bastard offspring? Anyway, I talked a while back about shotgun art, and I think this is what’s going on here.

Sometimes, in books and movies, we’ll see storytellers who just pile on the characters. One after another after another, many of them with only the thinnest connection to the main plot. It’s the cousin of the best friend of a supporting character in one plot thread. Or, y’know, even less than that. I read one story where we spent two whole chapters with a character who’s only purpose was to bump into one of the main characters in a third chapter. That was it. She served no other purpose in the story except to be that two page delay in his day And, y’know, fill out the page count a bit.

What struck me a few weeks back is when storytellers are doing this—layering on dozens of simple, almost stereotypical characters and conflicts—is they’re taking the spaghetti approach and just throwing everything at the wall. Rather than developing any of these characters or elements to any degree, they’re just giving us lots and lots of quick, shallow ones. I mean why spend time making a complex character when I could just create fivecharacters with only one character trait each? It’s so much less effort, right? I mean, ex-wife, former best friend, alcoholic rival, pregnant woman, aggressive military guy—there’s got to be something there that strikes a chord with my reader, right?

That example I gave up above? The woman who served no purpose except to bump into one of the protagonists? She was late for work. That was it. That was her entire character. I mean, she had a name. She had some dialogue. She had a pet in a tank in her apartment (some kind of lizard, I think). But that was it. The only other thing we knew about her—her alarm didn’t go off, she overslept by almost two hours, and she was late for work. We never learned why her alarm didn’t go off (power outage? forgot to set it? sabotaging pet lizard?). We never learned why she was so tired she overslept by two hours (drastically overworked? got blackout drunk? a wild hookup that left her exhausted?).

Heck, weird as it sounds, we never even found out why being late was a bad thing (on the verge of being fired? abusive boss? big presentation?). We just knew she was late, had to get showered and dressed fast, had to get to work, and that was supposed to be enough for us. Anything else would require more thought about who she was, what she wanted out of life, and what she was actually getting.

And this book had over a dozen characters like her. Seriously. It spent a significant amount of time with people who could be 100% completely summed up with things like “Wakko needs some drugs,” “Dot’s worried about her dog,” or “Yakko is a no-nonsense soldier.” That’s it. That’s all of who they were.

One place you may recognize this from (tis the season after all) is old slasher movies. Okay, and some modern ones. Most of the cast is one note characters with just barely enough depth that we can tell the machete went through them. They’re the bulk filler of the plot. The serious woman. The goofball. The jock. The nice girl. The drunk/ stoner. They just exist to be minor obstacles between our killer and the one or two survivors.

Now, again, the idea is that the reader (or the audience, if this is a B-movie) has to find something more-or-less relatable in these broad stereotypes. I mean… you’ve known somebody who’s late for work before, right? Or was a jock? Or a serious woman? Okay, well… I bet you knew someone who was worried about their dog at some point, right?

I think people do this for two reasons. One is that they’re nervous about creating complex characters. Maybe they don’t think they’ve got the skill to do it, or possibly just not the skill to do it in the number of pages allotted to it. Perhaps they think their plot can’t function with only three or four threads. Or possibly they’re worried about having such a limited number of viewpoints.

I think the other reason is they’re worried about having characters with no traits. Like that woman running the register at the gas station. She doesn’t even have a name tag. She’s just there to sell the protagonist gas and a couple snacks. She’s got no arc or backstory or tragic flaw. That doesn’t seem right. We have to give her something, right? Maybe she could be, I don’t know, late for work or something?

Thing is, no matter what my reasoning is for this flood of one-dimensional characters, this always ends up leading to one of two things. Either we mistake their lack of depth for deliberate avoidance (“Hmmmmmm… why isn’t the writer saying why she was up late last night? Is she the murderer???”) and then we get frustrated when this goes nowhere. Or we recognize these characters don’t actually serve a purpose and get frustrated waiting to go back to someone who’s actually going to affect the plot in some way.

I also think it’s worth noting the three traits of good characters I’ve mentioned here a few dozen times—likable, believable, relatable. And yeah, I’ve also mentioned that supporting characters can sometimes get away with only two of these traits. Catch is, when characters are this flat and undeveloped, they almost always end up unbelievable—their actions and reactions just seem ridiculous because there’s no depth to ground them in. So we’re down one good trait already! Then my shotgun approach means they’re going to be randomly relatable at best, and lots of folks fall back on “snarky jerk” as a default personality, soooooooooooooo… Not a lot going for these folks.

Y’see, Timmy, burying my story in simple characters doesn’t work because it’s forgetting a basic truth of the spaghetti test. All those noodles that didn’t stick to the wall? I don’t sweep them up off the floor and put them back in the pot. The whole point of doing it all was to see what did and didn’t work—to figure out what shouldn’t be in my story.

So said noodles definitely shouldn’t be part of my finished entree.

Everyone gets the food-book metaphor here, right?

Anyway… next time…

Wow. Already halfway through October. I guess next time I could do the obligatory horror post. Or maybe talk about NaNoWriMo? Any preferences?

Either way, go write.

August 27, 2020

On the Third Day…

I got a request from Rhyen, which is great because I still haven’t really hammered those ideas on endings or comedy quite into shape. So that’s still some stuff for the future. Or, y’know, somebody else could ask something.


Rhyen wanted to know about worldbuilding. Not just “our world, but with secret werewolves” but full-on, hardcore fantasy worlds, sci-fi worlds, and so on. How (and when) do you come up with histories, cultures, and all that other stuff?

Y’know what? Let’s make this post super-active rather than me blathering away. Right here, right now, let’s look at werewolf world. The other version of it where everybody knows werewolves are real.

Now, I know, we said we were going to do more hardcore settings but just go with me for a minute.

I’ve mentioned Charlie Jane Anders once or thrice before, and her little note that there’s no such thing as “a world just like ours, except…” because any noteworthy “except” is going to change everything. If there really were werewolves and everybody knew about them, so much would be different in the world. Tonsof things.

Don’t believe me? Let’s go over a few things real quick. Just off the top of my head…

Here’s an easy change. There probably wouldn’t be any silver coins. In WereWorld anything with even a scrap of silver would’ve been gathered up and turned into anti-werewolf weapons or defenses. The government would be treating silver like uranium. 

Which, hey… how would warfare be different? Forget atom bombs… imagine if the Manhattan Project involved deliberately infecting a hundred or so troops with lycanthropy and then dropping them all on Nagasakiand Hiroshima on the night of the full moon. A hundred unstoppable killing machines running wild in each city. That’s a terror weapon, right there. And of course, if the Japanese capture two or three alive, now they’ve got their own werewolves.

But now without the USpouring all that money into nuclear warfare and missile programs… where does it all go? Infrastructure? Social programs? Schools? Would there be a Cold War? A Bay of Pigs? And if the Soviet Union leaned into werewolf warfare… what kind of arms races would there be? Would the USSRhave financially collapsed?

And we haven’t even talked about dating or sex in WereWorld. Hunting laws? Home security? Profiling? Legal issues—if I kill someone as a werewolf, am I legally responsible? Is it murder, which requires a degree of forethought, since the werewolf’s essentially an animal (or is it?)?

And all of these assume we just “discovered” werewolves somehow back in the early 1940s. What if it was even earlier? How would global exploration and trade have gone differently five hundred years ago if every twenty-nine days  one of your crew members might kill everyone on the ship? How different would the world map look right now?

Again, this is all off the top of my head. Seriously, I’ve spent maybe ten minutes on this. But I’ve completely rewritten the world, just by being aware that things would inevitably change in this situation.

So, with that in mind…

Creating a setting, any setting, is a lot like creating a character. I want to know them backwards and forwards. It’s fantastic if I have lots and lots of factoids about them easily on hand (you may remember that back before we all took the pandemic plunge, I talked about characters and their underwear choices).

I’ve mentioned character sketches once or thricebefore, and I think worldbuilding can be approached the same way. We come up with the bare basics and then we start fleshing it out by asking questions and maybe following a few paths to their logical outcome. Like I did up above with WereWorld.

Or let’s do something even more divorced from our world. Let’s say it’s going to be a fantasy world, maybe one with some gearpunk elements. So, easy one—is there actual magic in this fantasy world? Is it kind of rare or very common? Does it need components? Are they rare or common? Do people have spell-component gardens the way we might have an herb garden?

How about the gear-tech? How precise is it? Do you need mathematically perfect brass gears or do lots of people carve wooden ones after dinner? What do they use for power? Springs? Counterweights? Two or three big guys turning a crank?

Does magic dominate the gear-tech, or vice versa? Is one notably newer than the other? Does either have detractors, vocal or secretive? Are magic and/or gear-tech novelties or parts of everyday life? Do they ever cross-pollinate, so to speak? Are they expensive or so common everyone has access to some aspect of them?

Considering all of this, now… is this mostly an agrarian world? Are more people farmers? Hunters? Are there gearpunk tractors or crossbows? Magic millstones or knives that can skin anything? And if none of this ever filters down to the common folk… how do they feel about that?

Has the magic or gear-tech made travel easier? Are people still isolated in villages or are there much bigger cities, made possible because of these advances? Do people know more about the world?

Heck, how fantasy is this world? Are there supernatural or mythological creatures? Are they common? Domesticated? Are there things we know or all-new creatures? Does the farmer have a six-legged hexox dragging his plow? Are there gods? Demons? How do they feel about humans playing with magic and gear-tech?

Or heck… is it even humans? Is this about magical halflings or gearpunk elves? I just pictured a gearpunk lizardman and that seemed pretty cool.

If you’ve answered a lot of those questions, I bet you’ve got the beginnings of a pretty solid world in your head. And probably spun off a question or three of your own. Enough so that you can start setting up your plot.

And one thing to keep in mind—just like with characters, this might change as I go along. As the story grows and progresses, I might change a lot. I might add even more. It’s an ongoing process. Halfway through my outline or my first draft, I might realize I need to address currency. And, hey,  maybe this world has a really crappy exchange rate, so it matters if you’re getting paid with glowing quartz or brass gear-coins.

Again, the world is here to serve the story. You’re going to change and tweak it as you go. Maybe all the way up to your last draft. And just like with characters, you’ll keep coming up with cool little details and anecdotes.

Now… there’s three key things to remember…

First, I know I talk about editing things down a lot, but we can all breathe a small sigh of relief here. If I’ve got a story set in another world—a drastically different world—most editors are going to give me a little bit of leeway, word-count wise. They understand I’ll need a few extra pages to explain why Yakko is riding a gearpunk tractor powered by magical crystals.

This doesn’t mean I can go crazy listing details. Or that I can be really blunt with them. No pausing for two pages to randomly describe the wooden sun-and-planet gears in Yakko’s trailer. Or the long history of the mining guild that provides those magic crystals. One more time—say it with me—the world is here to serve the story. It’s okay to have a little extra flavor here and there, but I shouldn’t lose track of what my book is actually about.

Which brings me to my second point. Whenever I create a character, there’s a lot of things about them that are never going to come up in the book. Or maybe they come up, but they’re never explained. I might have tons of rich backstory and weird little details, but a lot of it just never becomes relevant.

For example, in the Threshold books, I know a ton of things about Veek. I know why she’s abrasive with most people. Why she likes wearing men’s suits and ties over women’s power suits. Heck, I made a note of when/how she lost her virginity. But the truth is, none of this has been relevant to any of the books she’s been in. It’s stuff I know, and it helps me make her feel more three dimensional on the page, but ultimately… it’s all kind of irrelevant if it doesn’t have anything to do with this book—with the plot I’m telling and the character’s arc through that plot.

Worldbuilding is the same way. No matter how fantastic or amazing the details of this world might be, they only matter if they’re going to have some kind of impact. While it may be very interesting how this society ended up with a hexadecimal/base sixteen number system, do we need to know any of that history for this story? Yes, WereWorld does have eleven continents and there’s a fascinating story behind it… which has nothing to do with this book.

And even then, I’d argue that if there’s no real reason for something to be different… maybe it shouldn’t be. I think one thing that confuses some people is they see this rich, historied world that the story’s set in and forget the world only exists to serve the story, not the other way around. If you look back at my A2Q discussion about the world Phoebe and Luna live in, I made choices based on what would be interesting for the plot and story, not what would make for an interesting world.

So I shouldn’t be coming up with (and using) new things just to come up with new, different things. I mean George RR Martin just uses leagues for distance in worldbuiding heavyweight A Song of Fire and Ice(perhaps better known by it’s Hollywood stage name, Game of Thrones). It sounds good, a little archaic, and he doesn’t have to waste half a page explaining what hekkrets are.

Or heck, here’s another example… any of you remember that old 70’s indie movie, Star Wars? There’s a great scene where Ben and his would-be-protégé are trying to hire a ship from some lowlife smuggler. And Ben tells him “We can pay you two thousand now plus fifteen… when we reach Alderaan.” Remember that?

So… two thousand what?

No, no, no. Don’t run to novelisations or books or articles that retconned this. Right there in the movie you watched… two thousand what?

Truth is, it doesn’t say and it doesn’t matter. For this story, the type of currency’s irrelevant. I don’t care if it’s Imperial credits or Old Republic scrip or gold-press latinum or Jawa skulls. Okay, I might care if it’s Jawa skulls because WTF Kenobi why do you have two thousand of these laying around?! What the hell have you been up to out in your little desert hut?

Anyway… no, all we need to know is that two thousand is a good amount (judging off everyone’s reactions) and fifteen more makes it a very good amount. Past that, we just don’t need to know why Solo wants all these Jawa skulls Kenobi’s collected. It’s not important. The dialogue’s solid and sounds believable, which is far more important that a brief segue to explain the various types of Galactic currency and their exchange rates.

This brings me to my third and final point.

Worldbuilding is, in my opinion, a really easy trap to fall into. Because worldbuilding is fun. Seriously. That question game we played up above? We can do that for weeks with worldbuilding. Months. Maybe even years. My world is going to be so huge and so complex with so many races and creeds and economies and social structures and seriously we can spend so much time doing this instead of…

Y’know, actually writing the story.

And that’s how I generally approach worldbuilding. You may need to change this approach a bit, depending on your own story and the kid of setting you want for it, but hopefully this’ll get you a little further down that path. Or help you find your own path.

Next time… endings.


Until then, go write.

August 20, 2020 / 1 Comment

An Old Favorite…

It’s Thursday morning and it struck me that I don’t have anything ready for the ranty blog. I’ve had a few different ideas rattling around in my head for posts about endings and comedy and jargon. But they’re all kinda big things and a bit… delicate? I don’t want to be giving bad, half-thought-out advice, and I’m not 100% sure that I have good advice on these precise topics quite yet. Thus all the rattling around in my head.

Or maybe those are LEGO bricks? Might be. Really, anything goes in 2020.

Hey, speaking of years and what’s possible and what’s acceptable, I realized I could babble on for a minute or two about a topic that pops back up every four or five months.

See, I recently watched an adaptation of something I loved many years back. And, being a proper nerd who read and re-read the original and then read it again a seventeenth time, I picked out little changes here and there. I mean, yeah, it’s an adaptation. Things are going to change. They always do because they need to. But these were different changes. A lot of them were in how people were addressed. How other people reacted to them. Nothing gigantic, but it stood out to me because—as I said—I was a big fan of the original.

Okay, fine, I was nitpicking.

Anyway, I can’t remember at what point in the movie it clicked, but it hit me that the movie had updated a lot of the original story’s views on sexuality and gender. Just little tweaks, nothing that affected the plot in any way. But the movie was a bit more modern, inclusive, and—in a few places—a little less mocking.

I thought Good on them.

But then, shortly afterward, I had another moment. Because, hang on a minute, I’d read this many, many times back in those formative years and I’d never noticed any places where people were excluded or mocked or anything like that. The book was fine. Was this movie overreacting? Were they just changing things in the adaptation to please a tiny, vocal minority?

And the more I thought about it, the more I realized ohhhhhhhh no. No they weren’t. I just didn’t notice because, at the time… I was cool with all of that. My views then echoed a lot of the views of, well, then. Just like the book did.

This book was big for me. If someone asked me, it’d probably end up on my personal list of “twelve most influential books/authors” or something like that. But… yeah, it’s got some flaws. The book is a fixed artifact of thenand there are aspects of it that the world has moved past. And, thankfully, I’ve moved past.

It’s a rough thing to go back and realize things you loved in the past don’t quite measure up anymore. Sometimes in minor ways, sometimes in… well, really big ones. I re-read a classic sci-fi novel a year or two back and it terrified me with some of its views on sex. Re-read another formative series to my partner when she was really sick and discovered wow was there a lot of casual racism in it. Just a few weeks ago I watched one of my favorite comedy movies from my teens, one I must’ve seen this at least a dozen times (yay USA Up All Night) and holy crap that was just full-on, no question sexual assault, arguably attempted rape from the main character. That was seriously uncomfortable to watch.

And I get why admitting this sort of thing can be tough for people. To admit these early, formative works are flawed. That the people who made them were flawed. Because admitting this means opening ourselves up to the idea we might be flawed. We might’ve absorbed views and lessons that, in retrospect, were not good.  It’s painful to think the movie adaptation of our life might get that same horrified reaction.

The world always changes. It progresses, it moves forward, and hopefully… we move with it. We learn more. We understand more. This sounds really dumb to say, but I’m very happy my views have grown and evolved since I was five. Or fifteen. Or twenty-five. Not on everything, but on a lot of things. It’s not weakness to say I’ve changed my views—it’s growth.

This doesn’t mean we have to abandon those old, formative works or throw them on bonfires. But we need to be honest and acknowledge what they really are… even when it means a bit of apology and internal cringing on our part. I can say this book and that book are on my list of formative things because… well, they were. I can’t deny it. They’re part of why I’m a writer today.

But I don’t need to embrace them or constantly defend them. I can admit their flaws—some minor and some seriously glaring—even if it possibly means admitting some flaws of my own. Because in writing and in life, I can’t improve if I never admit that I need improvement.

Anyway… just some random thoughts. I know other folks have said similar things in a better way.
Next time…

Well, as always, if anyone’s’ got a specific question, feel free to drop it in the comments below. Or over on a Writers Coffeehouse videoif you want to get answers from better writers. And if not, maybe I’ll sort out some of those bigger ideas to talk about.

Until then… go write.

September 26, 2019 / 1 Comment

Getting It

Is it just the view on my screen, or has the tag cloud over there in the right margin kind of… collapsed? Shattered? It doesn’t look right, that’s for sure. Apologies if you’ve gone looking for something and it’s especially hard to find.

I stumbled across an issue recently in two very different books, and then in a movie, and it’s semi-related to some things I’ve talked about before. So I figured it might be worth a little refresher. And, not to sound silly but.. some of you are going to get this immediately and some of you aren’t.

There’s an idea I’ve mentioned here a  few times, which I first heard (read, really) from Damon Knight.  If we’re presented with a fact we don’t know, it’s information. If it’s a fact we doknow, it’s just noise. I don’t bother to explain what the ranty blog is about every week, because if you’ve found yourself here odds are you already know. But I will discuss Phoebe’s height a lot this week (she’s over six feet tall) because it’s kind of germane to the discussion, as one might say.

It’s very important that Phoebe is tall in my story. In fact, it’s semi-critical that my readers know she’s just over six feet. It’s a key point for her, and I can’t have them picturing her shorter—let alone drastically shorter—because it’ll make things very confusing at a later point in the story.

So… how do I do this? How do I make sure that when readers picture Phoebe, they picture her as just-over-six-feet in height? That it’s one of her defining details, something they absolutely picture about her?
Well, yeah, I have to put it in her description, sure. Writing it out is kind of a given. But I’ve talked before about how descriptions don’t always stick. We get mental images of characters that don’t always match up with their written descriptions. And, as I’ve mentioned, it’s really important that people remember Phoebe’s pretty tall (she is, as I may have mentioned, just over six feet).

Which brings us to another idea I’ve talked about—repetition. I’ve talked before about repeating words, phrases, and structures to get a certain effect. What I’d like to talk about today is using repetition on a slightly more visible level to try to cement important details (like Phoebe’s just over-six foot height) in my reader’s mind.

And I’d like to do that with the obvious example—A Christmas Story.

For those of you who are somehow unfamiliar with the movie, A Christmas Story is about a boy named Ralphie who wants… well, we can probably say is obsessed with getting a Red Ryder BB gun. It’s pretty much all he talks about. In fact, in a  ninety-three minute movie, he mentions it by name almost thirty times. He’s basically saying it every three minutes. If we go off standard script timing the Red Ryder BB gun comes up every three and a half pages. Is this a good rate to mention something important? I mean, A Christmas Story’s a legendary film, so it’s gotta be doing something right, yeah?

Let’s keep a few things in mind, though. Ralphie’s an obsessed little kid. He’s basically the nice version of Eric Cartman ranting about what color MegaMan he wants for his birthday. He’s single-focused in a way most mature adults grow out of pretty quick. And while it’s funny in small doses, I think we can all be honest and admit that Ralphie’s… kind of annoying. It’s in a cute way, but there’s no way he’d get away with this if he wasn’t a chubby-cheeked little kid with glasses.

(who later grew up to hate Iron Man and run tech support for Mysterio–seriously!)

But if I’m not writing from the point of view of an adorkable pre-teen, this level of repetition can get annoying real fast and start dragging my story down. Take Phoebe and her just over six-foot height for example. I only mentioned her five times (six counting this one), but the mentions of her and her height were starting to get on your nerves, weren’t they? There’s just so many times I can repeat this information before you’re grinding your teeth and saying “Yes, I get it, can we move on now please…”  In this case, repetition is more of a necessary evil, because there’s no way for us to get things across without putting it on the page somehow.

So… how many times?

As a good rule of thumb, I think I’d like to fall back on, well, another rule of thumb I’ve mentioned here once or thrice before. The rule of three. Really, really quick and dirty, the rule of three basically says by the third time I mention something—who Dot got the necklace from, needing to be worthy to lift the hammer Mjolnir, or how tall Phoebe is—my audience almost always gets it.

I’d like to add a small proviso to that, just for when we’re talking about this specific instance. Whatever my super-important detail is, I should mention or give an example of it twice very early on. If it’s Dot’s necklace, maybe she can muse about it once and someone can ask her about it. If it’s about that hammer, maybe Odin can whisper about it once and Thor can demonstrate it fifteen or twenty minutes later. Maybe Phoebe can address some part of her morning ritual she needs to adjust for her height (crouching in the shower) and then someone else can actually flat our comment on it.  These are all early, act one sort of things. Formative things. A one-two punch to land the information and drive it home before it has a chance to become noise.

And then forget about it. If a moment comes up in the story that absolutely calls for this detail to be mentioned again, but if not… don’t. Trust that your audience has it in mind.

The third time should be very close to the payoff, even if it’s hundreds of pages later. This is my last chance to nudge that idea into the reader’s mind before the reveal slams it into their eyes. Or ears. Okay, also into their minds. Look, this isn’t an exact science, okay?

And again, this is only if that fact or detail is really important. Like, deathly important.  Story collapses without it important. If it’s just me wanting Phoebe to be a blonde or, hey, the hammer has a woven leather grip… well, these are just regular bits of description. They’re the things I don’t worry about because my readers are probably going to have their own mental images for them. And that’s fine.. Seriously. If you want to picture Phoebe having auburn-brown hair, that’s cool  And because it’s not important, I don’t want to be driving that point of description home.

Actually, y’know what? I just thought about a better analogy (thus rendering most of this post irrelevant). We’ve talked about names here a bunch of times. How it’s okay not to name some characters? I can just let them sort of be in the background? 

That’s what details are like. There will be a lot of details in my writing that can be beautifully done, but ultimately they’re just sort of there and that’s okay. My reader can enjoy them in the moment but doesn’t need to keep them firmly in mind for things to work in my story. The ones I want to repeat, the ones that need to be specific, are the ones that are going to have an effect on how things unfold.

Y’see, Timmy, much like with names, I don’t want to bog down or annoy my readers with a bunch of details that aren’t going to matter. And I still don’t want to overuse the ones that are going to matter, because that’ll annoy them, too. I need to find that sweet spot where the facts register and get remembered, but don’t become noise.

Next time, I’d like to talk real quick about going with the default settings on this thing.

Until then, go write.