Externalizing inspiration

<cite>North American Review</cite>, May/Aug 2009.

North American Review, May/Aug 2009.

Last time I wrote about keeping a writing notebook. Let’s say you started one, or have been keeping a notebook for some time. What do you do with it? Once you’ve filled a notebook with all these ideas, how do you transfer that inspiration to a final story or novel?

From an essay I wrote for North American Review regarding a short story of mine they published, I discussed how I used a writing notebook:

On occasion I revisit my writing notebooks for inspiration…Many of my stories evolve from my own (sometimes misplaced) attempts to wire two or three bits of disparate inspiration together and see if sparks fly.

The inspiration for the story the published (“The Obituarist”) came from three lines scribbled into my notebook years ago:

“The Obituarist – Dying, old age, writes obits for living ppl. Also writes fiction—short stories?—and has come to realize that man is reliant on conflict, tension, etc. because all our stories rely on them, and they are not stories otherwise. Speaking to a young person writing his obit. (Or he writes book reviews.)”

That was it. I had a title alright, and some idea of a character and his situation, but nothing further. As I explained for NAR, about a year after writing this in my notebook I began working on the story itself, which is now collected in A Concordance of One’s Life.

This is the true value of a free-form writing notebook. For some people, a writing notebook is to prevent forgetting something. For others a notebook is a journal, a way to talk to one’s self, a method of expressing pent-up emotions.

My writing notebook is to externalize my thoughts. Externalizing inspiration, no matter how crazy or random the inspiration may seem, is itself an act of creation. Writing an idea in a notebook is as important as sitting down before the computer and formally typing the story. Those erratic sentences I scribbled about the obituarist were not subsidiary or tangential to writing the story. Those words were the genesis. The story started with them, not a year later when I typed the opening sentence in my word processor.

By committing some scattered notions to the page, I’m getting them out of my skull, where they’re fluid, malleable, and insubstantial, and forcing them into the physical world, where they take shape and harden into form. It’s important to judge my ideas objectively in the bald daylight to determine if they’re worth expanding upon.

Plenty of my inspirations go no further than the notebook. That’s not a bad thing. Most do not age well. When I return to my notebook, I often blanch upon reading these old inspirations. I will hurry to turn the page—a sure indication I made the best decision not to pursue them.

Wiring sources of inspiration together

A Concordance of One's Life by Jim NelsonIn my NAR essay I wrote that “The Obituarist” grew from a single idea. More often I find success in combining ideas, “to wire two or three bits of disparate inspiration together and see if sparks fly.”

I hold a pet theory that true inspiration is rarely, if ever, a single atomic idea. I see inspiration as multiple ideas coalescing. They accrete mass over time until a tipping point is reached and the creator feels the urgent need to get the accumulation down on the page in the form of a story. (Or on the canvas, or modeled in clay, and so on.)

For an example of wiring disparate bits of inspiration together, I point to another story in the collection, “A Concordance of One’s Life.” The elements from my notebook contributing to the story include:

  1. Man writes a concordance of his own memoirs (but why?)
  2. Adult feels cheated about something that happened when he was young
  3. Small town becomes a literary tourist attraction (a la Hemingway’s house in Key West)
  4. A man with a name no one can pronounce

When I began writing “Concordance” the early drafts only involved points 1 and 2. When I paired them, I thought I’d answered that first question (“but why?”). I was wrong; the early drafts of the story went nowhere. I’d noted the second two bits of inspiration in my notebook before starting the first draft but failed to make a connection. I thought they were for a separate story, if I used them at all.

In a later draft I added the third inspiration and sparks began to fire. The quiet mountain town as a tourist attraction added a quirky backdrop to my drafts, odd scenes of faceless people going from location to location with their well-worn concordances in hand. Still, the story was shiftless and moody and failed to progress.

The final bit of inspiration came from waking one morning and, hazy-headed, realizing the cheated man was not the concordance’s author. Rather, the narrator was a friend or an acquaintance who went unmentioned in the concordance (even though everyone else in town is described within it). I’d given up on the story several times over a span of nearly two years. Patience and focus on the story’s needs led to plenty of sparks that Saturday morning. The draft I wrote became more-or-less what was published by Watchword later that year.

(Somewhere in this is a moral about not giving up on stories, but I must confess it’s sometimes good to cut anchor and move on. Some stories simply cannot be salvaged.)

The fourth point on inspiration—”man with a name no one can pronounce”—found its way into the story during the Saturday morning writing session. I’d been thinking about the man with the unpronounceable name as the basis for another story, but it had no feet. At the computer Saturday morning, I included it as a gag, a side bit of detail. As the story came to fruition, I realized it was one of the most important and salient aspects of “A Concordance of One’s Life.”

Making the most of your writing notebook

Pablo Picasso – Tête d’Homme (1969) (CC BY 2.0)

You keep a writing notebook, right?

Years ago I attended an exhibition of Picasso’s sketch pads and notebooks. People thronged he museum fascinated with the charcoal and pencil scratchings of a 20th century oil painting master. Most of the sketches were loose, ad hoc, even sloppy. None of Picasso’s originals were on display. Scaled-down reproductions were presented beside the sketches produced in preparation for the final work.

What drives my fascination with the exhibit are not the sketches themselves. As artifacts, yes, they were captivating. (Imagine pages upon pages of the best doodles you ever saw.) What was more fascinating was their role as the connective tissue between Picasso’s imagination and the final masterpieces he executed over a lifetime.

We have no analogue in the world of fiction. Perhaps Hemingway’s or Henry James’ notebooks are studied by literature students, but I can’t imagine the notebooks of even the most famous writers drawing the attention of Picasso’s notebooks (although some of those writing notebooks are not forgotten).

Don’t keep a writing notebook for posterity. Don’t expect anyone but you to read it. But if you have any interest in writing, I recommend keeping a writing notebook. If it was good enough for Picasso—and Hemingway, and Henry James—it’s good enough for you.

Not an organizer

Let’s get this out of the way: A writing notebook is not an organizer. Keep your to-do lists somewhere else.

I actually have two writing notebooks, one for inspiration and ideas, the second to organize the nuts-and-bolts of my writing: producing treatments, sending query letters, and so forth. For the second, I follow a simplified version of the Bullet Journal approach, which has served me well for years now.

You’ll be tempted to keep your organizer and writing notebook in the same physical book. I caution against it. An organizer is exactly that, a place of constraint, rigidity, and order. (In other words, it’s to get things done.) A writing notebook needs to be a free-form place. Random ideas, bits of dialogue, strange notions, bits of fleeting language disconnected from anything rational. A writing notebook can even hold drawings, things like maps or bizarre flora & fauna.

I separate my organizer from my writing notebook for a reason. If I combined them they’ll blend, and I’ll find myself attempting to organize my creative notions. Rigidity comes later in the writing process.

I’ve inhabited a number of different writing notebooks over the years. I once went through a series of the ever-trendy Moleskines, pocket-sized and hardbound with their handy elastic band to keep the book shut. Most memorable is their twee “As a reward: $______” on the inside cover, allowing the owner a chance to estimate the dollar value of their own musings.

There exists numerous Moleskine knock-offs fine for the job. I’ve gone through several and can’t recommend any one. To mix things up, I’ve tried other notebook form factors as well. I even once experimented with a high school composition notebook, thinking the different size might yield unexpected fruit. (It did, but not in the way I was expecting—which was the entire point.)

Don’t get locked into one writing notebook manufacturer or model. Different paper weight, rule widths, dimensions, and bindings will subtly produce variation in the words you pour across the pages. The same goes for ink and pen types. The only variants I’ve not explored are graph paper (which I fear will introduce too much inflexibility) and unlined paper, which sounds like pure chaos for this writer, a man who barely read his own cursive.

As far as organization, I go minimal with my writing notebook. If I have a story or novel in mind, I’ll write my working title at the top of a fresh page, add the date for my own reference, and start writing. (I usually have at least one title in mind when I reach for my notebook, even if doesn’t survive to the first draft.)

If the idea is a random thought not associated with a story, I’ll give it its own page with the most simplest or basic of titles at the top of the page, only to separate it out from the other work I’m developing.

Even if my idea is merely one or two sentences, I’ll usually give it it’s own page. Don’t fear mostly-empty pages. There’s no reason to be aggressively economical with page use. That’s about as far as I go with organization.

I also don’t worry about being orderly with my entries. For example, I have a novella side-project at the moment. When I longhand narration into my notebook I do not concern myself with entering the new prose in chapter order. I don’t worry if what I’m writing follows anything else I’ve written in the preceding pages, or even if I will use it at all in the final work. If I’m inspired to write, I write.

Giving myself the freedom to write whatever I want whenever I want to is important. Artificial barriers such as “I can’t write this until I’ve finished that” merely give me a reason not to write at all, the biggest threat for any writer.

I try to ensure I have my notebook on me whenever I’ll be in a place when I can allow my thoughts to wander and explore. No, I don’t carry it with me at all times. (I don’t even carry my smartphone with me at all times.) If it makes sense for you to keep it on you at all times, do it—but don’t forget to carry a pen as well. One without the other is all-but-worthless.

My writing notebook is also not merely for writing prose. For example, when working on a novel I might have a page or two dedicated entirely to listing the names of the book’s characters. This allows me to swiftly look up a name if it slips my mind while writing chapters. For Bridge Daughter I had pages of medical terminology, real and fictional, as the novel employed quite a bit of it and I wanted to ensure consistency.

I don’t produce a table of contents or an index for my notebooks (such as how the Bullet Journal system advocates). When I’m entering words in the computer, I trust myself to recall what I’ve written in my notebooks and dig it out on-demand. (This sometimes means having two notebooks handy when I’m typing, as my ideas on the book may span more than one.)

Nothing is wasted

Returning to Picasso’s notebooks, another impressive aspect was their sheer volume. He produced metric tons of work he never intended to show or sell. These were for him, not us, as a means to an end.

I’ve frequently heard of or witness writers being stingy with their output. They view five pages of prose in their notebook never being published—or even making it into a working draft—as a “waste.”

Nothing is wasted. All writing is practice for the next round of writing. If you view every word in your writing journal as precious and must be conserved the way crude oil or drinking water must be conserved, you’re doomed.

Like Picasso, view your writing notebook as a place to be sloppy and free, a place to expend language wantonly. Be verbose, be chatty. Don’t worry about passive voice or tense changes.

I save all my old writing notebooks (for nostalgia, I suppose), but I don’t obsessively mine them for ideas, thinking each little scrap of language or inspiration must be utilized. My notebooks brim with imaginative dead-ends. I’m fine with that. I’d rather my ideas rot in my notebook, off the vine as it were, rather than go to waste on the vine—lost as fleeting thoughts in my head.

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.

Writing better fiction with Syd Field’s three-act screenplay structure: Now write it again

Syd Field

Syd Field

(See my “Continuing Series” page for a listing of all posts about using Syd Field’s paradigm to write fiction.)

Previously I discussed the fiction writer’s treatment (and how it’s different than a film treatment) as part of this series on how to use Syd Field’s three-act screenplay structure for writing stories and novels.

To recap, a fiction writer’s treatment is a way to prepare yourself for producing a rough outline. The treatment asks direct questions about your story and force you to start thinking about its skeletal structure. The eight questions of the treatment are:

  • Protagonist: Who is the main character of this story?
  • Setup: What is the minimum of backstory, history, setting, or exposition that must be presented before the main story begins?
  • Inciting Incident: What event disrupts the rhythms and rituals of the main character’s daily life?
  • Plot Point #1: What reverses the main character’s daily life such that there is no easy return to normalcy?
  • Conflict: What is the primary or core conflict the main character now faces?
  • Assessment: What does the main character do to immediately resolve Plot point #1?
  • Midpoint: What revelation or reversal of fortune occurs that permanently shifts the story trajectory?
  • Plot Point #2: What dramatic or defining reversal occurs that leads toward a confrontation with the core conflict?

Although it looks like a lot of work, as I mentioned before, you should only be answering each question with one to two sentences. Remember, the treatment is for you and no one else—it’s to get creative juice out of your head, where your story is ethereal and plastic, and put it on the page, where it hardens and takes shape.

Writing down answers to these questions commits you to something. It puts a stake in the ground rather than allow your loosely-connected story ideas to jounce about in your skull. The treatment isn’t a hard contract, but it does dare you to commit to something regarding your story.

I assume some people reading this will already be skeptical about this process. I assume some will resist any process at all, in fact. But if you’ve come this far with me, I’m asking you come a little farther and see what happens to your creativity when you expend a little effort organizing it.

As I said, answering the above eight questions—on paper—is a kind of commitment on your part. Let me assure you: You’re not committing to anything. You’re free to write whatever story you want, or even not to write this story at all. For a little effort you can get an idea of just how much you have in the bank—and how much more you need to develop to finish your story.

A treatment is not saying “This is what the story is about.” Rather, it asks, “What if the story was about this?”

Also know that writing a treatment isn’t the end goal of this process. When you’ve finished answering the above eight questions, you’re not really finished. There’s two more steps to writing a fiction writer’s treatment.

First, walk away

That’s right, walk away from the treatment (and your entire story) for a while. Take an hour, a day, even a week. Keep your treatment with you or handy so you can review it during this duration.

If you feel the urge to write a chapter or a paragraph of your story, go ahead, but resist the temptation to jump in and write with abandon. It’s important to let your creative juices stew.

If you can get your head away from your nascent story for a period of time, you might discover later you’re surprised by what you wrote. That’s a good sign. You also might find yourself bored by what you wrote. What seemed exciting or fresh when answering these questions may become boring or predictable later. That’s important too.

You might discover that, out of the blue, new ideas arrive in this interim to supplement or replace your old direction. The plane crash on the nightly news might turn into an auto pile-up happening before your protagonist’s eyes. The widow who arrives in town with shocking revelations might become a widower with a long-lost will. And so on.

Be open to fresh inspiration and new ideas. Don’t dismiss new directions that don’t neatly fit into your initial notions of what the story is about. Receive them warmly—they may lead you in surprising directions.

Second, write another treatment

That’s right, after a brief period of time, sit down and write another treatment. Don’t look at the old one. Don’t revise the old one either. Write a fresh treatment, answering all the questions I listed above.

If you find yourself answering questions more-or-less the same as before, that’s fine. That likely indicates you’re happy with the answer and should continue pressing forward. (It may indicate you’ve run out of ideas on the topic—be sensitive to that as well, it may portend trouble ahead.)

As before, you’re not committing to this second treatment, but by externalizing your ideas, you’re putting a stake in the ground.

Rinse & repeat

There’s a third, perhaps obvious, step: Do this all again. Yes, wait a bit of time to ponder and consider—and then write another treatment.

Once you’ve done a few treatments, they shouldn’t take more than fifteen or twenty minutes to produce. (Be thoughtful. Don’t rush through it.) That strikes me as a pretty good bargain considering the novel I write might take years to complete.

Next: A case study in writing treatments

Computer programming & writing fiction: Is coding art?

Girl with an 8-bit EarringIn my last post comparing writing programming and writing fiction, I concluded both were similar because of their relationship with their practitioners. “Art is a kind of recruiting poster for itself,” I wrote. “An art attracts its own artists.”

Wait—is computer programming art? It’s accepted to call fiction art, but can computer programming really be considered

the conscious use of the imagination in the production of objects intended to be contemplated or appreciated as beautiful, as in the arrangement of forms, sounds, or words. (The Free Dictionary)

Think of what programming a computer really boils down to: Ordering and organizing a series of mathematical instructions followed precisely by the machine. The computer is allowed no imagination in its interpretation of those instructions (if it possessed an imagination, which it doesn’t, at least not today). If there’s an art in computer programming, it stands in the purview of the programmer, not the machine. That’s how it should be. The art of painting is not in the tubes or cans of paint, but in the painter.

But is the arrangement of those computer instructions somehow “beautiful”?

It’s important to discern a difference between a computer program being art and the act of programming as an artistic form. Let’s start with the latter.

I believe programming is an art form, at least by modern notions of the term. Writing fiction and writing code requires continuous subjective decision-making during the entire process (a “conscious use of the imagination”). A personal fervor is vital for quality results. When a writer lacks that fervor, it shows in the end result, both for fiction and computer programs.

Programming is not a rote process of memorization and recall. There is no “correct” way to write a computer program but, like writing a novel or a short story, there are many wrong ways.

Bill Atkinson, creator of the original MacPaint, painted in MacPaint. (Daniel Rehn, CC BY 2.0)

Bill Atkinson, creator of the original MacPaint, painted in MacPaint. (Daniel Rehn, CC BY 2.0)

Coding requires taste, aesthetics, and an eye for detail. Programmers develop deeply personal philosophies. Some coders prefer verbosity (like Henry James in his later years) while others prefer economy (like Hemingway or Cain’s early work).

There’s a scene in August Wilson’s Fences that is one of the most distilled scenes I’ve ever read: The father and son debate buying a TV to watch the World Series. On the surface a mundane domestic moment, the scene is actually Fences in-miniature. The beauty of this scene mirrors brilliant software design, where each piece of the program is intimately connected to the entire application.

Years ago, I could always tell when I was working with a programmer who started coding on the Macintosh versus a programmer weaned on Microsoft Windows—the two companies have distinct programming styles and philosophies. Programmers who learned to code on those operating systems carried those styles and philosophies with them to other platforms and projects.

A computer program can be functional, operating, and seemingly free of bugs, and a programmer may still read the code and say it doesn’t “look” right. (The trendy term for this is “code smell.”) What’s more, two programmers may say a program doesn’t “look” right for entirely different reasons. This reminds me a great deal of the world of poetry, where poets may agree a poem is poorly executed and then squabble over the reasons why. (There are similar disagreements in the world of fiction, but I find them to be less…doctrinaire.)

Writing and programming both involve elements of discovery and improvisation. Even though I’m writing a series of blog posts advocating outlining stories before writing them, I don’t believe an outline can—or should—contain every detail present in the final story. An outline should not be so rigid as to prohibit discovery during the writing process.

For a long time, there was a big push to eliminate discovery and improvisation in the world of software development, as “discovery” and “improvisation” seem undesirable in a field of proper engineering. (In the 1960s, IBM famously discovered that the number of bugs a programmer produced was proportional to the amount of code he or she wrote. Their solution: limit the lines of code a programmer could write per day, a logic straight from the pages of Catch-22.) Newer software philosophies, notably Extreme Programming and Agile development practices, have flipped that thinking and embraced discovery and improvisation as healthy and necessary.

Suspicion of programming as an art form probably springs from a general lack of understanding of how programs are written. Programmers share an arcane terminology among themselves. They build and manipulate mysterious machines that have come to play a powerful, sometimes menacing, role in our lives.

<cite>Ex Machina</cite>, a 2015 film about a computer programmer who falls in love with an artificially intelligent android.

Ex Machina, a 2015 film about a computer programmer who falls in love with an artificially intelligent android.

That suspicion probably also arises from stereotypes. Programmers don’t look like artists. In popular culture, programmers are portrayed as geeks more comfortable around machines than humans. Sometimes coders in film or TV even fall in romantic love with their own programs. (Never mind that this trope originated in antiquity and regards an artist and not a bricklayer or farmer or soldier.)

Another reason people question programming as an art is that computer programs “do” things. There’s an academic suspicion of pure art having any sort of utility, probably due to fears of commodification and commercialization. We don’t think of Vermeer’s Girl with a Pearl Earring as “doing” anything other than hanging on a wall in some drafty museum, but it must be doing something to cause people to stand in line for hours to view it. It’s funny, this idea that pure art doesn’t “do” anything when it so plainly does. If art didn’t do anything, why would we care about it?

And this rolls back to the distinction I made earlier: Is computer software itself art? I’ll challenge the question with a question in return. We regard skyscrapers and bridges and automobiles and colanders as kinds of art. We laud architects, automotive designers, and commercial illustrators as artists. Why treat computer programs and their creators differently?

Next: Iterative processes

Colander, c. 1600 - 1650, Museum Boijmans Van Beuningen

Colander, c. 1600 – 1650, Museum Boijmans Van Beuningen

Computer programming & writing fiction: Art as a recruiting poster

IBM SelectricHow is computer programming like writing fiction? Is writing code anything like writing stories?

When I was young, perhaps seven or eight, I banged out my first short story on a second-hand IBM Selectric typewriter my mother brought home from her office. Powered on, the Selectric vibrated the whole desk and emanated a low mechanical hum, some unseen engine in the contraption idling. I still recall the smell of the ink in the typewriter ribbon and the satisfying, officious schock as the typeball jumped from its perch and tapped lettering onto the crisp onion paper I’d fed into the roller.

The story I wrote was a retelling of Richard Connell’s “The Most Dangerous Game” transplanted to a science-fiction setting. (In fact, I think I creatively titled it “The Most Dangerous Game in Space”.) My determination to spend hours coping with that unforgiving contraption went beyond an affinity for the classic short story. As an avid young reader, I’d come to wonder if I could pen my own fiction. My aspirations weren’t so bold as to imagine being published, only to see if I could write my own, but later that dream crept in too.

The Most Dangerous GameAround the same time (this would’ve been 1979), I cajoled my parents into buying a home computer. Silicon Valley was marketing home computers as personal productivity assistants, devices to balance one’s checkbook, manage a home mortgage, track stocks, and so on. Home computers were also being pitched as tools to give students an edge in school. I couldn’t care less about schoolwork—and I’ll be damned if that computer ever balanced my parents’ checkbook—but with a home computer I could play video games, my only real motive for wanting one.

Innumerable hours playing videos games led me to try to write my own. It was a natural progression, just as reading I, Robot set me to thinking of my own robot stories.

I never did write a video game, at least not one that anyone would want to play, but software development did become my career path, one I’m still following over 35 years later.

Likewise, although I didn’t finish that short story, writing fiction remains an important passion in my life, even more important than programming.

Walking these paths, I’m sometimes asked if writing software and writing stories are the same. Or, at least, if they bear any similarities. And my answer is, yes, there are commonalities between the two.

I’ll explore more parallels in the future, but already I’ve alluded to one thing they have in common. I’ve never met a good writer who wasn’t first an avid reader, and I’ve never met a good programmer who wasn’t first an avid computer hobbyist.

Art is a kind of recruiting poster for itself. An art attracts its own artists.

Next: Is coding art?


Greatest rejection letter of all-time

Galaxy Science Fiction, March 1953Recently I picked up Robert Silverberg’s superb Science Fiction 101: Exploring the Craft of Science Fiction, an unfortunate title for a remarkably sturdy book. Part memoir, part writing guide, part anthology, I’d recommend it to every writer whether or not they’re interested in science fiction as a genre or pursuit.

Silverberg mingles his breezy autobiography of struggling to get published as a young man in the 1950s with nuggets of practical writing advice he picked up along the way. All of this package is humbly offered to the reader. Even when penning the book in 1987, Silverberg remains in awe of Asimov, Bradbury, and Heinlein (“our Great Exception in almost everything”), although by that time Silverberg’s name was mentioned in the same breath as those masters, and more.

Galaxy Science Fiction, August 1951Science Fiction 101 also reprints thirteen classic science fiction stories from authors like Damon Knight, Philip K. Dick, Robert Scheckly, Vance, Pohl, Aldiss…the table of contents reads like the short list of first-round inductees to The Science Fiction & Fantasy Hall of Fame. Alongside each story, Silverberg comments on why it impressed him and what he gleaned, offering hard, complete examples to his writing wisdom that so many other guides lack.

It’s fair to compare Science Fiction 101 to Stephen King’s On Writing. Both books are a bit more practical and pragmatic in their advice than loftier musings on the craft, such as John Gardner’s The Art of Fiction. I suspect Gardner would peer down his nose at writing advice from Silverberg or King, which is too bad. Anyone who can forge a lifetime career with pen in hand deserves to be listened to and considered.

As a young man, while sweating over a typewriter struggling to earn publication credits in the science fiction magazines of yore, Silverberg also earned a degree in English Literature at Columbia University. He applies some of that study here, coming up with incisive observations about storytelling I’ve not seen made before. Offering advice on how to build a story, Silverberg does something wonderful and avoids the conflict word. I’ve discovered “conflict” is off-putting to some young writers, possibly because it suggests violence or supercharged stakes or overwrought emotions. Instead, looking back to the ancient Greeks, he frames story as propelled by dissonance:

Find a situation of dissonance growing out of a striking idea or some combination of striking ideas, find the characters affected by that dissonance, write clearly and directly using dialog that moves each scene along and avoiding any clumsiness of style and awkward shifts of viewpoint, and bring matters in the end to a point where the harmony of the universe is restored and Zeus is satisfied.

It’s not the final word on how to write a story, but it’s a surprisingly serviceable start.

Galaxy Science Fiction, November 1951Silverberg’s candor and generosity to the reader is so no-nonsense, he even reprints the rejection notes he received while canvassing science fiction magazines with his early work. Big-name writers usually dip into their rejection stack for the wrong reasons: to settle a score, or thumb their nose at those who stood in their way years past. Here, Silverberg reprints rejection slips that served to make him a better writer, admitting how he deserved them, and how he was often too young to take their advice at face-value.

My favorite rejection letter comes from H. L. Gold, editor of Galaxy Science Fiction. Galaxy was a bit before my time (I grew up reading Analog, Asimov’s Science Fiction, and The Magazine of Fantasy & Science Fiction). but Galaxy was well-known to me merely by its reputation. Galaxy was a “serious” science fiction magazine, known for avoiding the lewd subject matter and titillating covers the other science fiction magazines lured in readers with. (I’ve included a few of Galaxy‘s best covers here. The Internet Archive has a remarkable collection of back issues, covers and inside matter, that’s well worth perusing if you have any interest in science fiction’s past.)

Galaxy editor H.L. Gold sent Silverberg this rejection in 1956, when Silverberg had already broken into the field and was padding the back pages of science fiction magazines:

You’re selling more than you’re learning. The fact that you sell is tricking you into believing that your technique is adequate. It is—for now. But project your career twenty years into the future and see where you’ll stand if you don’t sweat over improving your style, handling of character and conflict, resourcefulness in story development. You’ll simply be more facile at what you’re doing right now, more glib, more skilled at invariably taking the easiest way out.

If I didn’t see a talent there—a potential one, a good way from being fully realized—I wouldn’t take the time to point out the greased skidway you’re standing on. I wouldn’t give a damn. But I’m risking your professional friendship for the sake of a better one.

Robert Silverberg was 21 when he received this remarkable letter, perhaps the greatest rejection letter of all-time.