Story Update

I don’t have a big post for you today, but instead a story update.  In one of my recent goal update posts I mentioned that I wanted to get back to writing some more fiction.  I had the idea that I was going to share an original piece with you today, but due to time constraints that’s just not happening.

My thought process shifted to posting an older story, from one of my Google Drive folders.  I have a few sitting in there, but to my dismay – they’re not really ready.  There was one story in particular I was thinking about sharing, but when I opened it, I realized that I left it unfinished.  There are some comments on it that I got from a writing group but I never went back to it.

I’m going to update the story in the next few weeks, and create a cover art for it and release it as an eBook.  Actually, as I typed this I also found what looks like a pretty complete draft of another short story.  I’ll have to read it over but I think I’m going to give that one the same treatment.

I haven’t decided whether I should try to put them up for $1 on Amazon or something; or if I’d be better off just throwing them online in a pay-what-you-want format.  Either way I will make the stories available to readers of the blog in some form.

And so that I make sure the work gets done, I’m giving myself a deadline: Tuesday May 9th.  If you don’t see something from me by that date, yell at me!  I’m on Twitter at @stephen_g.

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax