Tag Archives: grammar

What exactly do they mean when they say “show, don’t tell”?

As a copy editor who does a lot of developmental editing with indie authors, Show Don’t Tell is one of the things that I find myself mentioning a lot. Problem is, a catchphrase like that is so easy to say and so hard to explain in only a few words without using examples and re-writing material so the author can see the difference – and I find that authors can sometimes be extremely touchy about someone rewriting their pages for them (they are, after all, that author’s creation – and therefore offspring of a sort – and parents have been known to go to battle over something derogatory said about their child).

When authors ask me how to go about showing instead of telling this is the advice I give them:

Use more dialogue to get the material moving along if you want things to move quickly, rather than using short sentences and paragraphs that tell us what you want us to know.

Don’t be afraid of adding lots of volume to your manuscript by adding descriptions (and remember that descriptive passages should engage all our senses, not just the eyes and ears), but do maintain a balance.

Letting the reader figure out what you want them to know on their own engages the reader more fully – don’t be afraid to add information later on instead of loading it on the front end of the story. Making the reader wonder about what is going on increases tension and therefore is likely to make them want to read more to discover the answers. This does not mean adding lots and lots of flashbacks – it means providing back story in small doses as you write the material, rather than all at once in the first chapter.

Along with the notion of adding tension, self-reflection on personal issues adds tension and allows a writer to tell rather than show when writing in first person, specifically because of that aspect. If an author has a very difficult time with the ‘show, don’t tell’ dilemma, changing writing style to a first person point of view can alleviate that somewhat.

Anything that is passive is usually ‘tell,’ so avoid passive writing – more about that in another post, but basically anything that uses forms of the verb is (was, be, has been, etc.) is usually passive in nature rather than active. Writers who have written a lot of non-fiction tend to use passive voice frequently since that is what is properly used in reports, or textbooks. It is sometimes harder for a technical writer to write fiction than it is for someone who has never written anything at all to do so.

I also usually direct people to a couple of websites for examples and information, so here are a couple of those.

Grammar Girl is always great at giving good examples and clear explanations: http://www.quickanddirtytips.com/education/grammar/show-dont-tell?page=all

This site is for grade school teachers, teaching writing to young students, but it is very clear and concise because of that: http://www.scholastic.com/teachers/article/show-dont-tell-whiteboard-writing-lesson

I also like the Purdue OWL, but was disappointed on this subject – the links were not opening for me or were imbedded in general advice:


And here are a couple of other links:




In fact, if you search “show don’t tell” you get a lot of links – even a very nice explanation from Wikipedia:


Perhaps it is not surprising to find that having references for the information I am providing is probably reassuring to authors. It may surprise you to know that I find a great deal of comfort in being able to point to a reference and say: “See, they said it too.” After all, knowing I am right about something doesn’t PROVE I am right about it, it is just my opinion in the end – but pointing at others whose work is respected and being able to say they said it too (or sometimes, they said it first) gives information more credence. Something for non-fiction writers to remember, even if what you are writing is a blog.



Filed under copy editor, writing

Writing in English…

Someone once asked me how I knew that they were writing in English but it wasn’t their first language. I didn’t really have to think about it, but at the same time I did. What I mean is that I knew instinctively that English wasn’t their first language, but I had to think about how I knew it.

Many of the things that tell me a writer is ESL (English as a Second Language) are things that just blare out at me and seem obvious, but could just as easily be really bad grammar or sloppy writing.

Things like inaccuracies in tenses, or mixed tenses, are a common error that many writers make – but mixing them consistently, even in the same sentence, is one of the signs that the writer is not used to using the vagaries of English in daily life.

Another error that is often seen with ESL writers is a lack of articles – not the articles you write for magazines or newspapers, the articles you use in grammar. These are the common ones: a, an, and the. The more articles that are missing, the higher the chance is that the author is ESL. Why? Because, in general, unless we write more formally than we speak we tend to write as we speak. We rarely write less formally than we speak unless it is a writing tool that we are using for a specific project. And English speakers may slur their articles in speech (for example, my husband using d’man instead of ‘the man’), but they usually remember to use them in some form or another when talking. On the other hand, many other languages not only don’t always use articles – they don’t even have them.

Then there is the whole pronoun thing…  Some languages imply gender with the word itself, unlike English which has to add a whole other group of words to indicate I, me, we, he, she, it, they, them, her, him, you, etc. When an author never uses pronouns or is not using them correctly, that is one more arrow pointing to the likelihood that they are ESL.

Then there is sentence structure. English tends to be noun-verb in the simplest of sentence forms. Most other languages follow a different placement of sentence structure. Or use words that combine the noun and verb into one word (an example from my extremely rusty Spanish: Vamanos!).  This tends to create confusion in the ESL writer’s sentence structure when it is translated into English, either by them or by a translation engine.

There are likely other things, more subtle cues that I pick up on in punctuation and grammar, but these are the ones that get me wondering. English is a horrendously complicated and difficult language to learn to write in, even for those who speak English as their first language. For those who are writing ESL, it can be a quagmire of complications!

Oh – and ESL applies to those who speak a language other than English as the language they grew up with, as well as to individuals who use sign language in one form or another, and those who are computer geeks (after a while, computer geeks don’t really speak in English anymore, even if they are English speakers – they speak in an abbreviated shorthand and coding in a language that is only known to them and which transcends any language barriers that used to exist).

As a copy editor, I need to be aware that an author is ESL for one major reason: Knowing what to watch for means I won’t make mistakes in the edit, or have to start over partway through as I realize what is going on. As a writer who is trying to write in English when it is not your first language, you can learn to look for these things yourself and improve the final product you produce to increase your ability to target an English speaking population in addition to your own. Or, you can at the least be aware that translation engines do not always give very good results if you rely on them to create your English version of the written product.

I once stuck a bit of Chinese into a translation engine, trying to see what an online Facebook friend was trying to tell me. It came out as something like: the sweet petals of the carrot sat on the fence. This made no sense at all, and when she translated it back to her own language she sent me a very crooked looking not-smiley face and tried again, putting it through her own translator to get something like: fences are carrots sit. We were not talking about carrots, or fences…


Filed under Uncategorized, writing