As an author, there are days where it is difficult to write. If you’ve been reading the blog, you will see for me there are many more days where “writing is too hard” and I do other things. I’m slowly grinding through the Luctation rewrite, and hit a bit of a wall with a subplot that needs content. Rather than face the need to create, I turned to “comfort food” of managing the business of writing. After all, I am a project manager by trade. The problem is I have a nasty habit of keeping everything in my mind.
As an author, I’m always looking for opportunities to improve my writing productivity. I recently had a chance to read a book entitled Million Dollar Productivity. That provided a lot of good advice about how to improve writing productivity and production rate so that you can get to a much more effective so you can enjoy a much more effective writing career.
Inspired by Jamie Rubin’s article on Scrivener & GitHub, I have fully moved my toolchain to Scrivener, while still using a private Git repository. I wanted to write a brief series on what I’ve done to convert my old process, or to automate certain housekeeping tasks. This is the first in the series, which shares a simple process for pushing commits of a Scrivener project to GitHub.
October is National Disability Awareness Month, so I’m a little early with this article. But I wanted to share a bit about how I was able to use an assistive technology to fix a decade-old plot problem.