Saturday, August 21, 2010

The Week in Words (August 21)

At the Editor's Desk

This week was so busy it ran into next week! Sorry for the late newsletter, but it's been delayed by some truly exciting projects, so I'm sure you'll forgive me.

Master of Professional Writing

This week I attended the orientation for new graduate students in the Master of Professional Writing program at the University of Oklahoma. It's a two-year graduate degree that focuses on writing novels, non-fiction books, and screenplays. You know I'm already focusing pretty heavily on the first two of those, and I've got secret dreams of seeing Gods Tomorrow as a screenplay within my lifetime, so there's incredible potential here.

I said a little bit more about orientation (and my expectations for the coming semester) over at the Consortium blog, in case you'd like to know more.

Gods Tomorrow

I've also spent most of the month really wrapped up in last-minute improvements to a two-year-old manuscript. That's because I'm planning to self-publish Gods Tomorrow in early September.

It's a huge undertaking, but I've been making rumblings here lately against the publishing establishment, and I've been linking you to article by J. A. Konrath who makes screeds against the establishment, so I'm doing my due diligence. I'm going to publish my best, most polished, most promising manuscript as a total gamble, and let you know what I learn.

Of course, I'm doing everything I can to bias the results, so I've been pretty busy planning a coverart photoshoot with the amazing Julie V. Photography (not to mention contacting Julie Roads for some help with the back cover copy).

On Unstressed Syllables

This week we covered two major topics: after exhorting you to accept your expertise as a writer (I called it "writing in the deep end"), I went on to demand that you obey some writing rules again.

Sunday I introduced the Technical Writing series on expertise with a story about throwing my daughter in the deep end of the pool, and watching her struggle back to the top. Ugh! Just typing that makes my stomach tie up in knots, but it turned out to be a good thing.


Then on Monday I talked about pretending to be an expert writer. I've spent most of the last year practicing what I preach, as far as that goes, and it's definitely turned out to be a good thing.


Then Tuesday I tried to tell you how to overcommit yourself as successfully as I have done. It's all about stretching your competence, and I'm pretty confident that's the only way anyone has ever earned the rightful title of "expert."


On Wensdy (as we sometimes say it in these parts), Courtney told us what she learned about writing this week when she returned to her writing Bible, a memoir/textbook written by Stephen King; in essence, she told us -- as he told us before -- to use the words we know and stay away from the big and fancy words, no matter how tempting they might be. I think it's good advice. How about you?


Thursday I introduced the Creative Writing series on writing rules with a story about a high school math teacher who let me sweat it out, before doing me a tremendous favor. Who would have thought math could be so suspenseful?


On Friday I talked about suspense, and the challenging balance of surprising your readers without keeping them in the dark. One of those things is a requirement of good writing, and the other one is absolutely against the rules. Fun.


Saturday's article cleared things up a little bit, though, because real suspense isn't built out of ignorance. The best way to write suspense is by creating real concern for fictional characters. Once that's in place, you can do more to worry your readers by revealing what's in store than by hiding the things they need to know. It's liberating...and incredibly powerful.

Saturday, August 14, 2010

The Week in Words (August 14)

At the Editor's Desk

This week my works in progress included four books, and all of the How Tos. That's not normally the way I run things, but this week has been an excellent exception.

Catching Up on My Reading

This week I didn't get any new scenes written for The Girl Who Stayed the Same, but I've been busy reading anyway. I finally read through Chris Baty's No Plot, No Problem (the NaNoWriMo book), and it was inspiring. I wanted to start writing right away. None of that's a big surprise (most of you know I'm a three-time NaNoWriMo winner), but the message wasn't a surprise and the book still got me ready to go. It's incredibly well written. I recommend it highly.

I also picked up ePub: Straight to the Point this week, and started working my way through it. It promises to teach me everything I need to know about digitally publishing a novel and making it beautiful. So far I'm a couple chapters in and it's telling me to do all the thing I'm telling you to do, but I have high hopes the second half will be the actual application bit.

Getting Behind on My Writing

And I'm not just getting behind on my writing for The Girl Who Stayed the Same. I'm making it worse by adding new projects to be behind on!

This week I designed and outlined a new e-Book that's all about using Google Docs as a Documentation Production Environment (or, put simply, getting the most out of Google Docs). Much of the book's foundation (just like the ePub book I bought) will be the stuff I've said here in the last month or so, but I'm going to get into some pretty detailed advice for management and publication in the e-Book that would be hard to present on the blog.

I'm also working on a new e-Book that's all about writing a novel during NaNoWriMo. And yes, of course, my finally reading No Plot, No Problem is related to that. I needed to make sure my book wasn't too much of a duplicate, and it's not. I think the two guides could coexist quite peacefully.

Two new e-Books, three novels I'm working on at the moment, and the publication of Gods Tomorrow scheduled for September. It's going to be a busy summer.

On Unstressed Syllables

This week we covered two major topics: programming your language and pointing your plot.

Sunday I introduced the Technical Writing series on programming languages with a story about writing a macro in VBA to handle complicated Word tasks. It protected my productivity and saved my sanity...and gave me a great chance to show off my technical skills, too.

Then on Monday I talked about automating tasks as a Technical Writer. Programming might not be a normal pastime for writers, but it's an incredibly valuable one.

Then Tuesday I told you which programming language you should start with, if you're ready to get started. Dive into Python. It's a programming language that does its best to read like a human language, and it can do remarkably cool things.

On Wednesday, Courtney told us what she learned about writing this week from painting trees for Julie V. Photography. She told us to get really good at the things we're good at, and...well, to get good at the things we're not good at, too. I think Chris Baty would agree!

Thursday I introduced the Creative Writing series on plot points with a story about my high school graduation, and the dedication of my first home. Both of them were monumental moments in my life, and both of them proved to be major turning points in my story. I think that qualifies them for a couple hundred words of memoir, don't you?

On Friday I talked about monumental moments and turning points in your stories. I explained the concept of plot points -- what they are, and what they have to offer.

Today's article came with a little caveat, though: they won't really pull their weight until you learn how to write effective plot points. It's a matter of deliberate design. You don't have to outline every scene in your book, but every scene should know which plot point it's moving toward, and what that change will bring.

Around the Web

I also found a couple of good articles around the web this week, that I thought you might find interesting.

Saturday, August 7, 2010

The Week in Words (August 7)

At the Editor's Desk

After last week's big reveal of my other project, I think it's time to get back to a real focus on what brings us all together here: hating Dan Brown.

Freelance Services

It's a shame that I've never gotten around to preparing a sales page around here, but as some of my blog posts in the last couple weeks have probably hinted, I do have some valuable services to sell. In addition to my own extensive experience with creative and technical writing, I've done writing coaching, document design (fiction and nonfiction), story editing, voice editing, line editing, copy editing, and several types of copy writing.

At the moment, I'm working on breaking into grant writing, and I'm in talks to maybe do a ghost writing gig. It all sounds like a lot of fun.

Incidentally, since I don't have a strong sales process set up at the moment, I've got some open availability, so if you find yourself in need of some of those services, you can feel free to send me an email (or use the site's Contact Form) to ask me for an estimate. I'm not cheap, but I'm terribly good.

The Girl Who Stayed the Same

There's the technical and the creative writing to do, though, and I'm still going strong on my current work-in-progress. This week I finished chapter seven and started chapter eight of The Girl Who Stayed the Same.

Someone finally asked Jonas if he was an angel (and he answered with a qualified no), and we also learned that Jonas is really terrible at chess. He's also pretty emotionally unstable, but what do you expect from a dude who hangs around with artists all the time?

On Unstressed Syllables

This week we covered two major topics: following directions and preparing a document according to the rules (specifically grant applications), and following the rules and writing stories with due respect for your readers.

Sunday I introduced the Technical Writing series on grant applications with a story about my three-year-old daughter learning to read...by memorizing the shapes of words. It's limited in a way phonetic alphabets aren't supposed to be, but it's also advanced in a way three-year-olds aren't supposed to be, so I'm considering the whole thing a wash.

Then on Monday I talked about grant money, selection committees, and how grant writing is just like the slush pile all over again. It's frustrating in ways, but it also gives experienced novelists a leg up on the competition.

Then Tuesday I took it a step further, saying that grant writing is just like writing Shakespearean sonnets. The metaphor isn't perfect, but the application is -- if you can learn to express your ideas well within someone else's strict structure, you're ready to call yourself a professional writer (and start raking in the dough).

On Wednesday, Courtney waxed domestic with a story about sewing up some torn garments, and in the process taught us how to patch up holes in our stories' plots. It can be a lot of work, and it's certainly the sort of thing we're often tempted to let pile up on our To Do lists, but a little extra effort can save a story from becoming scrap, and turn it into a perfectly serviceable Saturday shirt.

Thursday I introduced the Creative Writing series on writing rules with a story about Trish trying to watch The Da Vinci Code in spite of all my lecturing. The lecture's got to go someplace, though! So I spilled it through onto Friday and Saturday, too.

On Friday I talked about respecting your readers, and specifically focused on understanding and deliberately crafting your book's reading experience. When you consider how your story affects your readers (and what they're offering in exchange for your storytelling), it becomes far easier to stick to some of the core rules of writing.

Today's article tied that up with a detailed look at what some of those rules are: premise, verisimilitude, and the unforgivable sin named "Deus Ex." It's been a pretty academic week, and if you've followed along you probably deserve a couple hours of college writing credits for it. Alas, my blog isn't yet accredited.

Around the Web

I also found a couple of good articles around the web this week, that I thought you might find interesting. They're certainly relevant to our most recent discussion.

  • Writing this week's aggressive broadside against popular novelist Dan Brown, I couldn't help thinking about literary agent Nathan Bransford's fantastic article last week, The One Question a Writer Should Never Ask.

  • Wouldn't you know it, though, Bransford followed up with another excellent post this week on the same topic, Writing vs. Storytelling. Be sure you read both of these -- you'll be a better writer for it.