Thanksgiving is probably my favorite holiday ever. Turkey isn’t the reason—after all, we can have turkey anytime of the year. But I don’t eat it very often, because I like to save it for Thanksgiving, much as I don’t make fruitcake except at Christmastime. It might be good any time, but it’s not special if it becomes routine.
The only reason I mention that is because some people don’t like turkey—or they’re vegetarians and so don’t eat it, regardless of whether or not they like it. I know someone who says his ideal Thanksgiving dinner is steak. Seriously? No way. Gimme turkey. And stuffing. And an ocean of gravy. And rutabaga! Squash! Sweet potatoes!
And then more of the same all over again for a week straight, while enjoying the memory of Thanksgiving Day with family and friends and new acquaintances, and being thankful each day for God’s abundant blessings, both physical and spiritual. Yeah. All that’s wrapped up in the taste of the turkey leftovers I’ve been eating since Thursday. Turkey makes me smile.
I don’t associate cheese with Thanksgiving, though it’s compatible with it. Here’s why I mention it:
Some months ago, I was contacted by a fellow-writer, PD Richmond, asking if I’d be willing to be interviewed on his blog. He does an interview once a week, a feature he said he calls Featured Friday, and he apologized for the cheesy name.
I told him: “I’d be happy to do an interview with you on your Featured Friday page, cheesily named or otherwise. At least you don’t call it Feta Friday. Or Immental Interviews (except I guess the cheese is spelled Emmental). Or Tilsit Talks. Sorry…
Anyway, feel free to send me your questions at your convenience. I promise to answer them without mentioning cheese.”
(I must have been overtired when I composed that email.)
His reply: “I’m a sucker for a dodgy pun! I’m now going to be very disappointed if you don’t manage to slip at least one cheese reference into your answers. (I just hope it’s a gouda one!)”
And so the cheese fest began. I answered his interview questions as requested, sent it on its way, and he scheduled it in his lineup. As it happened, it went live the day after Thanksgiving, while I was still picking turkey out of my teeth. (Only to put more into them later in the day, of course.) You can find it here.
Before sending the interview on its way, I read it carefully, and re-read it, and felt good about it. But when I saw it in its published form this week, I found several errors! Missing words and things like that. I don’t blame the good Paneer Danby (you’ll understand if you read the interview); I have no doubt he published it just the way I sent it. But I cringe when I find errors in my published work.
Meanwhile, this underscores the need for a self-published author to hire a professional editor, no matter how competent the writer. We all need fresh, unbiased eyes to look over our stuff, not only to spot typos and missing words, but structure problems, errors in word use, improbabilities in the story, and other writerly things.
Even with the top-notch critique partners that I’m blessed with, I intend to have my current WIP professionally edited before I publish it.
If I had an editor helping me with this blog post, it wouldn’t have as many errors in it as I’m sure it has. (I don’t believe I’ve ever published a post without going back and making corrections afterward. Ever.)
And if I had an editor helping me with this blog post, he or she would encourage me to wrap it up a with a bit more style than merely ending it abruptly like this.
UPDATE: Since writing this, PD Richmond has allowed me to revise my post on his site. (How very un-cheesy of him!) Now you won’t see the errors, but there were three of them; two missing words and a misplaced apostrophe. Shameful. Thank you, Pete, for making the corrections.