jump to navigation

closing my eyes as I blog March 5, 2009

Posted by KC in metablogging, writing process.
add a comment

A number of blogs that I read have been apologizing recently for not posting very often or very regularly. Most say they’ve just been too busy, but at least one blogger has blamed Facebook for “sucking” his blogging energy lately. That’s an interesting idea, and I look forward to scholarly discussions of the generic and performative distinctions among blogging, Facebook, and Twitter. I am also not an especially prolific blogger. I think I’m averaging something like 1.85 posts per month. And I am aware that I’ve slowed down recently. However, I’m not sure this is something that merits an apology.

You see, I blog for me, and not for you. I don’t mean to suggest I don’t care about you. I totally do. But I recently realized that I write blog posts only when something gets under my skin, and the only way to scratch that itch is to write about it (or post pictures about it). Usually I don’t know what I’m going to write until I get into it. Each blog post, for me, is exploratory, an attempt to figure out and refine what I think about something — an “essay” in the original sense. I am not all that interested in persuading readers of something (all three of you tend to hold similar opinions anyway). I think of this blog as more of a sandbox for personal meaning making.

All this puts me in mind of Peter Elbow’s article, “Closing My Eyes as I Speak,” in which Elbow argues that we do composition students a disservice when we insist that they focus their energy on “audience awareness,” instead of having them write for themselves. I’ve got all sorts of problems with this line of argument (as those of you who knew me in grad school know), so I find it somewhat fascinating that this is essentially where I’ve wound up with my blog. Unlike other kinds of (academic) writing I do, this blog is mostly just for me. Is it possible that, for all my commitment to socio-cultural theories of language and literacy, I’m a closet expressivist?

It’d be fun if that were true. But that leaves me with a question: Why not just keep a private journal? If all this is just for me, then why do it publicly on a blog? Well, that’s where things get complicated. In all honesty, I don’t think I’d do any of this writing if it weren’t public, if there weren’t at least the possibility (despite my laughably low blog stats) that somebody else was reading this. When my writing is completely private, as in a journal or in notetaking, I take lots and lots of shortcuts. I don’t feel compelled to spell out everything, because I figure “hey, I know what I mean” (even if I don’t). When I write blog posts, however, I feel compelled to take a stab at making myself understood. I have to connect the dots for you (hypothetical reader) in a way that I am simply too lazy to do with private writing. So while I said that I blog for me, you are nevertheless an integral part of the process. Knowing that you might be reading this forces me to write in a way I find personally rewarding, whether or not it actually connects with you as well.

So, I thank you, dear reader, either real or imaginary, for being there (or not).

parking on a downhill slope March 4, 2008

Posted by KC in writing, writing process, writing tips.
2 comments

When you’re embroiled in a long writing project (like, oh, a dissertation), you pick up little tricks for staying productive. One of those tricks is to stop writing for the day  before you’ve exhausted everything you have to say, so that you’ve got something to get you started the next day. I think it was Joan Bolker who called this “parking on a downhill slope” in her book Writing Your Dissertation in 15 Minutes a Day (which contains much better advice than the title suggests).

This tactic works most of the time. But yesterday, I opened up my fifth chapter to find that I had finished my last writing session with this:

What is needed, I argue,

That’s it. I didn’t leave myself any indication what, in fact, was needed. As I tried to re-orient myself by looking at previous paragraphs, it struck me that “what was needed” was an end to that sentence. It didn’t help that I had written “what is needed, I argue” on a Friday, and I didn’t sit down to write again until the following Monday. I had two days to forget whatever it was I thought needed doing.

Without any breadcrumbs to follow, it took me a good five minutes to pick up the trail. Eventually, I scrapped the whole “what is needed, I argue” line and took the new paragraph in a completely different direction. In a sense, the frustration of having parked on a really awkward downhill slope made me reconsider — and improve — where I was headed.

There are limits to metaphors, so likening the act of finishing a writing session to “parking” only gets you so far. Maybe one problem with this particular analogy is that it reinforces the idea of writing as a linear activity, as if writing is like driving a car to a predetermined destination. But writing isn’t straightforward in that way. My experience yesterday reminded me that writing is full of fits and starts, messy and recursive. I ended up somewhere other than where I thought I was going.

revision tips September 13, 2007

Posted by KC in writing process, writing tips.
3 comments

Productivity blog, Lifehack.org, has a post on Nine Tips to Productive Revision. The tips themselves are useful, I suppose, but only if you think of revision mostly in terms of editing or proofreading. Take the first tip, for instance:

Try to get what you’ve written on paper. Scanning a piece on a computer makes revision extremely difficult, even though it may seem like the more sensible process. By printing out your computer work, you’re able to get more hands-on with your writing process. For most people, it’s also much easier to look at what you’ve written on paper rather than on a screen. Things you might not be able to see on your computer can show up when you’re marking your piece up with paper and pencil.

What, exactly, are these “things you might not be able to see”? Since the author doesn’t really say, I’m guessing he has in mind grammatical and spelling errors, or stylistic infelicities. I (sort of) agree that printing things out makes it easier to catch mechanical problems along those lines, although I find that reading drafts aloud is even more effective. (more…)

the problem with starting June 25, 2007

Posted by KC in metablogging, writing process.
add a comment

I’ve been wanting to start a blog for a while now, but I could never seem to get started. Paralyzing uncertainties suddenly introduce themselves: What should I write about? What should I call the blog? Which design template should I adopt for it?

In the end, I decided to take the advice I give my college writing students: just start writing. Putting pen to paper (or pressing a key down) isn’t an irrevocable act. Revision is always possible, and often necessary.

So, here’s my first post.