Category Archives: Learning to write

How Much “Grammar” Do You Really Need?

Put Your Editing Nightmares to Bed!

Across the online landscape for writers, there’s a lot of anxiety about producing that error-free query, synopsis, or draft. With reason—the first letter in “professional” is “p” for “perfect.” There’s no wiggle room on this one, is there? It’s got to be capital-R Right.Sad Editing!

As someone who taught college writing for 25 years and as a published novelist, I’ve been on the front lines of the effort to spread “good grammar.” The fact is, the whole question of what’s Right is more complicated than you think.

In the next few posts, I’m going to make an argument that we don’t need to obsess quite as much as we do. In fact, there are some “grammar rules” we can even trash!

Yes, You Have to be Able to Edit Your Work. . . .

I’m not for one minute telling you that your command of English syntax and usage is not important. It’s vital. But writers can all too easily get bogged down on trivia and even on myths (“OMG! I ended a sentence with a preposition! :-0”). One common cause of writer’s block is thinking that every comma is radioactive, ready to explode and destroy the known universe if mishandled. So for us writers, a little bit of a reality check is a good thing!

Today’s topic: What is good grammar? Answer: Depends on whom you ask.

(Yep, whom you ask. Why? Because it’s the object of the verb “ask.” Eeek! Relax. Nine times out of ten, “who” would be just fine in that line. Hang around; later I’ll explain why.)

Linguists, people who study how languages work, generally agree on three things: Continue reading

5 Comments

Filed under College writing, correct grammar for writers of fiction, Finding literary agents for writers, grammar rules for writers, Learning to write, looking for literary editors and publishers, Myths and Truths for writers, punctuation for writers of novels, self editing for fiction writers, style for writers, Working with literary editors

Speaking of Punctuation. . . .

Cormac McCarthy has a different take on things like commas. Do you agree with him?

Leave a comment

Filed under Learning to write, punctuation for writers of novels, style for writers, Writing and teaching writing

Comma Power

I have been thinking about the inordinate power of commas.

I had an intuitive understanding of this power from my manipulation of my own prose as a fiction writer. But I credit Martha Kolln’s textbook, Rhetorical Grammar, for making concrete, as an object of explicit study, what my instinctive ear told me. I never succeeded in passing on to many students a real, self-conscious understanding of how vital such a simple little mark can be to communicating precisely what we want readers to hear: there never seemed to be enough time to think much about style in the classes I taught. But if I had it to do over again, I would indulge myself by finding that time. I’ve worked hard not to be the natural Grammar Curmudgeon I am, but by golly, punctuation is a tool! We’ve all seen those fun exercises where simply moving a few little marks around completely changes meaning (a simple example is “Woman without her man is nothing,” which, with just a few tweaks, comes to mean its opposite). But punctuation also controls rhythm and emphasis, and in this regard, the comma’s a tough little drill sergeant, lining up every word in its place.

So: some disquisitions on commas. Rather, on what I think is going on with commas, with thanks for Kolln for systematizing these observations for me.

Today, emphasis. Read this sentence aloud:

There is in fact a reason for what happened.

Now add the commas in the most obvious places, around the “interrupter,” which grammar books tell us commas should, actually, set off:

There is, in fact, a reason for what happened.

To my ear, and Kolln substantiates this, the commas change the intonation and emphasis. In the second sentence, as in all uses of commas in this way, the emphasis is cast on the words before the commas. So the sentence now reads

There IS, in FACT, . . .

So we get increased attention to the “facticity” of what’s being claimed. The meaning hasn’t particularly changed, but the way we hear it has. We get a beat on the FACT of this utterance.

But that’s not all that happens. The commas break up the flow of the sentence, I would assert, in ways that reinforce meter. In this case, it’s our old favorite, iambic pentameter, the most ubiquitous meter for English speakers (Shakespeare’s meter). And that not only asks us to hit “is” and “fact” with extra emphasis, but also “REAson.” So that the sentence reads,

There IS, in FACT, a REAson for what happened.

This effect is, in part, due to what Kolln calls the “it cleft,” which I’ll investigate in a later post. But the commas hammer home the shift to emphasis on “REAson,” telling readers that this reason is going to be the focus of the ensuing follow-up.

I want to look more in upcoming posts at the comma’s power to break up sentences and direct utterance as words transfer from page to mind. For now, do you have examples of how commas control words in your own writing? Decisions you’ve made about how to re-organize sentences to take advantage of this little power tool?

7 Comments

Filed under College writing, Learning to write, punctuation for writers of novels

Rules for First Lines of Fiction: Rule 1

Rules you don’t actually have to follow 🙂

But for fun. . . .

Now that I’ve looked at four examples I found compelling, I feel emboldened to draw some generalizations.

As I do so, I realize I’m starting to wander into territory already pretty well covered by eons of literary, narrative, aesthetic, and rhetorical criticism. I’m not about to chase down citations. I’m going to talk about the pieces of this theorizing that have resonated with me, maybe not as theory (so Don’t Panic!) but as just what seems to work for me.

Rule 1: I already said I thought compelling first lines must make a promise. But what kind of promise? For me—and this goes as far back at least as Sophocles—a promise of a world overturned.

In other words, I want to sense that I’m about to enter a place where my day-to-day expectations will be thwarted. Things WILL NOT go on as usual. I will see, traverse, a new landscape, one with volcanic fissures I must be careful not to stumble into. This rule holds even for novels that are not mystery/suspense. A Visit from the Goon Squad takes me into a disquieting place, a hotel bathroom, where what is “usual” is decidedly not going to be “usual” for me.

We read to enter alternate realities (duh). This is true even—especially—for those of us who may read the same authors, enter the same worlds, over and over. We enter that foreign world again and again, by choice. Is this escape, then? Not necessarily. I learned of many new worlds in Americanah. But these worlds were not so much worlds where I could escape my own (though I guess I did quite a bit), but rather where I could see my own world slant, in Emily Dickinson’s image: upset, overturned. That can be an unsettling experience as opposed to one that lulls.

So I want the promise that I’m going to see slant. That I’m going to have to reconnoiter to know where I am. That I may just have to get the shotgun if things get out of hand. But that in the end, I will be a native of a larger landscape than before.

Do I need a promise that order will be restored? We enter here the classical territory of the well-wrought form, where the world is purged of the scapegoat entity that disrupted it and dust settles—NOT a metaphor/clichĂ© of abiding peace: dust is detritus, no? Indeed, I read with a firm sense of the artifice of any endings I’m going to encounter. In most mysteries, things settle, but only until the next body is discovered. In Americanah, Ceiling is invited in, but to what? More of the messiness we all experience in trying to live with each other.

As I look at that Dickinson poem, i will posit that reading fiction does “tell all the truth but tell it slant”: tell it in such a way that it’s bearable. That’s the meaning of “vicarious experience.” We experience disruptions in a form that offers the (false?) possibility that they can be resolved, that artifice is powerful enough to adjust all disproportion, smooth all curves. We enter a work of fiction with hope that, even if at the end all is still chaos, our minds can create a unified whole, a “reading.” The need for such a “reading,” a “making sense” of even the most inchoate flotsam, seems built into us—at least, into me.

I do think that such artifice is built into the first lines I find compelling. I note that each I’ve looked at is ironic, containing both the disrupted world and the world that was, but will not be possible to return to. The old days. A quiet rural county. A gymnasium. A hotel. Each of these used-to-be’s is attached to something that pokes a hole in it. I see both, side by side.

So Rule 1 for me: stand me on a cliff and let me feel the ground under me begin to crumble. Let me look down and see myself slide. Promise me a chance to build something out of the rubble, even if it’s only my own feeble creation.

That’s my Rule 1. What’s you

2 Comments

Filed under Learning to write

Great Novel First Lines: Part 3

We slept in what had once been the gymnasium.

Margaret Atwood, The Handmaid’s Tale

This one’s harder to analyze. Yet I think it qualifies as a terrific opening line for a haunting, even painful novel. I’m interested in how it does the work of leading me into such a book.

Two things stand out. First and simplest, “had once been” tells us that normalcy is endangered. Something staid and familiar is no more. Gymnasiums, those places that for me signify high-school PE with its silly short jumpsuits and sweaty-sock smells, Friday-night basketball games with their creaky bleachers and more sweaty smells, assemblies and pep rallies with their innocent pom-pom dances showcasing the popular girls: all no more. I see in my mind’s eye a building clawed at by vines and surrounded by crumbling brick, toppled trees, things that rustle in the overgrown grass.

There’s no reason, necessarily, to see the gymnasium this way. Except for “[w]e slept” there. Now, when do people sleep in gyms? After disasters, when the gym opens up as a shelter. So there has been a disaster, a loss. But not a recent, temporary one. In that case, the sentence would have read, “We slept in the gymnasium.” Because even after a hurricane, the gym will supposedly go back to being a gym. No, “what had once been” cuts off that line of speculation. This gym is done.

Do I think from this line that gyms in general are done? There’s such a hint, again from the fact that “we slept” there. This is a world in which people, this “we,” need a place to sleep and this is what they are given. A gym. Hard floors, cots at best, echoing barracks-like atmosphere. Moreover, we’re asked to compare this world where people sleep in gyms with a world in which “the gymnasium” is a familiar environment that doesn’t have to be explained. We all know what a gymnasium is. But “the gymnasium,” that fixture of every high-school and college campus, is not a place where people sleep.

So why do they sleep there? The novel’s promise is to tell us. What disaster of what magnitude is conjured by “had once been”?

The word “once” does work of its own: “Once upon a time.” Loooonng time ago. Once there were trees and a river (apocalyptic 1961 song from the Limelighters). All by itself, the word “once” used in this time sense speaks of things long gone and not coming back, except in dreams.

It conjures mythology as well. A time when monsters and gods roamed. The “once” referred to in this sentence, though, is not the time of gods and monsters; this “once” is ordinary time. Yet, that hint of myth gently infuses the sentence: perhaps there will be gods and monsters—if not then, now.

“We” is easy. I am teased into wanting to know who “we” are. Will I see myself in that “we” at some point? There will be a lot of us; it takes a gym to accommodate us. Alternatively, “we” could be a couple of vagabonds who have sought shelter on this ruined campus. Or “we” could be a platoon of soldiers on the march. Either way, “we” are not reposing on satin pillows, under silk sheets. We are not here by choice; the gym is not Club Med. I sense a stop along the way to somewhere more permanent for this “we,” and I both fear and want to know where the next stop will be.

It occurs to me that the word “gymnasium” and not “gym” hints at foreignness–a time with which I am not all that familiar. A time when calling things by their formal names may offer some touchstone, some anchor, in a world where expectations are adrift.

That this sentence is so short, that it doesn’t explain itself, also adds to its accomplishment. It’s a bald statement of fact that the speaker accepts. There’s no protest, no sign of a need to “show” lurid details. I’ve made the case that there’s nothing mundane in this situation, yet the speaker’s revelation could not itself be more ordinary: There was this former gymnasium and that’s where we slept. Not dozed, rested, napped. Connotations held at arms’ length. As in the first line from Paris Trout, it’s in the ordinary that we’re promised doom.

And it’s in the way the ordinary is dropped without context into this most nebulous “we” and “once,” both untethered, that the unsettling contrast emerges.

I note that I’ve been focusing on first lines of novels of suspense and mystery. That says something about my own preferences, of course. But I wrote a paper in grad school arguing that all fiction is ultimately mystery, and certainly it’s all suspense. There’s always something that has to be found out, by the characters, by the reader, and whether or not it’s found out in time is what we read to know.

But for next time, I have one that’s not a mystery/suspense novel.

What are your candidates for “best first lines”? Why?

Leave a comment

Filed under Learning to write, Writing and teaching writing

Best First LInes of Novels, Part 2

This is the second in my series of attempts to understand what makes the first lines of novels compelling. Post your own favorites!

Earlier, I wrote on Daphne du Maurier’s My Cousin Rachel. Today:

In the spring of that year an epidemic of rabies broke out in Ether County, Georgia.–Paris Trout by Pete Dexter

I don’t remember as much about this novel as I should, but ever since I’ve remembered this stunning first line.

The heart-stopping word, obviously, is “rabies.”

What does “rabies” conjure? Easy: madness. And that’s “trouble” with a capital M. It’s a special kind of madness, a diseased madness. The diseased among us, against whom we must lock our doors. I find myself reminded of that scene in To Kill a Mockingbird, both the book and the movie, when Atticus shoots the mad dog. That’s another element of the word’s force: something benign that moves freely through our lives suddenly begins to foam at the mouth and attack. Its eyes go flat and malevolent as it staggers toward us. We lock the door, but we cluster behind it, meeting those blank eyes.

And not just an isolated dog in the street. Dozens of them. Epidemics get everyone. Us.

So this is going to be a book about madness. And men in the street with shotguns. In the hot sun. The hot, bright sun that goes with the word “rabies” itself is part of the horror. This madness does not have to creep about at night. It can get us, make us part of the horror, in the least moment of inattention. It can reel toward us right in the middle of hanging out the wash.

The sentence tells us it’s spring, true, not hot summer. But “spring” becomes an ironic juxtaposition. The gasping heat of that dog in the sun intrudes implacably. Right in the glorious springtime, when we’re out picking dandelions.

A smaller component for which my interpretation may be a stretch: the verb “broke out.” Its metaphorical weight is arguably several-fold. We “break out” in boils—a pestilential visitation with Biblical undertones. But also, something that “breaks out” has been among us all along, inadequately (it turns out) contained. It has let itself loose upon us. Get the shotgun.

In support of this reading of the verb “broke out,” I posit how different this line would have read had it stated, “The people of Ether County, Georgia, experienced an occurrence of rabies that spring.”

Similarly, “In the spring of that year,” two anapests, themselves have a Biblical rhythm. An “old” rhythm, potentially mythic. Not the way you write on Facebook. Somebody wants to take you to a strange land.

Finally, to me, the choice of “Ether County” for a location also opens up images of those dangerous creeping-madness streets. “Georgia,” of course, calls up “hot sun.” I have special associations with rural Georgia that may be my own: tall grass in vacant lots alongside dirt roads past ancient sagging barns where wasps hum. Not everyone will experience quite these same connotations. But “ether”: ether is what they use when they want to dim your mind. Do things to you. Ether is dizzy and queasy. Under its influence, you will lose your way.

So the book will take us to a strange land that is superficially familiar, but where things we thought we’d contained can come at us. Where we will wander out into sunlight only to find it full of dark things.

All in one sentence. Sixteen words. A whole book is set up.

Leave a comment

Filed under Learning to write

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.

4 Comments

Filed under Finding literary agents for writers, Learning to write, Working with literary editors, Writing and teaching writing

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

Leave a comment

Filed under College writing, Learning to write, Teaching writing, Writers' groups, Writing and teaching writing

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

Leave a comment

Filed under College writing, Learning to write, Teaching writing, Writers' groups, Writing and teaching writing

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.

 

Leave a comment

Filed under Learning to write, Writing and teaching writing