The Day @ChuckWendig Kicked My Arse

Last Tuesday evening I drove on down to Tattered Cover books in Denver to see Chuck Wendig on the last stop of the Wanderers tour. (“What’s Wanderers, precious?” I hear you say. It’s a bloody good book, I answer. Lookie here.) I walked into the store, then I walked into the man (really – he happened to be near the door and was right in front of me as I entered. I shook his hand. I haven’t washed that hand since.)

And I bought a hardback copy of the book (even though I already had the book on Kindle, because if I’m gonna get a book signed, I want the book signed), and I sat and listened as he described how the book came to be (on which I will say more) and then took questions including one from me even though he couldn’t hear me properly because I’m still getting over this damned throat bug and I’ve been speaking in a hoarse whisper for a month or more.

At the end he signed the book and I got a selfie with him (which is pretty awful – I should have asked someone else to take the pic, but it didn’t occur to me at the time). And sometime during the proceedings, yea verily, he kicked my arse.

(checks video)

Ok, he didn’t literally kick my arse.

Let me go back to the bit where he talked about the genesis of Wanderers. He mentioned that the story just started off as a very simple idea: a little girl starts sleepwalking – and doesn’t stop. She walks out of the house and into the world and other sleepwalkers join in. (Not a spoiler – that all happens on the first page or two of the book, and sets the stage for everything that happens after.) That’s it. From that simple seed he built the rest of the story.

I’ve mentioned my own story-developing process several times (I even wrote a little book about it). It involves spreadsheets and timelines and peril/tension scales and so on. And if you take a look back at earlier posts here you’ll see that I was working on timelining a story a few months ago.

That sort of died; as I’ve also mentioned, stuff has been happening since December that’s made finding time and staying focused on writing really hard for me, and thanks to that the timeline work ended up fizzling out. (It’s not 100% dead. It just dried out like a mummified corpse. Add the right kind of juice and it might come back. I haven’t decided yet whether to resurrect it; I’ll figure that out when things get back to something more like normal.)

Back to Tuesday. Wanderers starts off as a one-sentence seed of an idea.

Wednesday, I think about that. I also think about a one-sentence idea that had been niggling away at the mid-brain for a couple of weeks. And I start writing it down. Started with that scene, then what happened next and then what happened after that.

Yesterday (Sunday) evening, I wrote the ending (although I’d had the bones of the ending in mind since Wednesday or maybe Thursday). But the whole thing was down on paper (well, actually I used my reMarkable, which made it go waaaay faster. But still, handwriting.)

No timeline, no spreadsheet, no scene cards. No tech. No process-with-rules-I-feel-I-should-stick-to. I just started with this opening scene that I hadn’t been able to get out of my head, and five days later I had a story.

I started off thinking it would be a short story, but it grew like kudzu. At this point it’s just a story, not a book, but it is going to make a book. Not immediately, of course – I’ve put it to one side for a couple of days and then I’ll review what I have and look for inconsistencies, and even though I already have my characters (they became people as I was writing the story) I want to write down some back stories to help me keep their little details straight in my head. And then I’ll start banging actual keys and writing actual words that will become an actual first draft.

For the first time in months, I’m excited and ready to write this thing. The dry spell is over – for good, I hope – and it’s all because Chuck Wendig (figuratively) kicked my arse.

Until next time . . .

Spoke Too Soon

A couple of posts back I mentioned that I’d got my storyline to the point where I’d started working on the timeline.

As it turns out, I got a little bit ahead of myself. I’ve had to stop working on the timeline because I realised I’d made a mistake with the story. And boy, is it a doozy.

The way I had the story set up, the first of the four stories starts with my protagonist having a problem. And the way the story went, that problem had been worked out by the end of that same first story.

That doesn’t work; it would mean she’d need a new problem to take into the second story. And if she’d already dealt with the biggest obstacle in her life, then what possible hurdles could she have in the second story that would even come close to that?

Here’s a couple of examples of the kind of thing I’m talking about; this should make it clearer.

First, look at Harry Potter. His problem is Voldemort. And while he wins fights against The Dark Lord in each book, Harry doesn’t actually beat him for good until the final battle at the end of the last book.

Another example: Neo’s fighting the machines and we find that out early in The Matrix, but he doesn’t end the war until the end of the third and last movie.

Last example: Frodo encounters the One Ring not far into The Fellowship of the Ring, and the story only ends when he destroys the ring—and Sauron—at the end of The Return of the King.

Ringfrodo

You get the picture. I’ve had to go back to my plotting and change things so that the problem my protagonist has at the beginning of the first book carries her through a series of adventures all the way through the complete set of four stories. And that in turn has meant adding in a bucketload of back story to support things—and the rabbit hole gets deeper as she learns more about the truth behind her original troubles a little at a time; she only finds out the complete details close to the end of the last story. It also means that what was to be the second story in the series will be pretty much torn down and replaced, and the way things are going it’s not impossible that I’ll need a fifth book to complete the whole tale.

So at the moment timelining is suspended until I get all the details worked out and written down. What I thought was going to take a few days is now looking like it’s going to take a few weeks at least. This thing is becoming a monster.

I’ll post more on this as I progress.

 

Finish Your Book now in print

FinishYourBookKindle

AFTER a certain amount of messing about, Finish Your Book is now available on paper here: https://www.amazon.com/dp/1522043837 — cheaper than a $6 cheeseburger, and better for you, too. (Disclaimer: please don’t eat the book; I suspect the inks and stuff are not exactly FDA approved.)

And of course the non-dead-tree version is available from all good eBook vendors. See https://petefordwriter.com/books/finish-your-book for details.

Finish Your Book updated

I found out that the Finish Your Book file I uploaded to Smashwords didn’t get converted properly (my bad—I messed up a paragraph style). As a result the text ended up with first-line indents on every paragraph instead of the block paragraphs I wanted.

The problem is fixed; I uploaded a new file with the corrected formatting. If you bought the book on Smashwords you can download again (you already paid for it, so no need to buy it again). The way I understand it, if you got it on a Nook, Kindle, or Kobo, your device copy will update automatically within a few days. If it doesn’t, I believe you can remove it from the device then re-download it and you should get the updated version.

FinishYourBook

Now, I need to go and update the links on the Books page to add the B&N link.

Thanks to all who’ve bought and downloaded the book. I hope you enjoy it and it helps with your writing!

Coming soon: writing process book

IF you’ve been following updates on my Work-in-Progress (WiP) page, you’ll know that I’ve been working on a short non-fiction book about my writing process while I’m (1) waiting on markups for The Artemis Device from my copy editor, and (2) waiting on responses from agents for the query letters I sent out for Smoke & Mirrors. The first could appear at any time; the second I don’t expect for at least another couple of weeks.

So in the interim, and before I get properly to work on the SF novel I’ve been thinking about, I decided to do something I’ve been wanting to do for a while—document my writing process. And thanks to the writing workshop I’ve been going to the last few weeks, I also decided to write it up in a form that I can self-publish, in the hope that maybe I can do something that will help other aspiring writers.

By short I mean that the main body will probably end up being around thirty pages; my writing process, boiled down to just the essentials. The stuff I wish I’d known when I was just getting started, in a form that someone can read in an hour or less and keep handy as a reference after.

I started with a series of about half a dozen blog posts I wrote here a while ago; I’ve cleaned those up, expanded on them with some better examples and some additional material, and changed the order of things around a little bit to make it a bit more logical.

It’s just about done; the main text is complete, I think—I’ll be checking it through again to see if I missed anything. It needs a few things yet: a cover page, a proper title, and some front and back matter. And I have to re-read the Smashwords guides to remind myself how to format it all up. But I expect to have that all done in a couple more weeks at the most, and then it’ll be out (and of course I’ll announce it here when that happens).

On that note, time for coffee and a read of that Smashwords formatting guide. Until next time . . .

(p.s. I’ve decided to cut down on the political comment a bit. Not completely; if and when I have something I want to say regarding “president” Loco Pandejo and the Keystone Kabinet, I will. But since I managed to get myself back on the writing horse the last few weeks, I want to focus more on that. I seriously considered unfollowing all the politically-related Twitter accounts that I’ve added over the last six months, but I still feel the need to stay up with what’s going on so I guess I’m stuck with those until the Jedi arrest Trump and the rest of the traitors and pack them off to prison.)

 

Writing Process #7: Submitting

YOU’VE self-edited your script, and now it’s much better than that first draft you had before. Is it perfect? Probably not. You could do another editing pass and I’ll bet you’ll still find something wrong. Lots of somethings, in fact. But there comes a point where you can honestly say to yourself that your typescript is something you’re happy for someone else to read. Are you ready to get it published?

How do you get it published?

20151106_130440

There are a number of options:

  • Self-publishing. There are plenty of places to do that. My very first full-length work was self-published on Smashwords, and as part of that process it was automatically made available on Amazon, Barnes & Noble, Kobo, and several other platforms. But to self-publish properly, you have to do all the work that a publisher would do. You must BECOME THE PUBLISHER. You need, really need, a professional editor to work with you on polishing the work to a high shine. (I can’t stress how important that is. Some people can self-edit to a professional standard, but those people are as rare as rocking-horse droppings; do you really, honestly think you can self-edit to that standard?) You need someone to format it properly for publication. You need cover artwork. Of course, you could do all that yourself, but you’re better off getting professionals involved—and that costs money. So you have to ask yourself, are you happy to spend the cash with no guarantee that you’ll make enough sales to get that money back?
  • Go directly to a publisher. Smaller indie publishers will generally accept submissions directly from authors. Larger publishers, not so much (see the next bit, about agents). Work up a list of publishers that deal with books in your genre—you might be surprised just how many people submit work that’s in a genre the publisher just doesn’t deal with. Make sure they’re accepting submissions (many publishers only accept submissions at certain times of year; some only open for submissions when they have the bandwidth to take on work). Publishers have guidelines for submissions—for example they might ask for the first ten pages of your story to be pasted into an email cover letter. Some will ask for a synopsis. Many will delete emails with attachments unread. So read the guidelines carefully and follow them to the letter.
  • Find an agent. The bad thing everyone thinks about agents: they take a percentage of the profits of sales of your book. Well, of course they do. They have to pay the rent on their double-wide, same as you. But the good things about agents outweigh the bad by a good margin. An agent can submit your book to publishers that won’t take submissions direct from authors. They can help make sure that a publishing contract isn’t screwing you. They can get you better contract terms (for example a better percentage on sales) than you might be able to manage on your own. In the end, the fact that agent takes, say, fifteen percent, is more than made up for by the fact that she’ll get you a publishing deal that makes you more sales. Some agents also suggest edits to improve the work. As to finding an agent . . . well, there are a few ways. Follow Writer’s Digest (@WritersDigest) on Twitter—they often send out alerts when agents are looking for books in specific genres. Check out QueryTracker—this is a great tool that can help you search for agents. When you find an agent to submit to, the rules are much the same as for publishers—check genre, make sure the agent is accepting submissions, follow submission guidelines closely. When it comes to writing query letters, check out Query Shark.

This is IMPORTANT: No reputable agent or publisher should ever, ever, EVER ask you for money up front to “cover costs” or for anything else. Real publishers and agents take their percentage from sales of the book AFTER it’s been published. If an agent or publisher charges for their services up front, they’re almost certainly scam artists intent on taking your money. Take a look at the Writer Beware site for more on this.

Here’s another thing: Be ready for rejection. In fact, expect rejection—that way it won’t faze you when it happens. And it will happen, over and over and over. At a rough estimate based on what I’ve seen, the chances of any one agent accepting your work is something like five percent. Indie publishers appear to have higher acceptance rates, but it’s hard to be certain about that because good data is hard to find. The thing is, agents and publishers are taking a risk when they accept your work. They have to cover the costs of doing their job until your book is on the shelves and making sales—in the case of agents, time spent dealing with publishers, and in the case of publishers, paying editors and artists and everyone else involved in getting your book out there. Maybe you’ll sell hundreds of thousands of copies and you’ll all be rolling in cash. Or not. It’s a gamble, and it’s on their dime, which is why agents and publishers are so picky about what they accept.

Now let’s say your work is accepted. What next?

AFTER you’ve celebrated a little bit (because getting accepted IS a big deal and worthy of a little celebration), be ready for what can be the hardest part of this whole thing. Remember all that self-editing you did? Well, now it’s about to happen again. Only this time, someone else—maybe your agent, maybe a copy editor working for a publisher—will be picking your book apart and finding things you didn’t even suspect weren’t right. They’ll be coming back at you with lists of things that need changing. (They should not be making those changes themselves, beyond maybe correcting simple, obvious stuff like spelling errors; they should just be telling you this passage or that scene needs fixing, and they might suggest ideas for how to fix it. But it’s your book, and how you fix it is up to you.) And you might very well find yourself working to a deadline.

Here’s a story for you; at the time Mr. Gunn & Dr. Bohemia was accepted, I had no idea that I was about to spend the next SEVEN MONTHS editing the typescript for publication. Seven months of working on it evenings after work, and hour upon hour at weekends. It was tough, and not just on me—I swear my wife had plans to throw my laptop out into the yard and then set it on fire. (This is why so many books have an “acknowledgements” page where the author thanks their spouse for putting up with it all for so long. Until you’ve been through it, and put your other half through it, you have no idea just how much mutual understanding is needed for this.) But seeing the book out where people could buy it made it all worth it.

And guess what? Once you’ve been through it once, the lessons you learn will make the next one go that much easier.

That, I think, concludes this short series of posts (unless I think of something else to add). I hope, gentle reader, that this helps in some small way.

Until next time . . .

Writing Process #6a: I Found This Great Book

I was in the process of writing the #7 post for this short series when I came across a book . . .

SnowflakeGuy

It’s How to Write a Novel Using the Snowflake Method, by Randy “Snowflake guy” Ingermanson. (Here’s a link to the web site.) And having read it, I have to say that if the articles I’ve been writing about my own process resonate with you, then you should have a look at this book. Ingermanson’s method is very similar to my own in many respects, but formalises some steps that my own process tends to leave a bit vague. (On the other hand, my process seems to have a couple of additional aspects—for example the way I think about characters—but I should be able to merge bits of my own process as described so far without any conflicts.)

The way the book’s written comes across as a little weird at first—Goldilocks goes to a writer conference and learns about the Snowflake Method, meeting the three bears, the big bad wolf, Mother Hubbard, and other storybook characters along the way—but it makes for a more entertaining read. The last couple of chapters summarise the method and show in detail how it was used to write the book itself.

I’ll definitely be using this method for my next book (or to be more specific, I’ll be creating a Frankenstein hybrid of Snowflake and my own, using Snowflake for the framework and adding in my preferred way of thinking about characters together with the way I like to build my timelines).

Does Ingermanson’s method supersede the posts I’ve already done in this series? Maybe. Probably, even. But I’ll leave them up anyway. Does it mean #7 won’t happen? No, it doesn’t—because that’s going to be about getting a work published, which is something the Snowflake method doesn’t get into so much (beyond writing short and long synopses, but that’s still considered part of the process of developing a story as well as being something you can use when submitting for publication).

So, watch this space for #7 in the series, which should be up within the next few days. (Sorry for the delay on getting it done, by the way; life intervened and pretty much blew away last weekend, which was when I’d planned to finish it up and get it posted.)

Until then . . .

Writing Process #6: (Self) Editing

YOU have a first draft! Great! But . . . it’s not ready to be published. Not yet. Trust me on this. There’s work to be done.

20151006_181845

The work needs to be edited. Ultimately it needs editing by a professional editor, but before it gets to that stage there’s a lot you can do. For one thing, you just wrote the thing and it’s going to have rough spots all the way through it.

As I mentioned in the previous post in this series, after I’ve written each scene I go back over it—just a quick pass to spot obvious screwups. Missed and doubled words, errors in spelling, grammar, and punctuation. That’s about it. There’s not much point trying to do more right after I’ve written the scene because, well, I’ve only just written it. The words are still in my head. I’m still too close to it. As a result, I can read the scene and still miss some glaring errors.

That’s why, after I’ve written each scene, I only give it a cursory once-over and move on. When the last scene has been written, something like three months will have passed since I wrote the first scene. So if I look at those early scenes again, I’m seeing them a little bit more clearly. Ideally I want to be reading it as if I’d never seen it before, so what I should do next is put the draft away for about ten years, so that I forget I ever wrote it. No, of course that’s not practical.

The first thing I do when I go back to the first scenes I wrote, three or four months earlier, is to re-read, carefully, looking for mistakes. Many people will tell you to read it aloud. The thing about doing that is, it forces you to slow down the pace and avoid just skimming, and that will help you spot errors better than just about anything else. The other thing you’ll find by doing this is passages where the wording is awkward or convoluted. If it doesn’t trip off the tongue, it’ll tie your readers’ brains in knots.

Here are a few of the things I look for in particular:

  • Obvious mistakes in spelling, grammar, and punctuation. If in doubt, use a style guide. (I use The Chicago Manual of Style, because that’s what my publisher uses.)
  • Consistency. If you use the Oxford comma (I do), then make sure to use it wherever it applies. If you have hyphenated words, use the same hyphenation everywhere. (Example: one of my early stories had a thing called a “road train”—but in some places I hyphenated it as “road-train”, and in others I didn’t.) If you italicise your characters’ thoughts, then be consistent.
  • Passive Voice. This can be difficult to spot, because it’s sometimes very subtle. For example, the difference between “someone shot at me”, and “I was shot at”. (I think you’ll agree that the second phrase is a little stronger than the first.)
  • Dialogue layout. I open a new paragraph as each character speaks; I find that makes it easier to follow who’s saying what. (I’ve read books in which the different characters’ lines are all mashed together into a single paragraph. It’s horrible, and hard to read.)
  • Again, in dialogue, I rip out superfluous uses of “he said, she said” and similar. Most times, you know who’s talking. If there’s a potential for confusion, especially in a long conversation, I’ll add something every half dozen paragraphs or so to make it clear who’s doing the talking.

And of course I’ll spot errors of other kinds as I’m going through. Dialogue in which it’s not clear who’s speaking. Characters acting or talking in ways that aren’t in line with their personalities (that can be harder to fix). And sometimes entire scenes that come across as so wrong that the only thing to do is tear them down and rewrite them. It happens.

When I’ve finished editing the last scene, I put the whole thing to one side for a bit—maybe a week, maybe a month—and then . . . I do it again. And I can guarantee you that I’ll spot a whole herd of obvious, glaring errors that I didn’t spot the first time round. Errors that are so in-yer-face that it’s hard to believe I could possibly have missed them earlier. And yet, there they are. And then I do it again, and I find a bunch more mistakes. AND THIS NEVER ENDS. I think I could go through it a hundred times and still find mistakes. Eventually there comes a point where I just have to say “good enough” and stop. And of course, bear in mind that the book will still be going to a professional editor, and she’ll spot things I missed, too.

Another thing I do is write a synopsis. I usually do this after the first or second editing pass. Basically I skim each scene and note what happens, in the form of a single sentence. The result is similar to the one-paragraph-per-scene timeline, but there are a couple of important differences:

  • I have one sentence per scene, and I put the sentences together so that I have one paragraph per chapter*.
  • I’m actually working from the draft text, not the original timeline; that’s important because during the writing, what I actually end up writing very often drifts away from the timeline description a little bit because a new idea comes to me as I’m writing.

(*At this point a chapter is just a file containing around 2,500 words. Whether the final book’s chapters line up with this or not is irrelevant—it’s just a convenient size when it comes to editing. The final book might not even have chapters; for example The Artemis Device is in the form of a series of scenes with no other divisions.)

Having a synopsis is valuable, because many agents and publishers will ask for one as part of the query/submission process. If you’ve created one as part of your process, you won’t have to put one together in a rush later when you suddenly find you need one. But building the synopsis is priceless, for a couple of reasons:

  • You get back to a high level view of your story’s structure, and that in itself can help you spot problems that you might not notice otherwise. For example, while I was writing a synopsis recently, I found that I had a character recovering in bed after being attacked—and then, just a couple of scenes later (in terms of time, a matter of a couple of hours), he’s up and about in a different part of the city. Oops! When I checked the timeline I found I’d missed an entire scene in which he decides he has to go after his assailant despite his injuries. Somehow I’d skipped over it.
  • As I’m writing each sentence to describe each scene, I sometimes come across scenes for which adding a sentence to the synopsis seems like padding. When that happens I can ask myself, is this scene really needed? If I rip it out, does the story suffer? If the scene doesn’t have a function—if it doesn’t drive the story forward or explain something about a character, it can probably be removed.

When do you stop editing? I guess, when it’s time to submit your work to an agent or publisher. And so, in the next and quite possibly last post in this series, I’m going to get into that a little bit.

Until next time . . .