Saturday, June 26, 2010

The Week in Words (June 26)

At the Editor's Desk

This week I finally started on a novel I'd been talking about for ages. And I talked to many people for many hours. And I learned way more about CSS than I ever wanted to know.

The Consortium

After about a week of researching various art grants, I met with an accountant Wednesday to figure out what I need to do to get incorporated and registered as a nonprofit. Turns out what I need to do is "pay this dude $1,800 and have a lot of patience."
That's not stopping me, though. I also met with several of my artists about projects we can start on now to get things moving in the right direction, and I'm taking my first halting steps at playing Mr. Manager. I'll let you know how that turns out.

The Girl Who Stayed the Same

The Girl Who Stayed the Same is now one or two scenes away from the end of Act I, and it's been a pretty intense week in Paris. I had two very different scenes this week that were each challenging in very different ways. It was fun.
Once again, you can follow that story on my private series page at the Creative Copy Challenge, or just wait for the e-Book coming to digital purveyors near you in February 2011.

SEATAC

SEATAC, my new sci-fi title, finally has a Google Doc to call its own. Well...it's actually had a Doc for a while now, but that was prewriting. Now it's real.
Two days of work to come up with 400 words of real....

On Unstressed Syllables

This week we covered two major topics: markup languages, and the blogstory style of Julie Roads.
Sunday I introduced the Technical Writing series on markup languages by telling the story of the college mission trip that crippled my faith. It was all about labels.
Then on Monday I took labels a step further, with a look into how markup languages (like HTML) can be used as document authoring tools.
Then Tuesday I got specific, telling you how to apply heading tags (and which tags to use) in WordPress. Blog better.
On Wednesday, Courtney learned another important lesson about trusting her brain when she forgot it was Wednesday already. See? That's why you need a scribblebook. If you're still craving the article you missed, just go back and reread last week's. It really was that good.
Thursday I introduced the Creative Writing series on the blogstory style by introducing the blogstory master (or...mistress?) Julie Roads. If you were reading along, you got to know that name quite well.
On Friday I told you why I thought she was so special. It's not just that she's a great blogger, but that brought the fundamental value of story her blog, and perfected the mix. If you're not already reading her blog, you should be.
I wrapped that up today by talking about you. Well...no, not really. I talked about Julie some more. And about me. But it applies to you! Because Julie got as good as she is by choosing a writing style she loved and practicing perfection. You can do the same thing, no matter what type of writing you do.

Saturday, June 19, 2010

The Week in Words (June 19)

At the Editor's Desk

Perhaps my biggest accomplishment this week has been the production of an email newsletter. It has taken me a hair shy of seven weeks to prepare.

I do apologize for the delay. I changed the blog posting schedule at the same time I took on three major new projects, and the newsletter fell through the cracks

I might have a thing or two to say about some of those projects, though.

The Consortium

That's right. After realizing I probably shouldn't be giving away my new genius business idea a full decade before I had the resources to pull it off, I have nonetheless continued in pursuit of that idea (and those resources). I've also discovered a handful of things that make me think maybe it won't take quite so long to make it real. And maybe I don't have to be quite so secret.

I'm not going to go into detail here, though, because that would rob me of a month's worth of blog post material. You can look forward to an interesting series throughout July, though, as I build the case for my right-brained brain trust.

The Girl Who Stayed the Same

I've also continued the serial novel I first announced in the debut Week in Words. This week I finished chapter four, and I dare say it's finally getting interesting.

You can follow that story on my private series page at the Creative Copy Challenge, or just wait for the e-Book coming to digital purveyors near you in February 2011.

On Unstressed Syllables

This week we covered two major topics: document outlines, and story structure.

Sunday I introduced the Technical Writing series on document outlines by telling about my own harrowing encounter with an outline-wielding high school debater.

I thought I was doomed, but it turned out I could easily get over the fear of failure by not trying to win. That's the happy ending to that story (although my debate partner didn't much appreciate it).

Then on Monday I got down to the nitty gritty, explaining why you actually need to understand and use document outlines. Turns out they're a fantastic way to visualize and improve your document's structure.

Then Tuesday I told you how to actually do one, with a detailed explanation (and examples) of the standard outline format. It was awesome.

On Wednesday, Courtney forgot what she was talking about, which made for a fantastic WILAWriTWe reminding you that you should get (and use) a scribblebook.

Thursday I introduced the Creative Writing series on story structure with the tale of a year when I wandered away from writing to focus on designing and drawing mazes.

On Friday I explained what that had to do with writing. If you look at it the right way, the structure of a story is just like a maze, and there are several principles of mazemaking that can help you improve your story structure. One of the most significant: solid structure doesn't have to be obvious structure.

I wrapped that up today by pointing out the big difference between mazemaking and storytelling. In this business, it's absolutely your job to make sure readers can follow the plot of your novel. If they get, ahem, lost somewhere in the middle, you've dropped the ball. And I'm going to be classy here and not mention the writers of Lost at all.

Across the Web

I do intend to include interesting writing-related links in these newsletters, as I was doing for the few short weeks that "The Week in Words" ran as a Saturday blog post. I don't have any for you this week, though. Maybe next week I'll manage my time a little better. One can always hope.

Tuesday, May 25, 2010

My 48 Hours

Last Thursday, while I was still at work, T-- took the kids to Wichita to spend some time with her family there. The plan was to stay through a big birthday party Saturday evening, then drive home late Saturday night.

I intended, as I often do on these occasions, to take advantage of the peace and quiet to get some good work done. Mainly I had some computer stuff I wanted to do -- reviewing a blog for a new friend, getting caught up on my own blogging after a busy few weeks, and putting together some notes on a new project I'm working on (the Consortium). I figured I'd do a little lawn and house work, too, since our property got hit pretty hard with last week's apocalyptic hailstorm.

Anyway, when I got home from work to an empty house Thursday afternoon, the first thing I did was make a To Do list. (I estimated roughly that each item in the "Must Do" list should represent about 90 minutes of work).
  • Must Do
    • Thursday night
      • Write Sun/Mon/Tue blog posts for next week
      • Prepare newsletter for Saturday
    • Friday morning
      • Mow the lawn
      • Clean out the gutters
    • Friday afternoon
      • Write Thu/Fri/Sat blog posts for next week
      • Set up blog review spreadsheet on GDocs
    • Friday night
      • Review Julie's blog posts
      • Review Julie's blog posts
    • Saturday morning
      • Chainsaw some trees
      • Paint hall and bathrooms
    • Saturday afternoon
      • Review Julie's blog posts
      • Review Julie's blog posts
    • Saturday night
      • Edit and link next week's blog posts
      • Prepare next Saturday's newsletter
    • Sunday afternoon
      • Email Julie about the Consortium
      • Complete detailed descriptions of the Consortium in Wave
    • Sunday night
      • Write Sun/Mon/Tues blog posts for next week
      • Outline blog posts for June
  • Remember to Eat!
    • Lunch with D-- (discuss Consortium as non-profit)
    • Dinner with K-- and N-- (discuss Consortium network/software)
    • Lunch with Courtney (recruit her to the Consortium)
    • Dinner with B-- (discuss Consortium business plan)
  • Extra Credit (if I have free time)
    • Recruit Carlos to the Consortium
    • Social Writing
    • Help Toby program BookMaker utility
    • Get in touch with Doolin
    • Email Julie about blog review
    • Get Courtney her photos (from a Julie V shoot)
    • Design novel template in GDocs
    • Scan many things
    • Edit/link guest posts for Doolin
    • Make chapters for Carlos's e-Book
    • Review Carlos's other support requests
    • Call OU Admissions department
    • Email Shawn about the Consortium
    • Finish Ivanhoe
    • Email Courtney about her blog
    • Contact Schwinn customer support
    • Lowe's run
    • Fix exterior lights
    • Drop seed, weed killer, and fertilizer on lawn
    • Clean out garage work area
    • Put some stuff in the attic
    • Convert Becca's and Bryce's books to e-Book format
    • Read Becca's and Bryce's books
    • Check out Courtney's new WIP on GDocs
    • Write Thursday's Creative Copy Challenge post
    • Reply to many comments on my blog and Doolin's
Those were my 48 items in 48 hours (I mentioned them on Facebook). And...well, technically four of those items were scheduled for Sunday, but I'd have my whole family home on Sunday so I figured I'd need to get much of that done in advance.

Of course, I ended up adding to the list before I was done.
  • Added since Thursday afternoon (all extra credit)
    • Email Courtney about new photo policy at my blog
    • Update About Page photos in color
    • Clean up storm detritus on driveway, porch, and sidewalks
    • Replace shattered plastic house numbers over garage
    • Pick up a birthday gift for K--
    • Fix fallen A/C register and attach headboard to bedframe
    • Murder weeds growing in driveway, porch, and sidewalks
    • Patch busted wood trim around bathroom door
    • Caulk floor joints both bathroom
    • Organize tool chest drawers
    • Wash and put away three loads of laundry
    • Paint over garage hail damage
    • Take out the trash
    • Do the dishes
    • Email Cindy about the Consortium as a non-profit
And I made time for my 4.5-mile jog every morning, because with all that cerebral work going on, I needed some physical exertion to balance it out.

The problem, it turned out, was that 45 minutes jogging wasn't close to enough time to balance it out. I got started working on the lawn Friday morning, and found myself still working outside when it came time to go to dinner Friday night. Woke up Saturday, went for my jog, and figured since I was going to have to shower anyway, I should do a thing or two outside first.

By the end of the day Saturday (my forty-eight hours), I'd spent about fourteen hours sleeping, eight hours at business/social meals, and a hair over an hour (total) sitting at my computer. The other twenty-five hours I spent toiling -- repairing my house, cleaning, or working in the yard. And none of that was by choice or priority -- it just sort of happened. I was driven.

When everything was said and done, by the time I went to bed Sunday night, I'd completed 34 of the 62 items on my To Do list, including just half of the "Must Do" items. The finished list looked like this:
  • Must Do
    • Thursday night
      • Write Sun/Mon/Tue blog posts for next week
      • Prepare newsletter for Saturday
    • Friday morning
      • Mow the lawn
      • Clean out the gutters
    • Friday afternoon
      • Write Thu/Fri/Sat blog posts for next week
      • Set up blog review spreadsheet on GDocs
    • Friday night
      • Read Julie's blog posts
      • Read Julie's blog posts
    • Saturday morning
      • Chainsaw some trees
      • Paint hall and bathrooms
    • Saturday afternoon
      • Read Julie's blog posts
      • Read Julie's blog posts
    • Saturday night
      • Edit and link next week's blog posts
      • Prepare next Saturday's newsletter
    • Sunday afternoon
      • Email Julie about the Consortium
      • Complete detailed descriptions of the Consortium in Wave
    • Sunday night
      • Write Sun/Mon/Tues blog posts for next week
      • Outline blog posts for June
  • Remember to Eat!
    • Lunch with Dan (discuss Consortium as non-profit)
    • Dinner with Austins (discuss Consortium network/software)
    • Lunch with Courtney (recruit her to the Consortium)
    • Dinner with Bruce (discuss Consortium business plan)
  • Extra Credit (if I have free time)
    • Recruit Carlos to the Consortium
    • Social Writing
    • Help Toby program BookMaker utility
    • Get in touch with Doolin
    • Email Julie about blog review
    • Get Courtney her photos (from a Julie V shoot)
    • Design novel template in GDocs
    • Scan many things
    • Edit/Link guest posts for Doolin
    • Make chapters for Carlos's e-Book
    • Review Carlos's other support requests
    • Call OU Admissions department
    • Email Shawn about the Consortium
    • Finish Ivanhoe
    • Email Courtney about her blog
    • Contact Schwinn customer support
    • Lowe's run
    • Fix exterior lights
    • Drop seed, weed killer, and fertilizer on lawn
    • Clean out garage work area
    • Put some stuff in the attic
    • Convert Becca's and Bryce's books to e-Book format
    • Read Becca's and Bryce's books
    • Check out Courtney's new WIP on GDocs
    • Write Thursday's Creative Copy Challenge post
    • Reply to many comments on my blog and Doolin's
    • Email Courtney about new photo policy at my blog
    • Update About Page photos in color
    • Clean up storm detritus on driveway, porch, and sidewalks
    • Replace shattered plastic house numbers over garage
    • Pick up a birthday gift for Kris
    • Fix fallen A/C register and attach headboard to bedframe
    • Murder weeds growing in driveway, porch, and sidewalks
    • Patch busted wood trim around bathroom door
    • Caulk floor joints both bathroom
    • Organize tool chest drawers
    • Wash and put away three loads of laundry
    • Paint over garage hail damage
    • Take out the trash
    • Do the dishes
    • Email Cindy about the Consortium as a non-profit

Friday, February 5, 2010

Flying Ice

Monday this week was a day made for disappointment. It always is, but this week was worse than most. After an ice storm lent me another four-day weekend, it was a real bummer to come back to the office. Nobody was in a great mood, and everybody had a lot of work that needed doing, to get caught up. I put in my nine miserable hours, packed up some extra reading to take home with me, and then called it a day.

The roads were pretty clear by then, except for the steep-walled piles of dirty gray slush spilling onto the sides, but the drive still posed some little risks. I felt my car slip a little turning onto MacArthur, and again as I pushed up the ramp onto the highway. It was nothing dangerous, really -- just little reminders that the road wasn't really dry.

I hardly needed them, though. My windshield was enough evidence of that, with the thin, semi-transparent patina of slush thrown up by the cars ahead of me. That got a lot worse when I got onto the highway, and I was leaning forward, waiting for another pass of my worn out wipers, when the car in front of me threw up more than just slush. A pebble the size of a BB flipped up and smashed against my windshield, inches from my nose.

The sound of it startled me -- surprisingly loud crack in the still of my car --and as I flinched back, I wondered if it had chipped the glass.

I first started driving in 1995, and I drove for fourteen years without ever getting a cracked windshield. I've certainly taken my share of pebble bombardment, but they make those suckers pretty strong. Still, the thought crossed my mind because, only a week earlier, gravel bouncing out of the back of a dump truck had put a big score in the driver's side glass right above the dashboard. First time in my life, and here came another pebble one week later.

And then the wipers blurred by, smearing away the muck, and they left behind a single glittering spot, ten inches above the week-old chip. I grunted in frustration, I rolled my eyes, I probably thought something mean about the driver of the dirty white Tercel.

But then a sarcastic smile twisted my lips. I shook my head and chuckled, and said, "I wonder if I constructed that." See, I believe in something called social constructionism, and one aspect of it is that the things we expect, the things we anticipate, are the things that are likely to show up in our reality. By worrying about my glass getting chipped, had I made it happen? It was a swift-passing thought. I sighed and let it go. Probably just coincidence. It's a funny old world, after all.

The words were still fresh in my mind, the smile still on my lips, when I heard the distant groan and rip just before a sheet of ice tore free from that same car. I'd seen it happen on my drive in that morning, and even once or twice already on my drive home, but this time it happened right in front of me. A blanket of ice and snow packed two-inches thick suddenly caught the wind, dancing like a kite up into the air for two seconds, three, and slashing back down to earth.

I was too close, though. I got in the way. The largest shard -- probably two feet across -- came stabbing straight down at me. I braked, I swerved, but there was no time. I caught a dozen pounds of ice dead center on the passenger side of my windshield, at sixty miles per hour. It boomed like an explosion, and the whole windshield shattered -- safety-glass holding the fractured bits in place, but ruined.

It was five o'clock on a Monday afternoon, northbound in the left-hand lane of one of the city's major thoroughfares, so I had sixty-MPH traffic right on my tail. As soon as I knew I was still alive, I put my foot back on the gas. My heart thundered, and I had to fight to catch my breath, but the windshield held. I had a small rectangle, maybe two feet by one, right at eye level on the driver's side where the glass was whole. It was enough to give me a clear view of the road, as long as I leaned forward. It was enough to get me home, anyway.

So I drove on, terrified every time another piece of ice flipped up into the air and wondering if the shattered windshield might give way yet. Ten miles still to go, and nobody else on the road cared how fragile my situation was. I just focused on breathing, focused on getting home safely.

And while I was at it, I tried my hardest to ignore that chip, right in front of my nose, marring the one bit of good glass left to me.

(I prepared this post according to the assignment description in this week's Creative Writing exercise over at UnstressedSyllables.com. I'd love any feedback you've got to give.)

Tuesday, February 2, 2010

Journal Entry: February 2, 2009

We ended last year with an honest-to-goodness blizzard that rolled in on Christmas Eve. Mom and Dad were here in town, staying at our place for the week before heading out to Germany on Christmas morning, and that ended up being quite an adventure. They made it, though.

Anyway, we had a repeat of that foul weather last week, when heavy ice started coming down on Thursday afternoon, followed by a thick coat of snow all Thursday night. I did end up going in to work on Thursday, but they let us out early and closed the offices on Friday.

That gave us a nice long weekend, trapped in the house. T-- has been sick with a respiratory virus for nearly a week now, so it was a good thing I was home to take care of the kids (especially in the mornings). We had fun, though. AB and I played out in the snow for half an hour on Friday, we started testing out bedtime stories, and she learned how to control my warlock's flying carpet in WoW.

XP and I worked on enunciation and word choice, motor control, and screaming unreservedly for no reason whatsoever. That was a little less fun.

We watched a bunch of Berenstain Bears cartoons with AB, and the first season of 30 Rock when she wasn't looking. I also played a lot of WoW.

Saturday night, like Noah sending the dove out from the ark, we ordered a pizza and were delighted when it arrived in a reasonable amount of time. Sunday morning we finally ventured out, meeting my little sister and her family at IHOP for lunch.

We were not the only people in town with that idea. Alas.

Anyway, we had no real problems on the roads, and afterward T-- dropped me and AB back at the house, and then went to do some grocery shopping. Sunday evening we had sandwiches, and finished off the second season of our show.

Then Monday morning it was AB's turn to be sick, and she was hacking something awful when I had to head to work. T-- seems to be on the mend, though, and it was only really bad for three days or so. So maybe AB will be better before the weekend.

Oh! On the drive home from work I had some serious drama, but that probably deserves a post of its own. I'll get that up as soon as I can. I did end up running some errands in the evening, including a trip to Walgreens where I learned we might have another ice storm coming. Yay!

Other than that, it's just things and stuff.

Monday, February 1, 2010

I Am a Writer

I've been a writer all my life. I started inventing worlds and stories when I was in first grade, and I started learning the mechanics of it all even before that, when my granddad taught me touch-typing on a battered old typewriter.

The Prologue

I first started thinking of myself as a writer in a sixth-grade English class, when I was supposed to write a one-page story incorporating a least half of our vocabulary words, and I wrote eight pages and used them all. I made that the first in a series of absurd detective stories that I developed over the course of the year. When I was twelve my family moved to the big city, and I dealt with the frightening upheaval in my life by writing my first novel. I wrote my classmates into the story to make friends.

When I was in high school I spent an afternoon patiently explaining to my dad that I didn’t need to go to college. My only goal in life was to be a writer, and I already knew how to write. I was well into my second novel by then, and I was marking up my Creative Writing teacher’s noir mystery in my free time. My dad's wisdom prevailed, though, and when I got to college, I discovered not only the limits of my understanding but also the real value of others’ ideas. I chose Oklahoma Christian University for its creative writing program, and took a writing class every semester for four years.

In the process I learned the rules of the craft, I learned to develop my narrative voice, and I learned how powerful a diversity of styles can be. I’ve since had the opportunity to coach my dad in creative writing, and I was able to teach him using some of the same methods I learned in that college program I’d once assured him I would never need.

The Process

Those methods have become more and more important in my life. They include everything from the intensive character development and plot architecture that I've used to build my Ghost Targets series, to the minute attention to mechanics and detail that makes me such a good Technical Writer (and pays for my two houses).

When I first started in the industry, I hated that I was selling out and getting a day job, and I spent a lot of energy separating technical writing from creative writing in my head. All I got out of that was a lot of heartache, and a couple novels that languished as unfinished drafts for years. I've recently come to appreciate the similarities in the two disciplines, and learned how to play to my strengths in both fields. As a result, I've got pretty much the same writing process for both.

I start with as much prewriting as I can reasonably do, whether that's real-world research or rough scene lists, but I always limit the amount of time I dedicate to that. When I've got enough material to put together a draft, I stop researching and start writing. I do a first draft start to finish, with as little editing as possible. When I'm done, I take a quick pass through the document to smooth some of the roughest edges, then hand it off to one or two test readers to get feedback.

From there, I go through multiple stages of dedicated revisions. I've talked about that elsewhere, but it's critical to the process. It also usually takes two to three times as long as the prewriting and writing stages combined, so I've got to dedicate time and energy to the review process from the very first, or I'll find myself in a real bind when deadlines start looming.

The Products

Honestly, I end up applying that process in nearly every type of writing I do. That includes my journal entries here, emails to my friends and coworkers, and my articles on Unstressed Syllables. I've used some of my training to create some extremely effective tutorials, and to prepare business letters and queries for all my many projects. I end up doing a lot of editing work for friends and family, too. All of it is good practice, and all of it depends on my continued dedication to quality writing.

It's rewarding, too. Just last week I was skimming through an old draft of an unfinished novel, looking for an illustration for my blog, and I accidentally got caught up in the narrative. Half an hour and two chapters later, I remembered what I was supposed to be doing, but I came away from that with a determination to get that novel cleaned up and in the hands of some readers. That's an incredible experience, stumbling across some long-forgotten scene and rediscovering the magic and creativity that helped make it happen in the first place.

Currently, that's where most of my energy is focused: getting all my old, unfinished projects up to code, and getting them in the hands of readers. That has me working simultaneously on a utopian near-future sci-fi and a dystopian near-future sci-fi,on a dry political think-piece masquerading as traditional fantasy and on a juvenile emo romance masquerading as traditional fantasy. And, of course, through it all I'm constantly creating new stories. I have a fourth Ghost Targets in the works, and half a dozen story ideas spawned from dreams or debates. I have a handful of non-fiction works germinating, and a rather significant investment in UnstressedSyllables.com. Oh yeah, and then there's the full-time job. No question about it, I am a writer.

(I prepared this post according to the assignment description in this week's Technical Writing exercise over at UnstressedSyllables.com. I also posted a link in the discussion board there, so you can feel free to leave comments here or there, depending what you want to discuss. I'd love any feedback you've got to give, though.)

Monday, January 4, 2010

Unstressed Syllables

This isn't really news to any of you, but I've spent most of the last month getting a new blog set up over at Unstressed Syllables.

I've told a couple people that I'd probably abandon my personal blog, but I don't think that'll actually happen. Not altogether, anyway. I've made the definite decision to give up on my efforts at daily blogging, but I still have a lousy memory and I still find much benefit in looking back on slices of my life from arm's distance, so I'll still be posting here as often as I reasonably can.

For the next month or so, as I get into the swing of things, I'd expect that to be a near-zero value. We'll see what actually happens.

In the meantime, come check out my blog. It's inspired by you, it's written for you, and it probably features some humorous and humiliating stories about things you've done in the past, so you'll need to show up from time to time to defend yourself. Sorry, that's just the way it is.

Other than that, it's just things and stuff.