...I am wondering if I should just stop writing stories.
I quit trying to write fiction after grad school for many reasons:
-Too many good writers, not enough readers
-Wanted a job I could support my family with
-Wasn't sure that writing was a good way to have impact in the world--great books have been written for hundreds of years, but the world is still full of bad people (many of whom have read those great books).
-I sensed that the profession of literature made you kind of a dick, based on the fact that almost every professor (of literature) I knew in grad school was a dick. (Only one who was MY professor, but plenty were lurking about.)
-Even if I were a great writer, there was no guarantee I'd ever be lucky with publication
-I have no desire to write something if nobody or practically nobody will ever read it.
-I felt that after grad school, I was out of step with what made literature "great."
-Rejection is very hard psychologically on me. So why should I voluntarily add 50 to 100 instances of it a year that aren't strictly necessary? (It doesn't get easier with practice.)
-Tangibly helping people in the world is probably worth more than writing a great story.
So I didn't write for ten years. I barely read--at least nothing that was in English. My job is to translate, so I read stuff in other languages. But I never read English novels or short stories. And you know what? I was kind of happy.
In the 13 months of my mid-life crisis writing experiment, I think I've lost some of that happiness. You could crack wise about how wisdom brings suffering or something, and say that I was just filling those ten years I thought I was happy with mundane stuff. Isn't that what humans do, though? We focus on the secular, because it's what here. We eat, drink, and make human connections, and the time passes, and soon we're old enough to die and end all our troubles.
I'm going to let it play out a little longer, but this is very much an activity whose worth is under assessment.
Friday, October 31, 2014
Wednesday, October 29, 2014
A nice personal note to go with my rejection...or was it????
The flash fiction piece I wrote last month got rejected by Apeiron Review, but came with a personal note with the rejection (first one I've gotten--everything else has been form letter "no" and the one acceptance).
Thank you for sending us your work. We appreciate the chance to read it. Although it does not suit the needs of the magazine at this time, we wish you luck with placing it elsewhere.
Just a note: this piece has a lot of potential, and we held onto it for so long so that we could really get to know it. The last line, in particular, held a lot of meaning. We hope to see more of your work in the future.
All the best to you!
Sincerely,
Apeiron Review
Funny thing is that they didn't hold onto it that long (a little over a month). Could this be a fake personal note? But why? They didn't try to sell me anything. The last line of my story I actually did not like--it felt to me like a borderline hogwash summary. However, I can see where they might have thought it was pregnant with meaning. I'm pretty sure this is a sincere "close, but not quite."
I'm calling it a moral victory.
Thank you for sending us your work. We appreciate the chance to read it. Although it does not suit the needs of the magazine at this time, we wish you luck with placing it elsewhere.
Just a note: this piece has a lot of potential, and we held onto it for so long so that we could really get to know it. The last line, in particular, held a lot of meaning. We hope to see more of your work in the future.
All the best to you!
Sincerely,
Apeiron Review
Funny thing is that they didn't hold onto it that long (a little over a month). Could this be a fake personal note? But why? They didn't try to sell me anything. The last line of my story I actually did not like--it felt to me like a borderline hogwash summary. However, I can see where they might have thought it was pregnant with meaning. I'm pretty sure this is a sincere "close, but not quite."
I'm calling it a moral victory.
Tuesday, October 28, 2014
The award for best form rejection letter by a writing journal goes to...
I just got a rejection from Carve Magazine, the same magazine whose literary services I used in August to get a sense of what editors think when they read my stories. Here is their form rejection letter:
Jacob,
We appreciate the opportunity to read your work, but we will not be publishing “Savage, Maryland.”
Editorial decisions are ultimately subjective, so we encourage you to keep writing and submitting. When your work finds a home, we’d like to know so we can share the news with others. Tell us at carvezine.com/reject.
We hope you continue to enjoy reading future issues of Carve, and you are welcome to submit again.
Sincerely,
Editor and Staff
Carve Magazine
carvezine.com | carvelit.com
P.S. If you're looking for in-depth feedback, check out our editing services at carvelit.com. We offer a broad range of editorial and mentoring services.
Why do I like this? Several reasons. #1) There is never even a flutter of anticipation that you got picked, only to feel crushed later. #2) There is an admission that there is an element of randomness to this. Other zines do this, of course, but not as well or with as much seeming integrity. #3) The magazine has a "REJECT!" section, where you can show up with a story they turned down that someone else wanted. Now, the skeptical might say that this is just an opportunity for them to hawk the "premium" edition to you, but I have no problem with this. A lot of journals are trying sneaky things to get you to spend the coin to be a full member, and at least this one shows a little humility.
I'm a little concerned that this rejection came so fast. One day under a month. That means it was a quick throw-out. I don't think I'm writing obvious throwaway stories anymore. Makes me a little concerned that they think I am. But, oh well. They're not in my top ten favorites, anyway.
My first published story comes out on Baltimore Review on October 31st.
Jacob,
We appreciate the opportunity to read your work, but we will not be publishing “Savage, Maryland.”
Editorial decisions are ultimately subjective, so we encourage you to keep writing and submitting. When your work finds a home, we’d like to know so we can share the news with others. Tell us at carvezine.com/reject.
We hope you continue to enjoy reading future issues of Carve, and you are welcome to submit again.
Sincerely,
Editor and Staff
Carve Magazine
carvezine.com | carvelit.com
P.S. If you're looking for in-depth feedback, check out our editing services at carvelit.com. We offer a broad range of editorial and mentoring services.
Why do I like this? Several reasons. #1) There is never even a flutter of anticipation that you got picked, only to feel crushed later. #2) There is an admission that there is an element of randomness to this. Other zines do this, of course, but not as well or with as much seeming integrity. #3) The magazine has a "REJECT!" section, where you can show up with a story they turned down that someone else wanted. Now, the skeptical might say that this is just an opportunity for them to hawk the "premium" edition to you, but I have no problem with this. A lot of journals are trying sneaky things to get you to spend the coin to be a full member, and at least this one shows a little humility.
I'm a little concerned that this rejection came so fast. One day under a month. That means it was a quick throw-out. I don't think I'm writing obvious throwaway stories anymore. Makes me a little concerned that they think I am. But, oh well. They're not in my top ten favorites, anyway.
My first published story comes out on Baltimore Review on October 31st.
Monday, October 27, 2014
The right way to lie
"Specific, definite, concrete, particular details--these are the life of fiction. Details (as every good liar knows) are the stuff of persuasiveness. Mary is sure that Ed forgot to pay the gas bill last Tuesday, but Ed says, "I know I went, because this old guy in a knit vest was in front of me in the line, and went on and on about his twin granddaughters"--and it is hard to refute a knit vest and twins even if the furnace doesn't work."
-Writing Fiction, Burroway et.al., 7th edition, pg 26
Most readers can probably be divided into those who love great sensory descriptions of scene, those who let their imaginations go with the details, and those who are happy enough just skipping over that stuff. I've been one of the second most of my life. I first noticed this tendency in myself when I was nine and reading Lloyd Alexander's Prydain series. He was describing his characters traveling through a woods, and try as I might to bend my imagination to the details Alexander wanted me to see, I could only see the woods behind my house. Even after the characters had traveled for days, I still had only moved them from one end of the woods to another.
Later, in high school, I read Lewis and Tolkien. I got very badly stuck for two days once on the same two-page description of some outdoor scene. They used British terminology for topography, and in those days learning a term you didn't know required getting a dictionary or encyclopedia. I eventually just said to myself, "this is a mountain," and moved on.
I guess I'm a Philistine with details that set a scene. Jhumpa Lahiri or Khaled Hosseini's pearls are trampled by swine like me. In the last few years, I've been better about appreciating scene, partly because I've tried to write it but mostly because I can now just push an unknown word in Kindle and get a quick definition. This helps keep me on track. It's also critical that a deepening sense of how to view scene like it were film, with all the possibilities of meaning available there, have made it more enjoyable to put in the effort to imagine what I'm supposed to imagine.
But it still doesn't come naturally to me. Here's the beginning of an early favorite story of mine:
A certain man had two sons. (What were their names? What did they look like? What were their favorite colors and subjects in school?) And the younger of them said to his father, "Father, give me the portion of goods that falleth to me" (What did the father do to gain his wealth? How did his sons feel about this occupation?) And he divided unto them his living. And not many days after, the younger son gathered all together, and took his journey into a far country, and there wasted his substance with riotous living. (What was his motivation for leaving? Did he plan to party his money away, or did it just work out that way? Did he justify his decisions to himself, or was he deliberately blocking the voice of reason in his head?)
You get the idea. You can put together a fine story without a lot of details. Flash fiction (which I don't really like that much, but everyone swears it can be as powerful as its longer cousins) necessarily drops details in order to keep the word count under 1000 and still have something happen.
I think there's a much deeper reason why I tend to be anti-details than just my own laziness or lack of spatial and artistic intelligence. The passage I started this post with says that details tend to hide a lie. But don't they also tip the skeptical among off that a lie is being told? If a student starts to tell a long story about how the homework didn't get done through no fault of his own, or if the employee begins to talk a long time on the phone about why she is calling off, the teacher or boss gets a tingly feelings that all is not well. It's the same in fiction. I hit a point where, after too many too close details, I start to call bullshit. Here is a totally unfair example of a passage I recently read and hated. It's from "Depth Perception" in Carve Magazine by Laura Gibson. There are a number of well-crafted details that I accepted and even enjoyed for some time:
-Sitting on an old milk pail between rows, he stopped for a moment, a clutch of pineapple weed in one hand..
- I sat up and leaned over the booth table and put my face close to Lou’s, inhaling his sawdust and wood smoke flecked with motor oil, a whiskey after-burner.
But then I get to this line:
-The bottoms of his boots smooth and worn, so thin near the balls of his feet he’d have to have them re-soled soon.
And I just felt that the story was bullshit and had a hard time going on emotionally. Her lead character was putting the corpse in the rig, but my willingness to follow the story stayed there in the bar. Why? It was one detail too many, and too fine a detail. Nobody notices things like that with that amount of detail. It leads me to wonder: who is the narrator? Is it a disembodied person seeing through one character's eyes? Is that why he can see better than the person herself? (Incidentally, I'm not at all calling this a bad story, or saying Gibson should have written it to my taste. I'm saying that this is a taste I have, and I find it offended often in 2014.)
Well, of course that is exactly what third person limited is. But muscular or fine details have a way of making that too clear to me, and ruining my ability to listen to the disembodied voice. It just announces itself too much when I need it to stay hidden. It's like realizing what eggs really are in the middle of eating an omelet. It's too good of a lie, and it makes me feel uneasy about the whole prospect of listening to a lie for the next 15 minutes to 20 hours, depending on the length of the lie.
Of course, there is a way around this for me. Tell me tons and tons of lies. Make your lies outrageous. Because then, it'll be clear to me that you're just spinning a yarn that's meant to make me enjoy myself, and I can forget about suspending disbelief. This can be done in fantasy, of course, but it can also be done with really self-conscious description. The Corrections comes to mind. I of course know that all the too-fine thoughts going on are all Franzen, but he's not trying to hide that, so I just go along with Franzen, and it turns out Franzen is a pretty entertaining liar.
Sunday, October 26, 2014
A book I should have read a long time ago
I just ordered Against the Academy: Provocations, Polemics, Controversies by Anis Shivani. Given that this whole blog is nominally dedicated to my dislike of the university workshop (and the literature it engenders, which seems to occupy most of the journals considered worth reading by the literati), I guess I should have read this a long time ago. I've been busy. Mostly doing stuff having nothing to do with literature.
I found the book when I came this review while looking for criticisms of The Road by Cormac McCarthy, which I just read. Man, Shivani is a strident son of a bitch. Too strident, I thought, in his sweeping smashing of nearly all literature that DOESN'T deal with death and the thinness of capitalism. But maybe that will be just the ticket for something I think is as obviously a failure as university writing programs, but that seems to go on and on like McCarthy's road. I am planning to read it just to enjoy vicariously feeling his seething rage and he makes points I've thought about, but do not have the wit to phrase as sharply as him.
I found the book when I came this review while looking for criticisms of The Road by Cormac McCarthy, which I just read. Man, Shivani is a strident son of a bitch. Too strident, I thought, in his sweeping smashing of nearly all literature that DOESN'T deal with death and the thinness of capitalism. But maybe that will be just the ticket for something I think is as obviously a failure as university writing programs, but that seems to go on and on like McCarthy's road. I am planning to read it just to enjoy vicariously feeling his seething rage and he makes points I've thought about, but do not have the wit to phrase as sharply as him.
Friday, October 24, 2014
My first ever review
Blake Kimzey is getting a ton of publicity from this blog--or will, when more than five people read it--as a result of having been the guy who was randomly assigned to edit a story I sent to Carve magazine. I recently read his winner of the 2013 Black River Chapbook Contest, Families Among Us.
I've never done a book or story review on here, and I'll think I'll do one now. But since this blog is supposed to be mostly about writing, I'm also going to be looking at it from the view of craft (getting ideas of what to do, developing an aesthetic, uncovering strategies, etc.)
One of the most striking things about this slender book (six short stories, four of which are very short, 32 pages total) is that for a book of short stories, they mostly fit together pretty well. A lot of short story writers joke about how they try to come up with convoluted ways in which they can present their short stories as a coherent, related collection when it really isn't (because, of course, nobody publishes short stories). Four of these six are so closely related, I really hope they were written with each other in mind. Otherwise, Kimzey uses the same idea an awful lot in his short fiction.
Because the stories work together so well, it's nice to consider this chapbook as a text to be taken whole. In this manner, we end up with an interesting structure (spoiler alert times a million, although I don't think it will ruin the book much--in most of the stories the surprise is given away early on):
Story One: A family crashes on a jet, sprouts gills and lives underwater for a long time. They decide to come to the surface to re-adapt to life on land after an indefinite amount of time. It doesn't take, and the boy and girl cast off their clothes and return to the sea.
Story Two: A boy is born with a "beetle back" and wings. He learns to fly, although he is otherwise normal. He eventually sheds his clothes, flies off, and is never seen by the family again.
Story Four: A boy is born with what seems to be a worm-like mid-section. The boy eats dirt. The boy eventually casts off his clothes and squirms away, never to be seen again.
Story Five: A boy turns into a bear. Before he completely transforms, he casts off his clothes, heads to the forest, and finds a bear companion after hibernation.
Stories three and six are the change-ups. Story six actually acts like a nice ending to stories 1,2,4, and 5. It's the story Kimzey had published in Tin House for "Flash Friday." Here, a village has gone out to seek a lost child, and they find him after he has apparently fallen from the stars. What happens next is up to interpretation.
Story three is the one story that doesn't quite fit. It was also my favorite, although I have to say if Edward Said read it, he'd probably go ape shit. (Let me save you some time. Orientalism is a million pages of stodgy prose that basically says that people tend to read themselves into the "other.") An American bicycle tour guide in Paris is fascinated by the owls who live in his neighborhood and by the burka-clad woman who lives upstairs. Turns out, the burka-clad woman who lives upstairs is hiding a part-owl body beneath her covering. He is mesmerized, but the girl's father takes her off to the forest to lay her oeufs.
I have to admit that by story four, I was a little tired of the story cycle. The most exciting moment came for me in story #2, "Up and Away." In the first story, "A Family Among Us," we get a perspective that might technically be third-person objective: we see all the actions of the family, but do not enter their thoughts. "Up and Away," though, gives us a nice use of third-person omniscient, a now rarely-used technique that stole the spotlight of this story. Because here, we get a truly family-level perspective of what is probably the core legend of this clan. We jump from mother's brain to sister's brain to father's brain in the same paragraph, much like one might hear a family tell one of their favorite vacation stories by talking over one another.
The final story, "And Finally the Tragedy," strikes me as a fitting ending to all the stories except three, because it is as if the village has gone to try to find all those children who have gone feral and ventured off into the wild. They have found the child, but the child brings back a revelation, something indecipherable: he opens his mouth, but instead of speaking, his mouth is "as cavernous as a two-story movie theater," leaving the narrator (the only first-person narrator in the book) to fear "he would swallow us whole."
Yet this first-person narrator, the town's reverend, still feels it is his duty to interpret the meaning the boy brings: "It was up to me to make sense of the boy." And so we, as readers, must make sense of Families.
When reading magic realism, a form to which these stories undoubtedly belong (story four even has a boy who eats dirt, a la Rebecca in One Hundred Years of Solitude), I like to think that one key to unlocking the cipher is something that George McDonald said in The Miracles of our Lord: many of the miracles of Christ were just exaggerated versions of something God does all the time in nature anyway. God always turns water into wine (okay, you need other stuff, too). God always makes fish and bread. God always makes fig trees wither and die.
So in the magic realist story, you have an element that is like the world as we know it, but stretched out of proportion. Children may not have beetle backs or fly or have gills, but they are a part of the natural world, as much as we parents try to convince them they are not. (Is there anything more savage than the birth of a baby? How did we ever get to celebrating this event with soft blue and pink balloons?) They do eventually leave (unless they major in English).
The first story is a slightly different story arc. The family actually begins by leaving the fuselage of the plane, where they have lived, as inside a womb, beneath the sea for who knows how long. But the children chafe at wearing clothes, and long before they even see civilization, they are playing a dangerous game of seeing how long they can hold their breath beneath the ocean, wishing to re-grow their gills to get back. So we all somewhat reject being taken from the womb, and long to return to breathing our air through gills.
Rather than emerge from pre-life and wish to go back, the boy in the final story has returned from post-life and brought something of the terrible mystery back with him to trouble civilized folk.
The stories have much more harvest to yield than this, and the best thing I can say about them is that they brought me enough of joy that I am willing to keep trying to reap from them. I have said before that I like a story that has a point, that says something a cashier or a bouncer or a Marine can carry with him or her that will make life richer or maybe even just tolerable. But I don't always need to be able to fully realize what that thing is. I want there to be something to eat. If I enjoy the atmosphere and the appetizer was appealing, I am willing to wait for the main course, even if the main course does not come for decades. Whatever treasure is hiding in these stories (enough metaphors mixed in one paragraph?), there is enough of a map here to spend some time enjoying looking for it.
I've never done a book or story review on here, and I'll think I'll do one now. But since this blog is supposed to be mostly about writing, I'm also going to be looking at it from the view of craft (getting ideas of what to do, developing an aesthetic, uncovering strategies, etc.)
One of the most striking things about this slender book (six short stories, four of which are very short, 32 pages total) is that for a book of short stories, they mostly fit together pretty well. A lot of short story writers joke about how they try to come up with convoluted ways in which they can present their short stories as a coherent, related collection when it really isn't (because, of course, nobody publishes short stories). Four of these six are so closely related, I really hope they were written with each other in mind. Otherwise, Kimzey uses the same idea an awful lot in his short fiction.
Because the stories work together so well, it's nice to consider this chapbook as a text to be taken whole. In this manner, we end up with an interesting structure (spoiler alert times a million, although I don't think it will ruin the book much--in most of the stories the surprise is given away early on):
Story One: A family crashes on a jet, sprouts gills and lives underwater for a long time. They decide to come to the surface to re-adapt to life on land after an indefinite amount of time. It doesn't take, and the boy and girl cast off their clothes and return to the sea.
Story Two: A boy is born with a "beetle back" and wings. He learns to fly, although he is otherwise normal. He eventually sheds his clothes, flies off, and is never seen by the family again.
Story Four: A boy is born with what seems to be a worm-like mid-section. The boy eats dirt. The boy eventually casts off his clothes and squirms away, never to be seen again.
Story Five: A boy turns into a bear. Before he completely transforms, he casts off his clothes, heads to the forest, and finds a bear companion after hibernation.
Stories three and six are the change-ups. Story six actually acts like a nice ending to stories 1,2,4, and 5. It's the story Kimzey had published in Tin House for "Flash Friday." Here, a village has gone out to seek a lost child, and they find him after he has apparently fallen from the stars. What happens next is up to interpretation.
Story three is the one story that doesn't quite fit. It was also my favorite, although I have to say if Edward Said read it, he'd probably go ape shit. (Let me save you some time. Orientalism is a million pages of stodgy prose that basically says that people tend to read themselves into the "other.") An American bicycle tour guide in Paris is fascinated by the owls who live in his neighborhood and by the burka-clad woman who lives upstairs. Turns out, the burka-clad woman who lives upstairs is hiding a part-owl body beneath her covering. He is mesmerized, but the girl's father takes her off to the forest to lay her oeufs.
I have to admit that by story four, I was a little tired of the story cycle. The most exciting moment came for me in story #2, "Up and Away." In the first story, "A Family Among Us," we get a perspective that might technically be third-person objective: we see all the actions of the family, but do not enter their thoughts. "Up and Away," though, gives us a nice use of third-person omniscient, a now rarely-used technique that stole the spotlight of this story. Because here, we get a truly family-level perspective of what is probably the core legend of this clan. We jump from mother's brain to sister's brain to father's brain in the same paragraph, much like one might hear a family tell one of their favorite vacation stories by talking over one another.
The final story, "And Finally the Tragedy," strikes me as a fitting ending to all the stories except three, because it is as if the village has gone to try to find all those children who have gone feral and ventured off into the wild. They have found the child, but the child brings back a revelation, something indecipherable: he opens his mouth, but instead of speaking, his mouth is "as cavernous as a two-story movie theater," leaving the narrator (the only first-person narrator in the book) to fear "he would swallow us whole."
Yet this first-person narrator, the town's reverend, still feels it is his duty to interpret the meaning the boy brings: "It was up to me to make sense of the boy." And so we, as readers, must make sense of Families.
When reading magic realism, a form to which these stories undoubtedly belong (story four even has a boy who eats dirt, a la Rebecca in One Hundred Years of Solitude), I like to think that one key to unlocking the cipher is something that George McDonald said in The Miracles of our Lord: many of the miracles of Christ were just exaggerated versions of something God does all the time in nature anyway. God always turns water into wine (okay, you need other stuff, too). God always makes fish and bread. God always makes fig trees wither and die.
So in the magic realist story, you have an element that is like the world as we know it, but stretched out of proportion. Children may not have beetle backs or fly or have gills, but they are a part of the natural world, as much as we parents try to convince them they are not. (Is there anything more savage than the birth of a baby? How did we ever get to celebrating this event with soft blue and pink balloons?) They do eventually leave (unless they major in English).
The first story is a slightly different story arc. The family actually begins by leaving the fuselage of the plane, where they have lived, as inside a womb, beneath the sea for who knows how long. But the children chafe at wearing clothes, and long before they even see civilization, they are playing a dangerous game of seeing how long they can hold their breath beneath the ocean, wishing to re-grow their gills to get back. So we all somewhat reject being taken from the womb, and long to return to breathing our air through gills.
Rather than emerge from pre-life and wish to go back, the boy in the final story has returned from post-life and brought something of the terrible mystery back with him to trouble civilized folk.
The stories have much more harvest to yield than this, and the best thing I can say about them is that they brought me enough of joy that I am willing to keep trying to reap from them. I have said before that I like a story that has a point, that says something a cashier or a bouncer or a Marine can carry with him or her that will make life richer or maybe even just tolerable. But I don't always need to be able to fully realize what that thing is. I want there to be something to eat. If I enjoy the atmosphere and the appetizer was appealing, I am willing to wait for the main course, even if the main course does not come for decades. Whatever treasure is hiding in these stories (enough metaphors mixed in one paragraph?), there is enough of a map here to spend some time enjoying looking for it.
Wednesday, October 22, 2014
Counterpoint: Readers are sometimes great
In my last post, I wrote about how readers can be terrible. They can, and this has some ramifications for writers. First, you have to realize how easily you can lose a reader. That doesn't mean you've got to always spoon-feed or hit them with pap or otherwise try to compete with less demanding forms of entertainment. That's likely to end badly for you: cat videos will always be more cat-video than you can ever achieve, and you'll just earn contempt for trying. Fiction isn't something people read primarily because they have to. They do it for enjoyment, and people enjoy being challenged a little bit. Just don't take that willingness to take on a challenge for granted, or push it beyond its natural limits.
Secondly, you can maybe sometime give yourself a break as a writer if you think you wrote something great and you got feedback that perplexes you. It's possible that your reader was distracted, in a weird mood, or just isn't a very good reader. That doesn't mean you can just dismiss all advice you don't want to hear because the guy's a knucklehead anyway. But it's a factor worth considering.
All that truth about readers often being ass hats remembered, though, sometimes readers really are pretty great. I mentioned two stories I gave up on early on for bad reasons. I eventually finished both stories. It just took me a while to work up to them. Readers are people, which means they will often (most of the time?) confound you with their thickness, but they'll also knock you over with their perceptiveness. They'll make you feel grateful for the loving, giving way their read your stuff.
I mention this because I don't think it's helpful when actually writing to think too much about the asshattery of readers. If you worry too much about it, you'll never write. Instead, picture a really good reader (maybe you), and write to that person. Don't exhaust your good reader more than you would someone you really like, unless you happen to like being exhausted. But write with confidence and certainty that your work will find a good reader if you accomplish your goal in execution.
Considering what twats readers can be is something you should only do after you've written and gotten feedback either pre or post-publication. Consider well what you hear from a reader, and be willing to be humble enough to make changes. But also take everything with skepticism. A lot of people just comment to have something to say. Many people weren't paying much attention when they read. (Obviously, I think almost everyone in my college workshops fits this description. They were just overworked, and probably more interested in getting, rather than giving, good feedback.)
Secondly, you can maybe sometime give yourself a break as a writer if you think you wrote something great and you got feedback that perplexes you. It's possible that your reader was distracted, in a weird mood, or just isn't a very good reader. That doesn't mean you can just dismiss all advice you don't want to hear because the guy's a knucklehead anyway. But it's a factor worth considering.
All that truth about readers often being ass hats remembered, though, sometimes readers really are pretty great. I mentioned two stories I gave up on early on for bad reasons. I eventually finished both stories. It just took me a while to work up to them. Readers are people, which means they will often (most of the time?) confound you with their thickness, but they'll also knock you over with their perceptiveness. They'll make you feel grateful for the loving, giving way their read your stuff.
I mention this because I don't think it's helpful when actually writing to think too much about the asshattery of readers. If you worry too much about it, you'll never write. Instead, picture a really good reader (maybe you), and write to that person. Don't exhaust your good reader more than you would someone you really like, unless you happen to like being exhausted. But write with confidence and certainty that your work will find a good reader if you accomplish your goal in execution.
Considering what twats readers can be is something you should only do after you've written and gotten feedback either pre or post-publication. Consider well what you hear from a reader, and be willing to be humble enough to make changes. But also take everything with skepticism. A lot of people just comment to have something to say. Many people weren't paying much attention when they read. (Obviously, I think almost everyone in my college workshops fits this description. They were just overworked, and probably more interested in getting, rather than giving, good feedback.)
Subscribe to:
Posts (Atom)