<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>FlashFiction.Net</title>
    <link rel="alternate" type="text/html" href="http://flashfiction.net/" />
    <link rel="self" type="application/atom+xml" href="http://flashfiction.net/atom.xml" />
    <id>tag:flashfiction.net,2009-07-13://1</id>
    <updated>2009-07-11T11:01:54Z</updated>
    <subtitle>Making (very) tiny things count.</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 4.261</generator>

<entry>
    <title>27 Rules for Flash and Life in General</title>
    <link rel="alternate" type="text/html" href="http://flashfiction.net/2009/07/27-rules-for-flash-and-life-in-general.html" />
    <id>tag:flashfiction.net,2009://1.7</id>

    <published>2009-07-10T20:55:55Z</published>
    <updated>2009-07-11T11:01:54Z</updated>

    <summary>written by Christopher JamesThis week, in an effort to learn more about writing, I started cobbling together a few ideas and suggestions about what I thought might make a better flash. The ideas are based on what I noticed reading...</summary>
    <author>
        <name>Randall Brown</name>
        
    </author>
    
        <category term="Flash Craft" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="craft" label="craft" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="fictionwriting" label="fiction writing" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="flashfiction" label="flash fiction" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="microfiction" label="micro fiction" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="shortshort" label="short short" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://flashfiction.net/">
        <![CDATA[<span class="Apple-style-span" style="color: rgb(0, 0, 0); font-family: Verdana,Arial,Helvetica,sans-serif; font-size: 14px;"><div><span class="Apple-style-span" style="font-style: italic;">written by Christopher James</span></div><div><br /></div>This week, in an effort to learn more about writing, I started cobbling together a few ideas and suggestions about what I thought might make a better flash. The ideas are based on what I noticed reading other people's stories and what others noticed reading my stories.&nbsp;<br /><br />The rules, and I hesitate to use that word, are in a&nbsp;<i>particularly</i>&nbsp;unhelpful chronological order, tacked on as and when they occurred to the listmaker. Some are very personal to me whilst others are thrown out to the world at large. The list is by no means exhaustive, though it exhausted me!&nbsp;<br /><br />Maybe you agree with some, and disagree with others. About two thirds of them are pretty serious and the remaining third are good for a giggle and little more. I think number 21 is one of the big ones, and I know I want to try and start bringing a lot more of that into my writing. So reaching 21 could be a pretty life changing moment for some of you. You know who you are.&nbsp;<br /><br /><ol><li>Don't use humour in a sad story unless the humour adds to the effect you want to achieve, and vice versa. A funeral scene might make your fart joke hilarious, but a fart joke is unlikely to make your funeral scene heartbreaking. (Note: This is not always true. It was pretty heartbreaking when my Uncle Joe thought it would be funny to tickle the pallbearers carrying my Aunt Stella to the church.)&nbsp;</li><p></p><li>Ambiguity is not subtlety.&nbsp;</li><p></p><li>Having a character stare at something for a couple of seconds cannot replace internal thought unless you do it very well.&nbsp;</li><p></p><li>Efficiency.&nbsp;</li><p></p><li>…is great but sometimes less is less. Don't lose clarity.&nbsp;</li><p></p><li>Throwing a disabled person into a story (a la four weddings) can be a cheap trick to manipulate sympathy—so do more of that.&nbsp;</li><p></p><li>Just kidding. People's reactions to the disabled are interesting, though, especially since many people are not themselves often around disabled people and don't know how to behave.&nbsp;</li><p></p><li>If your readers are going to want to know something, maybe you should let them know. I recently wrote a beautiful love story set in rural Tennessee during the time of the Great Depression, but I forgot to tell my readers that the primary protagonists were time-travelling robots. This absent mindedness on my part led to some confusion for my readers in the finale when it began to rain and my heroine caught on fire.&nbsp;</li><p></p><li>Specifics…&nbsp;</li><p></p><li>Don't write and submit as quickly as possible. Remember all those things you notice after you've submitted? Maybe sit on it for a couple of days. Think about what you want in the story and revisit it. Check again that the edit makes sense—and then submit. If possible, go back and add character details, rhythm, etc.&nbsp;</li><p></p><li>Try to read your piece with virgin eyes. What sounds funny? What doesn't make sense? What will make you stumble on a good read? Rewarding repeat reads is great, but the first time has to be special. ALSO you have to read the story more carefully than any of your readers. You have much more invested in this than they do, so you'll spot things they won't. Readers are big fat lazy slobs, and they want someone to do all the hard work for them. Never ever forget this. I find it helpful to write 'FAT SLOBS' on a postcard and keep it on my desk next to my laptop.&nbsp;</li><p></p><li>Treat your reader! Think about the things you like to see in somebody else's story (mango and vodka!) and put them in your story. Who doesn't like getting bucket loads of treats?&nbsp;</li><p></p><li>SOUL. GET SOUL. NEED SOUL. HAD SOUL BUT LOST SOUL? FIND SOME MORE SOUL. Soul is quite important in a story, and thanks to the vague and hazy definition of what SOUL is, you might often find readers complaining your story has a distinct lack of it. They'd like to be more helpful, sorry.&nbsp;</li><p></p><li>Don't write entire words in upper case. It hurts my eyes.&nbsp;</li><p></p><li>Surprise the reader, sometimes. Question their assumptions.&nbsp;</li><p></p><li>Try to teach the reader something new and interesting in a fun and interesting way. For instance, I bet you never knew that there are no honey bees in Northern Ireland, did you?&nbsp;</li><p></p><li>Be careful with the ugly stuff, and get ugly with the careful stuff.&nbsp;</li><p></p><li>Don't repeat yourself unnecessarily. This rule was, in fact, the set up to an unnecessary repetition joke which I have now decided to cut. Don't be afraid to drop cherished elements of your story.&nbsp;</li><p></p><li>Plot holes. Remember how they ruined <i>Terminator 2</i> for you?&nbsp;</li><p></p><li>Don't repeat yourself unnecessarily. Also, don't be afraid to cherish dropped elements of your story and throw them right back in there.&nbsp;</li><p></p><li>AND THIS IS A BIG ONE. Think about the things you would really really like to do—like live life as a pirate—and write that into your story. Closely related to mango and vodka.&nbsp;</li><p></p><li>Be very careful with tense shifts. This is a pet problem in my writing, but I'm sure I'm not alone.&nbsp;</li><p></p><li>Have fun. This is one of those pieces of advice that also applies to life outside flash fiction writing. The same cannot be said for rule number 22.&nbsp;</li><p></p><li>Say&nbsp;<i>yes</i>&nbsp;to strangers.</li><p></p><li>I wrote a scene involving a romantic meal in a Chinese restaurant, and my friend Cortney read it and said "Chinese restaurants don't have romantic music." Sometimes you want to challenge your reader's bizarre prejudices(!) and sometimes you don't because it distracts them and takes them out of the story.&nbsp;</li><p></p><li>Consistency is very important.&nbsp;</li><p></p><li>Screw 'show don't tell'—do whatever you like. Too many people blindly repeat that without thinking about it.&nbsp;</li><p></p></ol><br />The 'screw this' advice given there in rule 27 can apply to all so called rules of writing. Just remember though, when you're up to your knees in a telling-not-showing frenzy, that readers really like it when you have a good showing moment that involves them in figuring the story out for themselves. There's a reason why the rules started, so you'd better have a pretty good reason for breaking them.&nbsp;<br /><br />Note to readers. The 'screw' in rule 27 is part of the made for television edit of this list. A director's cut, complete with previously unseen footage, can be obtained from the list's author.&nbsp;</span><div><font class="Apple-style-span" color="#000000" face="Verdana, Arial, Helvetica, sans-serif" size="4"><span class="Apple-style-span" style="font-size: 14px;"><br /></span></font></div><div><b><font class="Apple-style-span" color="#000000" face="Verdana, Arial, Helvetica, sans-serif" size="4"><span class="Apple-style-span" style="font-size: 14px;">About the Author</span></font></b></div>
<b><i><br /></i></b><a style="padding: 0px 6px; float: left;" id="aptureLink_WqT49w9WyI" href="http://www.flickr.com/photos/28101640@N06/3487424556/"><img title="feelin kindov" src="http://farm4.static.flickr.com/3565/3487424556_98146b7ebb.jpg" style="border: 0px none ;" height="150" hspace="15" width="175" /></a><b><br /><br /><br /><a href="mailto:sutcliffechris@hotmail.com"><i>Christopher James</i></a></b><i> lives, works, and writes in London, England. He has an eye on writing and living more, and working less, in other parts of the world.&nbsp;</i>]]>
        
    </content>
</entry>

</feed>

