This post is a follow-up to my last post because that one was published unfinished. I’m laying the blame on SUE for that mistake (and before you smack me for not taking personal responsibility—SUE stands for stupid user error.)
For those of you unfortunate people who don’t have a WordPress blog, I’ll explain that WP takes precautions to make it hard for such an error to occur: the Preview and Save Draft buttons are well above the Publish button and are simple black text on white buttons, while the Publish button is set off in a colored bar and is brightly colored itself. So, yeah, it takes SUE to click the Publish button instead of the Save Draft button.
I had already published a post 12 hours earlier and had intended to post my rant today, Monday. I wasn’t even aware I had prematurely published that rant until I received notice that someone had commented on it. And that reader (I thought) had misunderstood my intent, so I quickly unapproved her comment and sent her an email explaining the problem. Then I re-read and made a couple edits to the original post before too many people read it … of course, those of you who subscribe by reader or email saw the unedited original. (I later added the disclaimer at the top of it.)
Besides my premature original post not making it clear that I like Elizabeth Strout’s opening paragraph, I also intended to make clear that I understand that for some genres, a paragraph like hers would be the kiss of death. If your story is action-driven, do not write an opening paragraph like Strout’s.
Another mistake I’ve made is in reading too many agent blogs and how-to manuals directed at other genres. Very confusing!
The intent of my post was a slap to my own face for mistakenly trying to apply rules for those other genres to my writing. This misunderstanding resulted in my opening undergoing several revisions, until I felt it no longer represented the tone of the novel.
Anyway, my last post was a cautionary tale: Know thy genre and be steadfast and true to it.
[tweetmeme source=”cassidylewis” only_single=false]