The other big milestone, in terms of what I've been writing, that I hit in 2013 was getting solidly underway on Banshee.
Banshee is a project that's been stewing in the back of my mind for a long, long time, and has gone through several permutations in that slow cooking process.
Part of the reason I took such a long time to get around to this is the little promise I made to myself to finish the first books of my four "Maradaine" series before I really moved on to a new major writing project. I'm not entirely sure why I felt I had to do them first, but that's how I felt, but on some level it was probably a good thing.
Because the Banshee I would have written several years ago is not the work I'm writing now. Not even remotely. Essentially everything except the central character (Lt. Samantha Kengle) and the name of the ship (and only tangentially) is different now. And in the older versions, Lt. Kengle was more the nominal lead in an ensemble, and now she's in the central spotlight, the only POV character.
Part of that had to do with the worldbuilding. I started the Space Opera setting that Banshee lives in way back in 2002, but it's evolved and grown a lot in the past eleven years. As have my writing skills. My first attempts at Banshee, some of which reached nearly 50,000 words, were all wrong. Essentially fanfic for a universe that only existed in my head. It was only after I really started to interrogate what the story was, and who it was about, and why it was about them, that the pieces really came together.
When I shipped Way of the Shield off to the agent, Banshee was really ready to go like gangbusters. And in about three months, it's about two-thirds to three-quarters done. Not too shabby.
So that was 2013, which turned out to be a pretty good year for my writing. And I have a very good feeling that 2014 will turn out even better.
Monday, December 30, 2013
Thursday, December 26, 2013
Way of the Shield, and the Geena Davis Rule: 2013 in Review, Part Two
The next big milestone of accomplishments in 2013 as finishing the draft of Way of the Shield, cleaning it up and sending it off to the agent. He just recently sent it back to me, so now I've got a last round of tweaks and polishes to put on it before sending it back to him to put out into the world.
Long time readers will be aware that Way of the Shield was something of an albatross around my neck for much of 2012. I was working on it and it simply wasn't coming together at all. I had actually decided to put it to the side and focus on other things early this year, but it kept poking at me until I cracked the problem I had been having with the antagonists. It actually came together when my beta reader/sounding board guy asked me a simple question regarding Way of the Shield, and that brought about a breakthrough in writing out a long and complicated response. Doing that brought me from a manuscript languishing at around a third of the way done to complete in two months.
Breakthroughs can work like that.
The other thing I did with Shield, both in the original draft and again in the current clean-up, was confound the gender expectations of the old knightly orders that Dayne is a part of. Druthal and Maradaine are hardly a paradise of gender equality, but I wanted the Orders to reflect the idea that anyone who gets through the training process is considered an equal.
But my first chapter had no female characters.
Then I was thinking about this bit of advice Geena Davis recently gave regarding female characters in Hollywood movies, advice I think can easily apply to genre fiction as well:
And it stuck me, if I've already established this idea that the Orders have more gender equality than the culture at large, then why not just have Dayne's chapterhouse master in Lacanja (the city Way of the Shield starts in before Dayne returns to Maradaine) be a woman? I never gave Master Thall a given name, male or female, to begin with, so rewriting the scene involved little more than some pronoun switching. But, I think, it will have a strong effect on the worldbuilding of the Orders, which will ripple through the rest of the book-- which already has many female characters in a variety of roles.
Regardless, as I mentioned back in May when I finally finished the draft, it felt very good to get this particular project out of its long, slow, "work-in-progress" state.
Long time readers will be aware that Way of the Shield was something of an albatross around my neck for much of 2012. I was working on it and it simply wasn't coming together at all. I had actually decided to put it to the side and focus on other things early this year, but it kept poking at me until I cracked the problem I had been having with the antagonists. It actually came together when my beta reader/sounding board guy asked me a simple question regarding Way of the Shield, and that brought about a breakthrough in writing out a long and complicated response. Doing that brought me from a manuscript languishing at around a third of the way done to complete in two months.
Breakthroughs can work like that.
The other thing I did with Shield, both in the original draft and again in the current clean-up, was confound the gender expectations of the old knightly orders that Dayne is a part of. Druthal and Maradaine are hardly a paradise of gender equality, but I wanted the Orders to reflect the idea that anyone who gets through the training process is considered an equal.
But my first chapter had no female characters.
Then I was thinking about this bit of advice Geena Davis recently gave regarding female characters in Hollywood movies, advice I think can easily apply to genre fiction as well:
Go through the projects you're already working on and change a bunch of the characters' first names to women's names. With one stroke you've created some colorful unstereotypical female characters that might turn out to be even more interesting now that they've had a gender switch. What if the plumber or pilot or construction foreman is a woman? What if the taxi driver or the scheming politician is a woman? What if both police officers that arrive on the scene are women — and it's not a big deal?
And it stuck me, if I've already established this idea that the Orders have more gender equality than the culture at large, then why not just have Dayne's chapterhouse master in Lacanja (the city Way of the Shield starts in before Dayne returns to Maradaine) be a woman? I never gave Master Thall a given name, male or female, to begin with, so rewriting the scene involved little more than some pronoun switching. But, I think, it will have a strong effect on the worldbuilding of the Orders, which will ripple through the rest of the book-- which already has many female characters in a variety of roles.
Regardless, as I mentioned back in May when I finally finished the draft, it felt very good to get this particular project out of its long, slow, "work-in-progress" state.
Labels:
2013,
Druthal,
gender,
state of the writer,
Way of the Shield,
writing
Monday, December 23, 2013
Jump the Black- 2013 in Review, Part One
On January 1st, 2013, I sold Jump the Black to Rick Klaw's Texas-themed sci-fi anthology Rayguns Over Texas, which was my first pro-level genre sale.*
I haven't ever really talked about the story itself, as it didn't seem appropriate when I first sold it.
When it was coming out, it made more sense to talk about the anthology as a whole.
I should preface this by saying I'm really not a short-story writer. It's just not a format I have a lot of affinity for, and I don't tend to write them without a specific purpose or plan. However, "invited to submit to this anthology" works very well as a specific purpose or plan.
So, I received the invite and remembered a nugget of an idea that I had had for a sci-fi story. It was little more than this: A sci-fi future with a large interstellar, multi-alien community, but Earth isn't a part of it. Earth is the place you leave to have opportunity. Earth is Mexico.
I did some research into border crossings, the lengths people go to in order to get in the States. I thought about "coyotes"-- those who "help" others get across the border, and the methods they use to do it. The conditions people will submit themselves to, the trust they will place on those bringing them, and the hope that when they emerge on the other side that an opportunity will be there that will make it all worth it.
And I wanted something in there that could be a direct allegory to swimming across the Rio Grande. Thus "jumping the black"-- where the smuggled humans, freshly awoken from the paralytic "sleep" they were put in to avoid getting noticed by the scans-- have to leap through empty space from the smuggler's cargo hold to a port left open on the space station, so that they're off the smuggler's ship before his cargo gets inspected. If the humans jumping don't make it safely... that's their problem. Also, if they get caught right when they get in the station, their problem.
I really enjoyed writing this, and it definitely clicked one big button for me: I could write a lot more of it. I kept it at 4000 words to make it fit easily in the anthology, but I could easily expand the story to novella length, building out what happens next once the humans make it off the rock.
But, as I said, selling that on January 1st was an excellent way to start 2013, and I was quite pleased to see it in print in September.
--
*- My story for The Norton Anthology of Hint Fiction was paid at over a dollar per word, but it was only 21 words long. Twenty-two with the title. But it wasn't genre.
I haven't ever really talked about the story itself, as it didn't seem appropriate when I first sold it.
When it was coming out, it made more sense to talk about the anthology as a whole.
I should preface this by saying I'm really not a short-story writer. It's just not a format I have a lot of affinity for, and I don't tend to write them without a specific purpose or plan. However, "invited to submit to this anthology" works very well as a specific purpose or plan.
So, I received the invite and remembered a nugget of an idea that I had had for a sci-fi story. It was little more than this: A sci-fi future with a large interstellar, multi-alien community, but Earth isn't a part of it. Earth is the place you leave to have opportunity. Earth is Mexico.
I did some research into border crossings, the lengths people go to in order to get in the States. I thought about "coyotes"-- those who "help" others get across the border, and the methods they use to do it. The conditions people will submit themselves to, the trust they will place on those bringing them, and the hope that when they emerge on the other side that an opportunity will be there that will make it all worth it.
And I wanted something in there that could be a direct allegory to swimming across the Rio Grande. Thus "jumping the black"-- where the smuggled humans, freshly awoken from the paralytic "sleep" they were put in to avoid getting noticed by the scans-- have to leap through empty space from the smuggler's cargo hold to a port left open on the space station, so that they're off the smuggler's ship before his cargo gets inspected. If the humans jumping don't make it safely... that's their problem. Also, if they get caught right when they get in the station, their problem.
I really enjoyed writing this, and it definitely clicked one big button for me: I could write a lot more of it. I kept it at 4000 words to make it fit easily in the anthology, but I could easily expand the story to novella length, building out what happens next once the humans make it off the rock.
But, as I said, selling that on January 1st was an excellent way to start 2013, and I was quite pleased to see it in print in September.
--
*- My story for The Norton Anthology of Hint Fiction was paid at over a dollar per word, but it was only 21 words long. Twenty-two with the title. But it wasn't genre.
Labels:
2013,
Jump the Black,
published,
Rayguns Over Texas,
sci-fi,
sff,
short stories
Thursday, December 19, 2013
Perils of the Writer: Fanfic of Yourself
I was thinking about one of my trunked projects, Crown of Druthal, as well as the process of novel midwifery that has brought Banshee to the point where it is now (i.e., a rough draft in progress that I feel relatively good about).
And I came to realize that the problems with Crown and the earlier versions of Banshee (which bear almost no resemblance to the current project) was that neither one was really a story. Sure, they had characters, they had setting, they had events happening... but neither one added up to a cohesive whole.
I was essentially writing a fun time hanging out with characters I liked in a setting I liked, and not doing much but enjoying doing that.
And that, dear readers, is essentially what fanfic is.
Mind you, I'm not saying fanfic is bad-- if you enjoy doing it, have at it. But you are quite limited in what you can do with it once you've written it. You can, essentially, share it with the fan community, and the degree that it can be enjoyed is based on the size of that fandom. No one who isn't already a fan is going to care in the slightest.
So if you're writing fanfic of a thing that only exists in your head, how many fans are out there?
Just you.
So, if you find yourself caught in that rut, how do you break out of it?
For me, it was a process of figuring out an actual story, tied to a central character (or characters). The central character came first, of course, but then figuring out what their story was brought in secondary characters as needed.
And that was a key place where I had gone wrong with Crown and early versions of Banshee. In both cases, I had come up with a wide, sprawling cast. Both involved ships (one at sea, one in space), so I had worked out who ALL the key people on the ship were, what their jobs were, how they all related to each other... but that had nothing to with any specific story. They were just there, giving me a deep bench of characters to pull from in any given situation, without any organic reason to have them all.
And in the long run, that won't give you a compelling story that will hook anyone who isn't you.
-----
A small plug for fellow agency-brother. Glynn Stewart's Starship Mage series has launched on e-books. The first one just came out, and the next one is due in March of 2014. Go check it out!
And I came to realize that the problems with Crown and the earlier versions of Banshee (which bear almost no resemblance to the current project) was that neither one was really a story. Sure, they had characters, they had setting, they had events happening... but neither one added up to a cohesive whole.
I was essentially writing a fun time hanging out with characters I liked in a setting I liked, and not doing much but enjoying doing that.
And that, dear readers, is essentially what fanfic is.
Mind you, I'm not saying fanfic is bad-- if you enjoy doing it, have at it. But you are quite limited in what you can do with it once you've written it. You can, essentially, share it with the fan community, and the degree that it can be enjoyed is based on the size of that fandom. No one who isn't already a fan is going to care in the slightest.
So if you're writing fanfic of a thing that only exists in your head, how many fans are out there?
Just you.
So, if you find yourself caught in that rut, how do you break out of it?
For me, it was a process of figuring out an actual story, tied to a central character (or characters). The central character came first, of course, but then figuring out what their story was brought in secondary characters as needed.
And that was a key place where I had gone wrong with Crown and early versions of Banshee. In both cases, I had come up with a wide, sprawling cast. Both involved ships (one at sea, one in space), so I had worked out who ALL the key people on the ship were, what their jobs were, how they all related to each other... but that had nothing to with any specific story. They were just there, giving me a deep bench of characters to pull from in any given situation, without any organic reason to have them all.
And in the long run, that won't give you a compelling story that will hook anyone who isn't you.
-----
A small plug for fellow agency-brother. Glynn Stewart's Starship Mage series has launched on e-books. The first one just came out, and the next one is due in March of 2014. Go check it out!
Monday, December 16, 2013
Tools of the Writer: Growing with the times
You know, way, way back in the day-- by which I mean high school-- I did my writing on WordPerfect, using the 8088 PC-clone that I had at the time. Before that I had an Apple II+, and I don't recall having a word processing program on that. I did actually learn to type on a typewriter, though it was probably a weird and strange choice made by a weird and strange child*. But my high school creative writing classes had us go to the computer labs, where we had to sign in with our TOTALLY SECRET IDS** and use WordPerfect to write our stories.
At some point around when I started college, I switched over to WordPerfect for Windows, which I mostly used on my dad's computer, since it would have made my 8088 explode. This did create a challenge in the college computer labs later, which all used-- I want to say WordStar for Windows, but it might have just been Mircosoft Word-- but the important thing was, NOT WordPerfect, and trying to transfer a *.WPW into one of those formats was an exercise in futility.
Ah, the early days of computer usage.
As a matter of fact, the process of transferring archives from one computer to another, regardless of utility, means I still actually have some *.WPW files on the laptop I'm currently working on.
Eventually, I switched over to Microsoft Word, once I got a desktop that could handle it, and pretty much stayed with it for quite some time. And that was handy, because it was a format I could use on computers at home and at work, and plenty of early writing was done on that. Even going back and forth between using PCs and Macs didn't impede me. Portability of projects was a very crucial thing for me.
Trunked novels "Fifty Year War" and "Crown of Druthal", as well as many plays, unfinished projects, and the early drafts of Thorn of Dentonhill, Holver Alley Crew and Maradaine Constabulary were all written on Word. And while I never had a problem with Word, the challenges of writing an entire novel on it were quite clear.
And thus, eventually, I went, heels dragging, to Scrivener. Which now that I'm here, I totally love it. I won't lie, it had a bit of learning curve that I resisted. But the process of transferring the drafts of those three novels so I could rework them into Scrivener taught me how it could be a valuable resource to me. Especially in terms of keeping all sorts of character and outline and conceptual information in one place, and being able to visualize the scope of the story.
And in writing Banshee, where I've been jumping around like crazy with regards to what part I'm writing any given day, Scrivener has been absolutely perfect.
Will I change again, when some other format presents itself? Hard to say. I know that any form of cloud-based writing holds very little appeal to me. Perhaps that's because I'm already gypsy enough with taking my laptop anywhere, but also because I like the files I'm working on to actually be on the computer I'm using.
But things may someday reach a point where I'm a dinosaur with my dying MacBook Pro, typing into outdated Scriviner files with the antiquated "keyboard", telling all you kids to get off my lawn.
----
*- Seriously. I went to a day camp as a child that let you sign up each day for your afternoon activity. While most children signed up for "soccer" or "swimming", yours truly, at the tender age of eight, signed up for "typewriting". And I'm pretty sure most of the other people in there were high school kids obliged to do it for summer school.
**- Mine was "MARMAR". My friend Dan Fawcett was "FAWDAN". Ken Chang was "CHAKEN". You can see how they stayed up all night coming up with the system here.
At some point around when I started college, I switched over to WordPerfect for Windows, which I mostly used on my dad's computer, since it would have made my 8088 explode. This did create a challenge in the college computer labs later, which all used-- I want to say WordStar for Windows, but it might have just been Mircosoft Word-- but the important thing was, NOT WordPerfect, and trying to transfer a *.WPW into one of those formats was an exercise in futility.
Ah, the early days of computer usage.
As a matter of fact, the process of transferring archives from one computer to another, regardless of utility, means I still actually have some *.WPW files on the laptop I'm currently working on.
Eventually, I switched over to Microsoft Word, once I got a desktop that could handle it, and pretty much stayed with it for quite some time. And that was handy, because it was a format I could use on computers at home and at work, and plenty of early writing was done on that. Even going back and forth between using PCs and Macs didn't impede me. Portability of projects was a very crucial thing for me.
Trunked novels "Fifty Year War" and "Crown of Druthal", as well as many plays, unfinished projects, and the early drafts of Thorn of Dentonhill, Holver Alley Crew and Maradaine Constabulary were all written on Word. And while I never had a problem with Word, the challenges of writing an entire novel on it were quite clear.
And thus, eventually, I went, heels dragging, to Scrivener. Which now that I'm here, I totally love it. I won't lie, it had a bit of learning curve that I resisted. But the process of transferring the drafts of those three novels so I could rework them into Scrivener taught me how it could be a valuable resource to me. Especially in terms of keeping all sorts of character and outline and conceptual information in one place, and being able to visualize the scope of the story.
And in writing Banshee, where I've been jumping around like crazy with regards to what part I'm writing any given day, Scrivener has been absolutely perfect.
Will I change again, when some other format presents itself? Hard to say. I know that any form of cloud-based writing holds very little appeal to me. Perhaps that's because I'm already gypsy enough with taking my laptop anywhere, but also because I like the files I'm working on to actually be on the computer I'm using.
But things may someday reach a point where I'm a dinosaur with my dying MacBook Pro, typing into outdated Scriviner files with the antiquated "keyboard", telling all you kids to get off my lawn.
----
*- Seriously. I went to a day camp as a child that let you sign up each day for your afternoon activity. While most children signed up for "soccer" or "swimming", yours truly, at the tender age of eight, signed up for "typewriting". And I'm pretty sure most of the other people in there were high school kids obliged to do it for summer school.
**- Mine was "MARMAR". My friend Dan Fawcett was "FAWDAN". Ken Chang was "CHAKEN". You can see how they stayed up all night coming up with the system here.
Labels:
Banshee,
process of writing,
tools of the writers,
writing
Thursday, December 12, 2013
Perils of the Writer: Clavicle and other crucial word choices
This week's work on Banshee brought me to an interesting point, somewhat unintentionally. In brief, my main character, Lt. Samantha Kengle, was injured on a mission (a nasty creature managed to bite her on the neck). She loses consciousness, and when she comes to, she's being treated.
Initially I wrote that she would wake up with her uniform coat off and one of the aliens pressing her hand to Kengle's bare chest. (Said alien can essentially function as a living diagnostic scanner).
But then it hit me about the unintended implications behind that. Sure, it's medical, but the point is my one female human character gets stripped down while unconscious, and wakes up being groped. Sure, groped in a medical fashion by a female fish-alien, but still. I had put in a layer of sexual vulnerability that I had never intended, and it rested largely on the word "chest".
I re-thought the scene. I needed the alien to be able to get at bare flesh and the injury, but keep it professional. Leave no doubt, no subtext, that what was happening was anything other than medical treatment.
So I changed "chest" to "clavicle". Made no difference in terms of the text of what was happening, but pulled away the subtext I wanted to avoid.
I'm not going to get all, "words are important, words have power", because I'm sure you all know that. But word choice is crucial, and sometimes we make strange choices-- subbing in a not-entirely accurate synonym to avoid repetition, going for an uncommon word to avoid a common one. And sometimes the words we choose have unintended consequences.
Fortunately, this time, I think I sidestepped it. But there may be other ones that I'll fall into.
Back to the word mines for now...
Initially I wrote that she would wake up with her uniform coat off and one of the aliens pressing her hand to Kengle's bare chest. (Said alien can essentially function as a living diagnostic scanner).
But then it hit me about the unintended implications behind that. Sure, it's medical, but the point is my one female human character gets stripped down while unconscious, and wakes up being groped. Sure, groped in a medical fashion by a female fish-alien, but still. I had put in a layer of sexual vulnerability that I had never intended, and it rested largely on the word "chest".
I re-thought the scene. I needed the alien to be able to get at bare flesh and the injury, but keep it professional. Leave no doubt, no subtext, that what was happening was anything other than medical treatment.
So I changed "chest" to "clavicle". Made no difference in terms of the text of what was happening, but pulled away the subtext I wanted to avoid.
I'm not going to get all, "words are important, words have power", because I'm sure you all know that. But word choice is crucial, and sometimes we make strange choices-- subbing in a not-entirely accurate synonym to avoid repetition, going for an uncommon word to avoid a common one. And sometimes the words we choose have unintended consequences.
Fortunately, this time, I think I sidestepped it. But there may be other ones that I'll fall into.
Back to the word mines for now...
Labels:
Banshee,
perils of the writer,
process of writing,
writing
Monday, December 9, 2013
A Rare Moment of Blatant Plugging: Give the Gift of Texas this Christmas
Folks: Christmas is coming, and I'm busy keeping balls in the air this week, so let's keep this short and sweet.
What are you giving your Science Fiction reading friends and family for Christmas this year? Consider the merits of giving Rayguns Over Texas, a compilation of science-fiction short stories entirely by Texas writers.
It's quite an impressive line-up of writers and stories, if I do say so myself.
What are you giving your Science Fiction reading friends and family for Christmas this year? Consider the merits of giving Rayguns Over Texas, a compilation of science-fiction short stories entirely by Texas writers.
It's quite an impressive line-up of writers and stories, if I do say so myself.
- “Pet Rock” by Sanford Allen
- “Defenders of Beeman County” by Aaron Allston
- “TimeOut” by Neal Barret, Jr.
- “Babylon Moon” by Matthew Bey
- “Sovereign Wealth” by Chris N. Brown
- “La Bamba Boulevard” by Bradley Denton
- “The Atmosphere Man” by Nicky Drayden
- “Operators Are Standing By” by Rhonda Eudaly
- “Take a Left at the Cretaceous” by Mark Finn
- “Grey Goo and You” by Derek Austin Johnson
- “Rex” by Joe R. Lansdale
- “Texas Died for Somebody’s Sins But Not Mine” by Stina Leicht
- “Jump the Black” by Marshall Ryan Maresca
- “An Afternoon’s Nap, or; Five Hundred Years Ahead” by Aurelia Hadley Mohl
- “The Nostalgia Differential” by Michael Moorcock
- “Novel Properties of Certain Complex Alkaloids” by Lawrence Person
- “The Chambered Eye” by Jessica Reisman
- “Avoiding the Cold War” by Josh Rountree
- “The Art of Absence” by Don Webb
Thursday, December 5, 2013
Perils of the Writer: Hooks and Investment
Let's talk for a moment about Marvel's Agents of SHIELD, possibly the biggest disappointment of the current season of television. And it was the biggest disappointment because the expectations were set high: take the biggest hit of big screen of 2012, a movie which successfully integrated the worlds of multiple movies to create a mega-star movie, and have the acclaimed and beloved writer/director of that movie helm a new show to explore the deeper nooks and crannies of the greater Marvel cinematic universe that a movie couldn't take the screen time to do.
How could it fail?
If I may be so bold, I'd suggest that it failed with its hooks. Namely, it treats its characters as its biggest hooks, when those characters are not hooking the audience at all. And it feels like it considers it's big hook-- its setting-- as more of an albatross than advantage. One of the executive producers was even quoted saying something like, "You shouldn't be looking for easter eggs".
Now half a season in, its somewhat clear that what we are seeing is not the "growing pains" of a genre show finding its feet. Rather, we're seeing the very show the creators want to do: in essence, a brighter, less skeptical* X-Files.
And that isn't hooking.
Now that's always the challenge a writer faces: that the characters that you love, these hooks that fascinate you... well, that it's just you. No one else is going to invest in it like you do.
And this is especially true with genre writers. We spent hours upon hours drawing maps and hashing out centuries of history. We are deeply, deeply invested in our work, even if the quality of the work itself doesn't match the passion behind it. I can't tell you how many manuscripts I've read for critiquing purposes that, while the writing didn't hold up, the love was practically pouring off the page.
I didn't get into the story, but I knew that the writer was utterly in love with it.
And, frankly, the craft can be improved, if the love is there.
---
*- By "less skeptical", I mean when they're investigating hovering bodies or apparent telekinesis, they approach it as you would in a world where superheroes beat off an alien invasion in downtown New York: as the sort of thing you have to accept happens now.
How could it fail?
If I may be so bold, I'd suggest that it failed with its hooks. Namely, it treats its characters as its biggest hooks, when those characters are not hooking the audience at all. And it feels like it considers it's big hook-- its setting-- as more of an albatross than advantage. One of the executive producers was even quoted saying something like, "You shouldn't be looking for easter eggs".
Now half a season in, its somewhat clear that what we are seeing is not the "growing pains" of a genre show finding its feet. Rather, we're seeing the very show the creators want to do: in essence, a brighter, less skeptical* X-Files.
And that isn't hooking.
Now that's always the challenge a writer faces: that the characters that you love, these hooks that fascinate you... well, that it's just you. No one else is going to invest in it like you do.
And this is especially true with genre writers. We spent hours upon hours drawing maps and hashing out centuries of history. We are deeply, deeply invested in our work, even if the quality of the work itself doesn't match the passion behind it. I can't tell you how many manuscripts I've read for critiquing purposes that, while the writing didn't hold up, the love was practically pouring off the page.
I didn't get into the story, but I knew that the writer was utterly in love with it.
And, frankly, the craft can be improved, if the love is there.
---
*- By "less skeptical", I mean when they're investigating hovering bodies or apparent telekinesis, they approach it as you would in a world where superheroes beat off an alien invasion in downtown New York: as the sort of thing you have to accept happens now.
Labels:
Avengers,
genre,
perils of the writer,
process of writing,
sff,
writing
Monday, December 2, 2013
Perils of the Writer: Disasters Big and Small
Little things can throw kinks in your day. A speeding ticket throws you ten minutes behind (and a minor headache to deal with). Ten minutes behind means you're now in the worst thicket of traffic that you had hoped to avoid, making that ten minute drive to your destination take twenty-five. Being late means you have to play catch-up, forcing you to miss lunch. The drop in blood sugar makes you slower, leaving you a pile of work that you have to take home that night. That takes up your whole evening, and what time is left for you to squeeze some writing in?
None.
Unless you sacrifice your sleep, and thus oversleep in the morning, come in to work late again, etc. etc.
And what happens when you have a real disaster?
Be it a minor, personal disaster (a grease fire in the kitchen, a fallen tree through the bedroom window, a leak in the bathroom necessitating ripping open the walls) or one's own story within a greater disaster (a flood or tornado tearing through one's home)-- disasters change our expectations of how the rest of our day, week, month, even life are going to go.
And while it's incredibly inconvenient, it's also the underlying source behind great drama in writing.
First off, the thing that comes to mind is the immediate, quick decisions that need to be made in the face of disasters. How we (or our characters) react when disaster strikes define us.
But once a disaster has hit, and the immediate repercussions have been felt, what next? For me, the thing I always start thinking about is the small details. For a personal example, the thing that sticks with to me (in the case of the bathroom one, which happened to us a few years ago) was less the big work of having to have the bathroom remodeled, but the steps we took to minimize dust from the remodel from covering the rest of the house, and cleaning off the bits and pieces of personal items that did get covered.
Stuff like that sticks with you-- sometimes literally, as you find something that got missed weeks later-- and as I work on Banshee, a story that is quite populated with disasters, and how each character deals with the big and small of the disasters that befall them.
Time to jump into the wordmines. See you when I get out.
None.
Unless you sacrifice your sleep, and thus oversleep in the morning, come in to work late again, etc. etc.
And what happens when you have a real disaster?
Be it a minor, personal disaster (a grease fire in the kitchen, a fallen tree through the bedroom window, a leak in the bathroom necessitating ripping open the walls) or one's own story within a greater disaster (a flood or tornado tearing through one's home)-- disasters change our expectations of how the rest of our day, week, month, even life are going to go.
And while it's incredibly inconvenient, it's also the underlying source behind great drama in writing.
First off, the thing that comes to mind is the immediate, quick decisions that need to be made in the face of disasters. How we (or our characters) react when disaster strikes define us.
But once a disaster has hit, and the immediate repercussions have been felt, what next? For me, the thing I always start thinking about is the small details. For a personal example, the thing that sticks with to me (in the case of the bathroom one, which happened to us a few years ago) was less the big work of having to have the bathroom remodeled, but the steps we took to minimize dust from the remodel from covering the rest of the house, and cleaning off the bits and pieces of personal items that did get covered.
Stuff like that sticks with you-- sometimes literally, as you find something that got missed weeks later-- and as I work on Banshee, a story that is quite populated with disasters, and how each character deals with the big and small of the disasters that befall them.
Time to jump into the wordmines. See you when I get out.
Labels:
Banshee,
perils of the writer,
process of writing,
writing
Subscribe to:
Posts (Atom)