Silver Wordsmith: An author's journey
Lately I’ve been feeling a bit like George R. R. Martin, if Martin had wrote the first chapter of A Game of Thrones and then promptly fucked off the face of the Earth. Success seems to be a favourite prey of ambition. One of my major follies is building up myself a lofty goal and then getting buried by the inevitable avalanche that follows. The only solution is then to burn the ruins to the ashes and move onto the next overwhelming task.
About three months ago, I ambitiously started my science fiction project, The Bloodlet Sun, which I planned to release as a web novel on this blog. Usually I’m a non-genre writer, but I’ve always had a soft spot for science fiction, so I figured I could write it off the side of my desk and share it with the rest of the world in an unhurried fashion. In mid-March, I finished posting Chapter 1. Almost three months later, Chapter 2 is a work in progress, and like George Martin, I am filled with wholehearted promises to get my audience the next installment.
In the meantime, instead of being content with tweets of lamentation, I figured I’d share in a bit more detail what I’ve been going through the last couple of months in terms of the creative process, and hopefully the other writers out there can glean something useful out of my experience.
First and foremost I want to say, I haven’t given up on the project, nor has it turned into a chore, which is one of the reasons why it’s been progressing so slowly. I didn’t want to be buried by the weight of my own ambition in this case. Instead, I carefully took a measured approach to keep my joy alive and to keep some kind of semi-regular release schedule. This turned out a bit harder than I thought, and the main culprit is quality control.
It is far easier to be mediocre than good. So while the plot outlines and character arcs existed as networks of interconnected neurons in my own mind, they were difficult to scrutinize. But now that they were made flesh by writing them down, they needed to meet a standard. I knew I wasn’t planning to make it as polished as my traditional stuff, but that was still no excuse to make it sloppy. There were standards I needed to meet before I could share my work with others.
So that was one of the issues I face – “writing as I go” isn’t as easy as I thought when an involved editing process was going to be a crucial part of it. The bit of pressure I feel to continue to share the work does take the edge off the editing trap – revising and revising until your figurative knuckles turn bloody – but any way you spin it, editing is still not my favourite part of the writing process and it grinds along.
The other major issue that has been bugging me is worldbuilding. Which is funny, because in my introduction to Drops I explain that incessant worldbuilding is the reason I threw up my hands in the first place and started to write instead of plot the story to death. In a way, this reason is related to the first – quality control. My world needs to be polished and consistent, and I can’t risk being blindsided by neglected details.
I thought setting out to write was all I had to do. Yet not even two chapters into the endeavour I discovered that whereas worldbuilding without writing would not satisfy me, writing without a careful eye to worldbuilding is just as unsatisfactory.
I don’t know how the great worldbuilders do it, but I doubt they have a catalogue of all their world’s minutiae stored in their head. It’s not a task that my mind is up for and I already caught myself either thinking that I introduced something when I didn’t, and introducing something I thought I didn’t share but actually established in the previous chapter. I realized that I couldn’t move ahead at a good pace because I was worried about messing this up.
Anytime I namedrop a species or a planet, I need to make sure I record this instance. Both for consistency, and to avoid repetition and unnecessary exposition every time something comes up. Every little fact and name needed to be cataloged. So where I thought that setting out all this detail in advance wouldn’t work for me, neither would I be successful if I didn’t set out this detail after had I introduced it through my writing.
So now that the problem had been identified, I needed to look for a solution. Something that could replicate the ease of navigation of a wiki but be stored on my computer. Now, there is probably an app out there that would do a better job, but I’m a simple man – I need to record stuff, I go to Excel.
So over the last little while, all those times where I otherwise I would have worked on chapter 2, I’ve been putting together this lore repository that I myself could consult. Everything is separated into tabs by characters, planets, species, objects, etc. And in each of those tabs I record everything said on the subject as well as the precise chapters where they were referenced. It’s a bit of a painstaking process to build up, but I’m hoping that once I have the base, it will go a little quicker and won’t slow down my writing too much. My main goal here is using consistency to bring the world to life and keep the reader immersed. Now let’s hope the story itself can do the same thing.
So there you have it, some of the misadventures behind this unfortunate delay. I admit it’s a bit of a learning process, but I’m still committed to the story. Hope to see you for the release of the next chapter, whenever that might be.
Michael is a husband, father of two, lawyer, writer, and is currently working on his first novel, at a snail's pace. A very leisurely snail. All opinions are author's own.