Today was one of those days where I couldn’t get anything written. I had a particularly intense day that had me fighting off a panic attack by 2. This is, of course, the sort of thing that happens when you’ve got 1 month to complete 1.5 months worth of work. Sigh. I’m tired. As a result, I really didn’t have the mental energy to solve my chapter 3 problem AND put it into prose that is at least an approximation of ‘not suck’. All that said, I had a good run today, and while I wheeled around the small gym track some forty times, I managed to come up with something like a solution. There are a few sticky details to work out, but once I actually sit down and put myself into the main character’s shoes in the scene, I should be able to see exactly how he manages to squeeze out of it. It’ll be difficult, for him, but I think it should be. So, tomorrow, after I’ve thought about it for a while, I’ll sit down and make it happen. For now though, I think I’m going to check out a nip of single-malt, and get some sleep. Tomorrow is likely to be just as intense as today.
Category Archives: writing process
The dreaded chapter 3 re-write
Right now, I’m staring down the barrel of a chapter 3 re-write. The second half of the chapter is generally pretty good, just needs polishing and copy editing. The first half, however, has major plausibility issues. Well, not major, but they’re annoying enough that they won’t work. It’s not so bad it can’t be fixed, and once I do it’s going to be a whole lot better. I just haven’t got the foggiest idea on how to go about dealing with it. Part of the issue is that the circumstances of the scene have been in place for such a long time, I’m having a hard time visualizing a different, better situation.
The more I think about it, the stupider it seems that I can’t just tweak it. As much as I want to rubber-duck* this, and have a solution, I’m still struggling to come up with one. Perhaps the solution is to try a few different things and see where they eventually lead me. I mean, I’m really only talking about twenty-five hundred words. So, with that in mind, I’m going to start by changing the situation to be impossibly difficult for the protagonist (and writer), then revise until it works. With any luck, I will have fixed the problem.
* For an explanation of rubber-ducking see my about page
Fantasy book research #1
I have notes everywhere. Some are on note cards, some scribbled in completely unreadable handwriting in one of a dozen or so spiral notebooks, plus two three-ringed binders. Not to mention the fancy journal, drawing pad, and odd bits of sticky notes and what not scattered about. Of course, I also have piles of digital notes which are about as organized. Today, I decided to flip through some of my digital notes and came across this little gem:
A trade-ship (Here based upon the east India men) averages 4-5 knots in favorable wind, providing 120 miles/day. (http://www.iro.umontreal.ca/~vaucher/Genealogy/Documents/Asia/asiaShips.html) OR formula of hull speed = 1.34 * SQRT(waterline length)(http://rpg.stackexchange.com/questions/12911/middle-age-transportation-by-river-questions) Rowing is likely to make no more than 3-4 mph. Barges of goods are pulled along the shoreline by use of oxen, and transport of persons or important goods will be done by ‘narrow boats’ which are rowed by 10-20 oarsmen, depending upon the size of the boat.
There was a lot of other stuff along with it, but this little excerpt points out something that is a rather large part of my writing process. Research. Now, I don’t even bother trying to research to the point where I might speak intelligently on the topic, though in most hobbies that’s where I go. However, I do try to get to the point where I can develop details that are, if nothing else, consistent with reality, or at very least can nose past a BS test. Sometimes I totally miss the mark, but I do try.
I think one of the most difficult thing about researching for a book is that when you’re looking into a topic, most of the stuff you might find on the internet is specific to ‘not-pretend’ applications, meaning that you get a lot of ‘it depends’ sorts of answers, which are less than helpful. Sometimes, I really just want information that would give me the bounds on reality. So, in the example above, which took a bit of searching, I could reasonably claim a 300 mile trip might take between 2.5 and 5 days. Now I have something that at least scrapes the realm of plausibility.