Showing posts with label Devs. Show all posts
Showing posts with label Devs. Show all posts

Who's your favorite character you've ever written?

Jul 22, 2011

So I lied. I said I was going to do a post analyzing a popular movie with the plot structure I talked about on Wednesday. My brain is not functioning well enough on a Friday to pull that off, so instead, I want to ask a question.

Who is your favorite character you've ever written? Or, if that's too hard of a choice, who is one of your favorites?

I love all of my characters a lot, so it's a tough choice for me. But one of my favorites is Quinn from Devolutionaries. He's a smart, tortured pain in the rear. He spent most of his childhood as a science experiment, which explains the tortured part. He's bossy, secretive, and works his tail off to defend a cause he thinks is right. Though he isn't the main character, he is extremely important in the story. I think I love him so much because even when he's being stubborn, he's managed to struggle above his circumstances to try to do something good.

So, my friends, I repeat the question: who's one of your favorite characters you've ever written?

Working on Multiple Stories, or What to do with a Shiny New Idea

Jul 15, 2011

And, I'm back! The draft is done, I've written lots of letters to my bro, and I haven't finished the huge work project (darn). The fun summery adventure is taking place next weekend in the form of a zoo trip, and I'm ready to jump into edits for TUGL.

I mentioned in my last post that I got a shiny new idea for a story I'm calling Perception. I used to just write down SNIs and leave them alone until I was done with my current project. This time, though, I've let it simmer in my brain during this last week when I took a short break from TUGL. That means I'm currently querying one book, editing another, and planning a third. I never thought I'd be able to handle three stories in my head at once, but it's amazing what you can get used to. In fact, I'm finding that I kinda like having stories in different stages.

I've discovered a lot of benefits of working on more than one project. For one, it helped get my mind off TUGL this week as I worked on Perception. I always try to take small (and sometimes large) breaks from my WIPs between different stages, and having something else to work on really lets my brain clear of the story so I can go back to it with fresh eyes.

Another thing I've figured out is how much it helps to let new ideas simmer for a few months at least. With Devs, which I'm querying now, I got the idea and immediately jumped into the planning and writing. Then, at 30,000 words, I realized I was writing the wrong story and started completely over. When I got the idea for TUGL, I was still in the middle of rewriting Devs, so it percolated in my brain for months. I considered and rejected multiple ideas-- before I ever put them on the page. I got all that figuring out of the story done before I started writing, making the writing so much easier.

Percpetion will go back to simmer mode for the next few months as I dive into rewrites for TUGL. In dull moments, my brain will play with it, think of new ideas, throw them away, and find better ones. Then, when I'm ready to send TUGL to beta readers and take a break from it, Perception will be waiting for some action.

So, my friends, how do you handle shiny new ideas when they come at an inconvenient time? Are you working on multiple stories, or do you prefer to handle one at a time?

How to Dump Info without Info-dumping-- Writing Lessons from Inception

Jun 29, 2011

I am a nerd. As a kid, I spent my summers doing science experiments in my giant white science book. For fun. And to this day, I get excited about things like sea slugs that absorb plant DNA and become photosynthetic. I get weepy about the space shuttle's last flight. It's why I write sci fi-- because I'm a nerd, and I love all that science stuff.

Here's the thing about writing sci fi: there's a lot of science in it. Which means there tends to be a lot of necessity for explanation, which leads to a lot of potential info-dumps. This isn't unique to sci fi, of course. Most authors have a lot of information to convey, and sometimes we have no choice but to reveal large bits of it at a time, potentially boring our readers just so they understand what the heck we're talking about.

I had some trouble with info-dumps in Devs, and it took me lots of revisions to get it right. And some of the biggest lessons I learned were actually from the movie Inception. There's a LOT of information they have to convey, but the movie never lags in its pacing. Here are the things I learned to apply in my writing. (Warning-- there are a few small spoilers if you haven't seen it before!)

1. Early in the story, weave as little information as possible to keep your reader engaged.

Inception doesn't start with Leo DiCaprio's character Cobb explaining the ins and outs of shared dreaming. We start with tension-- he's trying to convince Saito that he needs to train his mind to not be vulnerable to idea theft. Here's the thing. We learn, in a few brief sentences of dialogue, that someone can steal your secrets through shared dreaming. And THAT'S IT. We don't know how it works, or who can do it, or the history behind why it was developed in the first place.

We know just enough that when we learn everything we're watching IS a dream, we get it. Maybe we don't understand why Cobb gets dumped in the tub to wake him up, but we get it enough to be invested and intrigued. It's the technique of weaving small bits of information into a scene so we get small bits instead of large chunks. And especially for the first 30-50 pages of a novel, that may be as much as you need.

2. Have a character who doesn't understand what's going on so someone can explain things to them-- and the reader.

Enter Juno-- er, Ariadne. She's new to the team. She doesn't understand any of the history or the hows and whys of dream sharing. The team teaches her all the ins and outs, and as she learns, so do we. This neatly evades the "maid and butler" dialogue of "As you know, your subconscious is represented by all these people," and "Yes, Cobb, and they will attack us if they sense something is wrong in the dream." It's natural for Ariadne to be learning it, so it's natural for us to learn it too.

3. Don't explain everything at once-- use small chunks in addition to weaving.

The first time Cobb takes Ariadne into the dream, we don't get all the information about how dream sharing works. We get small bits. We understand that the dream can be changed by the people sharing it, sometimes in fantastic ways, and that the subconscious of the person dreaming can become aggressive when it's messed with too much. And, very briefly, we see again Cobb's projection of his terrifying wife. We don't learn much about the other parts of shared dreaming, such as the use of chemists, or about what on earth is wrong with Cobb's deranged wife. These things are woven in later as scenes.

Which brings us to another point.

4. Information should always be revealed as part of a scene.

Aka, NEVER SIMPLY TELL THE READER. Paragraphs that say, "and this is the history of x, and this is how y works," are the exact definition of bad info-dumps. In Inception, every single bit of information is worked in as part of a scene. In other words, it is not just giving you information. It's developing character, deepening mystery, and furthering plot at the same time. It brings tension around the very information we're receiving, and we're so engaged, we don't even recognize it as an info-dump.

For example, the scene where Cobb risks going behind enemy lines to find Eames, we learn about how inception is possible, and we learn about the idea of a chemist and using dreams within dreams. All around this information is the tension of Cobb being potentially caught by people who want him dead. And then, when we have just enough information, we get some action as Cobb is chased through the streets of Mombasa. We are kept engaged because it's a scene in a story, not an aside of information.

So, my friends, do you have trouble with revealing information in your writing? What are some techniques you use? What are some books or movies that you think do this well? And, just because I'm curious, did you like the movie Inception?

Finding the Theme Song-- and I'm being interviewed!

May 19, 2011

Today I'm being interviewed on Chantele Sedgwick's blog! Go check it out and learn more about me (you know...if you're interested. :D) Chantele has a great blog-- her Weird Word Wednesday posts always give me a laugh while expanding my vocabulary.

AND my husband was playing random songs on YouTube yesterday, and this amazing song started. And I went, "OMG, Ash [the MC in Devolutionaries] would love this!" And it became the theme song for Devolutionaries. It's a little scary how excited I am about it. Who knew the story would become a little more real to me with this song? So without further ado, I give you Uprising by Muse. (Sorry, it won't let me embed it.)

So, my friends, do you have theme songs for your stories? Anything you listen to that gets you in the writing mood?

The Tug of Two Stories

Apr 9, 2011

My writing progress for the last week or so has been sort of dismal. I'm crawling through edits on Devs right now at a much slower pace than I'd prefer due to a drated sinus infection (will the winter never end??). I think I'll still meet my end-of-April deadline, though, so I'm not too worried.

Instead of working away at Devs these last few weeks, I've actually been thinking a lot about what's coming next. I fully intended to work on The Unhappening of Genesis Lee once Devs is done.

Except.

I got a brilliant idea for Black and Blue, the story on hiatus. And now I have a problem. I LOVE the story of TUGL, and it's begging to be told. But I'm having trouble getting into my main character. With BaB, I LOVE my main character, but am still having some trouble with the story.

I've never had two stories warring for my attention this way. I've written the first three chapters of both of them, and just don't know which one I love more. Any advice, my friends?

Strengthen your Story: The Art of Lingering

Feb 1, 2011

I've got several awesome beta readers dutifully plugging away at Devolutionaries. I've even gotten feedback from a few already. And it's amazing to me how incredibly helpful it is to have readers who have never seen the story give their thoughts.

Two of those awesome readers (hi Hannah! Hi Teralyn!) mentioned something that got me thinking quite a bit. They said to take some more time on certain moments. Let the character experience that twist, feel the emotion-- because the reader will too. I thought back to a blog post I read ages ago (I wish I could find it again!) about letting moments linger.

There are certain points in your story that need to linger so the reader can feel their full power. Moments of great change or emotional impact. If those moments are passed by too quickly, they lose their impact.

Movies often do this by slowing the cinematography-- literally letting a moment linger by putting it in slow motion, or just letting the camera linger. Like in the newest Pride and Prejudice, when Darcy is striding across the misty field toward Elizabeth. The camera focuses on him for longer than a normal shot, allowing the audience to take in this moment where he's coming back to Elizabeth. It is thoroughly swoon-worthy (I'm getting fluttery just thinking about Matthew McFadyen in the mist with that billowing coat and open shirt). And the swoon is stronger because the camera lingered, letting the audience soak in that moment.

Lingering is useful not just to heighten the impact of a moment, but to deepen your character. Lingering on your characters thoughts, feelings, and reactions shows your reader what kind of person he/she is. It's also a moment for your reader to connect to your character through their own emotional reaction. I like to think of lingering as the action/reaction (or scene/sequel) sequence on a smaller scale.

So I'm putting that on my list of further revisions for Devs: let it linger. And I'm all kinds of excited about the possibilities.

So, my friends, what can you do to let it linger in your stories? What are some of your favorite lingering moments, either of your own or in another book or movie?

P.S. The awesomeness is coming. This Friday. You won't want to miss it.

It Is Finished...and a Hint of Upcoming Awesomeness

Jan 26, 2011

I. AM. DONE.

Whew! As of 12:43 a.m. this morning, Devolutionaries is finished and ready for beta readers. Which of course means it's not really finished, but it's finished enough that I'm calling it done. I celebrated with an exhausted "woot" and went straight to bed.

But now I'm awake enough for a full-on WOOT!!! And even a YAY!! And I'll add a YEE-HAW!! for good measure.

I'm afraid that's about all the blog post you're gonna get from me today...except for me to casually and slyly hint that there is much upcoming awesomeness on this blog. Featuring awesome prizes. And warm fuzzy feelings. And you.

It's gonna rock your socks off.

Reading Til My Eyes Bleed

Jan 24, 2011

I'm reading Devs out loud right now, trying to hone my sentences. It's completely exhausting, and it's taking much longer than I expected. So if I'm sparse on the blog this week, it's because I'm reading 'til my eyes bleed.

And yes, it's worth it. I've made so many tiny changes that I never would have caught otherwise, and the book is all the better for it.

Here's my favorite line of the day:

Lainey glared at him. "You’re better than this, Quinn."

"Maybe I am," he said. "But maybe, to make the world safe, I have to be worse than I am."

The Show Must Go On

Jan 22, 2011

So I've got to admit, I'm at that point where I'm totally ready to give Devs a month break when it goes to beta readers. If I have to read/edit certain sections one more time, I'm going to rip my hair out.

Well, probably not. I kind of like my hair.

Regardless, I'm finding it hard to push through my last few edits. I'm pushing it, though-- I've got to finish my plot chart, fix any holes I find, and do an out-loud read through. The show must go on, right?

I'm allowing myself little breaks, though. Last night, I worked some more on TUGL, and I'm getting more excited about it the more I figure out. I've got my setting planned-- there's two main settings that simultaneously echo and contrast with each other, and are symbolic of the society itself. I've got my character relationships starting to work themselves into lovely complicated little knots. I've got my plot beginning to rise from the mud. I can't wait to give Devs a little rest and work on this one.

With any luck, once Devs is back from betas, I'll be eager to jump back into it. I do really love the story, after all. We just need a little space to redefine our relationship.

So, my friends, have you ever had to muscle through a story? Rediscover your love for it? How is your writing going right now?

And now, before I go, I'd like to say thanks to Rachna Chhabria for the Fair Dinkum award, and to Jodi Henry and Margo Kelly for the Stylish Blogger award! You ladies are awesome.



How to Write Humor That's Actually Funny

Dec 15, 2010

There's a character in Devolutionaries that's given me trouble from the beginning. I love him-- he's goofy and funny and knows how to lighten dark situations. In some ways, he reminds me of my husband. But that makes him a tough character to write, because that goofy, joking person is not me.

It's not that I don't have a good sense of humor. I just have a different sense of humor than Lucas, my character. In my first draft, sometimes I had to write "[insert funny line here]" in place of Lucas's dialogue. My husband helped me make him funnier in subsequent drafts, and I also thought a lot about some notes I took in a class on being humorous from funny-man Howard Tayler. Here are a few tips from Howard (with a little Shallee-extrapolation) on writing humor that's actually funny.

1. There are five elements to being funny (He said six, but I apparently missed one. Sorry.):

Be recognizable- if the audience doesn't know what you're talking about, it's not funny. Be sure to introduce context early on.
Be clever- This can be a hard one, but it doesn't necessarily mean to come up with something brand new. Find a little twist on something old. Think about your audience's expectations, and bend them.
Be bizarre- Pull something out of your hat that doesn't just bend expectations, it completely takes your reader by surprise.
Be cruel- Just a little. Make your humor wry and just a bit biting.
Be cute- Or sweet, or silly, or goofy. Slapstick is still funny as long as it's not the only type of humor you rely on.

The key is to try to hit as many of those as you can-- even within the same joke. Layered humor has a much stronger effect on your reader.

2. Leverage the audience's imagination. Let them tell themselves the punchline-- the more you explain the joke, the less funny it is. This makes the audience find humor from inside themselves that you might not have even intended.

3. Context is the most important thing to humor. Introduce the context of a joke early on, so the audience knows what to expect. Lucas's very first line makes the reader realize he's a goof, so they know what's coming every time they see him.

4. Point of view can change the type of humor you use. Something can be funnier depending on whose head you’re in. If you have multiple viewpoint characters, you may want to tell a certain scene from one point of view to change the humorous effect it has. In Devs, Lucas isn't a witty character, or a sarcastic one. He's just a goofball. Some of his quips are genuinely funny, and some are silly-- but they're made funny by his goofy personality. In setting up his character and point of view, I can make even stupid things funny through him.

So, my friends, any tips to share on how you write humor? Or any tips on what you find humorous when you read? What are some of your favorite books or movies-- comedy or not-- that have humorous moments you can learn from? Please share!

Conquering the Fear of the First Draft

Dec 10, 2010

I finally got started on the actual writing of BaB yesterday. It took me a while to dredge up the courage, actually.

Yes, courage. Starting in on a new first draft terrified me. Why? Because I'm horribly afraid it's going to suck.

Newsflash to me: Of course it's going to suck. It's a first draft.

But I still don't have a clear idea of what my protag wants, or what my antag wants. My outline and character sketches are crap. I can't start writing until I figure all that out!

Second newsflash to me: Remember how you're a pantser and it took you 20,000 words to figure that out in Devolutionaries?

Oh. Right. Deep breath.

It's funny how I'm somehow expecting myself to write the first draft of BaB to be as good as Devs is after 3 drafts. I just try to keep reminding myself that it's okay if this draft sucks. It's supposed to suck. And when it does and I'm done with it, I get the joy of creating something awesome out of the first 70,000 words of sludge.

So, my friends, what scares the daylights out of you when you write? First drafts? Final drafts? Queries? Characters? Pacing? Please share!

Rewards

Nov 23, 2010

I finished draft 3 of Devolutionaries! I'm excited, even though I still have to overhaul one character completely and de-nebulate my antagonist (because it/he is in a state of great nebulosity at the moment. Get it? Sigh...yes, I did fry my brain getting through this draft so fast.).

Still, I'm calling it a completed draft. As a reward, I finally bought Paranormalcy today.

And there's a gigantic blizzard predicted for tonight.

And I have hot chocolate, curry, candles, and fuzzy socks.

It's gonna be a celebration of blizzard-ic proportions!

So, my friends, what do you do to reward yourself for finishing any part of your WIP?

P.S. Happy Thanksgiving!

In the Home Stretch

Nov 19, 2010

Good news: I am within ten chapters of having my third draft of Devolutionaries finished. Woot!

Bad news: I only have a little over a week to finish those ten chapters in time for the full novel critique my crit group is doing. And hopefully still have time to enjoy Thanksgiving.

Ergo: I will be sparse on the blog for the next week as I gleefully hack out the bad and add the better to Devs.

So, my friends, how are your wips going? Are you NaNoers on track? What's your planned progress over the holiday week?

Cliffhanger

Oct 25, 2010

So, I know I said I don't usually do blogfests...but a cliffhanger fest was too irresistible to pass up! Check out the other entries here, and here is the 500-words-or-less cliffhanger for Devolutionaries, chapter 1!

Grandad closed his eyes a minute, like he was listening for something. “They’ve come for me.”

“Who?” My throat tightened in panic, and my voice came out in a quiet screech. I already knew who. “What are we going to do?”

“Listen. They’re not going to kill me, okay?”

But there wasn’t another option. Unless… “They’re going to Disappear you? How do you know that?”

“I just know.”

What was that supposed to mean? Nobody knew exactly why the Government Disappeared anybody, just that somebody would suddenly be gone. None of their things missing, no hint about what had happened. No sign of a struggle.

“How can you—“

“Doesn’t matter,” Grandad said. “You just have to know they’re going to keep me alive. And you have to stay that way if you want to help. Now, I want you to stay here, behind the door. There’s only one of them. He’ll come for me, and when he does, run. Somewhere with lots of people. Go to the arcade. Then find Jay.”

I glared at him. “I’m not taking off on you like Wes. If there’s only one, I can attack him when he goes for you.”

“No!” His voice was sharp. “There’s only one because they only need one. He’ll kill you if you try that. You run. Find Jay.”

Suddenly, he stood up straighter. Then he strode across the room and stood over the boiling pot. “Do it, kiddo.”

He smiled at me, and I felt a sharp pain in my throat.

The door flew open and I threw my hand up to keep it from hitting my nose. Footsteps, then a clanging noise, a splash, a stranger’s yell. In my panic, a hysterical giggle rose up. There’d be signs of struggle after they Disappeared Grandad. Something crashed, and wood splintered. A sharp pfft echoed through the room, followed by a dull thump.

The room went silent, raising the hairs on my arm. Had he shot Grandad after all? I risked a peek around the door. The agent was kneeling next to Grandad, pulling the needle of a tranq bullet from a blue-stained spot on Grandad’s shoulder. He was alive. I started breathing again.

The agent’s back was still to me. It was now or never. I swung the door forward and dashed around it. My heart didn’t seem to beat to a normal rhythm, and I ran wildly through the night. I tripped over pavement cracks, darted into side streets, and skirted the corners where the military police clutched their guns. My feet pounded forward, and I grabbed at the pain growing in my side.

I stopped a few blocks from the arcade. Sucking in big gulps of air, I sank to the ground. I dropped my head between my knees. My mind buzzed, and thoughts didn’t stay long enough to register. Only two things made sense, and they pounded in my head with every gasping breath. Grandad. Disappeared.

Some people said Disappeared was worse than dead.

Devolutionaries-- First 250 Words Blogfest

Oct 16, 2010

Here's the first 250 words of Devolutionaries. Please feel free to give any thoughts you have! I have a thick skin. :)

Name: Shallee McArthur
Title: Devolutionaries
Genre: YA dystopian

Grandad lied to me a lot. I’d known that for a long time. But standing at the counter at the Distribution Center, I decided everybody lied.

“You only gave me four potatoes,” I said.

“Well, you only gave me four Produce coupons.” The clerk tossed her braid behind her shoulder. She smiled, making her pox scars wrinkle across her face. Was she flirting with me while she cheated me?

I ignored the smile. My eyes went to the shelves that stretched behind the counter, piled high with tin cans and semi-fresh produce. Including two more potatoes that should be mine.

“I gave you six coupons.” I glared at her through the damp brown hair hanging in my eyes. The ceiling fans circled above me, totally useless.

Her smile faded. “Maybe you dropped some. I only counted four.”

“Look, my boss doesn’t give me enough—“ I clamped my mouth shut.

Working in Kessler’s bike repair shop should have given me more coupons than it did, but Scavengers had an unspoken rule. We didn’t rat each other out to the Government. I didn’t want Kessler’s death on my head.

I glanced toward one of the military policemen in his blue uniform. He scanned the silent line of people that trailed out the door and bounced the butt of his automatic rifle in his pox-scarred hands like he was bored. Nobody made a sound under his watch. Most of them stared at the scuffed tile floor.

I turned back to the girl, who'd gone pale.

Today

Sep 25, 2010

Today, my friends. Today is the day.

The day I finished the first draft of Devolutionaries! Bwah ha ha ha ha ha ha!!!

Think of me jumping in crazed wild circles around the house. Even though I'm not 'cause it'll wake Gooser (the baby).

Okay. Breathing. I'm a little excited. Boone (my hubs) even gave me a round of applause.

And really? I totally deserve it! Even though I already know at least twelve places where it sucks, the completion of the first draft is utterly applause-worthy.

P.S. You all rock. Contest of 100 awesome followers begins on Monday, so stay tuned!

How a Minor Character can Make or Break your Plot

Sep 15, 2010

I'm getting so close to completing the first draft of Devs. Like, within 15,000 words-ish. Last week, I was sure I'd have it done by the end of this week. And then, something happened. You know when you're writing a scene you know is crap, but you just don't know what else to write? Yeah, that's what happened.

So I stopped for a few days, trying to figure out what wasn't working in that scene. I realized it actually wasn't that scene that was the problem-- it was one in the previous chapter. One where a minor character suddenly became incredibly important without me even realizing it. His actions would drive a good deal of what happened next, and his actions in that scene were...well...stupid.

After a while, I figured out what the core of the problem was: I had no idea who this character was.

He was a minor character, so I hadn't bothered to do much in the way of characterization. I usually fill out a big long document about my characters before I start writing, so I have an idea of who they are. This guy had no dossier. And while he's a minor character, he's a very important minor character. So I went in, figured out everything about him, and was shocked. He was a heck of a lot cooler than I'd realized!

Then I went in and pack-ratted two whole scenes. Out they went, and that problem scene got rewritten. Because now I knew who this guy was. I knew what he would do. And it causes major problems for my protagonist. Which is awesome, because now I know how the book is going to end!

So, my friends, the question is: have you had situations where a problem with a character created a problem in your plot? How did you fix it? Let's discuss!

Vacationing from Writing

Aug 10, 2010

I'm back from the fabulousness of Disneyland! Not only did I have a blast with my family and get to enjoy my son's constant excitement, I learned something interesting about writing.

It's good to take a vacation from it.

I got virtually no writing done on the vacation. (Duh, 'cause I was on VACATION!) I barely even thought about my wip. And then something amazing happened. When I started revving up my writing gears again, everything seemed so clear. I could see how my pacing was off. I realized where my character development was lacking. I knew which scenes I needed to tweak to bring in things that were missing.

In other words, I got perspective. After a week of zero writing-related thoughts, I came back to my story seeing it as a whole. Not only did that give me a better idea of what things to fix in a future rewrite, but it helped me better understand where to go next.

I always knew it was good to take a break from your work once you're done with it. Who knew a mid-wip break could be just as helpful?

When to Ignore Writing Advice

Jul 27, 2010

There have been several posts today on writing advice-- both the good and the bad. This is still one of my own favorites I've ever received.

I've gotten a lot of "advice" over the years, in the forms of classes, critiques, conferences, and blogs. My head overflows with the shoulds and shouldn'ts, the dos and do nots. And much of it, I'd even say most of it, has been very good advice. If it isn't, it usually doesn't take too long to figure that out.

There's a problem though-- it's just too MUCH.

I had another panic moment with Devolutionaries the other day in which I was sure my first chapter sucked. It didn't do this, and it didn't do that, and therefore, it failed! Except, I really liked my first chapter... Again, it was my wonderful hubby who reminded me that I am the writer of this story. I'd become so entrenched in a few of those "rules" I forgot that this story is mine. It doesn't have to follow anyone's rules. If it works, it works.

I once heard someone say that writing classes are turning all writers into the SAME writer. Now, I don't necessarily think that's true either. But I think it's important to remember that, despite any advice you've ever received, you are the writer. It's your story. Listen to the advice, but listen to yourself.

Sometimes, you can come up with your own best advice.

Hey, it could happen

Jul 21, 2010

On my research trip to Dugway, I got probably the greatest thrill of my writing life (not counting acceptances of stories). The guide was introducing everyone on the tour, and when she got to me, she announced, "This is Shallee McArthur. She's an author."

Just remembering it gives me a buzz.

I've always dreamed of being an author, starting from about age 5. So to be introduced as one, to be declared "legit," as it were, was a dream come true.

Dreams are part of who we are as writers (authors!). I have dreams of my book being used in high school English classes, or of a person at a book signing telling me how my book changed their life. I want my books to mean something to other people. I want to write something that touches someone's life the way so many books have touched mine.

Some of my dreams are silly, even vain. (Is it okay to be a little vain about my writing dreams? I do spend an awful lot of time being humbled as a writer, so I'm going to say yes.) You know how big-time authors claim they hate getting the "Where do you get your ideas" question? I've always wanted to get that one.

"Mrs. McArthur," an adoring fan will ask, "how do you get your ideas?"

I'll smile, and answer: "Ideas come from all around me. Sometimes in the quiet moments, like when I'm in the shower, or in noisy ones, like when I give my son a bath. I got the idea from Devolutionaries from watching an episode of Fringe.* It's important to remember, though, that ideas are common. What really matters is turning your ideas into a kick-butt story."

Of course, this assumes I'll have adoring fans, but it could happen! It's something to cheer me up when I get another rejection for the short story I've been shopping around, at least. (Numero dos for rejections on that one.)

Now, I want to know: what are your writing dreams? Whether they be serious, silly, or vain, let's hear them!

*In Fringe 2:21 (Over There part 1), Walter says: "We all had these abilities, until there was a moment in history when something was done to us and it was shut down. I suspect aliens." I'm willing to bet that a dozen people could hear that quote and all come up with different ideas and stories!

 
Shallee McArthur © 2013 | Designed by Bubble Shooter, in collaboration with Reseller Hosting , Forum Jual Beli and Business Solutions