Proofreading and editing can be such a chore, I tell ya! Thought I’ve never been very good at proofreading and criticizing other peoples work, I find that it is when I am called upon to edit and evaluate their work that I most want to retreat into my shell. I feel selfish when this happens, mainly because of all the people I have asked to review my own work and give me their opinions. You’d think I’d be better at this aspect of it!
But of course, I know that part of the reason I hate editing the work of others is because I hate editing my own. I’ve noticed this about most people who enjoy writing, composing, and anything else that requires active revision and corrections. By the time the work is done, they want to put it down and forget about it, to let others handle the business of finding the flaws and pointing out the necessary corrections.
Alas, I’ve had to check most of that baggage ever since I started to become a member of several writing communities. In fact, I’ve even volunteered to act as a contributing editor for two major projects, one of which is the “Yuva Anthology” (begun by Khaalidah and myself), the other being the “Worlds Undone” Anthology. The latter one people might remember from a few months ago, when I was doing mock ups for a cover and happened to find some primo artwork to feature in it. Thanks again to cazzyae at deviantArt for her talent and generosity of spirit for that one! Thanks to her, Createspace’s easy interface, and the suggestions of many people at G5N, here’s how the cover came out:
Unfortunately, that has opened up a different can of worms for me. While I’ve definitely managed to overcome some of my reservations about reading other people’s work, I find that my pet peeves, or what I consider to be the marks of weak writing, keep rearing their ugly head. After reading many stories, I began to think that a tutorial might be in order to help some of the newbies avoid some rookie mistakes, ones which I have committed at least a half dozen times. Each!
I should also take this opportunity to thank Kristen Lamb, who’s impressive article “4 Writing Crutches that Insult the Reader’s Intelligence” reminded me of this idea. After seeing the title in my Inbox, I immediately zoomed over to her site to see if we shared the same pet peeves and sensibilities. Upon reading it, I could tell she was much more versed in this whole writing thing than I am! Still, I happen to share her appraisal of some bad writing habits, especially item number four in her list, “telling instead of showing”.
So, to take a page from her book (no pun!) and to make good on something I’ve been planning to do for some time now, I present you with the list of rookie writing mistakes it is best to avoid. All are the result of what I myself have done repeatedly, and have managed to weed out (for the most part) after many years of practice:
- Avoid Infodumping: Never start a story with a long, drawn out passage telling the reader what they need to know in order to set up the plot. For that matter, never let your story digress into such exposition either. A story is by definition a journey, with information, details, twist, and revelations provided bit by bit over time. Even if it’s a short story, never, ever simply announce what’s happening or what the significance of it is. Such actions turn what is supposed to be a tale into a description and is boring to read.
- Less is More: When it comes to explanations and descriptions, avoid excessive detailing. You don’t need to tell the reader everything about what’s going on, moment for moment, nor do you need to describe the scene in perfect detail. A simple, straightforward description of the scene and the interactions taking place is enough, let the reader’s imagination fill in the rest. Think of it like telling a crafty lie: if you want someone to believe it, don’t tell them a long story loaded with details, keep it simple, straightforward, and plausible. (Editor’s note: lying is wrong!)
- It’s called Background for a reason: One of the best tips I ever got as a writer was to “leave the background in the background.” This kind of overlaps with points one and two, but I keep it separate because of how often I see it and how it has factored into my own work. Much like explaining a scene or dumping info into a chapter, going to great lengths to establish the wider context in which the story takes place (i.e. “universe building”) is a bad idea. Stick to the story, only include that which is absolutely necessary, and let the universe build itself. In time, and if you’re lucky, you’ll get a chance to write follow-up pieces which will allow you to delve into different aspects of your fictitious world in more detail.
- “No one talks like this!”: If there’s one thing I learned from the Star Wars prequels and the Dune spinoffs, it’s that wooden dialogue can totally ruin a story. When drafting scenes that call for verbal interaction between characters, always keep in mind that this is supposed to sound like a conversation between actual people. Do not allow yourself to be swayed by duty to the story or the need to establish character elements. Those things that need to be conveyed are best when done with fine strokes and subtlety, and never, ever let your characters fall into expository passages where they simply say what’s goings on. Or to quote the Robot Devil from Futurama: “You’re characters lack subtlety. You can’t have people just announce their feelings! That makes me so angry!”
- Referencing: When writing a story that is meant to have allegorical similarities to today, or is meant to make a point about a specific issue, avoid referencing them too closely. Never say, “this was just like that thing that happened back then” or “it’s this all over again”. Let the reader infer what you are referring to with your carefully crafted, fictitious comparison. In Foundation, Asimov never directly compared the Galactic Empire to Rome, nor did Frank Herbert ever mention oil in relation to the spice in Dune. Once again, trust in the reader to make the appropriate conclusions and avoid telling them anything outright. Otherwise, you risk turning an “ah-ha” moment into an unimpressed “oh.”
That’s all I got. Suffice it to say, I am still learning and still looking for ways to perfect my craft. That’s never going to happen, of course, but it’s the goal which provides endless opportunity for improvement. Speaking of which, more samples will be forthcoming soon as I work my way deeper into “Winston Agonistes”, “Crashland”, “Frontera”, and “Fortress”. And most importantly of all, Data Miners will finally be ready for distribution by August long weekend! Yes, after roughly six months of delays, the editing of that story is finally coming to an end. But more on that in a bit.
In the meantime, keep hammering those keys, keep working on those manuscripts, and keep reaching for the brass ring of artistic perfection. And while you’re at it, feel free to share with me some lessons that you’ve learned along the way and feel obliged to share with the newbies in your field. There’s no shortage of lessons, as there are no shortages of mistakes