I want to talk today about writer’s groups. No, not writer’s workshops. I’m talking about non-academic, not-for-university-credit, voluntary writer’s groups. I’ve recently gotten involved with one of these writer’s groups. Being a recent MFA graduate, it’s hard for me not to compare this other sort of writer’s group to the traditional grad school workshop, and I have to say, I find this sort of group immensely more useful.
Here’s the thing: the group of writers that I’m involved with is a group of people whose opinions and work I respect in a different way than the general respect I would give to everybody in a workshop setting. Sure, you should value any feedback that anybody gives you – feedback is precious and no matter who offers it, and no matter why, you should listen to it with an open mind – but feedback coming from people who write and read in similar styles to your own is, let’s face it, much more useful than feedback from people who would never read the sort of thing that you write unless they had to . . . for workshop.
Also important is how much you personally like the sort of writing that the other writers in your group do. If you’re not a particular writer’s audience, if he or she is doing things in his or her own work that would never interest you as a reader, that person’s feedback might not be as useful to you as another writer who is actually writing the sort of thing you would read in the real world.
There’s a lot to be said for starting your own group peopled with writers whose work and tastes match your own, and there are other advantages besides the audience issue, too. My writer’s group spent our first meeting discussing how we want to run each session. Rather than having a professor decide for the entire group how each session will be run, how much work each person can submit, and what sort of feedback the writers can give each other, we worked these things our for ourselves. The result is that our discussions are much more efficient because they are tailored to our own specific needs.
We are also able to guide the feedback, if we need to. If I know that you’ve already revised this piece twelve thousand times, I might offer you different feedback than if I know it’s a first draft and hasn’t yet found its footing. Likewise, if I know that you’re planning to submit this piece to, say, The Paris Review, I might give you different feedback than if I know that you’re not planning on submitting it at all, that you’re just writing it for therapeutic reasons or for an experiment.
In addition, writing group discussions are much more organic outside of an academic setting. The same is true, I’ve found, when you compare a conversation between a group of friends who all happened to read the same book to a formal classroom discussion, guided by a teacher or a fellow student who is leading the discussion, and always with the intention of making the discussion last for a specific amount of time. Those time constraints are the biggest issue for me. I can’t tell you how many times I’ve felt frustrated with a workshop discussion that degenerates to nitpicky sentence level complaints because there are still fifteen more minutes allotted to that piece, or on the other side a really useful discussion gets cut short because class is over.
I did, I should say, have one workshop in grad school that pretty much felt like the writer’s group I’m part of now, but for the most part, academic workshops are useful, but the boundaries of the classroom setting prevent them from being as useful as a home grown sort of writer’s group would be.
Read about MFA/MFYou Editor Ashley Cowger's experiences in an MFA Creative Writing program, her thoughts on how the program influenced her on her quest to become a succesful writer, and her thoughts on what the benefits are of not being in an MFA program. It's recommended that you read the Introduction first, to get a clear sense of where the Newsletter is headed, but after that, you should be able to click on any topic you might be interested in and dive right in.
Showing posts with label Workshop. Show all posts
Showing posts with label Workshop. Show all posts
Sunday, December 20, 2009
Sunday, September 27, 2009
Editorial Feedback
So one of the non-MFA writers that MFA/MFYou has published mentioned that he doesn’t feel he’s missed out on anything by not getting a formal creative writing education – he gets essentially the same (or one could argue more valuable) feedback that you get in workshop from editors when he submits his work. This is very true. Although not all editors give feedback on rejected submissions, it’s not uncommon for editors to give personal feedback on the submissions that came really close to getting accepted or even that they liked enough to bother spending the extra few minutes writing a real rejection and not just sending out the form response.
This past week I got a rejection that caused me to go back and revise a story – and the story, I feel, has greatly improved as a result. What happened was that the editor gave me a reason for the rejection that happened to be the exact same reason that another editor had given me a few months ago. The problem that these editors pointed to had to do with the amount of exposition that fell at the beginning of the story. The first time an editor told me this, I recognized that this was true of the story but I felt that it was alright – that it was still well written and engaging and I shouldn’t feel the need to change it just because the current standard is that we don’t like it when stories have a lot of exposition.
But when the second editor cited the exposition as the reason for rejection, I decided I would be wise to go back and revisit the story with that concern in mind. I opened up a new document and wrote a new beginning, working to address the problem these editors had with the story, but I kept the thought in the back of my mind that if I didn’t like the end result, I would chuck the revision and keep the story as it was. But I did like the end result and I think that the story is immensely stronger now.
This is similar to the experience MFAers sometimes have in workshop. You might cringe at some of the workshop feedback, but when several people agree that something is a problem you’ve got to be kind of arrogant to not seriously consider their concerns. The difference here is that I think in some ways the feedback you receive from editors should carry more weight. If more than one editor – having no knowledge of what other editors have said – agree that something isn’t working in your piece, you’d be wise to really think hard about whether they might be right.
I had another editorial feedback episode yesterday, this time for a story that has been accepted for publication (from a market that is both paying and international – woo-hoo!). The editor sent me some feedback and would like me to revise the story and get it back to her in a week. Much of her feedback was similar to the margin notes you receive in workshop. Not the major stuff that gets discussed out loud in class – no, if there had been major problems I doubt that the story would have been accepted at all. This is the sentence level stuff that gets marked on the individual copies of a piece: this sentence is a bit awkward, this bit of dialogue seems out of character, this is perhaps a bit of a cliché. That sort of thing. And it’s all (with the exception of one sentence that I plan to talk to the editor about – see if I can convince her why this is okay) stuff that I agree wholeheartedly about.
I feel like my workshop experiences were at least partially preparing me for the feedback I would later receive from editors, but I also think that you could skip the workshop environment altogether and, as long as you’re a mature enough writer (and human being) to be able to listen open-mindedly to criticism, you’ll be able to improve using the editorial feedback that will inevitably come your way. You may not always like it, and you certainly won’t always agree with it, but you should be happy to get it whenever you can. None of us can do this entirely on our own.
This past week I got a rejection that caused me to go back and revise a story – and the story, I feel, has greatly improved as a result. What happened was that the editor gave me a reason for the rejection that happened to be the exact same reason that another editor had given me a few months ago. The problem that these editors pointed to had to do with the amount of exposition that fell at the beginning of the story. The first time an editor told me this, I recognized that this was true of the story but I felt that it was alright – that it was still well written and engaging and I shouldn’t feel the need to change it just because the current standard is that we don’t like it when stories have a lot of exposition.
But when the second editor cited the exposition as the reason for rejection, I decided I would be wise to go back and revisit the story with that concern in mind. I opened up a new document and wrote a new beginning, working to address the problem these editors had with the story, but I kept the thought in the back of my mind that if I didn’t like the end result, I would chuck the revision and keep the story as it was. But I did like the end result and I think that the story is immensely stronger now.
This is similar to the experience MFAers sometimes have in workshop. You might cringe at some of the workshop feedback, but when several people agree that something is a problem you’ve got to be kind of arrogant to not seriously consider their concerns. The difference here is that I think in some ways the feedback you receive from editors should carry more weight. If more than one editor – having no knowledge of what other editors have said – agree that something isn’t working in your piece, you’d be wise to really think hard about whether they might be right.
I had another editorial feedback episode yesterday, this time for a story that has been accepted for publication (from a market that is both paying and international – woo-hoo!). The editor sent me some feedback and would like me to revise the story and get it back to her in a week. Much of her feedback was similar to the margin notes you receive in workshop. Not the major stuff that gets discussed out loud in class – no, if there had been major problems I doubt that the story would have been accepted at all. This is the sentence level stuff that gets marked on the individual copies of a piece: this sentence is a bit awkward, this bit of dialogue seems out of character, this is perhaps a bit of a cliché. That sort of thing. And it’s all (with the exception of one sentence that I plan to talk to the editor about – see if I can convince her why this is okay) stuff that I agree wholeheartedly about.
I feel like my workshop experiences were at least partially preparing me for the feedback I would later receive from editors, but I also think that you could skip the workshop environment altogether and, as long as you’re a mature enough writer (and human being) to be able to listen open-mindedly to criticism, you’ll be able to improve using the editorial feedback that will inevitably come your way. You may not always like it, and you certainly won’t always agree with it, but you should be happy to get it whenever you can. None of us can do this entirely on our own.
Sunday, June 21, 2009
Inspiration
I’ve heard a lot of talk about how there is perhaps more inspiration for writing material outside of an MFA program, in that fabled “real world” everyone talks about. I imagine this is probably true, and in fact as I’m preparing to move to Ohio in a few weeks I’m going back and forth with what would be better for me: finding a good teaching job at one of the many community colleges in the area, or getting a regular job and stepping away from the very different world of academia for a while.
But I do think there is a lot of inspiration to be had in an MFA program, and for me a lot of that inspiration came from reading the work of my peers and instructors. All the other students in my program at UAF were absolutely amazing writers and most of them had very distinct styles from each other and from me. I think one of the most useful things you can do as a writer is expose yourself to a wide range of writing and experiment around with some of the things you see other people doing. This is different from just reading a lot, since in an MFA program you can then actually talk to and get feedback from the very people that inspired you.
In my program there were two people in particular whose work I was just blown away by and who as a result really inspired me to push myself to step out of my comfort zone and see what would happen if I tried this or that. (That’s not to say that I was only blown away by the work of two people; there were many people in the program whose writing really impressed me. But there are two in particular who really inspired me to experiment around with some of the things they were doing).
One was a fellow student, who is in my opinion the best writer in the program (or at least whose writing is my personal favorite) and who has this incredible ability to meld fantasy-type genre stories with absolutely amazingly well crafted, literary writing. The first workshop I had with her she submitted a story that everybody just fell in love with, myself included. It had a touch of magic and fairy tale-like fantasy but also very strong character and voice, and I was super inspired to try to experiment around with magic realism in my own writing – which has been very fun and I think has helped me move to the next level as a writer.
The other is an instructor in the program, award winning writer David Crouse, who in the very last workshop I took at UAF actually submitted his own work to be workshopped alongside the students. Not only was it super cool to get to workshop such a successful writer’s work at the same time as our own work, but I felt really inspired to push myself to be less, well, obvious in my writing. I’m well aware that my number one problem as a writer is that I’m often heavy handed and come right out and say things that it would be better to let the reader put together for him or herself, and when I saw how much it can work to, as he says, “withhold” more, I made an effort to try to work more on that in my work.
This is a different sort of inspiration, yes, than what people talk about when they say there is more inspiration in the real world than in an academic program. But it’s inspiration nonetheless and I wouldn’t trade it for anything.
But I do think there is a lot of inspiration to be had in an MFA program, and for me a lot of that inspiration came from reading the work of my peers and instructors. All the other students in my program at UAF were absolutely amazing writers and most of them had very distinct styles from each other and from me. I think one of the most useful things you can do as a writer is expose yourself to a wide range of writing and experiment around with some of the things you see other people doing. This is different from just reading a lot, since in an MFA program you can then actually talk to and get feedback from the very people that inspired you.
In my program there were two people in particular whose work I was just blown away by and who as a result really inspired me to push myself to step out of my comfort zone and see what would happen if I tried this or that. (That’s not to say that I was only blown away by the work of two people; there were many people in the program whose writing really impressed me. But there are two in particular who really inspired me to experiment around with some of the things they were doing).
One was a fellow student, who is in my opinion the best writer in the program (or at least whose writing is my personal favorite) and who has this incredible ability to meld fantasy-type genre stories with absolutely amazingly well crafted, literary writing. The first workshop I had with her she submitted a story that everybody just fell in love with, myself included. It had a touch of magic and fairy tale-like fantasy but also very strong character and voice, and I was super inspired to try to experiment around with magic realism in my own writing – which has been very fun and I think has helped me move to the next level as a writer.
The other is an instructor in the program, award winning writer David Crouse, who in the very last workshop I took at UAF actually submitted his own work to be workshopped alongside the students. Not only was it super cool to get to workshop such a successful writer’s work at the same time as our own work, but I felt really inspired to push myself to be less, well, obvious in my writing. I’m well aware that my number one problem as a writer is that I’m often heavy handed and come right out and say things that it would be better to let the reader put together for him or herself, and when I saw how much it can work to, as he says, “withhold” more, I made an effort to try to work more on that in my work.
This is a different sort of inspiration, yes, than what people talk about when they say there is more inspiration in the real world than in an academic program. But it’s inspiration nonetheless and I wouldn’t trade it for anything.
Labels:
Community,
Faculty Guidance,
Peer Support,
Reading,
Workshop
Sunday, May 24, 2009
Oh that’s SO Cliché!
One thing I noticed a fair amount of when I was teaching Creative Writing last semester was the tendency students had to refer to each others work as “cliché” or “stereotypical” or “unoriginal.” It’s something I remember experiencing for the first time when I took my first graduate level workshop – being cliché wasn’t something I had ever been accused of as an undergrad, for some reason, but my first semester in grad school I grew to loath the word cliché. Oh they tried to say it nicely, mind you. Things like, “This is funny in a totally clichéd way – I assume that’s what you’re going for, right?” or, “Your narrator seems like sort of an idiot because he speaks and behaves in a totally clichéd manner – is that intentional?”
I’m not going to bitch and moan about how much it hurts to be told that your writing is clichéd (a lot) or how it hurts even more to realize that (GASP!) the things your peers are telling you are true. I look back on my first graduate level workshop as one of the most painful but also most useful experiences I have ever had in my life, and while some of those comments still sting a little bit (they remind me, you know, how little actual talent I have because any ability that I do have has come from a whole lot of hard work) I feel I have improved drastically because of them.
But what I want to talk about here is my experience looking at it from the other side this past semester, as a teacher. I did have one incident during the semester where one student’s feedback was so over-the-top cruel (saying that the entire story was just one giant cliché and that it could not possibly be revised and should be thrown away altogether) but overall most of the students were trying to be constructive when they repeatedly accused each other of being cliché, and in fact, most of them were essentially right (of course, I still encouraged students to come up with more constructive feedback than “this is so cliché”).
Though a majority of the writing coming from that class showed promise (and some of it I believe will be publishable if the student keeps working on it), I would also say, if looking at it from an objective manner, most of the stories that were written for that class contained elements that were not particularly original. While some of the stories were certainly less original than others, it did seem to be true that most of the students were inadvertently falling back on ideas that most of us (who are perhaps more well read than a class full of undergraduate Intro to Creative Writing students) would say we’ve seen a thousand times before.
But here’s the trick. In general, the reason why things become cliché is because they’re effective. This is true on the sentence level (how many cliché metaphors and similes can you think of that would just shock you with their beauty and truth if it wasn’t for the fact that it was a cliché?) and it’s true on the larger scale, too. Characters often have this or that personality trait because it successfully tells you something important about them. We’ve seen this or that plot twist so many times because it works. See? Most clichés becomes cliché because, in truth, they’re excellent examples of writing.
What’s that you say? But a good writer comes up with his or her own good writing? Here’s the thing: I’ve come to realize that, at the early stage of writing, many excellent writers use clichés not because they’re not good enough to come up with something for themselves, but because they haven’t read widely enough yet to know that this is a cliché. It may well be (and I think often is) an idea that the writer came up with on his or her own, it just happens to also be an idea that tons of other people came up with too.
This is part of the reason why I think reading A LOT is essential to success as a writer. You have got to develop a broad knowledge base of what’s been done already and what hasn’t. Of course, there are a number of other good reasons why you should read a lot, but this is one that I think gets forgotten sometimes. And the other important thing I’ve taken away from this is the belief that writing really clichéd stuff early on – when you’re still learning how to write – does not necessarily preclude you from developing into a very good writer. It may well even be a sign of developing ability – you’ve figured out this thing that works, you just don’t have enough knowledge in your field yet to know that somebody else figured it out before you.
So write your clichés if you must. Eventually you’ll have to move past them if you want to be considered good by anyone but your mom, but I don’t think it’s fair to say that all writers who write in clichés are inherently bad. Maybe all it really means is that they still have a lot left to learn, and really, don’t we all?
I’m not going to bitch and moan about how much it hurts to be told that your writing is clichéd (a lot) or how it hurts even more to realize that (GASP!) the things your peers are telling you are true. I look back on my first graduate level workshop as one of the most painful but also most useful experiences I have ever had in my life, and while some of those comments still sting a little bit (they remind me, you know, how little actual talent I have because any ability that I do have has come from a whole lot of hard work) I feel I have improved drastically because of them.
But what I want to talk about here is my experience looking at it from the other side this past semester, as a teacher. I did have one incident during the semester where one student’s feedback was so over-the-top cruel (saying that the entire story was just one giant cliché and that it could not possibly be revised and should be thrown away altogether) but overall most of the students were trying to be constructive when they repeatedly accused each other of being cliché, and in fact, most of them were essentially right (of course, I still encouraged students to come up with more constructive feedback than “this is so cliché”).
Though a majority of the writing coming from that class showed promise (and some of it I believe will be publishable if the student keeps working on it), I would also say, if looking at it from an objective manner, most of the stories that were written for that class contained elements that were not particularly original. While some of the stories were certainly less original than others, it did seem to be true that most of the students were inadvertently falling back on ideas that most of us (who are perhaps more well read than a class full of undergraduate Intro to Creative Writing students) would say we’ve seen a thousand times before.
But here’s the trick. In general, the reason why things become cliché is because they’re effective. This is true on the sentence level (how many cliché metaphors and similes can you think of that would just shock you with their beauty and truth if it wasn’t for the fact that it was a cliché?) and it’s true on the larger scale, too. Characters often have this or that personality trait because it successfully tells you something important about them. We’ve seen this or that plot twist so many times because it works. See? Most clichés becomes cliché because, in truth, they’re excellent examples of writing.
What’s that you say? But a good writer comes up with his or her own good writing? Here’s the thing: I’ve come to realize that, at the early stage of writing, many excellent writers use clichés not because they’re not good enough to come up with something for themselves, but because they haven’t read widely enough yet to know that this is a cliché. It may well be (and I think often is) an idea that the writer came up with on his or her own, it just happens to also be an idea that tons of other people came up with too.
This is part of the reason why I think reading A LOT is essential to success as a writer. You have got to develop a broad knowledge base of what’s been done already and what hasn’t. Of course, there are a number of other good reasons why you should read a lot, but this is one that I think gets forgotten sometimes. And the other important thing I’ve taken away from this is the belief that writing really clichéd stuff early on – when you’re still learning how to write – does not necessarily preclude you from developing into a very good writer. It may well even be a sign of developing ability – you’ve figured out this thing that works, you just don’t have enough knowledge in your field yet to know that somebody else figured it out before you.
So write your clichés if you must. Eventually you’ll have to move past them if you want to be considered good by anyone but your mom, but I don’t think it’s fair to say that all writers who write in clichés are inherently bad. Maybe all it really means is that they still have a lot left to learn, and really, don’t we all?
Sunday, May 17, 2009
Overwhelmed by Workshop Suggestions
I got an interesting rejection this week. It was for a story I had submitted to workshop a few semesters ago. This story had been a totally different sort of writing from what I usually do and so, when I had it workshopped, I was really sort of insecure about what to do with it, not even sure what I wanted it to be. The truth is, I was probably a little overzealous in my revision to accept every bit of advice that was given to me whether it was really the right choice or not. But at any rate, I revised the story taking WAY more of the class’s suggestions than I normally would and started sending it out when I felt like it was ready.
The editor who rejected the story gave me some extremely useful specifics on why he was rejecting it. He said he thought it was a great idea, but X, Y, and Z were holding it back. Every single thing he pointed out were things I had changed about the story to follow workshop feedback. The interesting thing about it is that I realized, as I thought about his suggestions and compared them with the original workshop suggestions, that in many ways I feel that both sets of feedback were right. But how can that be?
I read somewhere recently that suggestions that are given in a workshop should rarely be taken – they should only be used as a sign for something that might be wrong with the piece at the moment. Once you figure out what’s fueling the suggestion, you should, most of the time, ignore the suggestion itself and come up with something on your own to fix whatever problem lies at the heart of the suggestion.
My problem was that, not feeling very confident about the story to begin with, and especially since it was a totally different sort of writing from what I normally do, most of the suggestions that were given to me during workshop sounded like great ideas. So I decided to take many of them. But once they had actually become part of the piece, they created a whole new set of problems that I hadn’t noticed until this editor pointed them out to me.
This is one of the dangers of workshop. I can’t even remember all the times I’ve been given feedback that sounded great while I sat in the classroom feverishly taking notes, and then when I went to actually make the changes I realized that they would never work – they didn’t fit with what I was trying to do or they created new, much larger problems or . . .
My problem this time was really a complete lack of self confidence in my own abilities to, well, write the story for myself. Workshop is great, don’t get me wrong, but getting feedback can become almost like a crutch sometimes and if you’re not feeling very sure of a particular piece it can do more harm than good to have a large group of people, many of whom are probably not picking up on your intentions as the writer, give you suggestions on how to make it more like something they would have written.
So it’s important to remember that your workshop did not write the piece, you did, and only you can make the final decisions of what to do next. It’s difficult, I think, but extremely important to find the right balance between having the confidence to veto suggestions that are wrong for this particular piece and yet the wisdom to recognize when there are problems with the piece and when feedback should be taken.
The editor who rejected the story gave me some extremely useful specifics on why he was rejecting it. He said he thought it was a great idea, but X, Y, and Z were holding it back. Every single thing he pointed out were things I had changed about the story to follow workshop feedback. The interesting thing about it is that I realized, as I thought about his suggestions and compared them with the original workshop suggestions, that in many ways I feel that both sets of feedback were right. But how can that be?
I read somewhere recently that suggestions that are given in a workshop should rarely be taken – they should only be used as a sign for something that might be wrong with the piece at the moment. Once you figure out what’s fueling the suggestion, you should, most of the time, ignore the suggestion itself and come up with something on your own to fix whatever problem lies at the heart of the suggestion.
My problem was that, not feeling very confident about the story to begin with, and especially since it was a totally different sort of writing from what I normally do, most of the suggestions that were given to me during workshop sounded like great ideas. So I decided to take many of them. But once they had actually become part of the piece, they created a whole new set of problems that I hadn’t noticed until this editor pointed them out to me.
This is one of the dangers of workshop. I can’t even remember all the times I’ve been given feedback that sounded great while I sat in the classroom feverishly taking notes, and then when I went to actually make the changes I realized that they would never work – they didn’t fit with what I was trying to do or they created new, much larger problems or . . .
My problem this time was really a complete lack of self confidence in my own abilities to, well, write the story for myself. Workshop is great, don’t get me wrong, but getting feedback can become almost like a crutch sometimes and if you’re not feeling very sure of a particular piece it can do more harm than good to have a large group of people, many of whom are probably not picking up on your intentions as the writer, give you suggestions on how to make it more like something they would have written.
So it’s important to remember that your workshop did not write the piece, you did, and only you can make the final decisions of what to do next. It’s difficult, I think, but extremely important to find the right balance between having the confidence to veto suggestions that are wrong for this particular piece and yet the wisdom to recognize when there are problems with the piece and when feedback should be taken.
Sunday, March 22, 2009
Pushing Yourself
Perhaps it’s the fact that I won’t be going to school next semester (yes, that’s right, it’s been officially decided that I’ll be moving to Ohio so my husband can begin study at a masters program there. I’ll try to find the least undesirable job that I can and focus my attention on getting my novel ready to send out) but this past week I’ve suddenly had a heightened sense of the value of the feedback that you get and the things that you learn in an MFA program.
Feedback is something I’ve struggled with I would say my entire time in the program. Sometimes I want to ignore some points of feedback altogether – write it off as that person simply not being in my audience – and I know that other people are prone to this as well, often directing their peers with what sort of feedback they’re looking for when they turn something in to workshop (and I’ve been guilty of this, too). But I’ve been thinking more and more lately that that sort of attitude will hold you back from getting to be the writer that you have the potential to become.
I don’t mean that I’ve decided that from now on every single suggestion that anybody gives me I’ll just mindlessly take. But ignoring bits of feedback altogether isn’t useful either. Ultimately, whether somebody would be in your audience or not has very little to do with whether or not you should consider their points. They are readers and writers and how they react to your piece is worth knowing – even if you won’t change the piece accordingly.
What I mean is that, you learn, as a writer, every time somebody misreads something that you wrote. And no matter what, people will always misread things. Even if it’s ready, even if you get it published to great success, there will always still be people who read it differently than you intended, get hung up on certain parts that you put in as mere background, or just plain dislike it for whatever reason they may have. And it teaches you a lot about writing to know these things.
Another thing I’ve noticed is that, with my time in the program very near to its end, I’m finding myself more and more interested and willing to try to crawl outside of my comfort zone as a writer, to stop saying, “Well, I’m just not interested in writing like that” and begin to experiment around with some of the techniques that I used to consider pretentious and now realize can be really effective, if done well.
I still believe that experimental writing is overused and that most readers aren’t interested in it, but I do think that, if something nontraditional can be done in such a way that it doesn’t seem experimental – that is, it’s so flawlessly integrated into the text that the reader doesn’t even notice the experimental quality of it unless they stop and think about it – it can be effective. It’s true that most of the experiments that we see in workshops aren’t being done well yet, but if you think about it, of course they’re not – they’re drafts! And I think you learn a lot from trying these things, even when they don’t work out.
But experimental isn’t really the right word. I guess what I really mean is not being afraid to move beyond what sort of writer you’ve always been and instead opening up to the possibilities of what sort of writer you have it in you to become. There are certain things that I feel afraid of trying because I think, “I’m just not a good enough writer to pull that off,” but really, the only way I can get to be a good enough writer is to push myself and try those things and learn from my mistakes until I get to a point where I can pull them off.
Feedback is something I’ve struggled with I would say my entire time in the program. Sometimes I want to ignore some points of feedback altogether – write it off as that person simply not being in my audience – and I know that other people are prone to this as well, often directing their peers with what sort of feedback they’re looking for when they turn something in to workshop (and I’ve been guilty of this, too). But I’ve been thinking more and more lately that that sort of attitude will hold you back from getting to be the writer that you have the potential to become.
I don’t mean that I’ve decided that from now on every single suggestion that anybody gives me I’ll just mindlessly take. But ignoring bits of feedback altogether isn’t useful either. Ultimately, whether somebody would be in your audience or not has very little to do with whether or not you should consider their points. They are readers and writers and how they react to your piece is worth knowing – even if you won’t change the piece accordingly.
What I mean is that, you learn, as a writer, every time somebody misreads something that you wrote. And no matter what, people will always misread things. Even if it’s ready, even if you get it published to great success, there will always still be people who read it differently than you intended, get hung up on certain parts that you put in as mere background, or just plain dislike it for whatever reason they may have. And it teaches you a lot about writing to know these things.
Another thing I’ve noticed is that, with my time in the program very near to its end, I’m finding myself more and more interested and willing to try to crawl outside of my comfort zone as a writer, to stop saying, “Well, I’m just not interested in writing like that” and begin to experiment around with some of the techniques that I used to consider pretentious and now realize can be really effective, if done well.
I still believe that experimental writing is overused and that most readers aren’t interested in it, but I do think that, if something nontraditional can be done in such a way that it doesn’t seem experimental – that is, it’s so flawlessly integrated into the text that the reader doesn’t even notice the experimental quality of it unless they stop and think about it – it can be effective. It’s true that most of the experiments that we see in workshops aren’t being done well yet, but if you think about it, of course they’re not – they’re drafts! And I think you learn a lot from trying these things, even when they don’t work out.
But experimental isn’t really the right word. I guess what I really mean is not being afraid to move beyond what sort of writer you’ve always been and instead opening up to the possibilities of what sort of writer you have it in you to become. There are certain things that I feel afraid of trying because I think, “I’m just not a good enough writer to pull that off,” but really, the only way I can get to be a good enough writer is to push myself and try those things and learn from my mistakes until I get to a point where I can pull them off.
Sunday, March 15, 2009
Writing without Workshop
As March charges steadily toward its end I’m beginning to face the likelihood that I’ll be joining the real world next semester instead of continuing on as a grad student in a new program somewhere. So far I’ve gotten lukewarm responses at best – ranging from getting in to a program without being offered a TA to making it onto the wait list to getting flat out rejected. There are still two schools I haven’t heard back from but one of them I feel 99% certain I would have heard by now if I had gotten in and the other it’s likely will be a rejection, too, judging from the responses I’ve received from the other programs.
What does this have to do with workshop, you ask? That’s a very good question. I’ll tell you. Even though my preference would have been to get into a literature program, I had been planning on trying to take workshops as electives so I could continue getting feedback and being forced to grow as a writer. With the realization that I won’t be in school comes the realization that neither will I be taking workshops. And I’m starting to recognize this as a positive opportunity instead of something scary – something ominous – in my future.
I’m sure whether I’m taking workshops or not, I’ll share my work and get feedback from other writers (I’ll have to force myself to be brave about asking them is all). But instead of the broad range of readers in a workshop setting, it’ll just be the people I choose to share my work with and feel confident will give me the sort of feedback that will be helpful for me, personally, as a writer. I’m starting to see that this may actually be better, since I tend to take feedback very seriously – possibly too seriously – and it may be in my best interest to limit the feedback a little bit.
And aside from the obvious fact that it will be liberating to write whatever I want, revise it as I see fit, and not think about what a huge group of people with varied tastes would say, I think it’s also going to push me a little bit harder as a writer, too. I’ve spent the past three years taking into serious consideration the openly voiced opinions of my fellows workshoppers. I’ve learned a lot from it both as a reader and a writer and I’m able, now, to look at my own writing much more objectively and anticipate what major concerns a reader might have.
I think not taking part in the workshop environment will force me to put this skill to better use and force me to practice it, hone it. Instead of having the comfort of letting somebody tell me whether my suspicions about this or that aspect of the story not working are founded, I’ll have to work it out for myself – pinpoint the problems and figure out how to fix them. And I think it’ll help me take that next, necessary step forward as a writer.
What does this have to do with workshop, you ask? That’s a very good question. I’ll tell you. Even though my preference would have been to get into a literature program, I had been planning on trying to take workshops as electives so I could continue getting feedback and being forced to grow as a writer. With the realization that I won’t be in school comes the realization that neither will I be taking workshops. And I’m starting to recognize this as a positive opportunity instead of something scary – something ominous – in my future.
I’m sure whether I’m taking workshops or not, I’ll share my work and get feedback from other writers (I’ll have to force myself to be brave about asking them is all). But instead of the broad range of readers in a workshop setting, it’ll just be the people I choose to share my work with and feel confident will give me the sort of feedback that will be helpful for me, personally, as a writer. I’m starting to see that this may actually be better, since I tend to take feedback very seriously – possibly too seriously – and it may be in my best interest to limit the feedback a little bit.
And aside from the obvious fact that it will be liberating to write whatever I want, revise it as I see fit, and not think about what a huge group of people with varied tastes would say, I think it’s also going to push me a little bit harder as a writer, too. I’ve spent the past three years taking into serious consideration the openly voiced opinions of my fellows workshoppers. I’ve learned a lot from it both as a reader and a writer and I’m able, now, to look at my own writing much more objectively and anticipate what major concerns a reader might have.
I think not taking part in the workshop environment will force me to put this skill to better use and force me to practice it, hone it. Instead of having the comfort of letting somebody tell me whether my suspicions about this or that aspect of the story not working are founded, I’ll have to work it out for myself – pinpoint the problems and figure out how to fix them. And I think it’ll help me take that next, necessary step forward as a writer.
Sunday, January 18, 2009
The Balance Between Story and Craft
Last week I talked about Anne Enright’s short story collection, Yesterday’s Weather, and how it shows the importance of personal experience in writing. This is a difference between her earlier stories and her later ones that Enright herself noticed and referred to in her introduction. The stylistic shift that I noticed is more subjective and it may not be one that other people would agree with me about.
Enright has a very unique style: her stories are heavy on exposition and the narration tends to shift back and forth quite frequently from the “now” moment of the story itself and the characters’ pasts. There is also a certain vagueness to the storytelling, which is, I think, an attempt at subtlety that in my opinion often goes too far. I would almost call her writing experimental.
I noticed that, while there are certainly exceptions, I generally liked the more recent stories better. When I tried to put my finger on what it was about the more recent stories that I liked, I realized that many of them used this expositional shifting and vagueness far less than the older stories. A lot of them even had a normal amount of exposition, though some of them still had more than most stories would. And the vagueness, while it was still often present in these stories, was much more in line with what I would consider skillfully placed subtle hints about what it all means and what’s going on. The more recent stories seemed less like experiments and more like stories by a writer who has found her voice and has found the right balance for her voice.
It’s interesting, though, that many of the older stories reminded me of the sort of thing you see a lot of in MFA workshops. Writing that seems to focus more on doing something different than on telling a good story. I often think that one of the main differences you see from MFA writers and non-MFA writers is the attention paid to craft. I think a lot of non-MFA writers think more about the story, the plot and what events will take place. Whereas many MFA writers focus more on how to tell the story, what techniques should they employ and how should they structure this piece.
Ultimately, I think you have to focus on both for a story to be very good. More and more literary journals these days include in their submission guidelines that they aren’t interested in the sort of writing that gets manufactured in the MFA machine. Writing that pays little or no attention to plot, the story part of the story, and instead focuses entirely on employing artistic techniques that often leave the story completely incomprehensible unless you read it several times, extremely closely. Something that few readers and no editors will be willing to do. Really, only other writers have any interest in reading this sort of writing.
While Enright’s early stuff still managed to get published, I would argue that she has improved immensely over the years in large part because she has found a good balance between craft and story. I wonder if this is in part because she went and wrote several novels inbetween and you have to learn to pay attention to plot if you want to write a novel. Even writers looking for artistic inspiration are unlikely to bear with you for 300 pages of no plot.
In contrast to Enright’s collection from last week, this week I read a downright terrible book that has the opposite problem from Enright’s earlier work. I’ll talk about that next time.
Enright has a very unique style: her stories are heavy on exposition and the narration tends to shift back and forth quite frequently from the “now” moment of the story itself and the characters’ pasts. There is also a certain vagueness to the storytelling, which is, I think, an attempt at subtlety that in my opinion often goes too far. I would almost call her writing experimental.
I noticed that, while there are certainly exceptions, I generally liked the more recent stories better. When I tried to put my finger on what it was about the more recent stories that I liked, I realized that many of them used this expositional shifting and vagueness far less than the older stories. A lot of them even had a normal amount of exposition, though some of them still had more than most stories would. And the vagueness, while it was still often present in these stories, was much more in line with what I would consider skillfully placed subtle hints about what it all means and what’s going on. The more recent stories seemed less like experiments and more like stories by a writer who has found her voice and has found the right balance for her voice.
It’s interesting, though, that many of the older stories reminded me of the sort of thing you see a lot of in MFA workshops. Writing that seems to focus more on doing something different than on telling a good story. I often think that one of the main differences you see from MFA writers and non-MFA writers is the attention paid to craft. I think a lot of non-MFA writers think more about the story, the plot and what events will take place. Whereas many MFA writers focus more on how to tell the story, what techniques should they employ and how should they structure this piece.
Ultimately, I think you have to focus on both for a story to be very good. More and more literary journals these days include in their submission guidelines that they aren’t interested in the sort of writing that gets manufactured in the MFA machine. Writing that pays little or no attention to plot, the story part of the story, and instead focuses entirely on employing artistic techniques that often leave the story completely incomprehensible unless you read it several times, extremely closely. Something that few readers and no editors will be willing to do. Really, only other writers have any interest in reading this sort of writing.
While Enright’s early stuff still managed to get published, I would argue that she has improved immensely over the years in large part because she has found a good balance between craft and story. I wonder if this is in part because she went and wrote several novels inbetween and you have to learn to pay attention to plot if you want to write a novel. Even writers looking for artistic inspiration are unlikely to bear with you for 300 pages of no plot.
In contrast to Enright’s collection from last week, this week I read a downright terrible book that has the opposite problem from Enright’s earlier work. I’ll talk about that next time.
Sunday, December 14, 2008
Workshop Reflections
Because I am extremely sick today and because I think it might be interesting, I’ve decided to post as my blog for this week a portion of the assigned final commentary for my workshop class this semester. We each had to write a 5-8 page self commentary on the pieces we turned in this semester, our process of writing them, what we struggled with, our revision tactics, etc. One piece that I turned in to workshop this semester in particular I think of as a telling sign of how much I’ve gained through the program:
The second story I submitted for workshop this semester was one I had written a few years ago, and submitted to workshop during my first semester at UAF . . . to disastrous results. In response to this story people actually hinted in their feedback that nobody who would write something like this could possibly be a good writer – and I thought about giving up as a writer altogether.
Needless to say, I set this story aside after that workshop and I didn’t decide to come back to it until just this summer. I’ve always really liked the idea behind this story, and I thought that, since through my experiences in the program here at UAF I’ve grown a lot as a writer, perhaps I could rewrite the story entirely from page one and make it workable. I did just that over the summer, and felt like it came together much more smoothly than the earlier draft that had gotten ripped to shreds during my first UAF workshop class. I changed just about everything about the story (the narration, the characters, the tone . . .) except the core idea of the story.
The workshop feedback on this story this time around was much more encouraging while at the same time being very useful. I had the impression that people generally thought the story had potential (which is certainly a shift from that earlier workshop experience) and I got a lot of extremely useful suggestions on points to expand, points that need to be clarified or maybe left out, and ways that I can increase the tension and stakes for the main character. I’ve been working on revising this piece further for the past few weeks now and I plan to continue revising it over the break. It’s coming together well and my hopes are that by the end of the break I’ll be able to start submitting it to journals.
I learned a lot through the revision process of this story in particular because I was forced to really look at it not just from the perspective of “what happens in this story?” but from an angle of closely analyzing craft: how does the narration function; how can sympathy be created for a genuinely despicable main character; how can I include exposition that’s necessary without letting it take over the present scene? And because early drafts of the story were problematic because of an unintended metafictional element; I was forced to be more aware of craft from a perspective of things I did not want this piece to be.
I feel that this piece is a good gauge for how much I’ve improved as a writer during my experience at UAF. The first draft of it I actually wrote for an undergraduate workshop; then I revised that and took in a new version to my first graduate level workshop. Before I came to the program, as this piece can verify, I didn't think about craft on a conscious level; I just wrote what sounded good to me. But now, two years into the program, I was able to completely rewrite the entire story with more of an awareness of craft and technique and I think, even though I’m still revising it, it’s a much better piece now.
The second story I submitted for workshop this semester was one I had written a few years ago, and submitted to workshop during my first semester at UAF . . . to disastrous results. In response to this story people actually hinted in their feedback that nobody who would write something like this could possibly be a good writer – and I thought about giving up as a writer altogether.
Needless to say, I set this story aside after that workshop and I didn’t decide to come back to it until just this summer. I’ve always really liked the idea behind this story, and I thought that, since through my experiences in the program here at UAF I’ve grown a lot as a writer, perhaps I could rewrite the story entirely from page one and make it workable. I did just that over the summer, and felt like it came together much more smoothly than the earlier draft that had gotten ripped to shreds during my first UAF workshop class. I changed just about everything about the story (the narration, the characters, the tone . . .) except the core idea of the story.
The workshop feedback on this story this time around was much more encouraging while at the same time being very useful. I had the impression that people generally thought the story had potential (which is certainly a shift from that earlier workshop experience) and I got a lot of extremely useful suggestions on points to expand, points that need to be clarified or maybe left out, and ways that I can increase the tension and stakes for the main character. I’ve been working on revising this piece further for the past few weeks now and I plan to continue revising it over the break. It’s coming together well and my hopes are that by the end of the break I’ll be able to start submitting it to journals.
I learned a lot through the revision process of this story in particular because I was forced to really look at it not just from the perspective of “what happens in this story?” but from an angle of closely analyzing craft: how does the narration function; how can sympathy be created for a genuinely despicable main character; how can I include exposition that’s necessary without letting it take over the present scene? And because early drafts of the story were problematic because of an unintended metafictional element; I was forced to be more aware of craft from a perspective of things I did not want this piece to be.
I feel that this piece is a good gauge for how much I’ve improved as a writer during my experience at UAF. The first draft of it I actually wrote for an undergraduate workshop; then I revised that and took in a new version to my first graduate level workshop. Before I came to the program, as this piece can verify, I didn't think about craft on a conscious level; I just wrote what sounded good to me. But now, two years into the program, I was able to completely rewrite the entire story with more of an awareness of craft and technique and I think, even though I’m still revising it, it’s a much better piece now.
Sunday, October 19, 2008
Learning the Art and Craft
Do you know that when I started at UAF, I really wasn’t thinking of it as a chance for me to learn and grow and become a better writer? I knew, in a vague sort of way, that way where you don’t consciously think about it but if someone asked you directly you’d say “well, yeah, sure,” that the more practice you got at something the better you would become. But I honestly didn’t believe that writing was something you could learn. It was something you just either had in you or you didn’t.
This is a ridiculous opinion, but it’s one I shared with a lot of really successful writers. Thinking about it now, it’s irritating to look at famous writers who have made a lot of money based on hard work but who tell their fans that they were just born with “it.” Sure, they all admit that a lot of it comes down to the work, too, but many of them suggest that part of it is just natural talent and I think that’s a delusional crock.
At any rate, I came to UAF thinking not that I was going to learn a lot about writing, but that I would get three more years to focus on my writing and put off the inevitable moment of having to select a career a little longer. And I did get that benefit, as well as the benefit of developing an absolute passion for teaching, but I also learned A LOT about the craft of writing, how to write better, how to find the balance between what you want your art to be and what an audience will actually appreciate, too.
My first big breakthrough was with a story I wrote for my first graduate writer’s workshop, “Interpretations of Aurora.” I wrote this story in the style I had been practicing for a long time, with a dark, brooding, apathetic narrator who feels removed from the world around him. But just to do it, just because I thought it would be what the workshop would ask me to do, anyway, I included some really vivid descriptions of the setting. Sensory imagery. Movement, too. I had my narrator sitting down on the front steps of his porch folding autumn leaves and then piling them on top of the step below him as he has an argument with his wife.
This was a sort of snide addition on my part. I thought everybody would hate it, and I would think, “a-ha! But this is the very sort of thing you would have told me to include!” In fact, everybody loved it. The sensory imagery makes you feel like you’re really there; and this small, seemingly insignificant action tells so much about this narrator; and when the wife sits down on the step below him and she knocks the leaves onto the floor, it says so much about their relationship without the narrator having to say anything but what happened.
I went back and looked at the scene afterwards and realized that they were right. This was a great, telling moment. It got us out of the narrator’s head and let the reader be involved in the story, rather than just having the apathetic narrator, whose voice I still loved but who was standing in front of the reader’s line of sight, tell the story to the reader. And it had come about entirely by accident, by my trying to prove how pointless this sort of detail was.
I learned a lot during that first semester, and while it was, as I’ve said before, the hardest semester I’ve ever had to endure, it was also the most educational. Once I realized that I wasn’t brilliant and that I actually had to work at it and learn and grow and develop, I began to do just that. And now, as I’m entering the last stretch of the program here at UAF, I feel like I’m a much better writer than I was before I came, and I can only just keep getting better.
This is a ridiculous opinion, but it’s one I shared with a lot of really successful writers. Thinking about it now, it’s irritating to look at famous writers who have made a lot of money based on hard work but who tell their fans that they were just born with “it.” Sure, they all admit that a lot of it comes down to the work, too, but many of them suggest that part of it is just natural talent and I think that’s a delusional crock.
At any rate, I came to UAF thinking not that I was going to learn a lot about writing, but that I would get three more years to focus on my writing and put off the inevitable moment of having to select a career a little longer. And I did get that benefit, as well as the benefit of developing an absolute passion for teaching, but I also learned A LOT about the craft of writing, how to write better, how to find the balance between what you want your art to be and what an audience will actually appreciate, too.
My first big breakthrough was with a story I wrote for my first graduate writer’s workshop, “Interpretations of Aurora.” I wrote this story in the style I had been practicing for a long time, with a dark, brooding, apathetic narrator who feels removed from the world around him. But just to do it, just because I thought it would be what the workshop would ask me to do, anyway, I included some really vivid descriptions of the setting. Sensory imagery. Movement, too. I had my narrator sitting down on the front steps of his porch folding autumn leaves and then piling them on top of the step below him as he has an argument with his wife.
This was a sort of snide addition on my part. I thought everybody would hate it, and I would think, “a-ha! But this is the very sort of thing you would have told me to include!” In fact, everybody loved it. The sensory imagery makes you feel like you’re really there; and this small, seemingly insignificant action tells so much about this narrator; and when the wife sits down on the step below him and she knocks the leaves onto the floor, it says so much about their relationship without the narrator having to say anything but what happened.
I went back and looked at the scene afterwards and realized that they were right. This was a great, telling moment. It got us out of the narrator’s head and let the reader be involved in the story, rather than just having the apathetic narrator, whose voice I still loved but who was standing in front of the reader’s line of sight, tell the story to the reader. And it had come about entirely by accident, by my trying to prove how pointless this sort of detail was.
I learned a lot during that first semester, and while it was, as I’ve said before, the hardest semester I’ve ever had to endure, it was also the most educational. Once I realized that I wasn’t brilliant and that I actually had to work at it and learn and grow and develop, I began to do just that. And now, as I’m entering the last stretch of the program here at UAF, I feel like I’m a much better writer than I was before I came, and I can only just keep getting better.
Sunday, September 14, 2008
The Old Stuff and the New
My first semester of Workshop at UAF could reasonably be described as a disaster. Fairly early on, I submitted something that should not have been submitted, spent an hour of class time having my writing abilities attacked from every angle, and then drove home close to tears, seriously considering giving up my quest to be a writer. I just wasn’t any good, I realized.
They didn’t like the plot. Didn’t think the characters were interesting. Didn’t like the metafictional technique I had tried to employ. Thought it was riddled with clichés and pointless. By the end of the session, the discussion degenerated into complaining about the sentence structure (not enough variety, bland and boring to read . . .) and one woman came damn close to saying that anyone who would write something like this couldn’t possibly be a good writer.
For the rest of the semester I felt anxious and scared every time I had to submit something. I stopped reading the written comments by all but the teacher and two or three other people who I knew made an effort to say nice things on top of pointing out the problems, and who, when they pointed out problems, didn’t try to turn it into a story they would have written or suggest that these are mistakes only a very bad writer would make.
And I didn’t submit a single thing for publication the entire semester.
The problem was that I had turned in to Workshop something that I had written as an undergrad, a full year before. It was a piece that I thought was pretty much ready already. I’ve since noticed similar problems in other people’s work. There will be a story that seems of much lower quality than the other stuff that writer submits, and you find out later that this is one he or she wrote several years before. I would almost say that when you start grad school, you should write 100% new stuff and accept that everything you wrote before, or at least most of it, was just practice. But at least dramatically revise anything old that you do feel has potential (and I mean preferably rewrite the entire thing from page one).
You grow as a writer extremely quickly in an intensive grad school setting, and it doesn’t take long for your skills to far surpass wherever you were at before you started the program. This is a good thing. But it also means that you have to accept that not everything you ever wrote is good. I’ve heard that it generally takes something like 100,000 words of crap before anyone can write anything publishable and while a number like that (my own approximation of an approximation) isn’t exact, certainly not for each different individual, I think it’s true that you get better and better as you go and most people don’t start getting really good until they begin to seriously devote themselves to honing their craft.
One way that a lot of people do that is by joining an MFA program. Yes, you have to be at a high enough level that the people reviewing applications see your potential for you to get into an MFA program to begin with. But still, you’ll most likely become such a better writer so fast that most anything you had written previously won’t be a good representation of what you do. And if you’re dusting off stuff that you wrote a year before just to have something to turn in, you’re not really getting one of the major benefits of Workshop: motivation to always be writing new stuff.
They didn’t like the plot. Didn’t think the characters were interesting. Didn’t like the metafictional technique I had tried to employ. Thought it was riddled with clichés and pointless. By the end of the session, the discussion degenerated into complaining about the sentence structure (not enough variety, bland and boring to read . . .) and one woman came damn close to saying that anyone who would write something like this couldn’t possibly be a good writer.
For the rest of the semester I felt anxious and scared every time I had to submit something. I stopped reading the written comments by all but the teacher and two or three other people who I knew made an effort to say nice things on top of pointing out the problems, and who, when they pointed out problems, didn’t try to turn it into a story they would have written or suggest that these are mistakes only a very bad writer would make.
And I didn’t submit a single thing for publication the entire semester.
The problem was that I had turned in to Workshop something that I had written as an undergrad, a full year before. It was a piece that I thought was pretty much ready already. I’ve since noticed similar problems in other people’s work. There will be a story that seems of much lower quality than the other stuff that writer submits, and you find out later that this is one he or she wrote several years before. I would almost say that when you start grad school, you should write 100% new stuff and accept that everything you wrote before, or at least most of it, was just practice. But at least dramatically revise anything old that you do feel has potential (and I mean preferably rewrite the entire thing from page one).
You grow as a writer extremely quickly in an intensive grad school setting, and it doesn’t take long for your skills to far surpass wherever you were at before you started the program. This is a good thing. But it also means that you have to accept that not everything you ever wrote is good. I’ve heard that it generally takes something like 100,000 words of crap before anyone can write anything publishable and while a number like that (my own approximation of an approximation) isn’t exact, certainly not for each different individual, I think it’s true that you get better and better as you go and most people don’t start getting really good until they begin to seriously devote themselves to honing their craft.
One way that a lot of people do that is by joining an MFA program. Yes, you have to be at a high enough level that the people reviewing applications see your potential for you to get into an MFA program to begin with. But still, you’ll most likely become such a better writer so fast that most anything you had written previously won’t be a good representation of what you do. And if you’re dusting off stuff that you wrote a year before just to have something to turn in, you’re not really getting one of the major benefits of Workshop: motivation to always be writing new stuff.
Sunday, August 31, 2008
The Short Stuff
With the new semester starting in the next week (and having already turned in my first workshop submission to be discussed on day one) I’ve been thinking again about one of the major benefits you get from workshop: that strong hard push to work on short pieces, even while you might be totally involved in, say, a novel or some other big project.
Now, it’s important to point out that a lot of people bring novel chapters in to workshop, and that’s fine if it works for them. Personally, I only bring in a chapter of a novel if I’m trying to make that chapter work as a stand alone short story. I just think it’s too hard, as the reader, to give good feedback when you’re only reading a small portion of a larger work, and it’s too hard, as the writer, to get much out of feedback from a person who doesn’t know the whole story.
I’m at a point right now where I’m pretty preoccupied with book length works. I’ve got my thesis, which, once I get some feedback from my committee members, I’m going to be working on more revisions of soon. There’s my new novel, which I’m pretty much totally engaged in right now as I work on the first draft. And there are a couple of different children’s book projects, too, which I’m just doing as a fun side project but I’m having a really good time working on. This summer I’ve had to kind of force myself to keep up with my short stories, in the midst of all these other larger projects.
So I’m excited about going back into a workshop environment. Workshop takes the choice out of my hands. I feel more comfortable, now, setting personal goals that revolve mostly, or perhaps even entirely, around my book length projects because workshop will force me to spend time, as well, on short stories. I can’t get away with not working on those because it’s homework. And I’ll be in a position where I’ll be kind of refocusing my attention on short stories, too, because I’ll have people reading and responding to my short pieces. I’ll be looking at my stories in a new light and they’ll be pushed back to the front of my mind. I’ll be excited, again, to go back and tackle them.
And I think it’s really important, when you’re in the early stages of a writing career, to work on those shorter works, whether you’re finding ways to break up and publish small portions of a novel or what. This is true, I think, for all creative writers. You might, for example, be looking at your poems as a book length collection, but you should probably, also, think of them as independent sets that you can submit and try to publish in smaller chunks. I’m not saying don’t work on the book length projects, too; I intend to continue working on mine. But it’s my understanding that it’s extremely difficult to get an agent or a publisher interested in a book if you can’t show them that you’ve had several smaller pieces published, first. And workshop helps you keep that focus on the smaller works, the steps you have to take now, to get to that later stage where you can actually get that full book published.
Now, it’s important to point out that a lot of people bring novel chapters in to workshop, and that’s fine if it works for them. Personally, I only bring in a chapter of a novel if I’m trying to make that chapter work as a stand alone short story. I just think it’s too hard, as the reader, to give good feedback when you’re only reading a small portion of a larger work, and it’s too hard, as the writer, to get much out of feedback from a person who doesn’t know the whole story.
I’m at a point right now where I’m pretty preoccupied with book length works. I’ve got my thesis, which, once I get some feedback from my committee members, I’m going to be working on more revisions of soon. There’s my new novel, which I’m pretty much totally engaged in right now as I work on the first draft. And there are a couple of different children’s book projects, too, which I’m just doing as a fun side project but I’m having a really good time working on. This summer I’ve had to kind of force myself to keep up with my short stories, in the midst of all these other larger projects.
So I’m excited about going back into a workshop environment. Workshop takes the choice out of my hands. I feel more comfortable, now, setting personal goals that revolve mostly, or perhaps even entirely, around my book length projects because workshop will force me to spend time, as well, on short stories. I can’t get away with not working on those because it’s homework. And I’ll be in a position where I’ll be kind of refocusing my attention on short stories, too, because I’ll have people reading and responding to my short pieces. I’ll be looking at my stories in a new light and they’ll be pushed back to the front of my mind. I’ll be excited, again, to go back and tackle them.
And I think it’s really important, when you’re in the early stages of a writing career, to work on those shorter works, whether you’re finding ways to break up and publish small portions of a novel or what. This is true, I think, for all creative writers. You might, for example, be looking at your poems as a book length collection, but you should probably, also, think of them as independent sets that you can submit and try to publish in smaller chunks. I’m not saying don’t work on the book length projects, too; I intend to continue working on mine. But it’s my understanding that it’s extremely difficult to get an agent or a publisher interested in a book if you can’t show them that you’ve had several smaller pieces published, first. And workshop helps you keep that focus on the smaller works, the steps you have to take now, to get to that later stage where you can actually get that full book published.
Sunday, July 27, 2008
Workshop Benefits
The fact that graduate level workshops don’t give you the kind of encouragement that undergrad workshops do (and in my case, sometimes discourage me so much that I ask myself over and over again on the drive home whether or not I’m just wasting everybody’s time with my unattainable dreams of writing) is actually a good thing. It’s actually the very reason that graduate level workshops are so much more useful.
There are a few reasons why:
First, when you know that people aren’t going to be impressed at all with your sentence level skill, that is how poetic you can write, how beautifully crafted your sentences are, how much meaning you can pack into a tight space, when you know none of that will matter to anybody because they can all do that, too, you put out a whole new level of effort into actually making the stories, the plots, the significance of it all, the clarity and cleverness of what you’re doing, as good as possible.
For me, this was a completely new stage of writing. I used to just kind of think, well everything that I write is well written, therefore it’s all good. But in actuality, LOTS of people can write well, on the sentence level, but not everybody can write something worth reading and it’s something that you really have to work on and practice.
Consider, too, that while nobody is going to be impressed with your writing abilities, they will notice and dwell on all sorts of problems that you probably could have noticed on your own, if you had taken the time to look. So you push yourself to revise and revise and revise some more before you bring your stuff in to workshop. After all, you don’t want to waste your chance to have a bunch of people with different tastes and skill levels to look at your stuff and give you honest feedback. If you bring something in that has problems you, yourself, are fully aware of the entire class time will likely be spent discussing those problems and you will have gained nothing from the experience.
This is something that I know not everybody agrees on. Some people do prefer to bring in first drafts to workshop and I have to admit, I’ve done it, too (last semester almost everything I brought in was a first draft because I had been spending most of my time prior to that preparing for the Comps exam and revising my thesis). But generally, I like to work on my stories until I reach a point where I can’t see, anymore, what else needs to be done before I bring them in to workshop, and that’s definitely not something I worried about when I was an undergrad because I knew that no matter what I brought in I would rarely get any actual feedback, mostly just compliments.
The third and possibly most important reason why graduate level workshops are more useful is that they give you a chance to see just how good your competition is. Chances are, not all of your fellow students’ writing will be to your taste, you probably wouldn’t read all of their stuff for fun on a Sunday night, but you do have to admit that they are good at whatever it is that they do. This is a sharp contrast to what you probably experienced as an undergrad, where you may have been the only one in the class who actually wanted to be a writer. This is important (I would argue it’s perhaps THE MOST IMPORTANT stage you must go through to be able to reach any level of success as a writer) because if you don’t even get to that point where you realize that A) you are not some kind of literary genius, and B) the only way you can get your stuff picked over all these other peoples’ really good stuff is by really working at it, revising exhaustively, and really paying attention when somebody else reads what you wrote and points out problems with it.
I'll get into more detail in later posts about some of my specific workshop experiences but I would definitely say as much as we all like to have our egos stroked, this other way of doing workshop, the way where people take it as a given that you're good and instead try to help you make your stuff better, is better, in the end. It's the only way, really, that will help you move into those more advanced levels of writing skill.
There are a few reasons why:
First, when you know that people aren’t going to be impressed at all with your sentence level skill, that is how poetic you can write, how beautifully crafted your sentences are, how much meaning you can pack into a tight space, when you know none of that will matter to anybody because they can all do that, too, you put out a whole new level of effort into actually making the stories, the plots, the significance of it all, the clarity and cleverness of what you’re doing, as good as possible.
For me, this was a completely new stage of writing. I used to just kind of think, well everything that I write is well written, therefore it’s all good. But in actuality, LOTS of people can write well, on the sentence level, but not everybody can write something worth reading and it’s something that you really have to work on and practice.
Consider, too, that while nobody is going to be impressed with your writing abilities, they will notice and dwell on all sorts of problems that you probably could have noticed on your own, if you had taken the time to look. So you push yourself to revise and revise and revise some more before you bring your stuff in to workshop. After all, you don’t want to waste your chance to have a bunch of people with different tastes and skill levels to look at your stuff and give you honest feedback. If you bring something in that has problems you, yourself, are fully aware of the entire class time will likely be spent discussing those problems and you will have gained nothing from the experience.
This is something that I know not everybody agrees on. Some people do prefer to bring in first drafts to workshop and I have to admit, I’ve done it, too (last semester almost everything I brought in was a first draft because I had been spending most of my time prior to that preparing for the Comps exam and revising my thesis). But generally, I like to work on my stories until I reach a point where I can’t see, anymore, what else needs to be done before I bring them in to workshop, and that’s definitely not something I worried about when I was an undergrad because I knew that no matter what I brought in I would rarely get any actual feedback, mostly just compliments.
The third and possibly most important reason why graduate level workshops are more useful is that they give you a chance to see just how good your competition is. Chances are, not all of your fellow students’ writing will be to your taste, you probably wouldn’t read all of their stuff for fun on a Sunday night, but you do have to admit that they are good at whatever it is that they do. This is a sharp contrast to what you probably experienced as an undergrad, where you may have been the only one in the class who actually wanted to be a writer. This is important (I would argue it’s perhaps THE MOST IMPORTANT stage you must go through to be able to reach any level of success as a writer) because if you don’t even get to that point where you realize that A) you are not some kind of literary genius, and B) the only way you can get your stuff picked over all these other peoples’ really good stuff is by really working at it, revising exhaustively, and really paying attention when somebody else reads what you wrote and points out problems with it.
I'll get into more detail in later posts about some of my specific workshop experiences but I would definitely say as much as we all like to have our egos stroked, this other way of doing workshop, the way where people take it as a given that you're good and instead try to help you make your stuff better, is better, in the end. It's the only way, really, that will help you move into those more advanced levels of writing skill.
Subscribe to:
Posts (Atom)