COMMENTS WELCOME

If you've prowled around this site, you will have noticed there are no comments following any of the posts [as of June 21, 2014].

I'm not blocking comments (although I did check the settings a year or so ago and found it was set so that only "members of the blog" were allowed to comment—I fixed that). The reason there are no comments is because nobody has ever commented.

I have it set for me to moderate comments. Your text will come to me as an email and I have the option of posting it or not.

I know it's actually set this way because the other day I got my first comment. Yippie!

Oh, wait.

There was something about it that made me suspicious. The guy was listed as "anonymous" but ended his comment with a link to a Website. Something about a typing service.

That worried me because I couldn't see why you would log in as anonymous and then send me to your Website—where, presumably, your anonymity would very quickly fall away.

Unless your Website is also anonymous for some reason. For instance, so folks won't know who to blame when the malware kicks in.

So I did some snooping.

I found that this fellow posts on a lot of sites, commenting on the blog in glowing but rather vague terms. And each time giving the link to his Website.

In fact, I noticed other comments on these pages have laudatory but vaguely worded information—and a link to some other Website.

On one page, where there was no actual article or blog post visible, all the comments suggested the content was tip-top and very useful and the guy will be sure to bookmark the page for future perusal.

And all the comments ended with a link.

On one page, nearly all the links went to some sort of "removal" service. British, I think.

(Dead body cleanup? Was Mr. Wolf involved?)

One comment used the same text as the one I received, but the link went to a another Website.

The fellow who commented on my blog used a variety of names on other sites, all with different messages, but the same link.

In fact, I'm guessing all these bogus commenters have subscribed to a service that promises to bandy their Website links about the Web—by making fake comments of unspecific praise.

Either all those sites are setup to have all comments go straight through to print, or the moderator fell for the praise and let them pass.

Of course, it does benefit the sites where these messages appear. Legitimate readers are treated to comments that praise the content or the page design. Might even encourage the average Web surfer to form a favorable opinion of the site.

As for this blog, I actually do welcome comments.

But to get through the vetting process, the comment needs to be specific enough to make me think the blog post it's attached to had been read by the author of the comment.

If your praise is suspiciously vague, please don't end with a link to your Website.

Makes me antsy.

On the other hand, if you make a real comment and want to end with a link to your own blog, go for it.

THE BLACK BOX, AT LAST

My science-fiction novel, THE BLACK BOX, went live today, finally.

Since we last met, I went through it twice. Made over two hundred changes in the first pass, including the fixing of two actual errors.

The second pass generated about a third as many changes.

In between passes I targeted dashes (again), reducing their number from 86 to 20. I like writing in dashes, but it's a habit I really need to break. They just don't work well in ebooks. And they make the text appear a bit hysterical and gushy.

I also targeted ellipses, cutting them to the bone. Those guys are often even worse in appearance in ebooks, depending on the font size chosen by the almighty reader. If your characters use 'em a lot, they look tentative and a bit untrustworthy. (If that's what you're going for, fine.)

During the (most recent) final pass I noticed a pattern in my writing I needed to address. A character would ask a question of another, then "before he could answer, [this new event took place]." Some version of that sentence occurred a dozen times in 95K words. I revised all but three or four of them.

(I get hung up introducing unexpected action in a scene. I keep wanting to write something like: "And all of a sudden, the car blew up!" If I just wrote "The car blew up," that would certainly qualify as a sudden event, at least to the unsuspecting reader. I really shouldn't have to SAY the event occurred suddenly. Seems baldly stated, though, without a few words of introduction. It's just one more thing I have to work on.)

I added some images to the book: signs and lists and protest banners, etc. I think it's fun to do, gives the book some visual variety, and doesn't cost much. I used GIMP, indexed the image to eight colors, and saved it as a gif to minimize the file sizes.

The book (with its title page image) was right on the brink of tipping from seven to eight cents delivery fee. The images I added bumped it all the way, but not by much. Turns out, I had already done something else that put me squarely in the eight cent category.

The cover.

I tried using a cut-down cover to save money, but I found it looked skimpy in the Fire HD 8.9" Kindle. (According to Previewer.) Using the full sized display cover (1600 by 2500) got me a full screen cover image (from margin to margin) in every Kindle out there...and maybe some future versions, too. (In the HD 8.9" the image increased 47% when I went with the display cover file.)

I know handing KindleGen a big-ass image file (mine is 357,286 bytes) invites it to chop it down to 127K. I just think it does a fine job. But yes, doing it this way MAY bump you up a penny in delivery charges. (If you're already just over the half cent point, going this way won't cost you any more money.)

My next project will be the second book in the Trevor Blake middle-grade chapter-book series. (The first was THE EXPLODING WIZARD'S RIGHT-HAND BOY.)

Stay tuned.

REWRITES AND STUFF

First, I want to announce my ebook KINDLE CREATION FOR CONTROL FREAKS will be free for five days starting the Friday (the 6th).

As is typical for me (lately), I've clumped the full five days in one pile at the end of the book's Select period. It's easily the most inefficient method of giveaway—assuming you want to maximize the resulting downloads.

(Best would be one or two day periods, since the great majority of downloads occur then.)

The only excuse I have is that I'm buried beneath the rewrite (slash proof) of something called THE BLACK BOX. It's been a week away from going up on Amazon for the last month and half. And just two weeks away from going up for about two months before that.

(When you're so close to the end, you tend to put off other tasks—like writing posts for your blog.)

So: What the hell is my problem? Why can't I finish the book?

Easy: I can't stop making changes!

By now I've finished finding actual errors. Mostly I just revise what I have now (at last) discovered to be clumsy sentence construction. Or I find out some fast change from last time duplicated a word already in use in the same paragraph (or in a problematically "too near" paragraph). I hate unconscious repetition, and sometime even the sound of a word can trigger my reaction.

(Some of this super-sensitivity is idiotic, of course. Often, common words can be left alone to repeat as needed. Around the turn of the last century budding writers became obsessed with finding other words they could use instead of "said" when tagging dialogue. Whole chapters of How to Write books were set aside to list the alternates (uttered, pronounced, articulated, responded, averred, declaimed, gurgled, trilled, chortled, and so forth). By the second half of the 20th Century, writers came to believe the word "said" carries no particular weight with readers, that they pay no more attention to it than to the word "the." Exotic tags are only used now in a deliberate exaggeration of some character's bizarre style.)

Sometimes, between readings (that is, at the end of the most recent "final" reading), I wander around the house telling myself the story of the novel. I do this out loud so I can listen to the words and object to logical problems.

Just one session like this can lead to pages of notes—even at an advanced stage of the writing. Sometimes rather fundamental problems pop up.

Embarrassing? Oh, you bet! But better to embarrass yourself now in private than in "print" in front of strangers later.

What you dread finding—but must still be open to—is a logical flaw that seriously undermines the very CONCEPT of your book. That, of course, can be crippling. Or it can be a challenge that leads to excellent changes (and lots more excellent delays).

For me, the scary part is that new ideas keep coming that MUST be incorporated into the book. It often takes me a LONG time to see the obvious.

This is one of the pitfalls of indie publishing—the lack of outside feedback.

In the trad pub world, you have professionals to watch your back. Maybe you even have a development editor to keep you on track during the gestation of the work.

In the indie pub world, writers have to make do with beta readers. I've no experience there, but I should probably get some (readers and experience with them).

Right now, every time I read my book I make changes, but the number of those changes does tend to diminish over time. In other words, there appears to be progress, which is maybe the only thing that keeps a writer sane. (That "progress" might be an illusion, but let's not talk about that.)

What I try to do is go over and over a chapter (or even a section of a chapter) until I can find no more changes to make. Unfortunately, this doesn't guarantee all possible changes have been made. It just means things have quieted down for this part of the book. For now.

Theoretically, when you make that "final" batch of changes, you've made the section PERFECT. Which ought to mean you never have to go over it again.

So why do I find myself going over it again?

Partly, it might be a kind of OCD behavior.

After you leave the house, you begin to wonder if you locked the door. If you happen to have been preoccupied at the time (or in a hurry), that feeling can be very strong. So you go back. And find the door properly locked.

Or wide open.

Or it's locked, and your key is stuck in the lock.

Odd things can pop up when you go back to check.

With a book, you can metaphorically run back home to make sure the third floor of your "house" is in order, only to discover your second floor is MISSING.

That kind of structural problem can happen even if you plan your book out in great detail before you start writing. And if you're a "plunge-in" first-draft writer, you really have to keep your eyes open as you go forward.

I think there's another reason why "perfect" chunks of the book are compulsively reread. I've found the process of going through a long manuscript—and making LOTS of changes—can erode my confidence in those earlier "perfected" chapters.

The sheer VOLUME of new changes makes me queasy, afraid I haven't found everything I need to find. And guess what? A slow, detailed look at "finished" chapters often gives me proof I DID need to go through the damned thing again. There really ARE monsters lurking in the darkness, un-slain.

Ultimately, I'm always glad I went back and took "one last" look. And knowing THAT also undermines my confidence.

Another part of the problem is the TIME it takes to get through the book. Longer books may take five to ten days to read carefully and amend. By the time you get to the end, the sense all is well with earlier sections has simply melted away.

If the book were shorter—a novella, say—I think I'd have a much more realistic idea of its "perfection."

A short story can be revised multiple times in one day (like a single chapter in a book), so the sense you've subdued the sucker once and for all is intense. (Though it may be false.)

The rule of thumb in trad pub is this: If you and your editor go over the manuscript twice in a row without making any changes, the book is finished. For an indie pubber, one without professional help, maybe the number should be three or four.

How freaking tedious is THAT?

(Note: I don't mean three or four passes altogether. I mean three or four times in a row when you find NOTHING to change.)

So, what is the ultimate solution? Do the best you can with a "reasonable" number of rewrites and proofs (whatever's "reasonable" for you), then give yourself permission to review the book in the future, after it's been published. Say one year later. Or when you decide to put out a POD edition.

Give yourself one more FINAL reading, with permission to change ANYTHING—just not right now.

Because at some point you HAVE to get on with the next book.

Now, if you'll excuse me, I need to go read my book one more time.