CS Inman (aka Sän) has a surprisingly good synopsis up to read. Basically everyone, everywhere, hates writing their novel synopsis, so I’m automatically impressed by anyone that manages to write a synopses that’s entertaining and informative.

This even applies to the victims participants in Joshua Palmatier’s synopsis day. Now the synopses listed here were “successful” synopses, meaning that they were for novels that eventually sold. But even so, I found most of them dull, incomprehensible, or overly long. Probably the easiest one to read was Mike Brotherton’s synopsis of Star Dragon. That one suffered from the opposite problem: it was fast-paced and easy to follow, but the writing style itself felt amateurish. (I have no idea if that applies to the book itself, which I haven’t read.)

Reading all those pro synopses made me think that maybe the synopsis was free to be long and boring, which was good because my synopsis was long and boring. It was 2500 words of dull. It was a plodding, interminable death-march through a dozen names and a series of irrelevant places.

When I set out to pare it down this week, the first pass got it down to 1250 words and something of a respectable hook.Sän and Eva have both helped me further pare it down and spruce it up, so the final draft will be under 1,000 words, and hopefully will actually help sell the novel.

I’ve started up the novel that was giving me so much trouble, again. And I did what I originally said I wasn’t going to do: I’m starting from the top, and rewriting all of the chapters that have the new POV. This is, fortunately, less that I was originally afraid of, since most of the stuff that’s in the other POV will still work, though there’s some things to be moved around.

I don’t know, though. There’s a lot of cut-and-past, and a lot of scenes being rewritten with the same dialogue but different characters. I suspect that it’s turning out a mess, though that’s what first drafts are for, nu-i asa?

Sän has an interesting post about horror up at his blog. I would have commented on it earlier except, you know, I only meet Sän a few days ago.

His distinction between smart horror and dumb horror reminds me of something I got from Orson Scott Card a long time ago. This was from one of his writing books (I forget which one), and he suggested that there are three kinds of fear:

  1. Dread, which is the feeling when you know something is wrong but you don’t yet know what. Dread is the anticipation of Terror to come.
  2. Terror, which is the heart-pounding, adrenaline-fueled rush when you see the monster and (vicariously) experience immediate danger
  3. Horror, which is the revulsion and discomfort we experience in the aftermath of seeing something, er, horrible.

The strongest of these, he says, is Dread, but it’s also the hardest to sustain. Slasher films tend to deal almost entirely in Horror with snippets of Terror. OTOH, a really excellent thriller like Alien or The Ring manages to keep you in Dread for most of the movie. (In Alien, consider how rarely the monster is actually on screen, and how much time is instead spent creeping around in the shadows wondering where the monster is.)

Interestingly, Sän’s categories are almost entirely orthogonal to Card’s. You can do dumb Dread and smart Horror–in fact, some of the best stories I’ve read are best classified as smart Horror.

The last commenter mentions the Silent Hill games. Silent Hill 2 is the only game I’ve stopped playing because it was too frightening–and in gets this power almost entirely from Dread. The monsters in Silent Hill are not very frightening and you’re never in very much danger, so the Terror is pretty mild. There’s plenty of gore in some areas to provoke Horror, but they’re fairly rare. Rather, through a brilliant use of music, pacing, and lighting, the game creates a powerful atmosphere of Dread. So powerful that the game became no fun, because I dreaded putting the disk in.