In a so-far-rare turn of events, this post will represent a few of my own thoughts on language and writing, rather than linking elsewhere. Of course I'm doing so as a way of procrastinating on writing which I should be doing: a conference review for the Sussex University online journal Excursions.
I'm finding it tricky work, and a useful insight into the challenges presented by my own students, especially in the coursework they're required to do. Perhaps it's because I've had a full weekend of other commitments; but then we all have those. Perhaps it's because this one is to be published, so there's pressure to get it right: it'll be on display, with my name attached, so it matters. Well: so far, so like coursework; there's no taking that back once it's submitted either.
Writing for a journal is perhaps an especially tricky ask. The writing needs to be academic – so, cut those clichés – but nonetheless, to some degree journalistic and readable. Also, you have a word count to consider; so there's pressure to be concise. Again: just like with coursework. Finally, you feel you owe it, in a conference review, to accurately and adequately represent those whose work you are discussing – especially where you spent time talking to them about it in the pub afterwards.
A blog post is, perhaps, not so much of a worry. You can go on as long as you want, within reasonable bounds. A stylistic slip isn't the end of the world; you can always edit the post later. And the readership is smaller too. (Unless you're John Gruber, for example.)
So writing for my supper helps me to feel my students' pain. But it also reminds me of some core things which I've posted articles about earlier today: getting every piece of punctuation right is important. Proofreading your work is non-negotiable. Planning ahead is the only way you'll get the material covered. And, finally, you can't beat practice.
