Showing posts with label advice. Show all posts
Showing posts with label advice. Show all posts

Thursday, October 11, 2012

Something fishy this way comes


My family reads books aloud the way some families watch TV.  We don't have a TV, you know.
(Ooh, conservative-homeschooler-snob alert! Blare the alarms!)

We've been doing it since I was three and my mom began reading through the Little House on the Prairie series.  In the following fourteen years, we've made our way through The Swiss Family Robinson (blech), Old Yeller (amazing), Around the World in Eighty Days (great), The Yearling (twice!), Anne of Green Gables, A Little Princess, Treasure Island, From The Mixed-Up Files of Mrs. Basil E. Frankweiler, (love that one!) Robinson Crusoe, Gentle Ben, Oliver Twist, Journey to the Center of the Earth (don't ask...), The Cabin Faced West, Toby Tyler, Little House on the Prairie (again), and way too many others to count.  We're in Carry On, Mr. Bowditch right now, in case you're curious.

By now you're probably glancing back at the post title and asking, what does all this have to do with fish?  And what on earth does it have to do with writing?

Be patient.  I have to have an introduction, don't I?  Grab your attention and all that.

So I like fish.  I really, really like fish.  But I like them on a plate and not in the pages of a book.
(I mean that FIGURATIVELY, peeps.  Do you honestly think I've opened books to find flattened salmon squished inside them?  Please.  Peanut butter and jelly, yes, fish, no.)

Four or five years ago, my dad read aloud 20,000 Leagues Under the Sea to our family.  It was pretty good as far as Jules Vernes' science fiction goes-- better than Journey to the Center of the Earth (we didn't even finish that one) but not as good as Around the World in Eighty Days.  The premise of the story is fascinating-- it's all about this crazy guy named Captain Nemo who built himself a submarine, a marvel of engineering, in which he lives all the year round, hiding from the world in the depths of the ocean.  Oh, and he stabs ships with the submarine.  Did I mention it has a tusk thingy? He's actually become the enemy of pretty much the entire seagoing world: navies from dozens of countries are bent on finding Nemo and getting him to stop his unexplained ship-stabbing.

The book is told from a professor's point of view, an ordinary man whose ordinary ship sinks in the Atlantic. He and two of his friends are--quote, unquote--rescued by Captain Nemo and permitted to stay on the submarine, known as the Nautilus.  (It's chambered, by the by.)  Captain Nemo's mysterious existence fascinates the professor, whose name escapes me, and the professor and his friends are most curious to find out who this man is and why he does what he does.  They travel all over the ocean floor together, and a lot of interesting things happen (I won't give too much away, I promise) but for a good deal of the time, the submarine just zooms along quietly and a great many fish swim by the windows.

Fish!  Fish! There they are at last!  Now we get to the fish!

If you've read 20,000 Leagues, you'll understand what I mean when I say that the fish descriptions are... lengthy.  If you haven't read it, let me endeavor to explain.  Imagine that Jules Verne is an overexcited five-year-old sitting at the breakfast table recounting a long and involved dream he had last night.  Now imagine that he has a book contract and is being paid by the word.  Add a shake or two of Fondness For Description, be sure to include a bit of Let Me Educate My Ignorant Readers, multiply by 100 and repeat ad nauseum.

Um, okay, so I exaggerated a wee bit.  BUT STILL.  The amount of fish description that goes into this book is unbelievable.  In some parts it reads like an adventure story, but in others it reads like a textbook on marine life.  And the marine life parts are about as boring as Mr. Woodhouse's grocery list (which, if you're interested, consists of oatmeal, oatmeal, oatmeal and skim milk).

But why?  What's wrong with description?  Why can't Jules Verne drone about fish and hold our attention at the same time?  Is there something wrong with fish?  Does Amy have something against fish?  Hmmmmmm?

Nope, there's nothing wrong with fish.  Or description for that matter.  The point I'm trying to make here is not that fish and endless description are bad, but that they are often unnecessary.  Fish are good.  Especially with lemon butter.  Description is good too... when properly used.  You can have too much of a good thing, you know.

Part of the appeal of a book (for me at least) is that a truly good one will make pictures in my head without any effort on my part.  (Laziness may have something to do with my enjoyment of that...) A truly good book will allow me to "see" what's going on by combining just the right amount of words.  Too much description tempts me to skip.  A mention or two of the heroine's beauty is fine, but if every other page contains a drawn-out harangue on her porcelain skin and fine golden hair, I'm going to start yawning.  (Listen up, Baroness Orczy.)  Too much politicking and sewer history is guaranteed to put anyone to sleep.  (I'm looking at you, Victor Hugo.)  An overabundance of subplots and the full family history of Mrs. Wiggleflipper's godmother's milkman is not always interesting reading.  (Do you hear me, Charles Dickens?)

You notice I didn't mention Jane Austen in that last paragraph... there's a good reason for that and it's called One Does Not Criticize Perfection.   Jane Austen left things to the reader's imagination.  Sure, she described from time to time.  But she didn't whap her readers over the head with twelve-sentence paragraphs about the luster and sparkle in Elizabeth Bennet's eyes-- she merely said that Lizzy had fine eyes and left it at that.  (Could she have described a little more? Probably, yes, but she did an amazing job with what she did describe and as I said before, perfection cannot really be improved upon, thankyouverymuch.)

Jane Austen herself said that she did not write for such dull elves as had not a great deal of ingenuity themselves.  (See, she was a poet, too.  I bet she did not know it, eh what?) That is to say, she did not believe in over-explaining-- and that, I think, is a key to good description.  Teddy Roosevelt was fond of the maxim, "Stand up, speak up, and then shut up."  I'm inclined to apply this to writing as well.  Certainly there is always a time and place for good, well-executed description, but a clear word-picture of a beautiful part of the ocean need not become a biology lesson.

Unless, of course, you're writing a textbook on fish.  In which case, have at it.

But most of us aren't.  So if you aren't writing a textbook on fish, leave fish out entirely.  Leave any and all superfluous windbaggery out, for that matter, or else you may be saddled with a finished product looking something like this...


Also fish.

Saturday, June 23, 2012

Short and Sob-worthy

I frequently refer to myself as a verbomaniac.  (Anyone who knows me in so-called 'real life' will understand.)  I'm wordy.  I tend to say in eighty words what could be said in eight.  Because hey, words are fun.  Putting them together is fun.  Stringing out sentences is fun.  Saying what you want to say is fun.  Repeating yourself over and over is fun until it annoys your readers.

Ahem.

But being verbose isn't always a good thing (unless it's November, in which case bring it on).  Sometimes the very best stories can be told in a very few words.

I recently came across this anecdote that pretty much stopped me dead in my voluble tracks and made me shut my mouth (er, fingers) faster than you can say "get to the point of the story, Amy."  Ernest Hemingway, on being dared by some friends that he could not write a story in six words, wrote this:

For Sale: baby shoes, never worn.

The friends paid up.

I read that and teared up.

In just six short words, only two of which possessing more than one syllable, Hemingway told an incredibly sad tale.  He's a writer famed for being short and to the point, not wasting words to say what the reader can infer for himself.   That little story I reproduced above, the six-word tragedy?  He considered that his best work.

Food for thought, y'all.

Tuesday, May 15, 2012

What Do I Know?


I'm always waiting for things to be over so I can get home and commit them to paper.
~Erica Jong

"Write about what you know."

It's the advice every young writer hears at some point, the advice that many follow, the advice that many disregard.  I've struggled with it, to be honest.  I like the idea of writing what I know, writing from experience, writing from life.  But what, exactly, is the definition of "writing what you know"?  Does "writing what you know" mean that every piece of fiction has to be autobiographical, that each and every character must be based on someone of your acquaintance, that every scrap of dialogue must be at least paraphrased from something that really took place?

I think not.

One of my favorite scenes in Anne of Green Gables: The Sequel depicts Anne and Gilbert discussing Anne's literary endeavors.  Anne laments that her beloved story has become nothing more than a baking advertisement, and melodramatically announces that she will never write again.

Gilbert tries to offer some advice. "Oh, I wouldn't give up all together. Maybe if you just let your characters speak everyday English, instead of all that highfalutin mumbo-jumbo... "Wilt thou give up thy garter, oh fairest of the fair"? Anne, nobody speaks that way. And look at that sap Percival who sits around mooning the entire time. He never lets a girl get a word in edgewise. In real life she'd have pitched him. Well, if you want my opinion, Miss Shirley, I'd write about places I knew something of and people that spoke everyday English instead of these silly schoolgirl romances."

Anne ends up following Gilbert's advice and writes a book entitled Avonlea Vignettes, a fictionalized account of events in her hometown.   Jo March in Little Women does something similar-- after betraying her own conscience by writing sensational stories for a trashy newspaper, she turns her attention to something better and writes a semi-autobiographical novel about herself and her sisters.  With this kind of example before me, I started to wonder if maybe that was the only way to begin writing--to write solely about one's own experiences.  So I tried my hand at it, fictionalizing a few things here and there but attempting to recreate scenes in my own life in a novel for girls.

It flopped.

Since then, I've read quite a few books (and blogs :D) about writing, and I've come to the conclusion that every writer should write about what they know... because it's impossible to do otherwise.

Think about it for a moment.  The Preacher says in Ecclesiastes, "The thing that hath been, it is that which shall be; and that which is done is that which shall be done: and there is no new thing under the sun." (Ecclesiastes 1:9) Is it truly possible for any writer to write about things they don't know?  No.  It's not.  Every single character you create, every scenario you envision, every scrap of dialogue you craft has its foundation in something you've experienced in your life... or something you've imagined.  And the things that you imagine unquestionably fit into the category of "what you know"--because what other human being can know the workings of your mind better than yourself?

I'm not a psychologist, nor am I a professional writer.  (I say professional because I don't like to say "I am not a writer."  To say that I am not yet a writer simply because I don't get paid for what I write is inaccurate.  Anyone who writes is a writer.  I think Ernest Hemingway said that at one point, that there is no such thing as an aspiring writer.  Either you are a writer or you aren't.  Profound, no?)  So don't take what I say as an excuse to go nuts, write something ridiculous and then blame me for it.  (Not that you would.)

In conclusion (because every good essay or article or blog post has to have an introduction, body and conclusion), yes, I agree with the maxim that you should write what you know.  Want to capture the beauty of a wild thunderstorm in August?  Go for it.  Want to twine words together to describe a woman you met at the supermarket?  Do it.  Want to quote verbatim a hilarious conversation you had with your siblings at the dinner table?  Get thee to thy notebook or keyboard, and for pity's sake share it with the rest of us, because a good laugh over something like that can never come amiss.

But don't try to make "what you know" into a box and squeeze your writing into it.  Because your writing will suffer from lack of oxygen.  Trust me on this one.