Yeah, it’s another language post. Buckle up: today I’m going to talk about codes and stories.
Codes are awesome. I’ve already been through all the reasons you should have a different language in your books: giving the reader a code or puzzle adds a whole new layer of reader involvement. The best books have the reader constantly engaged, from investment in the characters to trying to figure out the shape of the plot.
This is the secret to video games: the puzzles and battles mean the player’s not just passively watching the story, they’re living it. It’s incredibly immersive. Books can make use of little immersion techniques, too. When you give someone a puzzle to solve, you’re giving them a personal investment in the book. They’re becoming a part of the plot.
Plus it is so much fun to make puzzles.
Query letters are tough. I mean, I have a hard enough time with my elevator speech: how the heck am I supposed to condense down everything I need to say into like four paragraphs? It’s nearly an art in itself. You need to get their attention, tell them about your book, and tell them why it’s going to sell– and you’ve gotta do it fast. Plus it needs to be fairly well-written, since your writing style is part of the selling point.
Which is hard, guys.
I’ve been reading up a lot on query letters lately. So I’m going to try and organize my research a little, and write it all down here.
Warning: All LTBooks articles contain spoilers.
Every Saturday at noon CST I livetweet a book as I read through it for an hour or two. It’s immensely enjoyable.
If you’re interested in following as I livetweet, my Twitter handle is @AlexPenname, and I have a little widget that posts my last few Tweets on the sidebar of my blog. You can also follow the tag #livetweetbooks and the name of whatever I’m reading that week.
I’m currently on an Artemis Fowl kick. I recently finished The Lost Colony. The Opal Deception was my least favorite of the series; this one was my most favorite.