Log in

No account? Create an account
09 August 2012 @ 03:49 pm
rookie mistake  

For the past six weeks I’ve been working on starting a new book. Now, it often only *takes* me six weeks to write a book, and although there have been some distractions, taking six weeks to get started is really a bad sign. Usually when I don’t want to work on a new project, it means I’ve done something wrong. I *know* that, so I kept looking at it, trying to figure out what I’d done wrong. I reached 75 pages on the manuscript twice, and the first time, I threw out half of them.

This, the second time, I have realized that the book’s structure is fundamentally broken. I’ve been trying desperately to insert conflict into the story, and it just has not been working. I finally realized it’s because I’ve made things too easy for my main character, right from page one.

From where I’m sitting, that’s a rookie mistake. I haven’t done that since about my fourth published novel, and this is something like the 28th one I’ve written. So yeah, rookie mistake. A really, really aggravating one, too, because it means absolutely everything I’ve written is useless, including my synopsis. I have to throw it *all* out, and start all over again.

And this, my friends, is part of what it is to be a professional writer: looking a complete failure in the eye, tossing it, and starting anew. *mutter*

(x-posted from the essential kit)

Kate Kirbykirbyk on August 9th, 2012 04:03 pm (UTC)
This is another case where being a professional programmer is much like being a writer. I've been doing this all day long for well over a decade, and still sometimes I'll be pretty far into a project and realize I've got the wrong architecture, and throw out everything to start over.

The good news is, I never regret it when I do that, because I've learned so much doing it wrong!

I'm pretty strongly of the belief that computer programming is mislabeled. There's a small part that's learning the grammar of a language - like learning the rules of a human language, really. But knowing not to split infinitives is not the part that makes you a good writer, and you have an editor (or compiler) to advise you on that. The parts that make you good are how you string the syntax together to be clear, expressive, understandable, appropriately thorough, and communicative.

Computer programmers who write in their spare time, in my experience, are very good programmers to work with.

I realize that I just went off on an unprompted tangent, but I'm waiting for my laundry to finish so I can pack for vacation, so there we go!