It's Okay to Write Slow

J. K. Rowling took five years to write the first Harry Potter.

It's okay to write slow.

Those of us who take a year or more to draft a novel are tempted to believe we're doing something wrong. Like we're too lazy, managing our time wrong, editing our words too much, or (God forbid) not meant to be writers at all. Some of those things might be true, but slow writing doesn't prove it.

(Terry Pratchett wrote his first novel at 400 words a day.)

You might be climbing a learning curve. My first novel took me 5 years to draft, 2 to edit. My second took me two years total. It's still slow, but I'm getting better. You will too. That's what practice does.

(The Harry Potter series took an average of 2 years per book to write.)

You might be a planner. Natalie Whipple can tell you that fast drafts don't mean finished products. They need a lot of editing after they're "done." Not that slow drafts are perfect, but sometimes slow can mean cleaner.

(George R. R. Martin took 6 years to finish the latest Song of Ice and Fire book. I still bought it.)

You might be unpublished. There are really only two reasons you have to write fast: (1) you signed a contract with a deadline or (2) you write to put food on the table. The rest of us have the freedom to write at whatever pace we want, learning as we go.

(Susanna Clarke took 10 years to finish her debut novel, which won some awards and got optioned for a lot of money.)

You might have a life. Maybe you have a full-time job, a family, and an X-Box. Kids are a full-time job on their own (I know, I have ten) and worth more than a publishing contract. Not that you shouldn't go for the contract too, but if you're sacrificing writing speed to play Guitar Hero with your daughter, I call that a win.

There are reasons writing can take a long time, many of them good.

Live life. Write slow.

(remixed from a guest post I did for Natalie Whipple)

5 Tips for Using a Foreign Language Without Sounding Like a Prat

Foreign languages are hard to use in fiction. Probably because most of us don't use them in real life. Here are some tips for helping the reader get that foreignness is happening, without feeling hit over the head by it.

1) USE LANGUAGE TO BE UNDERSTOOD. First and foremost, the purpose of speaking is to communicate ideas. So if a character is fluent in both English and Thai (say), but her listeners understand only English, she won't toss Thai words into her speech. If someone did that in real life, we'd think they were just showing off their knowledge. And (big surprise) that's how it comes off to the reader too -- like the author is showing off some language they picked up on their trip around the world.


2) THINK LIKE THE CHARACTER. If the character isn't fluent in English, then there will be words for which their native language comes to mind. Such a character may correct herself, which not only sounds natural, but gives you a natural way to translate what she says:

"Come on! We have to hurry to catch the rotfai. The train."

If her listeners are also bilingual, she wouldn't correct herself at all (this is called code-switching; it happens in our house a lot). In this case, you'd have to provide the translation some other way, either through direct telling or (better yet) through context -- assuming you need the translation at all.

She clapped her hands. "Children, our guests will be here soon. Gep your toys. Reoreo!"

3) DON'T MAKE THE READER READ UNINTELLIGIBLE GIBBERISH. What if you've got a character who only speaks Thai? Is it cool to drop a whole string of Thai on the reader then? Take a look at this example and see what you think:

The door flew open with a bang. Four masked men ran in, guns pointed at Bernice and her family. "Lukkheun!" one of them shouted. "Lukkheun diawnii!" She didn't know what they were saying, just put her hands on her head and sobbed. "Tah mai lukkheun diaw ja ying kah man. Ow mai! OW MAI!"

This isn't bad until that last sentence. Shoot, I speak Thai, and even I got bored parsing it. And if you don't speak Thai, you'd get no meaning from it at all. Let's revise it so it still conveys foreignness and Bernice's terror, without forcing the reader to slog through a bunch of meaningless phonetics:

The door flew open with a bang. Four masked men ran in, guns pointed at Bernice and her family. "Lukkheun!" One put a gun barrel to her temple, shouting in a language she didn't understand. She didn't know what to do. She put her hands on her head and sobbed, but it only made him scream louder. What did he want from her?

4) PUT FOREIGN WORDS IN ITALICS. This goes along with not making the reader work. Italics signal the reader that these are words they don't necessarily have to know (also that they're not typos). This even goes for words that you think everybody should know.* A good rule of thumb: if it's not in the English dictionary, italicize it. For example:

"You're hungry? No problema, I'll pick up some burritos."

* I've noticed this problem especially with Californians (like me) who assume everyone took Spanish in high school (like me). Also with British authors and French. Guys, I'm American, I don't speak French.


5) USE FOREIGN ACCENTS SPARINGLY. You've probably read stories where a character's foreign accent was annoying or really hard to read. It's hard to do right, but the general rule is: be subtle. Imply the accent rather than hit the reader over the head with it.


TO SUM UP, if you're using foreign languages in your fiction:

1. Don't do it just to show off.
2. Be intentional; think like the character.
3. Be subtle.

Got any other tips? Annoyances with how some authors handle it? Tell us about it in the comments.

(remixed from an older post)

First Impact: FATHER'S DAY by Hilary Swann

It's time for another First Impact Critique, where I take a look at your queries, first pages, back cover copy, etc. You want to make an impact right from the start, and we're here to help you do that.

If you'd like to submit your first impact material, send it to firstimpactAE@gmail.com. Details here.

Remember, anyone who leaves a critique in the comments is eligible to win a 15-page critique from INCARNATE author, Jodi Meadows. Your critique doesn't have to be long, just useful.

---

We have a short one this week: a picture book query from Hilary Swann. My inline comments are to the side, with overall thoughts at the end. Everything here is just my opinion. Your mileage may vary.


Query

I think even with such small word
counts, you're still supposed to
round to the nearest hundred.

Mia wants to celebrate Father's Day, but with two moms and no dad she doesn't quite know how. When her mom suggests making the day special, Mia has brunch, goes ice skating, and meets other families: some with dads and some without. Father's Day is story about embracing your family no matter what shape or size. It is 567 600 words.

  

Thank you for your time and consideration.


Adam's Thoughts
I have to start by saying I haven't seen a lot of picture book queries. I believe you usually submit the entire manuscript along with the query, and so the query is more like a cover letter. Mary Kole over at KidLit.com seems to agree with me.

But that doesn't mean the query isn't important. This looks really short, but I have to admit, I like this concept and would read this.

The only thing I think you could add is a little more meat about the middle. Does she have brunch and go ice skating by herself? Does she do anything with the other families? Don't go crazy, because I think this already does its job: entice the agent or editor to read on.

What do the rest of you guys think? Would you read this?

AFK

I'm in a mountain village (this one), and far away from my computer. So here's a picture of a cat.

I love the internet.

US Marines, circa 42012 A.D.

From Anthdrawlogy's Independence week. This one wasn't posted on the blog of any famous authors, but it's still one of my favorite drawings.

First Impact: GRIMOIRE by Marcy

Time for another First Impact critique. Remember, anyone who leaves a critique in the comments is eligible to win a 15-page critique from author Jodi Meadows.

And this feature can only continue with your submissions! If you have a query letter, first page, or even back cover blurb you'd like critiqued, send it to firstimpactAE@gmail.com. Details here.

---

Thank you, Marcy, for letting us take a look at your YA Historical Paranormal. As always, this is just my opinion. You are welcome to disagree.


Chapter One ~ February 1805

The last sentence threw me off on my
first read. I think the problem is the
first sentences are a bit misleading.

It was a fine day for a sale, brisk but sunny; -- a good day for traveling, as evidenced by the crowd in the lane. Most came to buy. Some came out of curiosity. But none of them noticed her sitting in the hall, left with nothing but a single trunk.

I love this paragraph. Great voice.
Great emotion. Totally draws me in.

Arlen watched them, blinking back furious tears, winding her fingers together so tight it hurt. She itched to slap their hands away from whatever they touched, snatch back what they'd bought. How dare they? These were her things!

Except they weren't.

Not anymore.

How long ago did this happen? How
fresh is her pain?

This last sentence is a bit awkward.

It had been an accident according to the coroner. Her parents, coming home from a dinner party in nearby Saxton Greene, were killed when their carriage careened into the pond at the entrance to the property. They were found with their driver all frozen and stiff the next morning when one of the kitchen maids walked in from the village.

And according to Mr. P. T. James Esquire, Ssolicitor to her father's estate, there was no money, therefore, nothing to bequest bequeath. In fact, the estate's debts were such that everything would have to be sold.

Now all the pretty things her parents had collected, the baubles and crystal lamps, the paintings in their gilt frames, the plants in the conservatory - even the lovely gown she was supposed to wear for her coming out ball - were walking out in the hands of strangers.

It was all she could do not to scream.


Adam's Thoughts
What a horrible day for Arlen. This is such a great start -- I'm feeling Arlen's pain and wondering what the heck is going to happen to her (does she become Batman? Please tell me she becomes Batman).

The only major thing I want to say about this is about the opening paragraph. It feels tricksy to me, but not in a good way. I like the irony of it -- that it's a nice day for a sale, but the sale totally sucks. But I don't like feeling like I was tricked into believing one thing, when the story's about another.

I also noticed a lot of little errors here and there -- misplaced commas, bad capitals, misused semicolons, etc. Not so much that I think you can't write (you obviously can, and well), but enough that I noticed.

On the one hand, I understand you shouldn't have to worry about these things until the meat of the story is polished. I get that.

On the other hand, I consider them to be our katas. Ultimately, we should be so familiar with them we don't even think about them anymore. We just do it right. I say this for everyone, myself included. Learn to care :-)

What do you guys think about this piece? Does the opening paragraph work for you? If not, how would you fix it?

How to Beat Your Fears

Step #1: Get in the ring.