While on a family vacation in northern Idaho, I was having dinner at a place called 1313 in Wallace, Idaho. I asked our waitress if she knew where the title of the restaurant came from. She did, indeed. The restaurant’s original dimensions were 13 feet 13 inches square, a mightly small building by today’s standards. But back in the 1800’s that was pretty typical for a mining town.
Then she told us that she’s the owner of a flower shop a few stores down and that during Prohibition in the 1920’s there were tunnels built under many of the stores on the same side of the street and her store is actually linked to the restaurant with such a tunnel. Cool!
I filed that nugget in my brain, thinking maybe someday Joshua Jones would pay a visit to Wallace. That may still happen but the thought lingered in my subconsciousness. Yesterday I came across a random bit on the internet about the Boise Tunnels.
Back in the 1800’s Chinese workers were employed in great numbers for mining and rail line construction. Idaho and especially Boise has a rich Chinese immigrant history. Apparently, there are rumors that many Chinese workers constructed tunnels under the city of Boise that were then used as opium dens. Today the existence of these tunnels is largely unproven and only a small number of dedicated history buffs believe they ever existed.
These two references to tunnels mingled in my brain and eventually made their way into the plot of Kill Dash Nine. I can’t go into the specifics for fear of spoilers, but suffice it to say, I can actually trace the idea back to two references to Idaho tunnels.
I’ve started taking screenshots of my word count for each day I write on Kill Dash Nine (KD9). Thought I’d share the link for you if you like such things. I also include my wristwatch in these shots, because I happen to like them.
Otherwise, you can follow me on Twitter @Johnny_Batch, where I post these pictures after taking them. You can also head over to my GitHub account from the link to the left and see what I wrote.
For the past week, I’ve been writing Kill Dash Nine in a text editor and saving my daily writing sessions by committing them to a code repository. This is pretty much what any programmer does on a daily basis. I’ve actually been coding a novel.
This is a short lesson learned post on how that is going for me. My initial issues seemed to be with what program to use to write my novel in text format. Text editors are serious business tools for programmers. Ask anyone who codes what editor they use and be prepared for some very opinionated answers. As someone who does a bit of coding for his job, I can tell you my favorite editor is Atom.
So it was with Atom that I started writing with this week. But code editors have to be modified to write prose. They don’t have standard features that word processors like Write and Word have for formatting and composing sentences instead of code. So I had to find the proper plugins and modify how the editor worked to suit my needs.
I was able to write in Atom without much difficulty, but I quickly realized that using the text format was not the ideal way to write a novel as a flat file. What I needed to be writing in was Markdown. Markdown or .md files are are a basically HTML files without all the crazy open and close tags. You simply put a # tag on your title to set it as an H1 font size. Once you learn these tags, you can write nicely formatted text that translates to HTML better than any .docx file and with none of the extraneous, proprietary junk that Word includes in every document.
This realization had me searching for a good Markdown editor that would work on Linux. I tried a few of them and settled on two – Caret and Remarkable. I could use either one, but for now, I’m using Caret now because I prefer how it looks.
The other program I’ve been using is GitKraken to commit my daily writing sessions to the GitHub repository. I use GitKraken at work every day and love it. So using it to store my writing is a natural fit. I commit my changes after every lunchtime writing session and this lets me comment on the changes I’ve made and lets me come back and see for every commit what scenes and chapters I wrote or modified. For stats junkies or anyone curious how a creative mind writes a story, those stats are very interesting.
Do I recommend every writer doing what I have done? No. Unless you are comfortable with using these tools and adapting your process to accommodate them. But if you’re a writer who also codes, you will be right at home doing things this way if you don’t already do so.
Not many writers are well versed in programming or have similar IT knowledge. I happen to have some technical ability in this area and occasionally, I use it. I’ve decided to move KD9 into a source control program that is freely available on line, called Git.
Git was created by Linux Torvalds, the creator of the Linux kernel. He was looking for a better way to keep track of changes to the core of the Linux operating system. Somewhere along the way Git took off and now just about every programmer uses it to store their code. I use it at my day job and my son uses it for the tools he makes in Python and Java.
Besides, I write tech mysteries, it’s somehow appropriate that I write them in a programmer’s editor, Atom, and store them in Git. In order to make this happen, I had to save my manuscript in text format and then convert it to .md. Now when I commit my changes which are actually new chapters and scenes, I can diff them just like I do with new lines of code. Manipulating text files is at the heart of what programmers do and in many ways it describes the nuts and bolts of writing too.
The larger issue at hand is that my novel is now publicly available for anyone to read and even more interesting, for anyone to download. Will this prevent me from making money selling it as a novel? Maybe. But it’s been my experience that it won’t matter at all to sales. Readers don’t peruse GitHub looking for hot new novels. However, programmers do peruse the repository looking for code projects. If one or two programmers stumble upon my mystery novel about a programmer – I just might get another fan.
I’m willing to get those kinds of fans every time. Because they’re the ones that really love what I’m doing. They get me and my work.
If you have been thinking about becoming an Amateur Radio operator, I invite you to watch or listen to the latest show on the TWIT Network – HamNation. The show is co-hosted by Bob Heil and Gordon West, two pillars of the Ham community. It’s a great show and a fun way to get introduced to the hobby.
This is a screen shot I took of Bob from the latest show. I circled a rig behind him, because that’s the radio I described in detail in my novel, Null Pointer. A Hallicrafter’s receiver.
Partner’s In Crime (PIC) meeting second Tuesday of the month at the Barnes and Nobel in Boise. This month will be my first meeting since baseball season started, so looking forward to seeing everyone. If you read or write Mysteries, come on out and join us!
There are two versions of Null Pointer out there in the wild. The only official version is the one by Johnny Batch. If you get one by Ken McConnell, it is no longer supported by GB Press. There are still some of those Code Ball cover versions available both in ebook and paperback, but they are inferior First Editions that are full of errors.
The new version by Johnny Batch is far better and cheaper in paperback at $9.95 and only $2.99 for the ebook. You can get the ebooks for Kindle, Nook and from Smashwords in other formats. It is not for sale in the Apple Store or Kobo. If you want an open version of the .epub, get it from Nook.
The Null Pointer paperback is ready for sale on Createspace for $9.95. It will be on Amazon soon. I’ll keep everyone up to speed on that. In the mean time, I’m back to plotting the next Joshua Jones book.
Createspace is really impressing me with their customer service. I uploaded the two pdf’s for my book Monday morning, had it approved by them before noon, and it was printed and in the mail before I got home that evening. I just got the proof copy in the mail yesterday. Four days from upload to in my hot little hands. That’s outstanding!
We opted for the 5 x 8 format this time and I just want to say, it’s a perfect size for a paperback. Slightly larger than a mass market paperback and more comfortable in the hand than the 6 x 9 trade paperback. The fit and finish of the proof is excellent. As good as can be with a print on demand service.
There are a few little changes that we need to make, but I’m confident that we can fix them this weekend and have the second proof in hand by next Friday. Which means I can probably push the “Go” button on selling it next Friday. That’s outstanding and unbelievably fast for taking a book to print.
I have not used Createspace for a few years and I have to say, they are impressing me with how efficient they are on ordering a proof. I sent them the latest files Monday morning and by that afternoon I got approval from them and so I placed my order. Before I came home that day, I had a message that the proof had been shipped. Expected deliver next Tuesday. Sweet. And super fast.
Here’s a sneak peek at the cover wrap around image.