- 50,000 to 70,000 words
- 10-12 chapters
- 5000 words per chapter
- First write the story, then worry about exact chapter breaks
- Chapters can be of different lengths
- Chapters control pacing
- Rules are meant to be broken
As part of an experiment I’m doing, I’m trying to write many characters in my story without revealing their gender via pronouns. It’s actually not that difficult and I find it a fun challenge, though it slows me down because I usually do a first draft with pronouns and then restructure without. I might even get used to writing like this. I never thought before about how my writing was littered with pronouns, and how with a bit of care I could work without them. So far, I think it improves the writing, but we shall see in a bit.
I would, of course, like to write when I’m inspired. Having a family and a day job means that my writing is adjusted to my real life. This means writing late at night, often when I’m tired. It’s actually not so bad. What I discovered is that having some ambient music going settles my ADHD and focuses me quite a bit. Not everyday is productive – things happen in spurts – but it’s all good. I don’t set myself any word goals for the day, I set myself a time goal. I sit and write for an hour each night. If it goes well, I keep writing. Of course, as a result, it’s very slow. But the thing is: if you want to write a 50,000 word novel that’s just 137 words a day for a year. 200 words will get you 73000 words by the end of the year.
And, even if everyday is not inspired at the outset, once I started to force myself to write no matter what, I think I got inspired more often. Of course the writing needs polishing, of course I need to strengthen the weaker spots, but the main battle is to get some words on the page.
The positive side effect of this is that I watch less TV and I no longer play video games or engage in meaningless arguments on the internet. These unproductive late nights have been transformed into something more rewarding, where I can see something being built little by little each night.
I was looking at a list of fine open source software for writers and wanted to mention the tools I use. I use Markdown (#8 on that list) which is a very popular, lightweight markup language. Markdown’s philosophy is that it should look great as plain text and the markup should resemble the kind of hand formatting we use (or used) when all we had were plain text files.
Markdown by itself has two important, relevant limitations: you can not include documents in other documents, and you can’t make an automatic table of contents. Both of these are features of LaTeX that I miss in markdown. Without these you are forced to write everything in one big file, which I hate and to generate a table of contents manually, which I also hate. Never fear! There is tooling for that!
I use VS Code to write. It is an excellent code editor, and it turns out, excellent for writing science fiction too! It has a plugin called Markdown TOC, that can be configured to generate a TOC based on the headings in the document. I use this for research notes documents, however, and not to create a table of contents for my manuscript.
For the actual novel I use pandoc which is a fabulous tool everyone should know about. It is the swiss army knife of document format interconversion. I use it to convert my markdown writing into beautiful PDF via LaTeX. Importantly pandoc allows you to easily combine multiple Markdown documents into one PDF.
My text organization is as follows: I order by chapters by naming them 010.first-chapter.md, 020.second.chapter.md … I learned this numbering trick from John’ MacFarlane’s pandoc tricks page. In addition, I have a preamble file that contains some LaTeX instructions.
I wish to use the SFFMS LaTeX style file but ran into many problems when used with pandoc. I found that someone had made a pandoc style file specifically for this, and found it to be just the ticket. I use the story.latex template.
I use git for versioning (#4 which mentions gitbook, which is a UI on top of regular git). I store a copy of the repository on different online services for safety – if my computer breaks down, I will simply be able to clone my repository and continue working.
Why don’t I use Word? Or Google docs? Or Scribus or some other handily packaged tool with lots of widgets for writing? First, I’ve been burned enough by Word crapping out when the document gets big enough that I just don’t trust it. Second, I will never trust my precious writing to a complicated, proprietary binary format. I know that .docx is some kind of XML which is nominally an open sourced specification, but honestly XML?! I don’t think this is better. Plaintext files with minimal, non-intrusive markup is what I find best, and Markdown fits the bill perfectly. git allows me to revision my work and many online git hosts have beautiful tools to check diffs. VS Code gives a word count.
I’m a computer programmer by day, so I find “compiling” my novel to PDF periodically with a command line invocation to be perversely satisfying. Most people don’t and that is OK. I like the control and freedom that this simplicity brings me. I find that without any complicated formatting tools to fiddle with, I write more. I don’t need any fancy “distraction free” mode in my editor. It’s just me and my plain text.
A fascinating story I first read on CNN. The short of it is that recordings from temperature probes put in the moon by the Apollo missions recorded a rise in core temperature after the astronauts landed that was different from how the moon’s core behaves normally. After some investigation scientists concluded that this was due to the astronauts stirring up the lunar surface. This sifting of the soil changed it’s reflectivity and caused those stirred up regions to absorb more solar heat, causing the moon underneath to warm up more than usual.
It’s not that I’m that far ahead, but sometimes a whole event or episode will spring to me. I will be on the train, or at a function, and the whole scene will play out in my mind, vividly. And it will repeat on different days. And then I must write it down. And that becomes part of a chapter.
There is a lot of wisdom around throwing away writing. Most of what a writer writes should end up in the waste basket, If I had a longer time, I would have written a shorter letter, and so on and so forth. A pack rat like me, therefore, has it especially hard. Why, just now, I was meaning to get rid of all the older versions of the snowflake document and keep the latest one I was finally satisfied with. As I went to hit delete, I decided to read the older files just one more time. I read them, then I decided that, just in case, I would append that text to the end of my current snowflake. Yes, throwing away things is hard.