Writanon dot com logo

A community helping writers grow skills, advertise successes, and build networks.


Writers Anonymous

Blog of the Bartender



search 2013 adfgs

Posts Tagged ‘writing’

Three Ways to Identify “Data Dump”

Monday, January 24th, 2011

Recently, I’ve advised several writers using our editing service to avoid the dreaded “data dump”.

A data dump occurs when you give a lot of information to the reader at once in a clunky or obvious manner.  Below are a few ways to detect when you’re dumping information on the reader.

The Laundry List

I often see this when we’re seeing a character for the first time.  Here’s an example (this and all others in this article are completely made up):

Bob Jones took off his wire-rimmed glasses.  He was 5′ 6″, and wore tan slacks with his blue button-down shirt.  His hands were old and gnarly, and age spots showed under the edge of his sleeve.  His shoes were brown.  His eyes were green, but one of the pupils seemed to be turning milky-white from cataracts.  His thin frame belied a desperate, inner strength.

While the description is nice, and you likely have a firm image of him in your mind, we have no idea why we should care about him.  Here’s a recommended edit of the above paragraph:

Bob Jones took off his wire-rimmed glasses.

It’s really all you need to know.  The other details can be sprinkled throughout the story elsewhere, or not at all (hint:  eye color rarely matters).

“As You Already Know…”

This is when one character tells other characters something they already know.  If you see this tag in your dialogue, consider eliminating it.

For example, if you see something like this:

“As you already know, we’re under attack from the vicious Culverians.  They’re our sworn enemies for millennia, and we need to kill them.”

It’s probably a data dump.  A revised version might look something like this:

“We’re under attack!  Man battle stations.  Let’s kill them all.”

Note how the second version appears much more active.  The reader doesn’t know all of the detail, but they don’t need to.  They know they’re reading about a battle, and that’s probably good enough for now.  Later, after the battle, you can reveal how they’ve been at war for millennia.

The Ambler

This one’s a little more subtle than the others.  Essentially, you’re trying to do too much in a single sentence or paragraph.

John slowly brought the fork to his mouth as he watched his wife, who he suspected was cheating on him, chat with a man across the street.

When you see a sentence that tries to describe two people doing different things, you should check it carefully.  When you toss in background information as well, you’re probably letting your focus wander.  You may also be dumping information on your reader.

A revised version:

John slowly brought the fork to his mouth as he gazed out the window.  His wife was chatting with a man across the street. 

She’s cheating on me, he thought.  I know it.

Look for these three symptoms to identify data dump in your writing.

What other ways do you detect data dump?  Are there other symptoms we’re not mentioning here?

Using Beta Readers

Monday, January 17th, 2011

Earlier this week, I received a two-part question:  Who are beta readers, and why should I be using them?

Beta readers are people who read early versions of your manuscript.  In general, they should be in your target market (e.g., if, like me, you’re writing a book in the fantasy genre, your beta readers will tend to read lots of fantasy).

Their job is to:

  • read your entire work
  • let you know what parts they found boring, unnecessary, confusing, or conflicting
  • look for specific problems that you’re curious about (consistent characters, believable sequence of events, etc.)
  • give you an overall rating of your book…ideally, “I would recommend this to a friend”

Note that beta readers are not critique partners.  It’s unlikely that they’re writers, or have knowledge of how to construct a story.  However, they are likely to “know good work when they see it”.

You should use beta readers when you think your book is nearing its final form.  For example, I am nearly finished with my novel, so I plan to use some beta readers starting in mid-February.  If you still have major revisions planned for your work, you probably should not be using beta readers.

With any beta reader, you should always set expectations up front.  I plan to send the following guidelines to my beta readers.

Thank you for agreeing to be a beta reader for my current novel.  Since this is a work in progress, I am looking for your feedback on the following items:

  • Did you stay engaged in the book?
  • Were the characters interesting enough to hold your attention?
  • Were there any parts that seemed long and/or boring?  If so, where?
  • Who was your favorite character?  Was there a reason you liked him or her?
  • Was there anything that made you think: “There’s no way that would happen!”?  If so, please describe.
  • Would you recommend this book to a friend?  If so, could you describe the person you would recommend this to (no names please)?

In this case, I value honesty more than my feelings.  We can still be friends even if you hate this book.

What other questions would you ask?  Do you disagree with this approach?  Have you used beta readers successfully?  Share your experiences below!


Contact Us | Privacy Policy
Free Domain Registration! Green Web Hosting Need a website?
Register your domain today!