So, that’s all well and good, but how close am I to publishing? Well, closer than you might think…
I entered the new year intent on completing my Writing Database, the software that started as a project to learn Visual Basic and coding with the goal of replacing the various three-ring binders I’ve accumulated to serve as Series Bibles. The whole idea is that I’d open the Database on my desktop (or laptop) and be able to access all my notes and information without being chained to my residence or having lug around three-ring binders that will only grow in weight and size over time.
I had this goal, because I wanted to try to release Book 2 of my Fantasy series nine months after I release Book 1 (Awakening). I have many books I want to write, 54 in total thus far (including Awakening), and releasing one book every nine months means I’ll finish all the books I want to write in only 40.5 years. No problem, right? 🙂
Ideally, I’d like to work my way through the current list, releasing one book every six months…but I’m not sure I’ll be able to maintain my day job, publish a book every six months, and still feel/act/be even slightly human. The most time I’ll allow between books, though, is nine months. Any longer than that, and it doesn’t look good that I’ll finish my writing list in my lifetime.
I came to realize, however, that I felt an incredible pressure/weight hanging over me to publish Awakening. It had been too long. The time was now. So, I changed my focus. Starting Sunday (28 January 2018) afternoon/evening, I began the Second Rubber Ducky Revision of my manuscript.
What is a Rubber Ducky Revision? Why, I’m glad you asked…
I never knew what it was called when I print out my manuscript and read through it aloud, making notes where things are wrong or don’t read well, until a colleague told me about the Rubber Ducky of computer programming. The story goes that developers will sometimes keep a literal rubber ducky (or some other object, like a bust of Napoleon or a stuffed howler monkey toy) on their desk or in/around their work area. When they hit a rough patch in programming where a piece of code isn’t the working the way it should with no apparent reason, the developer will then describe the piece of code, what it’s supposed to do, etc. to the rubber ducky (or whatever). The way the human brain processes auditory stimuli differently than just reading something silently, it’s not uncommon for the developer to discover the problem while explaining the code or code problem. Hence, the Rubber Ducky Method…
The whole process of reading your manuscript aloud makes a considerable difference, and I highly recommend anyone who can’t seem to find the problem with a chapter or page try reading it aloud. You never know what will suddenly become apparent, because reading aloud draws on many different facets of your brain.
After several hours, I have worked my way through the first 20 chapters. That means there’s only 39 left! I doubt I can keep up this pace; after all, I’m writing this at 2:40am on a work day, but I’m wide awake. I might as well be doing something productive, and my throat and voice are a little tired after reading through 20 chapters. That’s about 147 pages, in case you were wondering.
I’ve given myself a deadline of 10 February 2018 to complete the Second Rubber Ducky Revision, but if I can keep even close to the momentum I have so far, it won’t take that long.