Showing posts with label writer's workshop. Show all posts
Showing posts with label writer's workshop. Show all posts

Saturday, August 23, 2008

OryCon 30 Writer's Workshop


Don't forget to submit!  The workshop deadline is sneaking up!

I've got my submission all put together.  I just have to wait until email starts to behave again.  For some reason the server is being a pill.

Update:  Got a nice rejection.  Sent that baby right back out.  We're at 43 subs and 31 rejections.  Keep going, INKers!

Sunday, May 25, 2008

Storm

Hey, what did you all think of the storm that blew over us yesterday evening?  It went right over our house.  The hail tore the plants to heck and the lightning was intense.  Rory and I watched it come in under the deck gazebo and then came in when it started to get dangerously close (as in wow, that lightning hit right there close.)  A few minutes later the hail started, and we had sheets of rain, lightning blasting directly overhead and terrified dogs.  Everything smelled like we were in the midst of a logging clearcut operation.  We brought all the dogs in (after a little drama with Finn) and gave them all baths and they got to lounge about the house until about 2am.

I thought, gee, Carole must be writing on a great story idea even as we speak.

I sent off for info about the Dean Wesley Smith/Kristine Kathryn Rusch and guests seminars in Lincoln City.  I've heard nothing but great things about these seminars.  Yes, they're expensive, but not when you consider that you have a place to sleep on the coast (woot!) and instructional time with masters of the industry.  If I could scrape together the funds I'd be all over the master's course held in spring 2009, but I think that's out of my reach financially, even if it was possible for me to get in based on my writing.  I think I'm better off staying out of debt by taking the novel and the short story courses, with the accompanying less time off of work factors (assuming I'm still working retail then.)  

My writer's demon is bouncing up and down trying to get my attention and squeaking, "that's what credit cards are for, dope!  C'mon, let's go!  You've always wanted to!"  Yes, well, I've always wanted a horse, too, but you don't see one grazing out on the acreage, do you?  "But this might be just what Masks needs to become saleable!  You can pay off the credit card with your advance!"  You know, that--I don't even know where to start.  I don't think that's even worth a response.  "What?  Aw, man!  Please?"

Pardon me while I stuff him back into whatever dimension he slipped out of.  

Thanks for the heads-up from our friend, Jeff!  And you can totally snag a ride with me to the coast, assuming I can get into the class.  Just get yer kilted butt up here to the Pac NW and we'll head out toward the sunset.  Road trip!

Monday, November 19, 2007

On Critiquing

Orycon was a great success, for me anyway. I learned a great deal on several aspects of writing, but I thought over here I'd share my notes on critique groups, as I attended two or three sessions on the subject:

On Writer's Workshops and Critique Groups (one with David Levine, Rob Vagle, John Burridge, and Nina Kiriki Hoffman; a second with Irene Radford, Bruce Taylor, Jayel Gibson, David Goldman, and Stephen Stanley; a third with Richard Lovett, David Levine, Michele Avanti, and Kami Miller):
* Critiquing and hearing critiques can triangulate how you are reading a story. Does your interpretation match the other writers? What might you be getting that they aren't and why? What are you missing that they are seeing and why? (Thank you, David)
* Critique groups are great as producing mechanisms, setting external deadlines for the writers.
* "Ditto" is a useful tool when group commenting, so that the same issue isn't brought up again and again. As in "Ditto Kami about the tension in the first scene." Free to discuss new issues and benefits instead.
* Instead on manuscript format, either for electronic submission or hard-copy submission.
* Reading aloud can be beneficial to catching errors, but beware that a good reader can bring a problematic piece to life, while a bad reader could sink a good piece. Better: have someone not the writer read the piece aloud. Gives the writer a chance to judge body language and immediate response to the piece (gasps, chuckles, boredom).
* The audition process for incoming members if useful on both sides; gives the writer and the group a chance to feel each other out.
* The Clarion style of group critiques is tried and true, with the author remaining silent while the group takes turns with their own comments, but beware that the person who begins the critique sets the tone.
* Individual critiques avoid feeding off what others are saying, but limit the brainstorming possibilities that a group can offer.
* A writer writes in a vacuum; reader response is useful to judge how the story is going.
* There is a sharp difference between the 'I didn't like it' reaction and the 'I didn't like it because . . .' response.
* Knowing the predilections of the readers is useful: do they have biases against certain stories, are they more knowledgeable in a subject than an average reader would be, or less so.
* Writing to please the critique group will grind the edges off your story. Avoid using their foreseen reactions as your internal editor.
* There is such thing as overshooting a revision based on a critique that can wreck the heart of the story. Always keep in mind why you wrote the piece to begin with.
* Always deliver an honest critique with compassion, whether to an experience writer or to a novice. Honesty counts, and so does compassion.

There are notes on other subject on my personal blog. I also have several thoughts to throw at the INK group when we next meet for the Orycon Debriefing (nice phrase, Carole). And I have a new goal for myself based on not only the above notes, but my own critiquing experiences during the con. All of it will go a long way to improving not only how I write, but I how I critique, and I'm sure you will all thank me for that.

I can't wait for the debriefing! But now, I have to get back to our regularly schedule Nano. My novel is lonely after two days of sitting forgotten in a folder. Well, not completely forgotten.

Wednesday, September 26, 2007

I hate my reader thiiiiiiis much

Exploder has been crashing repeatedly when I try to post, and iCab gets into a loop of continuous info dump so that the average typing speed becomes about one letter every 2-3 seconds. Hence the infrequent posting. I'm expecting this to crash at any moment.

Or maybe not.

Anyway, OryCon 29 is coming up and as writer's workshop coordinator (or workshop fool, which may be a more accurate description) I've had the opportunity to watch the submission process from eager beginning to its black demise. Here are some observations that may be helpful, or may be simply suitable to inspire a sense of professional superiority in pro-minded individuals.

"I was terribly disappointed. I got almost no comments on my content and about ten pages of formatting information. Since then I've published in (X and X) magazines."
Gee, I was at that critique and that's not how I remember it, but who am I? This seems to be a classic case of not listening. This person may very well be turning out good prose, hence the publishing credits (which were both paying markets, btw) however it's really hard to go from good to amazing when you can't listen to comments. The hyperbole doesn't help--she didn't get even ten pages total of comments much less ten on formatting. There was plenty of room for improvement in the manuscript, including the formatting. But more on formatting later ...
Comments from anyone, whether they're a professional, fellow writer trying to break into the business, or helpful buddy are always a mixed bag. A great resume' does not make a great critiquer, unfortunately. Still, if that person wasn't impressed (and maybe couldn't say much more than stuff about your formatting) then something is falling flat. If you can't see it for yourself, then try to get a second and third and fourth opinion. If those other opinions are all about the excited enthusiasm and spewing about the perfection of your vision, then feel free to pat yourself on the back for writing the next international classic (or for finding the perfect audience or providing sufficient bribery or blackmail for this result.) It stinks to get a poor critique, but you gotta get what you can from it. Poor critiques require more advanced listening, reading between the lines, and before you decide that it was totally worthless (and some of them are) you need to take a healthy dose of objectivity. Sometimes you can do that all by yourself, but be careful. It's better to get another reader involved, hopefully one with a good skill set, and get at the truth that way.

Dear Cover Letter Reader--I have no idea what to say so I'll take a guess without looking at the big picture.
What's a cover letter's job? Sometimes it's easier to figure that out by looking at your entire submission package in the context of who is getting it. I'll use a writer's workshop novel package as an example. The package consists of a cover letter, a 500 word synopsis and a 7500 word chunk of novel. Logically we can deduce that the cover letter is an introduction. But then what? A key is to try not to double up on information. Another key is to not include extraneous information.
A good cover letter will include who you are, contact information, and date. Unearthing manuscripts from a haphazardly stacked pile is an exercise in surprises--giving the editor a chance to place your manuscript should it become misplaced is key.
A good cover letter will include pertinent information about your experience. Editors (or in this case pros reading your manuscript) want to know where you're at in your career. They want to know if you're just starting out, if you're in it for the long haul, get a sense of how prolific you might be in the case of novels (it's not inappropriate to mention if you've got other works in the works and what stage they're at) and if you've taken any major steps for self-improvement (degrees, Clarion, etc.) Be sensitive to the pro's pov as much as you can. They get no real information from 'I've been writing since I've been three years old.' Well, me too. I learned to write my name at three. They don't really get a sense of your quality or stick-with-it if you say you started writing seriously in high school, or in college. So what are they looking for? I majored in journalism (or English) in college. I have published work in non-paying markets from 1985 onward. If you're submitting for publication you may want to keep out information about the high school poetry chapbook unless you're close to high school age but if you're submitting to a workshop you have more freedom since you're not trying to sell your work. In a workshop you're trying to give the pro perspective so they can critique in context. For example, looking at it from the other side, if I'm critiquing something I want to know if I can say 'you slipped into passive voice during this action scene which slowed it down' and let it go or whether I need to explain what passive voice is. I'd like to know if I can boldly say, "this character was so unsympathetic I was ready to stop reading by page three" or if I should gentle it down--not leave out information, but get more technical and not assume that the writer is going to understand that I'm having a specific issue with the story, not with the writer or the prose or their worthiness to publish. With advanced writers you can use shorthand without coming across as brutal, taking a five minute explanation about a character's flaws, actions and inner dialogue and how that made me feel like they were a worthless whiner and pare it down to "this character whined too much. I wanted more protagging."
In short, a cover letter needs to give useful information, and in the case of a professional submission to a paying market, not too much information about amateurish stuff so you don't come across as an amateur. It doesn't need a description of the plot (handled in the synopsis) or a hook (handled on the first page of your manuscript) or how many margaritas you drank as research for this piece. Shorter is better, but include all the necessary parts.

Now, back to "...ten pages about my formatting."
The last time I helped someone with their formatting it took six pages of explanation. I kid you not. Not on how to do it--that was clearly outlined on the submission guidelines along with a .pdf example. But on how to fix the piece of I-don't-know-what-they-were-thinking workmanship they handed in as their submission. I kid you not! It seems that even the extensive precautions I took didn't prevent me from having to deal with very badly formatted manuscripts.
And why should an editor care? It's all about the content, right?
Readability. An editor's eyes are precious. They've chosen fonts and line spacing to accommodate their vision and not following those guidelines is a slap in the face. It says I care more about having this come in under ten pages by using ten point font than your vision.
Space to write. An editor needs room to write in comments, when they're inspired to do so (which is rare) and both the editor and typesetter, should you be so lucky as to have your work accepted, need scribbling room for editing and typesetting stuff.
Ability to estimate. An editor prefers to see how many pages there are and have a good idea of how much room it will take up in the magazine. They do this through word count as well, but word count doesn't always accurately measure room on a magazine page or thickness of the book because writing styles and word choices differ. The page length is another tool they like to use, and that's useless or misleading if you've used 1.5 line spacing or a font that they're not used to estimating with, for example.
Certainty of placement. An editor needs to know absolutely where a paragraph starts and ends, where there's a scene break, a new chapter, etc. without having to think. The problem with email-style paragraphing with no indentation and a double return after paragraphs is that it looks like stream-of-consciousness meets a monstrosity of scene breaks every paragraph (but missing the # sign that helps them determine that yes, this is a scene break.) Other style changes are even worse. Whenever a writer breaks out of standard format the editor has to adapt to that style, and I'm going to guarantee right now that the editor doesn't want to adapt. You can argue if you want that everyone is used to reading such and such a style. Personally, I prefer not to argue with someone I'm trying to sell work to, or someone I'm trying to gain a good opinion from.

Having done this job for several years, I sometimes wish that everyone in INK could take on this job for at least a year, preferably two, to help put the whole professional submission thing into perspective for them. I've often heard editors wish aloud that writers would take on an editorial job or slush pile reading, even if it's informally and just a short while. This is why. It's the experience of seeing other people's mistakes that help you figure out what to do with your submission, much more than being told what to do and what not to do.

Any takers?