Saturday and Sunday, April 11 and 12, I’ll be posting a two-part blog interview with New York Times best-selling author Will Lavender, author of Dominance and Obedience. Stop by to learn about Will’s experiences working with major publishers and developing ideas for his “literary thrillers.” Chime in with your own experiences. I’m excited and I hope you are, too!
Blog Interview! Will Lavender, Author of Dominance and Obedience: This Weekend!
Filed under Interviews, Working with literary editors
First Lines of Novels: What Works?
They used to hang men at Four Turnings in the old days.–My Cousin Rachel by Daphne du Maurier
In the spring of that year an epidemic of rabies broke out in Ether County, Georgia.–Paris Trout by Pete Dexter
We slept in what had once been the gymnasium.–The Handmaid’s Tale by Margaret Atwood
It began the usual way, in the bathroom of the Lassimo Hotel.–A Visit from the Good Squad by Jennifer Egan
I’m collecting first line of novels that I think provide particularly good models and possibly rules of thumb for those of us hoping for just that one read. Why are these so important? I can’t help remembering my trip to the Backspace Conference in New York, sitting around a table for a “two-pages-two-minutes” critique with editors and agents. Reader after reader got stopped before getting past one-minute-one-page, or in some cases, thirty-seconds-one-paragraph. “This is too familiar,” said the agent. “I’ve heard this a million times before,” said the editor.
That experience impressed on me something my own experience as a browser in bookstores confirms: yes, the language of your whole book has to sing, but if you want people to pay the price of the concert, the first line has to be so high and clear and pure it blasts through their earphones as they’re passing on the street.
I thought I’d spend a few posts thinking about why these are examples of first lines that did that for me, in hopes of deriving some ideas as to how it’s done. I’d love it if readers would post their own favorites, with some speculation as to what makes the lines work. Be specific! Don’t just tell us “I like this” or “It works for me.” Why does it work? How does it work? So we can see whether we’re hitting your criteria in our own efforts.
Obviously, it’s not that the first line carries the book. The paragraphs that follow have to bear out the promise. But I do think that one strength of these lines is that they do make a promise. We read on to see if that promise is going to be kept.
Okay, the Daphne du Maurier line: what promise does it make?
It’s actually fairly simple at first glance–this is a haunted place. Only something bad can be set in motion here.
That promise resonates for me because I’m a firm believer in the truism that in narrative, only trouble is interesting. Promise your readers upcoming trouble in twelve simple words and they will at least finish the paragraph.
There’s more going on, though, I submit. This, like Rebecca, is to a great extent a Gothic novel, and “the old days” conjure the fatally romantic past that, in Gothic novels, no one will escape. The old days aren’t gone; they’re hovering in the shadow cast by this nameless “they” whose memory just won’t be expunged. The whole atmosphere of the book emerges: something looming. Its shadow is that of the noose.
I hear the rhythm of the sentence as well:
They used to HANG men /at Four TURNings /in the OLD days
It breaks into three parts, like a poetic stanza, with an accent on the next to last syllable of each phrase. We almost have three anapests, with a falling syllable after each. There’s all kinds of literary and neuro-cognitive speculation as to why rhythm captures us as it does; suffice it to note here that the accented moments are the central moments that almost deliver a message in themselves: HANG, TURN, OLD. Something old is going to turn on us and deliver us to that noose.
I’m going to finish the series before I try to generalize some rules from this example. I’m curious whether I’ll see the same things in all four.
Kindle Author? Take a look
In case you haven’t seen it: Kindle author.
Filed under Money issues for writers, Self-publishing
The Answer is 42
Having had the benefit of a nice road trip during which I was able to contemplate the issue I’ve been exploring in the last few posts—the virtues or lack thereof of letting learners figure things out for themselves—I’ve arrived at an unexpected conclusion. The answer to the question of whether this is the ideal pedagogical method, for teaching writing or many other things, is—drum roll—42!
No, seriously, the definitive answer is yes and no. Or, put differently, it depends. Or: on one hand, on the other. Or possibly: sometimes.
A quick recap: I’ve always wanted to learn programming. Told that Python was useful and accessible, I bought a $35 book. Within hours, I was just barely resisting the urge to hurl the book at the stupidly blinking computer screen. The author adopted the “throw them in and they’ll teach themselves to swim (or not)” school at its most extreme. He provided readers with code they were to dutifully copy, producing a simple game called “Find the Wumpus.” I copied, I played, I found the Wumpus. But throughout, I had to puzzle out for myself what different commands meant—for that matter, even how to write and run a command, which was one of the numerous things this author assumed I already knew how to do!
I showed this book to a mathematician friend adept at programming. He told me to go to Louisville and throw it off the Big 4 Bridge. “This is completely wrong. The way to teach programming is to provide short bits of code that illustrate specific commands and functions. Get another book.”
I already had, being a Very Smart Girl. I bought two on my Kindle. I perused the first one. Within just a few screens, I knew what operators were, and what some major ones did. I knew what functions were. (I already pretty much knew what variables were.) I knew the difference between a number and a string! (It’s just a matter of punctuation. If it’s inside quote marks, it’s “text” and it’s a “string,” Ain’t that cool?)
And yet.
I learned how to tell the computer to add 2 and 3 and get 5. I learned how to convert the price of an Apple computer into euros using functions. I learned how many spaces I could insert before a decimal.
No doubt there are people out there who need to do these things. Who want to do them. It was unclear to me why I would want to do them.
Here’s the upshot. The Find-the-Wumpus game, maddening though it was, Continue reading
Maybe Just a Tiny Bit More Rant. . . .
And some thoughts on what it means for writing.
Last time, I wrote about the tendency of the author of my beginning Python book (computer programming) to leave out what seemed to me simple yet rather foundational instructions for the beginners he was supposedly addressing, my implication being that he failed to understand his readers’ needs, thus undercutting the effectiveness of his text. I wanted to take the experience of trying to follow his directions toward a discussion of why (in my experience) many writers, including writers of fiction, seem to actively resent being asked to explain themselves to readers.
But I have a new gripe after working through Chapter 2. (I suppose I’ll have to take a vow not to collapse into a rant after every chapter! I do plan to buy another book to supplement this one, so if you were thinking of suggesting that. . . .)
In this chapter he gives you lots of steps. He gives you whole programs to copy into your text editor (characteristically without explaining that it’s in the text editor that you’ll find that rather essential “run” command!).
But along with these whole-cloth programs, does he tell you what you just did, why you did it, and how it worked?
You have probably intuited that no, he does not.
Nor does he define terms as consistently as he would have you believe. “Because the player enters a string instead of a number—” Excuse me. I most certainly entered a number. I assume he doesn’t mean we’re doing some version of string theory here.
He implies—actually more than implies—that he’s operating under the theory that readers will learn best by doing and then by figuring out the “grammar” of this language on their own as they go along. I think he’ll eventually tell me some of the stuff I want so much to know. In the Find-the-Wumpus game he has me coding, in “raw_input(“>”),” what in the world is that little caret for? In “for i in cave_numbers” when you’re setting up caves that the player can see from a given cave, where did that “i” come from? Is it some arbitrary identifier? I could pick “s” or “m” just as easily? Maybe I should try the substitution and see what happens. But why not tell me instead of just dropping an unexplained item into the program for me to copy? Am I really better off figuring such things out on my own? Continue reading
Bad Writing: A Very Small Rant
Very small.
Steven Pinker can get away with ranting about bad writing, but it remains to be seen whether I can. But since my rant more or less illustrates Pinker’s on a smaller canvas, possibly I may be indulged.
And I can only do so with a qualification: this particular aspect of bad writing is inherent—perhaps even inevitable—in one of the most difficult genres known to writers: explaining how to do something to someone who comes to the lesson relatively or even completely ignorant of the topic.
I’ve run into this aspect of bad writing a lot recently because I’ve been teaching myself new stuff. Like GIMP. Like Python. It’s the particular Python experience I now rant about. And I do so, believe it or not, with sympathy for the challenges faced by anyone who dares explain virtually anything involving a computer.
The book cost $35.00. It has lots of sweet little cartoons. But its writer lacks that single magic ingredient of good writing. He can’t imagine his readers’ minds.
Now, no one can ever completely enter and know another’s mind. If we could, we’d be each other. It’s the growing knowledge of difference that makes the existence of an “I” possible. (I didn’t make this up. I got it, in roundabout ways, from Emmanual Levinas.) But like it or not, writing for others, writing to be read, demands at some point some tangents of contact between the writer’s mind and the reader’s. Otherwise, we have gibberish. True, between some minds there never is such contact, and between those writers and readers there is gibberish. (I submit that the intersection, when it can be created, is where what is called “rhetoric” takes place.) But on to my rant.
Having downloaded and installed the program and having read in the introduction how welcoming a beginner like me would find Python, I proceeded to follow the directions for setting up the program on my Mac. Never mind that there were pages and pages of instructions for PC users and only a couple of paragraphs on Macs that instructed me to go back and read the pages on Linux. I eventually did find the screens that showed up in the figures, although the screen that came up when I dutifully clicked “Update Shell Profile” was supposed to “run” and as far as I could tell it just sat there, no matter what keys I plunked. At this point, I was already starting to seethe.
He kept telling me to “run” things in a “terminal.” He kept talking about “running” programs from the “command line.”
Well, I got the word “terminal” to show up in the menu line (still not sure how I managed it or whether I can do it again), so I assumed that the box that opened, with various references to my name and the date in plain text, was the “terminal.” But nowhere was there any apparent command I could click to “run” anything. And a “command line”? I looked in vain for the blinking cursor I remember from my short experience with Basic (and of course Wordstar) from 30 years ago. At the end of the text in the “terminal” was a little box that sat immobile no matter what I did.
I can hear you out there, your derisive mocking howls. But you’re the problem! You really do not want people like me to learn your secrets. You want to protect your arcane universe from the uninitiated (cf. Pinker).
But I foxed you.
After some forty-five minutes of reading and rereading the chapter, looking in vain for some definitions or some moment when he said, “In order to run a program, you do this and then this,” I conjured from somewhere some basic intuition born of those 30+ years of mud-wrestling with computers, often armed with nothing but my instincts and willingness to push buttons at random. I thought, I wonder if that little box is the “command” icon. What happens if I try to type there? And then, with the lines of the little demo program waiting, inert but there, I did what intuition sweetly whispered: I hit return.
Now I ask you, what would it have cost to tell me those two things?
Let me quote from the back cover: “Even if you’ve never written a line of code before, you’ll be writing real Python apps in just an hour or two.”
Sure.
Another, very quick, related example: my first Adobe Connect session. No one conducting the session seems to have even considered the possibility that some in the audience had never been in that environment before. I missed the first twenty minutes of the presentation trying to figure out the basic layout, which proved to be accessible and useful with just the slightest bit of orientation.
There. I’ve said it. Done.
Except that this struggle to sense and foresee our readers’ needs is so fundamental to writing to be read that we ignore it at our peril. But why is ignoring it (or at least not recognizing it) so tempting, such a common phenomenon? I have a completely unprovable theory, which I’ll explain (with numbered steps) next time.
Filed under Learning to write, Writing and teaching writing
E-Book Market Review: Guide to 2015
Here’s something I’m finding useful on Publishing Insights. Thanks, Sherry Chen!
Anita Lovett gives an overview of the e-Book market in 2014 and prepares a guide for the new year. The literary market share of e-books continues to grow, and Forbes reports that e-books “have dominated 30 percent of 2014 book sales”. E-book sales have expanded to more than 45 times larger in the past five years, with people’s willingness to buy e-books “on the rise”. Lovett then highlights 5 major details that authors and publishers should pay attention to, in order to succeed in the e-book market in 2015: book cover design, book description, book reviews, genre identification, and extensive revision and editing.
In addition, Darrick Dean holds a discussion about whether Book Price Wars will be the “publishing battleground” in 2015. Some are concerned with the situation where traditional publishers will lower prices in their competition with indie authors. However, Dean argues that first of all, “there is always competition” regarding book…
View original post 66 more words
Filed under writing novels
Writing the Synopsis: Or, What Took Me So Long?
I’ve been away for a few days, and if you’ve been watching the weather reports, you know what I spent much of the day before yesterday dealing with–yes, it’s a four-letter word beginning with “S.”
I’ve also been dealing with an eight-letter word beginning with “S”: “Synopsis.” I’ve never met a writer yet who liked dealing with synopses. I’ve always believed I couldn’t write them–just didn’t get it. I’d tell what I thought was the story I’d told, only to have readers respond, “I’m totally confused.”
I faced the need to confront the demon synopsis because I’m trying to get my out-of-print suspense novels up as e-books, and I need covers. I had some ideas of my own, but my excellent and candid volunteer critics (or should I say “impressed” critics in the sense that sailors off merchant ships were once impressed into the British navy) generally agreed that I should solicit ideas from actual designers. At my university, we have students who do superb work. But could I ask students to read two fairly hefty novels between class assignments? Uh, no, not if I want to get the books up any time soon. Hence, synopses.
My first efforts were on a par with my earlier efforts. A masochistic colleague whose opinion I value actually volunteered to read the books and write the things for me. I spared him: read two hefty books between grading assignments in four (yes, four!) writing classes?!!! So he read the synopses I produced. I reproduce here the bare bones of this experience, because it was a eureka experience. For the first time, I was like, “Oh!” It’s what can happen when you have a truly good reader who is willing to tell you the truth and you are ready to listen–a crucial component, but I was desperate. They always want a synopsis. Who wants two pages to be the death of a three-hundred-page gem?
Here is the heart of what my colleague Tom O’Neal wrote for me:
I’m in Like Flint
I’ve just been reading Becky Lerner’s The Forest for the Trees: An Editor’s Advice to Writers. At least in the first few chapters, Lerner, a poet-turned-editor-turned-agent (and I gather still all of these things), offers advice at one end of a continuum I’ve noticed. Hers is what I would call a “soft” book for writers: strong on inspiration, on the emotional landscape of writing, on how you’ll know if you’re really meant to write and how to persevere through the cold winter of a writer’s disenchantment. At the other end of the continuum: books like Michael Larson’s book on non-fiction proposals, which I downloaded for help writing my proposal for Survive College Writing (a future bestseller currently interred in a massive data dump of all the things I want to say to the students I saw struggle so hard). Larson is in the “how-to” school; this is what you do and this is what it should look like, down to how long paragraphs should be. Quit yer belly-achin’ and just get going. What’s so damn hard?
In the middle I’d place Susan Rabiner’s Thinking Like Your Editor: How to Write Great Serious Nonfiction and Get It Published. This claims to be a how-to, but there’s a good amount of inspiration here–for example, she maintains that if you’re passionate about your topic, your heart will beat through your prose. But there’s also some of that hard-headed get-on-with=it spirit: All the passion in the world won’t help if you don’t do these X or Y Most Important Things.
Reading Lerner, I find myself thinking about the many conferences I’ve attended over the years. Lerner tells ms, forget about writing the next X or Y; forget about “Marley and Me meets ET.” Write what you’re obsessive about, what haunts you. Write the book that’s your book. Thus far, the implication is that if anything is going to sell and hit, that’s the book that will.
The real question is, where’s that line between “what we’ve seen before” and “we don’t know what the heck it is”? Lerner will presumably tell me if I’ve just gone too far, according to one of the Amazon reviews. I will await the event.
If I were in the inspiration queue–I’m not exactly; I know I’ll always write–I would find some solace in sentences like these from Lerner:
“It takes a certain kind of person to understand and cope with rejection as an appraisal instead of a judgment.” (See this post for another take on criticism of our work.)
“[T]he degree of one’s perseverance is the best predictor of success.”
I value information about what’s not working more than ever, and God knows, I persevere.
Update from 1/27!
I’ve revised to add some new more information about Gail Strickland’s book, Night of Pan. Check out her site. I hope she will visit soon for a blog interview about bringing her book to publication.
Just Can't Help Writing 