After about a month of planning and research, I have created a Plot Event List and have begun primary composition of the third book in the Taesian Chronicles. At this point, my working title is The Paragon's Call. Stay tuned on that.
My production rate is currently averaging 3,100 words a day, but unfortunately I'm only writing one day a week. Part of my problem is I rarely have the creative energy to write in the evenings after work. If I could do that, then I'd have my book written in a month.
As has been the case with my first two books, Ohlen's Arrow and its sequel, Ohlen's Bane, I'm relying heavily on the brilliance that is called Scrivener, from Literature and Latte. This program is a serious productivity tool for writers.
Showing posts with label Ohlen's Bane. Show all posts
Showing posts with label Ohlen's Bane. Show all posts
Thursday, January 22, 2015
Writing has begun on Book Three of the Taesian Chronicles
Saturday, November 22, 2014
Ohlen's Bane is now available
![]() |
| Ohlen's Bane is coming soon! |
I have made a free preview edition available in PDF. You can download it here.
Labels:
Amazon,
Barnes & Noble,
free,
iTunes,
Ohlen's Arrow,
Ohlen's Bane
Monday, October 13, 2014
Ohlen's Bane on target for Thanksgiving release
I have finished all revisions to Ohlen's Bane and released it back to my editor for mechanical editing -- grammar, spelling, punctuation, etc. -- and am on target to have the book ready for release by Thanksgiving.
Ohlen's Bane will be available for sale for Kindle at Amazon.com, for Nook at Barnes & Noble, and for iOS devices at the Apple iTunes Bookstore.
In additional news, I have begun the concepting phase of the third book in the Ohlen's series, which is as of yet untitled.
Ohlen's Bane will be available for sale for Kindle at Amazon.com, for Nook at Barnes & Noble, and for iOS devices at the Apple iTunes Bookstore.
In additional news, I have begun the concepting phase of the third book in the Ohlen's series, which is as of yet untitled.
Labels:
Amazon,
Barnes & Noble,
editing,
iTunes,
Kindle,
Ohlen's Bane,
trilogy
Tuesday, August 19, 2014
Could Ohlen's Arrow turn into a trilogy?
Ohlen's Arrow is published. The rough draft of Ohlen's Bane is completed and is now in the revision-editing phase. That was my original intention, just the two books. In the meantime, I had an idea for a new book that would be completely unrelated to the Ohlen's series and it has been bursting inside my head, eager to get written.
A friend gave me the idea of modifying my new story idea so that it can begin where Ohlen's Bane ends, effectively creating a third book in the Ohlen's series. After brainstorming some ideas, I found a way that I think may work. I am going to spend the next two weeks nailing down the overall plot points.
Once that is done, I will finish my revisions to Ohlen's Bane and move it forward into editing, then I will create a plot event list for the third book and move ahead with that.
A friend gave me the idea of modifying my new story idea so that it can begin where Ohlen's Bane ends, effectively creating a third book in the Ohlen's series. After brainstorming some ideas, I found a way that I think may work. I am going to spend the next two weeks nailing down the overall plot points.
Once that is done, I will finish my revisions to Ohlen's Bane and move it forward into editing, then I will create a plot event list for the third book and move ahead with that.
Labels:
Ohlen's Arrow,
Ohlen's Bane,
trilogy
Tuesday, March 25, 2014
Ohlen's Bane status update
This is just a quick update on the status of my second novel, Ohlen's Bane. Two out of four beta readers have provided feedback. Based on their comments, I am on the fence about how to proceed. The book has promise but needs some work. I may revise the story based on that feedback, or I may scrap the book I have written and start over with a brand new story.
Stay tuned.
Stay tuned.
Tuesday, February 18, 2014
Ohlen's Bane goes to beta readers
This past weekend I completed the first round of revisions to Ohlen's Bane and released it to my team of beta readers, one of whom has never read the prequel, Ohlen's Arrow. Their feedback in particular will tell me if Ohlen's Bane can be read on its own without the reader getting confused by not having Ohlen's Arrow under their belt. That was my intention when writing it.
When I receive the feedback from my beta readers, I will make another round of revisions based on what they tell me, then I'll hand the book over to my editor for a final edit -- this time focusing on the mechanics of the words: punctuation, grammar, spelling, etc. This is often called a line edit.
Then I'll proofread the book one last time before publishing it and making it available for sale. My goal is to have it online for sale by March 31st.
When I receive the feedback from my beta readers, I will make another round of revisions based on what they tell me, then I'll hand the book over to my editor for a final edit -- this time focusing on the mechanics of the words: punctuation, grammar, spelling, etc. This is often called a line edit.
Then I'll proofread the book one last time before publishing it and making it available for sale. My goal is to have it online for sale by March 31st.
Labels:
editing,
Ohlen's Arrow,
Ohlen's Bane
Monday, January 27, 2014
And so it ends
I have reached the end of Ohlen's Bane, having written the last scene over the weekend. I still need to go back and add some parts to fill in a few plot holes, but the first draft of the book is more or less finished.
The next step will be to read what I have from front to back, notebook in hand, and make notes of things that are wonky, missing, extraneous, or erroneous. Writing is the exact opposite of carpentry. The woodworker measures twice and cuts once. The author writes numerous times, and then measures once, right before publication. And sometimes even after publication.
As I discovered with Ohlen's Arrow, the revision and editing phase of a book project can often take longer than the writing phase. This is where the rough stone gets polished, hopefully into a diamond. And this is where my editor and beta reading team really come into play. Without them, every book would be nothing more than wasted paper (or electrons).
The next step will be to read what I have from front to back, notebook in hand, and make notes of things that are wonky, missing, extraneous, or erroneous. Writing is the exact opposite of carpentry. The woodworker measures twice and cuts once. The author writes numerous times, and then measures once, right before publication. And sometimes even after publication.
As I discovered with Ohlen's Arrow, the revision and editing phase of a book project can often take longer than the writing phase. This is where the rough stone gets polished, hopefully into a diamond. And this is where my editor and beta reading team really come into play. Without them, every book would be nothing more than wasted paper (or electrons).
Labels:
editing,
Ohlen's Arrow,
Ohlen's Bane,
process,
proofreading
Friday, January 10, 2014
And so it begins
This is just an update on my progress on the sequel to Ohlen's Arrow, Ohlen's Bane. I've written 39,000 words and expect the completed book to be about the same length as Ohlen's Arrow (which finished at roughly 64,000 words). These books aren't quite as long as some authors think they should be, but they have a lot of action at a decent pace, so by the time you're done reading them, you will have the same sort of breathless "Wow, that was fun!" reaction that you'd get after a roller coaster ride.
Thanks to designer Steven Novak, I also have a tentative cover design completed for Ohlen's Bane. I'll release it when I get closer to finishing the book, just in case the story takes an unexpected turn that influences the cover design itself.
Stay tuned.
Thanks to designer Steven Novak, I also have a tentative cover design completed for Ohlen's Bane. I'll release it when I get closer to finishing the book, just in case the story takes an unexpected turn that influences the cover design itself.
Stay tuned.
Labels:
cover,
design,
Ohlen's Arrow,
Ohlen's Bane,
process
Thursday, December 19, 2013
How Scrivener Makes Ohlen's Bane Possible
As I have mentioned on this blog and on The Ardent Scribe, Scrivener has proven to be a wonderful tool for my writing and creative productivity. It's not about putting words to electronic paper -- a basic text editor can do that -- it's about organizing and maintaining that text as the process unfolds.
My second book, Ohlen's Bane, is possible because I am using Scrivener.
I started out with a plot event list. This is basically a list of sentences, each describing a specific scene in the book, in chronological order of how they will appear in the book. Once that is done, I begin my work in Scrivener.
I create a new scene, or text card, for each sentence. The scene title is 2-5 words describing what happens, and the full sentence I created in my plot event list goes into the card description. I drag and drop those scenes into roughly equal length chapters.
In the research section of Scrivener, I create cards for each named character in the book that describes their physical characteristics, personality and background. I also create a page of place names and yet another filled with randomly created names that I may grab from as new bit players turn up in my story.
Once Scrivener is pre-loaded with all of my research and scenes, I fire the trigger and begin writing.
Ohlen's Bane started off somewhat slowly. I wrote the first six chapters, about 10,000 words, and then read over what I'd written. It dragged. I found myself growing impatient for the good stuff to start happening. Thanks to Scrivener, I was able to drag and drop scenes to rearrange their order. I scrapped entire scenes -- not by deleting them, but by putting them into a Scrap chapter. This gave me recourse in case I found a use for them later on, or even just to grab fragments of scenes.
After paring it down and reorganizing scenes into a better order, I was able to start cranking away again. Now that my story found a good rhythm, thanks to Scrivener's ability to keep my book organized, I was then able to crank out 12,000 words in a single weekend.
When I finish one scene, I open up the text card for the next. Since it has a brief 2-3 sentence description of what happens, I am up to speed on what happens next and can bang it out in record time.
Scrivener really is a brilliant piece of software, and I don't think I'd ever get my second book written without it.
My second book, Ohlen's Bane, is possible because I am using Scrivener.
I started out with a plot event list. This is basically a list of sentences, each describing a specific scene in the book, in chronological order of how they will appear in the book. Once that is done, I begin my work in Scrivener.
I create a new scene, or text card, for each sentence. The scene title is 2-5 words describing what happens, and the full sentence I created in my plot event list goes into the card description. I drag and drop those scenes into roughly equal length chapters.
In the research section of Scrivener, I create cards for each named character in the book that describes their physical characteristics, personality and background. I also create a page of place names and yet another filled with randomly created names that I may grab from as new bit players turn up in my story.
Once Scrivener is pre-loaded with all of my research and scenes, I fire the trigger and begin writing.
Ohlen's Bane started off somewhat slowly. I wrote the first six chapters, about 10,000 words, and then read over what I'd written. It dragged. I found myself growing impatient for the good stuff to start happening. Thanks to Scrivener, I was able to drag and drop scenes to rearrange their order. I scrapped entire scenes -- not by deleting them, but by putting them into a Scrap chapter. This gave me recourse in case I found a use for them later on, or even just to grab fragments of scenes.
After paring it down and reorganizing scenes into a better order, I was able to start cranking away again. Now that my story found a good rhythm, thanks to Scrivener's ability to keep my book organized, I was then able to crank out 12,000 words in a single weekend.
When I finish one scene, I open up the text card for the next. Since it has a brief 2-3 sentence description of what happens, I am up to speed on what happens next and can bang it out in record time.
Scrivener really is a brilliant piece of software, and I don't think I'd ever get my second book written without it.
Labels:
editing,
Ohlen's Bane,
process,
Scrivener
Monday, November 18, 2013
Be Willing to Kill Your Babies
When I was in high school, typing was a required course. We used IBM Selectric typewriters rather than computers. By the end of the one-semester course, I was the fastest in my class, banging out 90 error-free words per minute. It was the most useful thing I learned in high school.
Since moving to computers, I can edit as I type. I still type close to 90 wpm, but thanks to the backspace key, I type backwards even faster ... clickity clickity clickity WHACK WHACK WHACK clickity clickity clickity, etc.
Where am I going with this?
I'm working on my second book, the sequel to Ohlen's Arrow, tentatively entitled Ohlen's Bane. The first weekend I worked on it, I cranked out over 12,000 words. I typed a lot. Since then, my word count is up to 15,000. I decided to read over what I had so far, and although it was interesting, it wasn't engaging.
The last thing I want is for my book to require the reader suffer through to the fifth chapter before anything good happens. One of the things going for Ohlen's Arrow was its pace. It started with action and maintained an engaging level of action with few pauses throughout the story.
I am now killing my babies. As I read through my first four chapters, I am looking for sections that can be rearranged to maintain a better pace. I'm also looking for sections that aren't important at all. When I find them, I kill them. I'm not tied to the words I created. I can remove them and write new ones, better ones. The story also has sections that take far too long to get across what can be conveyed either indirectly or simply.
Because of my technical background, I tend to be rather verbose in my descriptions. I am learning to adopt a more compact and dense writing style, conveying an equal or greater amount of information in fewer words.
My goal is to write 100,000 words for Ohlen's Bane. I'll probably write more than that, because I know that during the revision and editing phase of the project, I'll be whacking the backspace key a lot more than any other.
I am willing to kill my babies.
Since moving to computers, I can edit as I type. I still type close to 90 wpm, but thanks to the backspace key, I type backwards even faster ... clickity clickity clickity WHACK WHACK WHACK clickity clickity clickity, etc.
Where am I going with this?
I'm working on my second book, the sequel to Ohlen's Arrow, tentatively entitled Ohlen's Bane. The first weekend I worked on it, I cranked out over 12,000 words. I typed a lot. Since then, my word count is up to 15,000. I decided to read over what I had so far, and although it was interesting, it wasn't engaging.
The last thing I want is for my book to require the reader suffer through to the fifth chapter before anything good happens. One of the things going for Ohlen's Arrow was its pace. It started with action and maintained an engaging level of action with few pauses throughout the story.
I am now killing my babies. As I read through my first four chapters, I am looking for sections that can be rearranged to maintain a better pace. I'm also looking for sections that aren't important at all. When I find them, I kill them. I'm not tied to the words I created. I can remove them and write new ones, better ones. The story also has sections that take far too long to get across what can be conveyed either indirectly or simply.
Because of my technical background, I tend to be rather verbose in my descriptions. I am learning to adopt a more compact and dense writing style, conveying an equal or greater amount of information in fewer words.
My goal is to write 100,000 words for Ohlen's Bane. I'll probably write more than that, because I know that during the revision and editing phase of the project, I'll be whacking the backspace key a lot more than any other.
I am willing to kill my babies.
Labels:
editing,
Ohlen's Arrow,
Ohlen's Bane,
process
Monday, November 4, 2013
NaNoWriMo and Ohlen's Bane
November is National Novel Writing Month, or NaNoWriMo. The goal is to write 50,000 words in 30 days. I had already begun writing my new novel, Ohlen's Bane, at the tail end of October, a process that included brainstorming and then creation of a plot event list. I set up Scrivener to have proper chapters and scenes based on that plot event list and had even begun writing Chapter 1.
Now that November and NaNoWriMo has come along, the timing is perfect for keeping me motivated. Over this past weekend I cranked out over 12,000 words on Ohlen's Bane and am now neck-deep in Chapter 4.
I set up Scrivener to have a project goal of 100,000 words, and a session goal of 3,000 words. It's very rewarding to see that 3,000 word goal whoosh by with tons of creativity and energy left in me. I think 50,000 words by November 30th is a very achievable goal.
Now that November and NaNoWriMo has come along, the timing is perfect for keeping me motivated. Over this past weekend I cranked out over 12,000 words on Ohlen's Bane and am now neck-deep in Chapter 4.
I set up Scrivener to have a project goal of 100,000 words, and a session goal of 3,000 words. It's very rewarding to see that 3,000 word goal whoosh by with tons of creativity and energy left in me. I think 50,000 words by November 30th is a very achievable goal.
Labels:
NaNoWriMo,
Ohlen's Bane,
Scrivener
Wednesday, October 30, 2013
Announcing Ohlen's Bane
I have begun writing the sequel to Ohlen's Arrow and have tentatively titled the new book Ohlen's Bane.
For the observant among you, you'll notice the A-B sequence between titles. This is intentional, but 'Bane' is not mere alphabetical coincidence, it is very apropos to the story.
Although I won't give away any spoilers, I can tell you that Ohlen and his friends will face the biggest challenge of their lives in this second book of the series.
Series? Does that mean there will be perhaps a third book, making it a trilogy? Honestly, I don't know. It's possible, though. Stay tuned.
For the observant among you, you'll notice the A-B sequence between titles. This is intentional, but 'Bane' is not mere alphabetical coincidence, it is very apropos to the story.
Although I won't give away any spoilers, I can tell you that Ohlen and his friends will face the biggest challenge of their lives in this second book of the series.
Series? Does that mean there will be perhaps a third book, making it a trilogy? Honestly, I don't know. It's possible, though. Stay tuned.
Subscribe to:
Posts (Atom)

