Collaborative Editing

Collaborative Editing

Another thing I had to work out with Paul (my editor) (no, saying “my editor” still hasn’t gotten old) was how to work together.

I do all my writing in Scrivener, a fantastic tool for creating, but when it comes to working with alpha readers or an editor, not so much.  Remember here that my work with Paul and my publisher is still very much in the world of indie publishing with little or no budget!

After trial and error, it seems that I have found a consensus: Google Docs.  Here’s the key features that I believe are making it so:

Ability to ask and answer questions: Is this the word you meant? This doesn’t make sense, what were you trying to say? etc.  Docs lets you highlight a chunk of text as a question, have a 2-way conversation, and ultimately mark it as “resolved.”

Concurrently working on the same document at the same time: This is a little one, but extremely helpful – I don’t have to worry about stepping on an alpha reader or editor’s work when I am responding and updating.  None of the save the file and let the other person know which version they should look at.  Handily even marks changes made by the other collaborators.  You can also open two copies of the same document if you need to look at something else without wanting to lose your place.

Chat: If you do happen to be working on the same document at the same time… you can online chat with your collaborators (in my case my editor) and sort things out on the fly.  I didn’t realize you could even do this until Paul (my editor) (nope, still not getting old) hit me up one evening while we were both looking at the same doc.

Versions and showing changes: This one seems pretty obvious, the the cool part for me is never having to think about it – it just does.  While not as powerful as revisions in Word, the ability to look at versions created over time is a great help in seeing what was changed.  And not having to fuss around with other settings is a plus.

Where is the Save button??? I add this mainly because I have had to get used to the autosave.  Even more dramatic, before I really knew about Google Docs, was not understanding why my daughter lost a term paper when borrowing my computer and using Word.  “What? You didn’t hit the save button?”  “Dad, what is a save button? (big mood)”  Point taken.

Mechanically, it is a little bit of work to use Google docs effectively.  Specifically, I export my writing from Scrivener in Word format to my Google Drive (which is shared with my editor)(…), open the document using Google Docs, re-save it in the new format.  Then I blow away the original Word Doc.  Going back the other way, I make a Scrivener snapshot of the scene and copy/paste the updated content back in.  A little bit of work, but well worth it in my opinion!

Apologies for the long post.  If you are still with me, my publisher (also not getting old) is planning a Kickstarter for the end of July to publish my short stories.  For more information, and to sign up to be notified when it goes live, head over to:

Voice and Editing

Voice and Editing

My first, introductory call with Paul (my editor) went great.  Total transparency here, I have never worked with an editor that would be taking a more technical look at my writing.  I have alpha readers, and I have greatly appreciated their feedback, but this feels like a whole other level for me.  In amongst geeking out on various things that we are, well… geeked about, we got to talking about writing and “voice.”

Before going any further – I have to say: I’m really excited about this project!  (bet you can’t tell)

One of the things we discussed was Voice and the use of colloquialisms. As an editor, this can make it hard for Paul to sort out whether I meant something to be grammatically incorrect as a colloquialism, or whether it’s just grammatically incorrect.

Stepping back for a second, its pretty cool looking at my writing through the eyes of someone else, an editor that is interested in preserving my writing style but also in cleaning up it and making it better.

We came up with a couple of basic rules (that I will also have to keep in mind as well!)
Grounders (lower social classes) generally walk on characters, will speak pretty heavily in slang and colloquialisms. Main characters, will be better spoken, but may slip into colloquialism when speaking with other grounders. Narrative voice will be the same. Highborn upper classes will be more formal.  I have read stories with slangy narrative voice and it just gets annoying pretty quickly.

Technical Plausibility

Technical Plausibility
One of the things I described to Paul (my editor) that I hope sets my writing apart from the usual steampunk is the plausibility of the technology.
The Brymlight stories rely on hydrogen as the source of energy – no crystals, alien substances, or other unexplainable magic. I tried to ground my writing in science and reality, if a bit stretched at times to make it work.
Hydrogen provides the lift that keeps the massive estates of the aristocracy afloat high above the plains of the American Colonies western frontier.  Ironically, those estates are both literally and figuratively tethered to the ground and their dependence on the lower classes that produces the hydrogen.
Production of the hydrogen is based on steam reforming, or steam methane reformation of natural gas.  One of the most common industrial approaches to manufacturing hydrogen and a number of other related products.  In the Brymlight world, the Whitley Hydro-Works is one of the largest producers of hydrogen, what our boffins are going to call “diprotium” and the more common term everyone else regularly uses: Brym.
Just for fun… steam reformation, in a deeper meaning, also refers to my break from the more traditional steampunk doctrine.