Rejected, but not Neglected

I’ve been invited to appear on a new podcast called Story Circle Jerk. It was started by my pal Kai Durkin to showcase short stories and music, either self-written or from others. We’ll be recording our episode at the end of the month, giving me a deadline to prepare material.

One part of my appearance will be an interview about my open-mike evenings. I’ll have to do some preparation for this, so I cover the all main points without overloading the listeners with information.

The other part will involve me reading one of my own short stories. The one I immediately reached for was a piece called Him, in which the narrator talks about seeing his life replayed through his own eyes after his death. I wrote this in 2014, with its most recent revision dated 2018.

Between these dates, the story was rejected by six different publishers. However, I’ve also read it to an audience on a number of occasions during that time; I deliver it in a slow and stark tone, inspired by Salman Rushdie reading Concerning The Bodyguard by Donald Barthleme. As such, it seems to work better on stage than on the page so I still have faith in it.

The story will need to be revised a little. The way I start the process is by reading it out loud, not to an audience, but to myself. If it sounds excessively wordy, or if I find myself unable to follow a plot point, it needs to be revised. This particular piece, however, shouldn’t need too much changing for Story Circle Jerk.

Another podcast I can recommend is The Beans Podcast, run by three friends. Be advised that it’s not specifically about writing, but covers many topics, from advice columns to caffeine to nuclear bombs.

Time and Motion

I’ve recently been placing a lot of effort into my Fun a Day project, which I talked about last month. It’s now been dubbed Junkuary, as it makes use of recycled materials.

This means that my writing has taken a back seat as I’ve made an effort to step away from using words and focus on visual art. However, this is only temporary, and I’ll go back to writing shortly.

Head over to my Instagram page to see what’s happening, and I’ll catch you here next week for more talk of prose and poetry.

Making Time for Editing

Beginner writers sometimes fall into a common trap after finishing a piece. That trap is reading over a freshly-written piece once or twice, correcting any obvious mistakes, then sending it out into the world. As a result, editors and competition judges routinely receive work that is littered with careless mistakes. Most of them are not inclined to read beyond the first few errors.

By contrast, more experienced writers know that creating a satisfactory piece of writing is not something that can be rushed. Editing work is a very distinct process from writing it, and the mind therefore needs time to switch between the two.

As such, it’s essential to leave an interval between writing a piece and looking at it again with a critical eye. That means leaving your work in a drawer – either physical or virtual is fine – and returning to it at a later time.

In just about every piece I’ve written, the passage of time has alerted me to spelling and grammar errors, sentences that are too unwieldy, or plot points that aren’t clear to the reader.

But how long should you leave that work in a drawer? This is a question I’ve previously considered on this blog, but I’ve returned to the issue as I consider how much breathing space is necessary once I finish my current long-form piece.

In an entry from three years ago, I proposed a minimum period of one minute per word or at least 24 hours if the length was under 1,500 words . Three years is more than enough time to revisit that entry and to tweak the formula I proposed.

My new recommendation is to leave at least three minutes per word, or at least 72 hours if the word count is 1,440 or below. The slight adjustment from 1,500 to 1,440 is merely a pedantic tweak to reflect the number of minutes in one day.

If you don’t have the luxury of time, cut those figures to two minutes per word, or 48 hours for 1,440 words. And whatever deadline is absolutely looming, I still strongly recommend one minute per word or – you guessed it – 24 hours at the lower end.

This works out at between one and three days for most poetry and flash fiction, while a 20,000-word novella would be left between roughly two and four weeks.

When you open the drawer after that time, one of the best ways to spot mistakes is to read it out loud without an audience, as any blips are more difficult to ignore. It’s also a good idea to read it at different times of day, when you’re in different moods, and so forth, and see how you react to it then.

If you still have the time, there’s nothing wrong with leaving it aside again and coming back to it at an even later date.

With these blog entries, there often isn’t a lot of time as I want to publish by 6pm every Tuesday. But I always aim to make sure it’s typed up early, and I go back to iron out the inevitable mistakes.

After these periods of resting and editing, that’s the time to send your work out. Naturally, there is still no guarantee of success, but there is a higher likelihood that editors and competition judges will read more of the work you send them and take it more seriously.

Pomodori Doppi

With National Novel Writing Month (NaNoWriMo) underway, there is currently a worldwide race among members to tap out 50,000 words each by the end of November. But how does someone find the time to jot down an average of 1,667 words per day?

For someone like me who generally works core nine-to-five office hours – with at least one shift per week lasting until 6:30pm – I have to make use of any time possible.

I also organise the events for our region. Throughout the year, we have two hours of ring-fenced writing time every Tuesday evening, and an extra two hours per week on a Saturday throughout November. While at meet-ups, it’s relatively easy to crack on with work because everyone else is also trying to reach their word count goal.

The difficulty arises on non-meeting nights. I want to achieve a certain number of words per day, but I also need to tidy the flat and catch up with correspondence. The solution I find works best for me is based upon the Pomodoro Technique. In fact, one of the official NaNoWriMo Twitter accounts ran Pomodoro word sprints just today.

In the classic technique, you carry out a task for 25 minutes and take a break for five. However, I find that isn’t enough time to allocate to writing, so I prefer a double Pomodoro: write for 50 minutes and tackle another task away from the PC for 10 minutes.

I also have an instrumental playlist that lasts for approximately 50 minutes and helps me slip into the mood for writing, as that’s what I chiefly do when I listen to it.

Whatever time management techniques work for our members, however, we the organisers always make it clear that National Novel Writing Month is supposed to be fun.

If anyone finds it overwhelming, we want them to know it’s perfectly acceptable to leave aside a project, and there is no shame in not hitting the 50,000-word target.

Plans on my Hands

Having received my kit from the headquarters of National Novel Writing Month, I’ve been thinking about our group’s plans for when the contest starts in November. I also need to do some work on Hotchpotch, my open-mike for writers.

As such, I’ve had no time to write a full entry. However, we should be back next week with something to say.

The Long and The Short of It

This week, I’ve been looking through some of my old short stories and flash fiction.

I started exclusively prose in 2010 before moving gradually to poetry. As a result, I have an archive of pieces that are complete but are unedited.

Looking through them, I can now immediately spot where I’ve told the reader what was happening instead of showing it through action or dialogue, and any clumsy phrases that I’d now strike down. Here’s an example:

“How much have you had to drink?” she laughed, as he picked himself up. They had enjoyed only a small wine before heading out.

Today, I would probably have shown the character picking himself up in a different way, and placed the information about the small wine into dialogue.

However, I did spot a piece of flash fiction that I still wouldn’t edit very much. This is You’re Going Down.


The referee in the first boat shouted to the other two.

“The race is from here to that island. I want a fair competition, no funny business, no putting each other off. Understand?” They agreed, not quite in unison. “All right. On your marks, get set.” He blew a loud horn.

As soon as they picked up their oars, the man on the left began to regret his drunken bragging the previous week. Still, he felt sure he would win. The small hole he had drilled in his opponent’s boat would take care of that.

Cohesion

Having read last week’s entry, a friend gave me feedback that she felt it ended without a conclusion. I agreed with this analysis: the final paragraph had linked to a page on Reddit that was too loosely connected to what had gone before.

On writing a story, I know it’s finished when the characters are where I intended them to be. For a poem, I work more by experience; when I feel I’m dragging it out, I know to stop.

I find a blog entry is more difficult. I’m not often telling a story, nor conveying an emotion through poetic language. In those cases, I would leave the most exciting parts until nearer the end and perhaps introduce a twist.

On WordPress, I’m writing factually about writing, and some subjects don’t lend themselves well to a linear narrative or a logical progression of events.

I therefore asked my friend how she would rewrite the end of the blog entry in question. She’s worked as a reporter and an editor, so has much more experience in writing factually. She told me it’s a bad idea to introduce something new in the last paragraph, and suggested summing up what was said near the beginning,

I revisited the entry, removed the dodgy last paragraph and replaced it with one that refers back to the first paragraph. As a result, we agreed it’s more cohesive than the first version.