Revision is where the magic happens

“Yorkshire Sculpture Park” (scrappy annie, CC-BY-NC 2.0)

Recently on Twitter I wrote: “Revision is where the magic happens.”

I’m not trying to be mysterious here. I truly believe revision is where a story is honed, sharpened, and distilled. Revision is where the writer’s vision and passion surface after cutting away the dead weight and dead prose. The act of revision is pruning back a bush and revealing the topiary within. Revision is cutting away the stone block to find the sculpture trapped inside.

My tweet was in response to a question (“What’s your favorite part of the writing process?”) which was followed by a warning (“If you say revising I will have a hard time believing you”).

What can I say. Every stage of writing is difficult. There are no moments of pure pleasure for me. Even calling a manuscript finished and walking away is painful. The satisfaction is in the sum of the parts (akin to “work is its own reward”) as well as pride in the finished work.

One response to the question said something to the effect of “getting paid is the best part of writing.” That’s not part of the writing process, no more than collecting the bill is part of the cooking process in a restaurant. Even if you’re earning enough from writing to keep the lights on, great, but that’s not the writing process.

Make your phone your next writing notebook

A smart phone and a writing notepad.
r. nial bradshaw (CC BY 2.0)

Last week I finished my fourth novel and I used my phone throughout the entire writing process: developing, researching, outlining, plotting, and revision, all the way to my final draft. For all purposes, my phone was my writing notebook for this novel.

I didn’t write the novel on my phone. I’ll probably never do that. When I’m writing I want the full typewriter experience, real keys designed for human hands, the tactile sense physical buttons offer, the whole shebang.

But planning and revising a novel on your phone is certainly possible, and my latest book is proof of that.

In the past I’ve relied on paper-and-ink writing notebooks. A writing notebook is a tool I evangelize to anyone who will listen, mostly because I believe it functions as a kind of “inspiration laboratory” for writers. However, towards the end of my last novel (Hagar’s Mother) I found myself turning to electronic note-taking tools during the final editing process.

In the final stretch of editing a novel a torrent of small details begin erupting. When the edits are coming hot and heavy I find removing my hands from the keyboard to be a distraction, so I began using a free note-taking software packaged with my MacBook Air, Apple Notes. Rather than reach for a pen and my trusty notebook, I would Alt+Tab to Notes and add a bullet point to a little checklist I kept. As I kept working I would periodically consult my checklist and be sure the appropriate changes were made.

Well, Apple Notes is also available on my iPhone. At all times my writing notes were synchronized between my computer and my phone. That meant I could review my checklist while at work, on the bus, even in bed. It also meant I could add more ideas at any time. Later, when I returned to my computer to resume writing, they were there waiting for me.

That’s the hard reality I faced, one I’m certain most writers face as well: While I sometimes leave the house without my writing notebook, I never leave without my phone. These little devices are simply invaluable to us (which is why I encourage writers to keep them in mind when writing their own fiction).

After Hagar’s Mother, I decided to try an experiment and use Notes as my primary writing notebook for my next novel. I told myself if I had the slightest of problems I would bail out and revert back to my old paper-and-ink notebook. It seemed a risk-free experiment.

Well, I finished my novel and I’m here to tell you: I’m sold. Yes, you can plan, write, and revise your next novel using your phone as a notebook. What’s more, you don’t need to spend an extra dime on additional software as long as you’re using a reasonably up-to-date computer and smart phone. The note-taking software already installed is probably good enough, and if it’s not, there are free alternatives available.

Ways of note-taking

Let me get this out of the way: I’m not a shill for Apple. I’m happy with Apple Notes and how cleanly it intersected with my creative process. That doesn’t mean you should use Notes if you don’t own Apple products or want to try something else. (I list some alternatives at the end of this page.)

Looking back over my notes, I see three “types” of pages I developed, each representing a period of time in the novel-writing process.

The earliest pages are scrapbooks of ideas, thoughts, and research. Random notions fill these pages alongside bits of dialogue, descriptions, even character names. (With my fiction I try on character names the way I would try on a pair of pants.) For every novel I will read up on related subject matter to ensure I’m getting basic facts and terminology correct. Using my phone’s Share button I could add any page—Wikipedia, a news article, even a word in my phone’s dictionary—to a note. Although the foundations of the book are laid here, much of this primordial stew didn’t wind up in the final draft.

Later in the writing process, the pages start becoming more organized and less free-form. Here I was thinking about scenes I was developing. Dialogue and descriptions on these pages often reached the final draft. I also began roughing out timelines in these pages, primarily fleshing out the backstory of the main character.

The last note pages are highly organized. The novel was gelling; the big ideas are down on the page and I was more concerned about the small details and tightening up the narrative. In this stage my note pages are mostly checklists of changes to be made. The pages are broken up into sections: Characters, Details, Terminology, Important, and so on. When I made the edit, I would check off the item.

This stage is where I wrote a final character list (to keep track of names and relationships) and lists of terminology and spelling (useful in a novel with imaginary technology). I also built a final master timeline which incorporated the chronology of the novel into the backstory—useful when a character is talking about an event as happening the day before when it actually occurred two days before.

A few points here. First, notice the pages are structureless because the process is structureless. Even the later page’s organization is more-or-less free-form. The notebook met whatever need I had at the moment and never imposed a system on me. Some writing software wants to “guide” you through steps or categories for organizing your work. I’m not sold on that idea. I could use the digital note pages for anything I wanted to preserve for later. Make your writing notebook a tabula rasa.

Likewise, avoid reminder or to-do style software. Yes, I use checklists in my writing notebook, but I also used it for so much more. Task software imposes organization on your creative output. (“Mark this task High, Medium, or Low?”) That’s not what you’re looking for with a writing notebook.

These notes did not happen in concerted bursts. They represent hundreds of points in time, some slivers of seconds to type out an idea. At any point in the novel’s progress I was adding notes on the bus, at work (shh), in my easy chair, even while in the gym sweating and madly tapping a thought that came to me on the treadmill. The phone was always there. Losing even a single story idea to the frailty of human memory and our shortening attention spans is a loss.

Before you start

If you’ve read this far, you might be excited to start using your phone for your next big writing project. There are downsides to keep in mind before you start.

First, be aware you’re entrusting your precious creative output with a third-party corporation. Apple (or Google, or Microsoft, or whomever) could, at any time and with no warning, discontinue the software, discontinue their services, or even go out of business. Whatever software you work with, be sure you can export your data, even if it’s nothing more than printing out your notes or saving them as a PDF. You absolutely do not want to wind up in a situation where a corporation has your precious creative output locked up—or has deleted it.

Just as you protect your word processing files, make periodical backups of your notes in case of disaster. Most modern note-taking software has some method of doing this in such a way that the backups can be restored later if necessary.

Do a little research into your software’s data security practices. While you’re at it, make sure you’re using a strong password. No, I’m not worried about an author “stealing” my ideas, but I do worry about unknown persons accessing my notes without my consent. My writing notebook is a creative and freeing place. Part of that freedom rides on an expectation of privacy.


If you’re curious or excited to start using your phone as a writing notebook, your first step is choosing your software. My checklist for baseline features it should include are:

  • It should run on your phone and your writing computer. While you could turn to your phone while typing on your writing computer, I found it invaluable to be able to read and update my notes without leaving the screen. Being able to Alt+Tab to my notes and Alt+Tab back to my word processor was invaluable when the story was flowing and I couldn’t type fast enough.
  • Your notes should synchronize between every computer you use. In the 1990s synchronizing data between computers required specialized software and arcane cables. These days synchronizing should occur across the Internet, all-but-invisible to you.
  • Your notes should be available on the Web. It’s handy to be able to access your notes from anywhere. In the case of Apple, I can login to Your software should have this feature as well.

You’ll notice that the above three points revolve around a single convenience: access. The key to my success with note-taking software was that I could access it at any time. You never know when or where inspiration will strike. Recording and returning to inspiration is the entire reason for keeping a writing notebook.

(The reason I like being able to access my notes outside of a Web browser is simple: I turn off Wi-Fi when writing. Disabling Internet access is a great way to avoid temptation.)

Those are my top-tier must-haves for a digital writing notebook. Features I think are desirable include:

  • Checklists. It’s great to be able to add checkboxes next to the edits I need to make. It’s even better to check them off when they’re done.
  • Scrapbooking. Surprisingly, I found myself harvesting ideas from Web pages more often than I expected. Being able to store links, photos, dictionary definitions—even maps—was invaluable.
  • Folders & note organization. Eventually I would fill a page with so much raw material I needed to create a second page to continue, and subsequently a third. Organizing all these pages into distinct folders is a must.

Other features to look for:

  • Drawing or sketching. If you like to doodle in your writing notebook, you might seek out software that supports drawing. (Alternately, you could use a separate sketchpad app and add it to your notes.)
  • Audio notes. Some note-taking software can attach voice memos to a note. It’s not how I work, but it might be yours.
  • Searching. It’s surprising how many times I remembered a key word but could not find the exact note for it.
  • Collaboration. Some software allows you to share your notes with one or more people. If you’re collaborating on a novel with another writer (or illustrator, or editor), this might be a real need for you.

If you’re not an Apple user or seeking alternatives to Notes, there are other options you can investigate. I’ve not had a chance to use any of these but they seem promising:

Good luck!

Computer programming & writing fiction: Iterative processes

Repetition (elPadawan, CC BY-SA 2.0)

Repetition (elPadawan, CC BY-SA 2.0)

Previously I’ve noted the similarities between computer programming and writing fiction, saying both attracted their own practitioners. I then explained why I view computer programming, as well as computer programs, as forms of art.

How else is writing fiction like computer programming? Practicing the two, one common aspect I’ve gleaned is their repetitive natures. Both are iterative processes.

I cannot in good faith declare any fiction I’ve written “done” until I’ve read the final draft from start to finish eight or more times. (Usually the number is higher.) With each read, sentences are moved or removed, paragraphs rearranged, punctuation revised, word choices are evaluated, and so on. Shaping prose is one of the most important skills a writer can cultivate. (Journalists do this in their sleep. Minutes after the final out, San Francisco Chronicle baseball writer Susan Slusser files a game summary that is polished, informative, and to the point.)

In fiction, editing is usually described as fine-tuning a manuscript, but more often it’s about being bold—knowing when to strike a paragraph, a page, or even a chapter, all in the service of a better story.

As any computer programmer can tell you, this is a familiar process. Programmers probably spend more time at the keyboard revising existing code than writing new code. Small program edits—similar to line edits or word choice—are common enough, but when more major surgery is performed, programmers will often use a special word: refactoring. Refactoring is restructuring existing code without changing its external behavior. (It’s usually done to make the code easier to read and maintain, not to add a new feature or fix a bug.)

That’s the crux: Without changing existing behavior. It’s funny, in writing fiction, if you make a lot of bold changes, it’s considered a success if the story seems “new” or “better” to a reader. In writing code, success is if you make a bold refactoring and the program operates exactly as it worked before.

The Ouroboros

I enjoy reading how other authors developed their fiction. Authors selected for Best American Short Stories (and other volumes in the Best American series) are given the opportunity to write a capsule for the books’ back matter. They often discuss inspiration for the story, and how external factors shaped its outcome. Writers’ correspondence is another goldmine for learning creative processes. (In particular I recommend Raymond Chandler’s Selected Letters, which is a master class in writing, style, and technique.)

Often when an author discusses how they developed a story, I’ve noted they can’t pin down the exact moment of inspiration. There might be some flash where the creative process launches, but so many times writers confess how stories come from a nagging itch to write on a subject or develop some character trait. Long-forgotten inspiration will come roaring back to life for some reason. Writers some times talk about stories as though they “demanded” to be written.

Programmers have similar stories, although the inspiration may not be as abstract as, say, a line of dialogue or a character detail. Usually it’s a need driving the creation of new software, needs like “I wish there was a web site for me to connect to all my friends” (social networking) or “I wish I had a typewriter where it was easy to correct mistakes, and it would even check my spelling for me” (word processor).

Many times I’ve read of authors returning to old work and fighting (or succumbing to) the urge to edit it. The edits may only be a comma here, a semicolon there. They may be larger edits , striking paragraphs or scenes in the pursuit of a tighter tale. Programmers deal with this urge too, always looking to tighten up code and make it more efficient or elegant.

I’ve quoted this elsewhere, but it’s worth repeating:

…software development is an iterative and incremental process. Each stage of the process is revisited repeatedly during the development, and each visit refines the end product of that stage. In general, the process has no beginning and no end. [Italics mine.]

That was written by Bjarne Stroustrup, the inventor of the C++ programming language. Everything in this quote pertains to writing fiction as much as it pertains to writing code.

When I edit stories, I visit and revisit the story as part of the editing process, to smooth and refine the language, to ensure the story flows smoothly. Programming has a similar process, a continual revisiting and revision of the code to remove flab and tighten up its execution.

That’s what Stroustrup meant when he said the process has no beginning and no end. Stories and computer programs are never finished. They can always be made a bit better.

Sometimes alteration worsens the final product. When coding, I often talk serious changes as “surgery.” While it might be necessary, it’s possible to hurt the program while improving it. Touching code in one place can break code in another place. This is why sometimes you’ll download an update to an app and it seems slower or simply broken, even though the developer swears they’ve made improvements.

Likewise, fussing over a novel or a story can hurt it too. In the original editions of The Martian Chronicles, the chapters were dated like a diary, starting from 1999 and ending in 2026. Today, revised editions use dates from 2030 to 2057. A small change, undoubtedly made to preserve the story being told “in the future,” but it stole away some of the book’s charm. In my youth, 1999 was a magical date, a momentous odometer signaling a shift to the bold 21st century. 2030 is just another number.

A common adage among software developers is “Don’t fix what’s not broken.” The same can be said for fiction.


Paul Joseph. (CC BY 2.0)

Paul Joseph. (CC BY 2.0)

Programmer Ben Sandovsky observes:

Treat yourself [the programmer] as a writer and approach each commit as a chapter in a book. Writers don’t publish first drafts. Michael Crichton said, “Great books aren’t written– they’re rewritten.”

Sandovsky is exhorting computer programmers not to make hasty changes to a computer program, but to edit and revise those changes before officially adding them to the program.

Late in the editing process, I’ll often read my stories aloud to make sure they flow well. I’ve never read my code aloud—computer languages aren’t like human languages, for the most part—but I’ve certainly eyeballed my code closely, going over it line-by-line, before committing it.

I often use the word distill for both pursuits—to purify, condense, and strengthen through repetitive processes. Writers and coders don’t simply edit their work, they distill it down to its essence.

Lazy writing makes for boring reading. Lazy programming makes for buggy software. In general the process has no beginning and no end. The art is knowing when to let go and release your hard work to the world.