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.
This house in the Boise North End was the inspiration for Mashers, a video arcade on the first floor of a home near Boise High School. I just love the look of it including the wrap around porch and the stone first floor. Beautiful home with just a touch of mystery to it.
Mashers makes its debut in Kill Dash Nine the sequel to Null Pointer.
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.
Caret Markdown editor.GitKraken Git client.
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.
This week has not been a particularly productive one for the novel. I’ve missed two writing sessions leaving me with just three days in which to add to the novel’s word count. I normally write during my lunchtime in what I refer to as my lunchtime writing sprints. They are just like coding sprints but only last an hour each work day.
On a good day I can write about five pages of the manuscript in an hour. Over time, that’s a pretty decent pace to produce a novel in about three months time. But I can’t write every day and sometimes I write on the weekends and in the evenings so it all averages out in the end.
The novel is currently sitting at 63 pages and just over 16K words long. I’m on Chapter 7 and I’ve just written the first turning point in the story. This is usually when the hero realizes that he’s now in full danger of dying and must decide to act in order to survive. Normally I would get to this point in less than 20 pages so I’m thinking this novel will either need to be re-structured or will wind up being much longer than the first one, Null Pointer. I’m leaning towards the later as I would prefer to give the reader more story to chew on this time around.
Above is a shot taken near the Boise Convention Center in downtown and you can just see the condo building where the main character, Joshua, lives. The neon lights are a new feature and look amazing at night. You can easily imagine that one of the lights in the windows of the condo is Joshua sitting at his computer, coding away.
You read that correctly, your eyes do not deceive you. It’s 2018 and I have started writing the long awaited sequel to Null Pointer. Kill Dash Nine is the official title and it of course is named after the Unix Kill command. You can follow my progress by coming here and eye balling my daily word count and watch pictures. I’m just over 50 pages into the first draft and things are progressing nicely. I would like to finish it before Summer, but if it takes longer, I’ll gut it out. It should be released in ebook form at Christmas.
Here, enjoy this mock-up of the proposed cover art by yours truly.
I haven’t written a mystery in a long time now. It’s not my primary genre to read or write. But that doesn’t mean I don’t think about the next Joshua Jones book on a nearly daily basis. I’m always coming across interesting bits of information and jotting down notes. Usually those notes are saved online from either stories I’ve visited or research I’ve come across while online. But lately I’ve also started to compile old fashioned paper based notes into notebooks that are primarily used for journals.
For Kill Dash Nine (KD9) I’ve started such a notebook to capture my notes about characters, plot and locations. Anything related to the novel that I don’t want to forget, once I start writing. When I write a novel I usually follow an outline. I create this outline first and having it before me as I write helps keep the story flowing in the right direction and allows me to avoid writer’s block.
I write my novels these days using Google Docs. This allows me to use my primary laptop and a Chromebook backup laptop as needed. All my writing is backed up and in the cloud and updated instantly when online. It’s very convenient for my writing lifestyle. But it’s good to organize things on paper too.
It’s finally happening. I’m writing the sequel to Null Pointer. It’s called Kill Dash Nine. The first step is to build a Spotify playlist of songs that will inspire me. You can listen to this playlist here. It’s constantly changing according to my whims. NSFW.
The second step is to outline the novel. That is in progress. The actual writing will commence this summer. Stay tuned…
Wow, I can’t even do yearly updates to this blog. Fail. I haven’t begun writing the next book in this series, largely because the first book, Null Pointer has not exactly padded my wallet. At all. The best way to get an author to write more books that you like is to spread the word about the book and get others to buy it. It’s now only .99 cents on Amazon and Nook. I’ll be running some specials for it this year to try and boost interest.
But fans of Null Pointer need to leave reviews and spread the word before I can justify the time needed to write more books in this series.
See you in 2017, if I remember.
I’m putting together the outline for the next Joshua Jones novel in preparation for writing it in 2014. Hopefully that means you will have it in your hands in 2016, at least the ebook version. Not sure if I’ll do a paperback right away. Depends on how many of you are interested. The title is going to be Kill Dash Nine.
The other exciting news for 2014 is the production of a Joshua Jones Universe short story as a student short film. My short story “The Safe Cracker” is being filmed this fall as a student thesis film. More details later.
Thanks for you patience as this series was on hold for so long.