The absence of technology in literary fiction

Smartphones by Esther Vargas. (CC BY-SA 2.0)

Smartphones by Esther Vargas. (CC BY-SA 2.0)

One of my complaints about literary magazines—both the small lit mags of university English departments and the literary lions like New Yorker, Tin House, and so forth—is the peculiar absence of up-to-date technology in their fiction. Characters don’t send much email. People rarely text each other. Voicemail is about the most modern of the Information Age conveniences in contemporary literature, and even then, it’s usually summarized by the narrator rather than “heard” by the reader. Why?

It’s no longer cyberpunk for your characters to have instant access to cyberspace in their coat pocket. It’s not science fiction for your character to read the morning news on a handheld view screen. Literary fiction often preens itself as being “realistic” compared to genre fiction, but how realistic is it today for a mother of two in Long Island not to have a 4G touch tablet in her purse or a FitBit on her wrist reminding her she’s not burned enough calories today?

Unless it’s set in the past or some truly remote locale, you forfeit your right to call your story a work of realism if your characters don’t have access to the Internet and they’re not using it fairly regularly. Digital access is simply that pervasive, worldwide. Yes, there are exceptions. I’m certain some writers think their characters or their settings are those exceptions. Probably not, though.

One reason for technology’s absence in literary fiction, I suspect, is that modern tech screws with storytelling. As greater minds than me have pointed out, we live in a age bereft of bar bets. The Guinness Book of World Records was originally conceived to settle, once and for all, pub arguments over sports records, but it was Wikipedia that ultimately fulfilled that burning need. Any question we have about the world or history, the answer can be located in an instant.

It carries into personal relationships as well. People no longer craft letters and post them in a box, then anxiously await a reply over the next days or weeks. When I was young, a friend might say he would call at eight—and so I would have to wait by the phone in the kitchen at eight o’clock, telling everyone else in the house not to make a call because I was waiting for one. My parents would wake my brother and I up in the middle of the night to say hello to our Midwestern relatives because the long-distance rates dropped after 11pm. (Remember paying a premium for long distance calls?) For years, many of my extended family members were nothing more than a tinny voice at the other end of a phone line and a yellowing Kodachrome print in my mother’s photo albums.

For all the nostalgia value of these tales, I’m happy to no longer be bound by such ancient analog technology. The key word of modern communications is instant. Unfortunately, such friction-free gratification often runs counter to a lot of storytelling precepts, things like tension (which involves time) and desire (which involves immediacy).

But mostly I suspect the writers of contemporary literature simply don’t like modern tech. Receiving a pop-up on your phone for an email explaining a long-forgotten lover’s death lacks a certain airy elegance that a hand-penned note on hospital letterhead offers. The terseness of SMS and instant messaging grates against the literary author’s desires for eloquence and nuance.

More broadly, there’s a general disdain for popular American culture in our contemporary literature. SUVs and dining at Olive Garden are often literary code words for boorish, crass people. Sympathetic characters tend to read the New York Times on Sunday mornings, walk to work, raise a vegetable garden, and run into friends at farmers’ markets.

This is one reason why I don’t buy the assertion that contemporary American literature is realistic. Too often it presents a world the writer (and their readers) would like to live in. That’s not hard realism. And this restrictive view of proper living feeds back on itself: literary magazines print these stories, developing writers read these stories and think they represent “correct” fiction, and so they write and submit likewise.

Give your characters the technology they deserve. If you’re writing about the past, that’s one thing, but if your story is set in modern times, don’t shortchange your characters’ resources.

Instead of viewing commonplace technology as a liability to storytelling, consider how vital the technology has become for us. Watch this magic trick, from Penn & Teller’s Fool Us:

The audience feels the risks the emcee is taking when instructed to place his own phone in an envelope. The surprise when the mallet is brought out, the tension it raises. Look at the audience’s visceral reaction when the mobile phones are hammered up. Even though Penn & Teller see through the act, there’s a kind of narrative structure to the magician’s “story.” At each step of the act, the stakes are raised.

Do this: The next time you’re out with a group (people you know and people you’ve just been introduced to), pull up a photo or a message on your smart phone, and then hand your phone to someone else. (Or, if someone offers you their phone, take it, twiddle with it, and hand it to another person.) Rare is the person comfortable with this. We don’t like these little things leaving our grasp.

That means, as writers, these devices are a goldmine.

We are wed to our new conveniences in way we never were with “old” modern technology like microwaves, refrigerators, or even automobiles. Americans may love their cars, but they are married to their smart phones. Our mobile devices are lock-boxes of email and text messages, safe deposit boxes of our secrets and our genuine desires (versus the ones we signal to our friends and followers). Gossipy emails, intimate address books, bank accounts, baby pictures, lovers and lusts—our lives are secreted inside modern technology. This is rich soil for a writer to churn up, this confluence of personal power and emotional vulnerability.

Why dismiss or ignore this? Why not take advantage of it in your next story?

A fourth alternative to the Iowa writing workshop format

In my last post on writing workshops I discussed the Iowa writing workshop format and three alternatives to it: Liz Lerman’s critical process, Transfer‘s submission evaluation, and playwriting workshops. Thinking about those alternatives led me to think about a hybrid that I hope makes the fiction workshop more constructive.

This hybrid isn’t merely a group discussion structure, it’s a collection (or, less charitably, a grab bag) of suggestions for organizing a workshop. I’ve grouped this grab bag into three sections: organizing the group, managing manuscripts, and the group discussion itself.

Organizing the group

Define the goals of the workshop

For some people, the primary goal of a writing workshop, perhaps the only goal, is to make fiction publishable. For others, a writing group is a place to receive direction and encouragement toward completing a larger project, like a collection of short stories or a novel. Some writers are there for the camaraderie and to maintain a semblance of a writing practice in the face of hectic modern schedules. Others write for themselves (or a small audience) and have no broader ambitions of mass publication. For some people it’s a combination of these things, and maybe more.

In my experience, most people attend workshops with the goal of eventual publication. But even if everyone agrees on that goal, it only raises more questions: published where, and for what audience? Can any member in the group really claim knowledge of when a story is “publishable”? Genre writers add a monkey wrench to the mix—someone who regularly reads Tin House, The New Yorker, and The Paris Review might not the best arbiter of when a science fiction novel is ready for shopping around.

(In my experience, editors and publishers are in better positions to decide if a story is publishable or not. I was once told a story was unpublishable and weeks later landed it in a highly-regarded magazine.)

Liz Lerman’s process has some applicability here. As a baseline, agree that everyone in the group has an opinion of successful versus unsuccessful fiction, “success” being related to the quality of the work and not who might or might not publish it.

Also agree that everyone in the group is present in order to make everyone’s work more successful, not merely their own.

How a writer uses that successful fiction—publication, independent distribution, blogging, or simply personal satisfaction—is the purview of the writer and not the group as a whole.

Agree what’s expected of each member

Most people join a workshop thinking they know what’s expected of them and everyone else. Rarely does everyone truly agree on those expectations.

On a basic level, people understand they’re expected to

  • read the manuscripts presented to the group,
  • formulate some manner of thoughtful response,
  • attend the group meetings with some regularity,
  • and engage with the group discussion.

I’m not a big fan of credit-and-demerit systems, but some groups use them for motivation (such as “you must attend three meetings to submit one manuscript”).

Additional expectations are discussed below, but the point I’m making here is to verbalize (and even write down and share) these expectations. If you’re organizing a workshop for the first time, you might use the first meeting to allow everyone to air what they expect from the others, then coalesce those points into a list. Differing notions of expectations can lead to headaches later.

Cover the workshop’s agreements with each member

For each new member, go over the group’s structure and policies and goals with all the other members present—in other words, don’t do it privately over email or the phone. This ensures that everyone’s on the same page. It also refreshes the memories of long-time members. Avoiding miscommunication is incredibly important in a workshop group.

Stick to your workshop’s structure unless everyone agrees a change is necessary (or, after a vote).

Don’t make exceptions. Exceptions kill the group dynamic. People begin to see favorites, even if no favoritism exists. Remember, this is a peer group evaluating peer writing.


Enforce page count and style

The era of the 25-manuscript-pages short story may be receding (I wish it wasn’t), but that hasn’t stopped writers from penning them. The problem with bringing so many pages to a workshop is that people are bound to skim long work. That means they have less understanding of the story and are less qualified to discuss it. The peer pressure to discuss it remains, however, and so people will.

I’ve brought in long work many times to workshops. In almost every instance, I’ve heard comments (or outright griping) about the length. It seemed odd to me that writers would complain about having to read 25 double-spaced pages, but then I reminded myself they’re reading work they probably would not pick up on their own.

I’ve also noticed my shorter work almost always received higher-quality reads and discussion.

Some groups limit submission length to 20 or 25 pages. My suggestion is to go further and require manuscripts be no longer than 10 or 12 pages. Yes, that means having to split long short stories into two or three segments, but the writer will get a better read of those segments. Chuck Palahniuk’s writing group in Portland has such a page count restriction. Its members seem to have done fine by it.

Page count restrictions require basic, common-sense manuscript style formats. Make it clear: double-spaced, 1.5″ margins, 12-point Times New Roman, or whatever format your group decides. I’ve seen writers game the manuscript format to subvert page counts. Don’t stand for it.

Agree on the role of manuscript edits

A lot of people in fiction workshops think there’s big value in marking up the manuscript itself. I’ve had manuscripts returned to me so marked-up I didn’t know what to make of them.

Some readers drew lines like football plays over my pages instructing me to cut sentences, insert or remove paragraph breaks, rearrange scenes, and so forth. One workshop reader circled every instance of “has”, “had”, “is”, and “was” to alert me of my overabundance of passive voice, even where no passive voice existed. Other readers circle words and mark them “wc” (“word choice”), insert and strike commas, semicolons, em-dashes, and so on.

Drawing attention to typos and misspellings is hard to argue against. Yes, if you see one, go ahead and circle it—but that’s gravy. Indicating confusion (“Who’s saying this?”) or highlighting passages that pop off the page have utility as well.

I’m arguing against line edits that are a matter of taste or philosophy. Telling me I should

  • change a word you found inexact or unfamiliar,
  • never to use passive voice,
  • only use “said” or “asked” for dialogue tags,
  • drop all semi-colons,
  • or strip out all adverbs,

these changes are not the purview of the workshop reader and, I would argue, counterproductive to a quality workshop experience. Too often the editorial mark-ups are writing lore masquerading as rules or received wisdom (and usually associated with some well-known writer who counseled them).

Assume everyone in the group is a capable writer. You are responsible for the fine-detail work in your manuscript, not the group. The workshop’s purview is to locate larger, broader issues in the story and (potentially) suggest paths forward for the next revision. Workshops are not editorial services for you, the writer.

My experience has been that people who make fine-detailed edits to others’ manuscripts are expecting the same in return. When they don’t receive them, feelings begin to bruise and grudges are harbored. Notions of equal work loads and reciprocity is often the source of fracture lines in a workshop.

If your group thinks it’s the purpose of the workshop to offer editorial changes, then make it an explicit policy.

Agree what the group will read

Again, this may sound obvious, but it’s worth verbalizing it rather than risk trouble later.

Agree on genre. Some fiction workshops will accept creative nonfiction, but rarely poetry or plays, if ever. I won’t argue one way or the other, but like my other suggestions, make sure everyone in the group is aware of restrictions. For example, I’ve witnessed friction where one member kept bringing prose poetry to a fiction workshop.

Some people will balk on this next point, but I’ll draw a line in the sand: The group should agree that the workshop isn’t there to critique first drafts. First drafts are too undeveloped and scattered to be productively critiqued in a group setting. Does it make sense to use six to eight other people’s valuable time to inform you of your first draft’s (usually obvious) problems? Especially when first drafts stand a high chance of being abandoned by the writer?

Likewise, late drafts are usually too set in concrete to receive any help from a workshop. If you’re unwilling to make substantial changes to the story, then asking the group to find its weaknesses is wasteful. (Never bring a manuscript to a workshop expecting unconditional praise. It never happens. Never.)

My rule of thumb: Workshops should be seeing stories after three or four drafts (or edit passes) and not after eight or ten drafts/edit passes.

Some groups allow submitting work previously read by the group. I would add the proviso that the work must’ve received substantial edits since its last go-around. Other groups may prohibit it or require full agreement. As before, don’t make this up as you go. Choose a policy and stick to it.

No one should ever submit a published story to a workshop. Yes, people do this. (One exception to this rule: The story is up for republication and edits are permitted by the publisher, i.e. it’s being anthologized.)

Formulate a written response format

Some groups may forgo written remarks, especially if the manuscript isn’t handed out ahead of time. Otherwise the response format should be agreed on by everyone.

I don’t mean page length (“one page single-spaced”), I mean what questions should be answered in the written response. It doesn’t have to be a fill-in-the-blanks approach. You could simply have a list of questions and ask each member to verify those questions have been answered (in one way or another) in their written response.

My suggestion? Use Transfer‘s system. Each reader writes on a 3-by-5 card a 1–2 sentence reaction to the story and uses the remaining space to describe its strengths and weaknesses. Use both sides of the card. Then the cards are read to the group verbatim. Readers will learn not to use the watered-down language so often found in a full-page responses (“I really like this piece,” or “This is strong.”) From there, launch into the general discussion.

If a 3-by-5 card seems too small a space, choose a longer format, but I still propose a length limitation to elicit thoughtful responses.

I’ve become convinced that the real magic in a fiction workshop lies in the discussion, not the written remarks. By giving each person only a sentence or two for strengths and weaknesses, the discussion can zero in on those thoughts and use them as a springboard for exploration.

The group discussion

Read the story aloud before discussing

As mentioned in my prior post, I noticed in playwriting workshops how reader-actors became invested in their characters. For fiction, even with an eight-page limit, it would take too much valuable group time to read aloud the entire manuscript.

What’s more, fiction is an inherently different experience than theater. A person reading a story aloud will not become as invested as an actor reading a script.

Still, I’ve been in groups where a selection of the story was read aloud before the discussion, and it did seem to help. Getting the story into the air brings the group together around the manuscript. Everyone is hearing it one more time—the language, the setting, the narrator’s voice, the dialogue.

If your group meets every other week, it’s possible a few people haven’t read the story in ten or more days. (It’s also possible some read it in the Starbuck’s around the corner fifteen minutes earlier—there’s not much you can do about that.)

Remember, the writer shouldn’t read their own story aloud.

Keep the discussion to what’s on the page

Discuss the story as it’s written. Avoid peripheral issues (such as personal viewpoints) and comparisons to other work (other authors, television shows, movies, and so on).

Personal viewpoints are a good way to poison a discussion. Saying things like “I would never do what the character did here” isn’t useful. A better question is: Would the character do what they did? Everyone holds a subjective internal logic. Most of us hold several subjective internal logics. Does the character’s actions match their internal logic(s)?

While a comparison to another work may seem harmless (“Your story reminds me of Mad Men“), popular culture is a kind of safe zone for people to retreat into. Pop culture will derail a workshop discussion. When the harmless comparison takes over, all discussion becomes re-framed by it. Instead of discussing the story, the group is discussing how the story reads in light of this other work or issue. (“Mad Men focuses on women in the workplace. You could add more of that.”) The story becomes secondary. This is unfair to the author, who has brought their work in to be critiqued on its own merits and weaknesses.

Workshop formats (including Liz Lerman’s) will often declare that readers shouldn’t make suggestions without the writer’s permission. This baffles a lot of people; if I’m not making suggestions, then what I am here to offer? Unearned praise and tender nudges?

Rather than distinguish between suggestion and not-suggestion, I say keep the discussion to what’s on the page. Staying close to the page means, for example, suggesting the writer remove a spicy sex scene because it’s unnecessary to (or even dragging down) the story. But suggesting the writer remove a sex scene because that would make the story suitable for young adults—a hot market right now—is straying from the page. Both are suggestions, but the latter is not the purview of the workshop per se.

Maintain a discussion structure

The Iowa workshop discussion format usually works like this:

  1. Each reader gives a broad reaction to the story.
  2. A general discussion opens between the readers, the writer only listening.
  3. The writer asks the readers questions.

Lerman’s approach is more involved and (as I discussed last time) more difficult to stick to, but it has some nice features that could be incorporated. For example, a workshop could be structured as so (incorporating some of the suggestions above):

  1. A portion of the story is read aloud by one of the readers.
  2. Each reader in turn reads their written remarks (or a summary of them) aloud. (This makes the 3-by-5 card approach more desirable.)
  3. General discussion by the readers. Keep the discussion to what’s on the page. Start with strengths, then move to weaknesses and confusion in the manuscript.
  4. The writer is offered an opportunity to respond to the discussion, ask questions for clarification, and prompt for suggestions.
  5. The writer summarizes what they’ve heard by naming three to five new directions the plan to explore in future drafts.
  6. If the group is open to re-reading work, the writer can announce what changes they intend to make before submitting it next time. (This is probably more useful in a graded academic setting.)

This is not radically different from the Iowa format, but by specifying the goals of each step, they aim to direct the group’s energy toward better revisions and, hopefully, better writing.

Appoint a discussion leader

In academic settings a discussion leader is naturally selected, usually the teacher or an assistant taking that role. Leaders occasionally run private writing groups when one member first organized the group or has been around the longest. Otherwise, workshop groups will often lack any formal leadership.

There’s a difference between an organizer and a discussion leader. Organizers solicit for new members, remind everyone when the next meeting will occur, arranges for a location to meet, send emails and make phone calls, and so forth. This is all important work (and harder work than it looks), but it doesn’t imply that the organizer should lead the group discussion.

I suggest rotating the role of discussion leader around the group. Round-robin through the members, skipping writers when their manuscript is under discussion. (The writer whose work is under scrutiny should never be the discussion leader.) Or, if multiple writers are “under the knife” at each meeting, let the writer not under discussion lead the group, and then switch the role to the other writer.

A lot of writers express disdain for discussion leaders, or for any manner of hierarchical organization. I would love to agree, but experience has taught me otherwise. There’s tremendous value in having someone appointed to direct the flow of the conversation and cut it off when it’s deviating from the agreed-upon format. I’ve witnessed a few situations where such a leader could have saved a group discussion, and even the group itself.

If you’re organizing a workshop, or are in a workshop and looking for positive change, I hope this ignites ideas and discussion. If you use any of these ideas, let me know in the comments below or via the social networks.

Writing better fiction with Syd Field’s three-act screenplay structure

Syd Field

Syd Field

If you’re a writer, consider if this sounds familiar:

An idea snaps into your head—a character, a situation, a setup, a name—and you dive in, pumping out a promising first chapter in no time at all. You clean it up and bring it in to a workshop or writing group. You get some input and take away some praise and criticism. Back at home you move on to the second chapter, and the third, and then…kaput. You’re out of gas. You make a couple of aborted attempts to keep at it, but it’s just not in you.

Months later you pick up the manuscript, tinker with it, and slide it back in the drawer. And that’s the end of your novel.

The frustration goes beyond hard work being “wasted.” (I don’t think any writing is a waste, it’s merely practice for the next round of writing.) No, the frustration is the hollow feeling that, with just a little more inspiration or skill, you could’ve pushed on and completed that novel. The frustration is the suspicion that, with just a little more planning, you would have a clear path forward.

I’ve not outlined or plotted every story I’ve written. I’ve completed a few stories without any serious planning at all that I would say I’m proud of. I might even say they’re “successful.” But I also know how many failed and false starts I’ve accumulated, a frustrating pile of corpses that simply didn’t pan out. I started thinking about how to outline a story and realized I didn’t have a definite idea of how to do it. I had a couple of notions, but nothing concrete.

Some time ago, when I was first coming to grips with how to write fiction—especially longer forms—I grew interested in the three-act structure screenwriters use. It’s a form Hollywood follows slavishly. Books on screenplay writing are almost entirely devoted to the structure, going deep into the mechanics and timing (that is, the page count) of each act. They detail what questions must be posed in each act and when those question should be answered, even breaking down each act into smaller subunits. It’s much more rigorous than anything I’ve seen in the world of fiction or poetry (which has an encyclopedia’s worth of its own forms).

My experience has been that fiction writers disdain the three-act screenplay structure. Actually, most disdain any manner of plotting or outlining, usually while murmuring something about “plot-driven fiction.” For them, the three-act structure isn’t a revelation, it’s the reason for all the pandering crap Hollywood churns out year after year. Others seem to have the attitude that outlining a novel is somehow “cheating.”

I’ve taken a fair number of playwriting classes and workshops. In them I was struck how theater, just like filmmaking, emphasizes structure over any other craft element. We found structure laced through plays as diverse as A Raisin in the Sun, Glengarry Glen Ross, Danny and the Deep Blue Sea, Noises Off, Cloud 9, and Fences—brilliant work, all of it, and nothing I would call “pandering crap.” But it’s right there on the page: structure, structure, and more structure.

The Headlight Method

Between all the fiction classes, workshops, writing groups, and how-to books I’ve read, it’s rare to find anything approaching screenwriting’s or theater’s level of emphasis on narrative structure. When I have, it’s usually a method for writing thrillers or “guaranteed” bestsellers, something to the effect of putting the character into deeper and deeper holes and forcing him or her to make harder and harder choices. Oh, and be sure to end each chapter with a cliffhanger. In the case of romance novels, structure is defined in terms of the types of motivations and the types of problems the characters will face. Others argue that most (or all) proper stories follow the Hero’s Journey, although I find that dubious, especially looking back on the literature of the last one hundred years. These are not the kinds of narrative structures I’m talking about.

Freytag's PyramidThe only vanilla structure I’ve seen consistently taught in fiction is the classic rising and falling action cliff ledge (also known as Freytag’s Pyramid). There’s tons of criticism of the pyramid out there. For my purposes, I ask if rising/falling action is an organizing principle or an observation. There’s a difference between a cake recipe and a photo of a finished cake sliced in half. In my mind, the cliff ledge is that photo.

Inevitably when discussing fiction and structure or outlining, E. L. Doctorow’s maxim makes an entrance:

Writing is like driving a car at night. You can only see as far as the headlights, but you make the whole trip that way.

Like opening a story with weather, this quote has become another scrap of writing lore, that body of accepted thought on the shall’s and shall-not’s of writing fiction. But reread that quote. Doctorow isn’t advocating structureless fiction or railing against the idea of outlining a story. All he’s saying is, you’re not going to know every little detail about a book before you start writing it. Even if you can only see as far as the headlight beams, there’s nothing wrong with having a map handy before you set out on your trip.

Last year I got serious about understanding how screenwriters craft a three-act movie script. In the process of researching the topic I molded the three-act screenplay structure into a form geared for fiction (novels and short stories) rather than movies. This process produces a rough guide for your story, disposable, and nothing more. I’ve applied it on a number of projects and found myself surprised at the results. And, yes, my writing has improved for it.

Syd Field

There’s countless guides, how-to’s, manuals, videos, and seminars on successful screenwriting. Syd Field’s Screenplay is, as I understand it, the Bible on the subject. First published in 1979, Field articulated his three-act structure (he calls it “the paradigm”) as a framework for telling a visual story via a series of scenes. Like literary theorists from Aristotle onward, Field recognized that most stories are built from roughly similar narrative architectures, no matter their subject or setting. In Screenplay he set out to diagram that architecture and explain how it applied to film.

Although Screenplay is the Genesis document, I recommend his Screenwriter’s Workbook (1984). It picks up where Screenplay left off, detailing discoveries and new thinking on his three-act structure. Syd Field made a lifetime career out of teaching people how to write movies; these two books are where he started.

Not everything Field discusses directly corresponds to fiction. Film is a different medium, after all. What I’ve tried to do is pare down and re-shape his three-act structure into something more appropriate for writing novels and, to a lesser degree, short stories. I’ve used this modified paradigm to write a four-page story (“The Last Man in San Francisco”), to revise a long novel that I thought was dead and lost (Edward Teller Dreams of Barbecuing People), and now a new novel (tentatively titled Bridge Daughter).

Let me be clear: this is not a robotic recipe for writing fiction. Syd Field did not lay out a formula for writing blockbuster movies, nor am I laying out a formula for fiction, bestselling or otherwise. This isn’t telling you how to write, it’s suggesting a creative process to engage with before you write. Basketball players take practice shots before a game; artists rough out ideas in their sketchpad before approaching the canvas; musicians practice their set before going into the recording studio. What I’m suggesting is for you to get some basic ideas about your story out of your head and on paper before you start writing.

Part two: “The paradigm”

“Never open a book with weather”

"In the Rain", Sascha Kohlmann (CC BY-SA 2.0)

“In the Rain”, Sascha Kohlmann (CC BY-SA 2.0)

Every profession, hobby, and field of study has its share of lore, that is, its own body of unsubstantiated knowledge distributed by word-of-mouth and emails, often winding up in textbooks and reference material. Most “common knowledge” is lore. Everybody knows that Macs can’t get viruses—but they can get malware, and they do. Everybody knows that the French eat better than Americans—but watch the Parisians line up at McDo’s for their Quarter Pounders and pomme frittes. There’s even office lore, the shared knowledge of how to unjam the printer and get around that bug in Excel. The thing about lore is, even if it’s accurate, no one knows why. If it works, the lore is reinforced; if it doesn’t, the lore may still survive. Lore is superstition for a modern world that thinks it’s shaken off superstition.

Lore shared among fiction writers is the worst. These received chestnuts of “wisdom” that all writers must adhere to continue to go unchallenged, both individually and as a body. Why is that? Why are we as writers so beholden to a list of unproven, unsubstantiated do’s and don’t’s?

Inevitably this writing lore is attached to the name of some Big & Important Author. If Carver or Faulkner or Flaubert said it, it must be true—or, more significantly, it must be deep and thoughtful. Another reason for the bulletproof status of this lore is that their rules are regularly reprinted in definitive texts and repeated by other authoritative authors.

Lore replaces thought. Instead of considering each and every sentence in your story, examining word choice and sentiment and motivation, lore is a handy feather-stuffed cushion to fall backwards onto. Lore in writing becomes a shortcut in an art form that is all about decisions. Ignorance of lore is to risk ridicule from peers and scorn from editors. Defying lore is to take a risk. That’s why it’s passed around so earnestly in workshops, writing groups, and creative writing classes.

It doesn’t help when a reputable literary bastion collects and collates this body of lore into a central location, even using the long-sapped form of the Top Ten list to help the practitioners organize their thoughts. Now, not everything on these lists is lore—plenty of it is hard-learned personal wisdom—but inevitably someone (“Elmore Leonard” being that someone) invokes that tired hand-me-down: “Never open a book with weather.” I’ve heard it phrased so many different ways I’ve lost count (maybe I should make a Top Ten list), but every variation involves “never”, “open”, “book” (or “story”), and “weather”. (The Guardian cribbed his list from The New York Times, incidentally.)

Elmore Leonard isn’t so stupid as to pronounce this absolutism and move on. He offers a justification (“If it’s only to create atmosphere, and not a character’s reaction to the weather, you don’t want to go on too long”) and an exception (“If you happen to be Barry Lopez, who has more ways than an Eskimo to describe ice and snow in his book Arctic Dreams, you can do all the weather reporting you want”). When you contemplate both of his exceptions, suddenly that “never” in “never open a book with weather” melts away like the warming Kilimanjaro snow.

Speaking of, this is what Hemingway wrote to John Dos Passos:

Remember to get the weather in your god damned book—weather is very important.

Hemingway managed to open “A Very Short Story” with a mention of the weather:

One hot evening in Padua they carried him up onto the roof and he could look out over the top of the town.

Here’s his rule-breaking opening to “In Another Country”:

In the fall the war was always there, but we did not go to it any more. It was cold in the fall in Milan and the dark came very early. Then the electric lights came on, and it was pleasant along the streets looking in the windows. There was much game hanging outside the shops, and the snow powdered in the fur of the foxes and the wind blew their tails. The deer hung stiff and heavy and empty, and small birds blew in the wind and the wind turned their feathers. It was a cold fall and the wind came down from the mountains.

Papa again, in “Cross-Country Snow”:

The funicular car bucked once more and then stopped. It could not go farther, the snow drifted solidly across the track. The gale scouring the exposed surface of the mountain had swept the snow surface into a wind-board crust.

I could go on. In fact, if you think of a story’s title as its true opening, Hemingway is even more guilty: “The Snows of Kilamanjaro”, “Cat in the Rain”, “After the Storm”, even perhaps The Sun Also Rises.

You might object that these openings are reflected in Leonard’s exceptions and provisos, but the lore of “never open a book with weather” that gets passed around somehow fails to mention any of them. Someone brings a story into a workshop that opens with rain drizzling onto a window pane and someone else pounces on the faux pas.

Worse, the lore of “never open a story with weather” is often misattributed to Hemingway, which is crazy: the man made a career and an unstoppable reputation based on writing about the outdoors. A writer of outdoors adventures would never respect “never open a story with the weather”—it’s like a mystery writer admonishing “never open a story with a murder.”

The prohibition against opening with weather is one more bit of lore designed to mystify and codify the craft. It bedazzles young writers who commit it to memory as the key to publication, and it offers easy ammunition to every hack who’s gone into a workshop oh-so-smug in the knowledge of why the story up for review is mortally flawed.