Patching e-books

Apparently, Amazon has been wirelessly updating error-ridden books, and it raises the obvious question: Should e-book patching even be a thing?

I'm torn. I mean, technology-wise, I think this is great, though I can see the potential abuses all too clearly.

Patching is not a new thing. Computer games have been doing it even longer than George Lucas.* Even print books get the occasional story-tweaking revision. So let's not pretend this is some new, infuriating thing that Big Publishing is doing to us. The difference now, though, is that eBooks can be patched immediately -- even automatically without the user's consent.

I'm going to say auto-patching is a Bad Idea because of Potential Abuse #1: Tweaking the story. Imagine a writer with Lucas Syndrome, endlessly fiddling with his masterpiece. You're halfway through his novel when a character references something that never happened -- except it did happen, in the revised version that got pushed to your device after you started reading.

Even without auto-patching, I fear this abuse. We'd all be arguing over whether Han or Greedo shot first, only to find out we were reading different versions.

Computer games show us Potential Abuse #2: Publishing the novel before it's done. In November, 1999, me and my fellow game developers were working 80+ hours/week to get our game finished before Christmas. We were close, but it was buggy -- critical cutscenes didn't play, others crashed the game, memory leaks made the game unplayable after an hour or so, important characters would kill the player for no reason, etc.

It sounds unplayable, and for some people it was, but they released it anyway. If we brought up a bug at status meetings, we were invariably told, "We'll fix that in the patch."

Don't get me wrong, we made a dang good game, but if you play it without that patch, I pity you. And I fear a world where authors release rough drafts of a novel for quick sales, knowing they can always "fix it in a patch."

That said, I think abuse would be the exception. I think most authors, if they updated their novels at all, would only make small changes. I say that because most film directors don't make controversial changes every time a new video format is released. Most game developers release playable games, using patches for bugs they couldn't have foreseen.

If it actually works that way, it could give e-books more value. We all know the things e-books can't do (can't loan, can't resell, DRM, etc), but print books can't be updated to make themselves better. You'd have to buy another copy for that. Mostly, I think this would be a good thing.

What do you think?


* Apparently, the term 'patching' is from the old punch-card days of computers, when a bug fix had to be literally patched onto the cards.

Why Do You Write in Your Genre?

Almost everything I write has some sort of fantasy element to it, something that defies understanding for the people in that world.

And I think the reason is my own faith. Part of my assembly code includes a belief that there's more to this world than we can see or understand. I feel like there must be.

So even when I write a story about a forgotten colony of Earth, something creeps in that is bigger than we are and beyond our understanding. Even when I try to set a story in modern-day Thailand, people start fires with their mind or something.

I'm not sure I could write a non-speculative, contemporary story even if I wanted to. Eventually, some character would discover unusual powers or receive visions of the future or at the very least witness something that may or may not be a miracle.

I can't help it.

What's your genre? And why do you write it?

Is Good Subjective?

(Remixed from a post I did a couple of years ago).

The Lost Symbol is formulaic. Twilight is simplistic, both in plot and writing. Eragon is ridden with cliches (Warning: TV Tropes link). The Shack reads like it was self-published (oh, wait).

And yet every one of these books sold millions of copies.

Millions.

For those of us who have devoted a significant portion of our lives to the written word, this can drive us nuts. It's unfair, we say. If people knew anything about quality literature, they wouldn't buy this cotton candy nonsense.

But that's just it. People don't know about quality literature. They don't know you're not supposed to start a novel with the weather. They don't know that the farm-boy-as-chosen-one plot is old. They don't know that adverbs are a Bad Thing.

But people know what they like. They know these books are thrilling, engrossing, uplifting. "But they're not!" we cry. "They don't even follow the rules!"

Okay, so here's the thing. I know this is going to be hard to hear, but...all those rules that agents and editors and critique partners keep telling us we should follow? None of them make a story good.

For those of us trying to break into the business, it's easy to convince ourselves that "good" is objective -- that all we have to do is figure out the rules and follow them. While the rules certainly increase our chances, nothing in this business is a sure thing. Nothing.

So how do you break in? Well, not having broken in myself yet, I'm going to go with the stock answer: Write lots. Write well. Get lucky.

Usually in that order.

Breaking the Rules

If you've been learning the craft for a while, you've heard the rules. Don't start with a character waking up. Don't start with dialog or the weather. Don't use a mirror as a device to describe the narrator. Et cetera.

Lies.

There's a book you might have heard about called THE HUNGER GAMES. You know what it starts with? Katniss waking up.

You may have heard of Natalie Whipple, whose X-Men-meets-Godfather debut comes out next Summer. (If you haven't, you're welcome). About her novel, she tweets, "TRANSPARENT opens with a flashback, then moves on to a mirror scene while she is getting ready for school."

I love that. You may argue that means Transparent isn't good, but then you haven't read Natalie's stuff and you would be dead wrong. I can't wait to read Transparent, and I love that it breaks the rules.

My own novel AIR PIRATES starts with dialog. While it hasn't gotten me an agent yet, it has generated a lot of requests which, if nothing else, tells me the beginning doesn't totally suck.

Listen, the rules are good things. You should know them. But don't be afraid of breaking them. Just know why you're doing it. Are you breaking the rule because you couldn't think of anything better, or is it because that's the best way to do what you want to do?

If it's the latter, I say go for it! What do you think?

(Hm. I just realized Post-Apoc Ninjas starts with the weather. Maybe I have authority issues?)

So You Think You're Ready to Query...

When I wrote my first novel, I just wanted to prove to myself that I could finish a whole novel. After 4.5 years, I did, and when my one of my two beta readers said, "I can't believe you wrote a novel! And it's good!" I thought maybe I could actually publish it.

It took me 8 months, 52 queries, and 0 requests to realize I wasn't ready. This is the post I wish I had read back then (though I probably would've ignored it and queried anyway).

HOW MUCH HAVE YOU REVISED?
Is the story basically the same as it was in the first draft? I don't mean prose and grammar. I mean big things: motivations, characters that need to be cut or added, scenes that need to be rearranged. Have you deleted/rewritten entire scenes and chapters? I barely scraped the sentence structure with my first novel, and it showed in my rejections.

Of course, it's possible you wrote something good enough the first time, but it's unlikely. I'm the most obsessive planner I know, but even I have yet to write something where I didn't delete whole scenes and rewrite entire chapters.

WHAT DO YOUR BETA READERS SAY?
Do they love it yet? If not, it's possible they might be wrong, but chances are they're not. Revise it until most of them can't put it down.

And who are your betas? Are they friends and family, or are they writers who are trying themselves to get published? Friends make fine betas, but nobody knows the business like those who have already gotten their butts kicked by it. Network. Swap critiques with people who aren't predisposed to like your work.

DO YOU KNOW YOUR MARKET?
I thought I did. I'd read books like Left Behind and Randy Ingermanson's Trangression and Oxygen and thought, "Hey! Christian sci-fi is a thing!" I was wrong.

That doesn't mean you can't write what you love, but know what you're getting into. If Christian SF was my one true love, I would've focused my attention on that market and figured out how to become the exception. But I'm easy. I shifted my focus to secular SF/F and ultimately to YA. I'm still writing what I love, but my chances have greatly improved.

HOW'S YOUR QUERY LETTER?
This is assuming you're going the traditional publishing route (although a lot of book bloggers require query letters too -- can't escape, can you?). Have you written one? Have you revised it a bazillion times? Have you read hundreds of examples, both good and bad, and then revised yours again?

Have you had any of your stuff (query, opening pages, etc.) critiqued online by anonymous strangers? It's scary, and you're likely to get conflicting advice and people that don't get it. But this is a good way to see how agents or the general public might respond to your stuff.


If I could do it all over again, I'd join an online critique group and milk it for all it's worth, critiquing and getting critiqued until every beta said, "I can't see anything wrong with this! I love it!" I'd spend hours at Query Shark, Evil Editor, Matt MacNish and JJ Debenedictis' sites reading queries and submitting my own until people were saying, "This looks good! I'd request this!" I'd do it right.

Ah, who am I kidding? I'd do it exactly the way I did. I was so excited. I couldn't help it! I just hope one of you will learn from my mistakes without making them yourself.


Veteran writers, what would you have done differently the first time around? (Assuming you got rejected. If your first novel got published, I'm not sure I want to hear it!)

Web Design Tips for the Cheap, Lazy, or HTML-Challenged

Everyone says you need a professional-looking website, but a professional setup and design can cost hundreds of dollars and a monthly hosting fee. If your website is making you money (for example, by selling books), that can be worth it. Otherwise, you want something that's both Free and Good Enough.

Whenever I tweak things on this site, I have four goals, many of them conflicting: (1) Make my blog nice to read/look at, (2) Differentiate it from every other blog out there, (3) Rarely mess with the template (HTML, CSS, and other scary acronyms), and (4) Spend little or no money. If that sounds good to you, read on.

STEP #1: GET A FREE BLOG.
Blogger is my favorite. It's relatively reliable and gives me a decent amount of control (though those qualifiers are important). You could also go with Wordpress.com, LiveJournal, or many others.

None of them give you total control, of course. For that, you'd have to buy your own webhost and deal with your own technical setup and issues, which defies goals (3) and (4).

STEP #2: CUSTOMIZE YOUR TEMPLATE.
As far as free templates go, Blogger has only 27 (at the moment). Wordpress.com is better with 148. But since there are a few more than 175 blogs out there, your blog will very likely look exactly like someone else's. That's why you customize the crap out of it:
  1. Get a custom background. Especially if you're good with a camera/live somewhere pretty.
  2. Make a custom header. Free fonts and your local Paint program can surprise you. Photoshop and a little design sense is even better.
  3. Tweak the heck out of it. Blogger, for example, lets you change the format, fonts, sizes, and colors of almost every little thing. Take advantage of it.
STEP #2A: MAKE EVERYTHING READABLE.
Fancy fonts and wacky colors will definitely make your blog unique, but don't go crazy. Everyone's screen and color resolution is different (some folks are even reading you on their phones!). The text needs to be big enough and plain enough to be readable. And the text color should contrast as strongly as possible with the background.

Here's where I tell you to use dark text on a light background. I know people disagree with this, but white-on-black burns my retinas like those creepy Jesus illusions. I won't say don't do it, but at least think twice before you do.

STEP #3: ORGANIZE YOUR INFO.
People come to your blog for two reasons: (1) to read your latest update or (2) to find specific information about you/your blog. Every blog makes the former easy -- it's right there in the middle. It's your job to make the latter easy to find.

Static pages are a good place to put professional stuff. The kind of stuff agents come looking for. Pages put that info right at the top (usually), give you space to write as much info as you need/want, and keep that stuff (which is usually old news to your regular readers) from cluttering your sidebar.

The sidebar is the second place for it. People like to throw everything they can think of in their sidebars, and that's okay, but know this: Visitors will not scroll down past the first screen unless they are looking for something specific. (I will entertain arguments on this only if you've read my blog footer or clicked on the Carpe Editio flag down there. I'll bet money none of you have (until now, of course -- now you're curious...).)

Think about what you want readers to see, and put that on top.

(OPTIONAL) STEP #4: REMOVE REFERENCES TO YOUR FREE HOST.
Free hosts insert their brand everywhere. Search bars on the top, mandatory attributions in the footer, and of course the domain name. You can usually get rid of this stuff, but it requires either messing with the template or paying money.

But often, it's not hard either. Removing the Blogger search bar is a single line of CSS, for example, and a custom domain name costs only $10-15 per year. It's up to you whether that's worth it.


Many of you already have beautiful blogs (I know, I've seen them). So tell me what decisions have gone into your blog? What other tips would you offer?