Razor Mountain — Bonus Development Journal

This is part of an ongoing series where I’m documenting the development of my serial novel, Razor Mountain.

You can find my spoiler-free journals for each chapter, my spoiler-heavy pre-production journals, and the book itself over at the Razor Mountain landing page.

But Wait…There’s More!

I write and edit each chapter of Razor Mountain as a single cohesive unit, but I’ve been splitting each chapter into multiple parts, usually between 1,000 and 1,500 words. For blog posts, this is supposedly the sweet spot for keeping readers’ attention, and it lets me draw out each bit of the story over a couple of days, to mitigate the fact that I usually only produce a new chapter every two weeks.

I sometimes take little notes as I’m writing, and once I’m done with a chapter I write the development journal for it. Usually this means I post the parts of the chapter early in the week, and the dev journal on a Friday.

A week ago, I released Chapter 17 in two parts and thought I was done with it. I posted the development journal. I did get feedback from my wife that this chapter felt a little short and ended abruptly, but I thought that was perfectly fine, and I moved on to working on Chapter 18.

As I wrote Chapter 18, I realized that it was going to be a short one, probably not even long enough to split into two parts. And then I realized that Chapter 17 flowed directly into it, with no significant shift in time or location. I reread the part of the chapter I had finished, and I had to admit, it was really a continuation of Chapter 17.

So, I decided to merge this into the previous chapter. This week I’ll post it as Chapter 17.3, and I’m posting this “mini” development journal to explain why.

Outlining and Flexibility

I am the kind of writer who likes to outline. For Razor Mountain, I knew I was going to be posting chapters as I wrote them. That’s a scary prospect, so I spent more time outlining in detail than I ever have for any other project before.

I know there’s supposedly this great schism among writers who outline or don’t outline, but I think it’s a false dichotomy. There’s a spectrum of more or less preparation, and more or less tweaking the story as you write it.

We outliners are a little smug about knowing exactly what’s going to happen in the story, but that can be dangerous. You can miss the opportunities for improvement that present themselves during the writing process, because they don’t “fit into the plan.”

The outline is an invaluable resource for me. I can’t imagine embarking on a project like Razor Mountain and not knowing exactly how I want the plot to flow or not knowing how it will all end. I’m not that kind of writer, and I’ve seen too many serialized stories crash and burn. But I also refuse to be beholden to the outline. I consolidated several chapters in the first act, and I’m happy to do it again. I’ve changed and adjusted a few minor plot points. The outline is a tool, a safety net, to be used only as long as it’s helpful.

The Upshot

The downside of making changes as you go, and the reason some writers are loathe to deviate from the outline, is that any significant changes mean the outline has to change too. Razor Mountain is a story of two different timelines, Christopher and God-Speaker, and thanks to my particular mental proclivities I have arranged it so that we get two Christopher chapters followed by a single God-Speaker chapter. Combining or eliminating chapters throws that off.

While that kind of consistent formula appeals to me, I don’t feel the need to force it when it doesn’t serve the story. Conveniently, the two timelines are fairly independent. The characters exist thousands of years apart, so while adjacent chapters may relate to one another indirectly or share similar themes, most of the book is fairly amenable to small re-orderings of individual chapters. I can probably pull chapters back to fill in the “gap” left by combining these two chapters. I just need to make sure the pacing feels good.

As evidenced by this post, this unexpected change also throws off my posting schedule. This sort of thing would have worried me back when I first started posting Razor Mountain. However, I’m now a year into the project (holy shit, yes, it really has been a year), and I’m slowly becoming less precious about the blog and how I present my fiction to the universe at large. As a small-time blogger, I now work under the assumption that none of my readership cares about my posting schedule as much as I do.

Besides, the whole point of this project was to provide a radically open view into my writing process, and I think this is a great example of that. Look for Chapter 17.3 this week, and then a return to the usual schedule.

Author: Samuel Johnston

Professional software developer, unprofessional writer, and generally interested in almost everything.

2 thoughts on “Razor Mountain — Bonus Development Journal”

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: