I’m preparing a context-setting/provocation video for a workshop I’m facilitating at the upcoming Australian Information Education Symposium on ‘repackaging’ information education.

And I need your help! I’m looking for answers to the following three questions:

  1. What do you think is the biggest challenge we (as a profession) are facing today?
  2. What do you think are the three most important skills, knowledge or characteristics graduate information professionals?
  3. What do you think LIS education should start, stop and continue doing/teaching? (Just one thing for each.)

I want a strong professional voice to set the scene for this workshop with LIS academics, so have your say here!

Please indicate in your comment whether you are okay with having your response in the video and how (or if) you would like to be credited (ie will I use your name? Your Twitter handle?).

** Disclaimer: I am not suggesting I’m a perfect writer. I once used the word ‘generalisability’ in a conference paper so I really shouldn’t be casting any stones. I’m a fan of using words and punctuation creatively. I’m an editor’s nightmare. But you will never, ever catch me using the word ‘whilst’. ;-) **

This post has been sitting in draft since *last* #blogjune, and since I’m about to embark on a whole load of marking, I figured it was timely that I post this now.

Have you read Fifty shades of grey yet? It’s a good example of formal language gone wrong. The dialogue is stilted because it’s unnecessarily and unrealistically formal.

Just as the dialogue in Fifty shades clunks because of its formality, some words commonly used in academic and business writing are archaic, wanky and off-putting. For me, these words fall into two categories: unnecessarily formal, and clunky joiners.

Here are some of my (least) favourites.

Unnecessarily formal

These are a bunch of words that people tend to use instead of simple language when they’re writing something formal or academic. There’s a common misconception that ‘academic’ means ‘verbose’, ‘complex’ or ‘not everyday’. Stick a couple of extra letters at the end of a common word and you’ve elevated your writing to a different level of quality, right? Uh, wrong.

There is never, ever any need to use these words. Unless you’re the Queen.

  • Whilst: while we *always* do. I hate this word more than any other in the English language.
  • Utilise (even worse if it uses a ‘z’): what’s wrong with ‘use’?
  • Thus: often used in really complex sentence structures and it just doesn’t work for me at all.
  • Therefore: so?

Clunky joiners

These are words people use to link sentences together and they are most annoying when they are used in a completely arbitrary way. An old friend of mine uses these words at random, without any recognition of the fact they actually have a meaning and need to be carefully selected. A few that really frustrate me:

  • Furthermore
  • Moreover
  • Heretofore

Used correctly and very sparingly, these words are okay. But there are much more elegant ways to craft separate sentences into paragraphs that flow. It’s just a little more work to pull them off.

Simple is beautiful

Writing economically is a bit of an art and it’s also a bit risky, I guess. If your language is simple, your content is on display. Some people attempt to hide less-than-perfect content with verbose sentence structures. For other people it’s less deliberate. They just think they have to use formal words in certain types of writing. But if you use these ugly, unnecessary words, you’re causing extra work for the reader. They have to dig through your language to access the content. This means you’re stopping your readers from understanding what you’re saying. And that’s never a good thing.

Does anyone else have a problem with these words? Or others? Please share yours in the comments!

I spent several hours this afternoon and this evening ripping the cars apart, on the phone to Vodafone and the police, and searching through my extremely well-filed receipts (no really, I have a great system… I just forgot how it worked for a while there), all because over the weekend, I managed to lose my phone. I kind of didn’t start worrying about it til today, even though I knew it was missing, because I figured it would be in the car. But since my mobile is my primary work phone (because I work from home most days), I had to start the search this morning. I was feeling pretty blasé about it really. I was certain it was in the car, and it’s insured, so I didn’t see the point in stressing. Then I discovered the hoops you have to jump through and the expense you have to wear to replace a lost phone on insurance. So all this made me cranky.

On top of that, I didn’t clear today’s to do list. And, worst of all, I discovered a series of what I like to call #lifefails. In short, every now and then, my habits of not opening my personal mail and using filters on my personal email to reduce noise come back to bite me.

It’s kind of amusing that I pay so little attention to keeping my life in order because I’m a pedant when it comes to work. It’s amusing, but not surprising, because the two are related. Sometimes I just use up all my #win on work.

Anyway, to get me out of my bad mood, I decided a grateful post was in order today. Here it is.

I’m grateful for the efficient and personable police officer who helped me lodge the mandatory report to allow me to make an insurance claim on my phone.

I’m grateful for loud speaker letting me work while I’m on hold for long periods.

I’m grateful for the shortest ever wait time on a Vodafone customer service line.

I’m grateful for the app Find my iPhone, but I’d be evn more grateful for it if I’d set my phone p to be found *before* I lost it.

I’m thankful for cold nights and potato bake.

I’m grateful that I’m finally feeling a bit better after being out sick for a week. And I’m grateful for getting my voice back a bit.

I’m grateful for Pinterest and all the pretty things I see there.

And I’m most grateful for the little cherubs who make me laugh all my cranky away.

…it’s time for me to do a bit of blogging. Or a lot of blogging. 30 days worth. A post a day. For the third year running, I’m joining a bunch of librarians and blogging every day in June.

It’s day 2, and I’m already a day behind. Well, sort of. I blogged yesterday over at the NLS6 blog, but I didn’t get round to doing my first post here. But here’s what I meant to say yesterday:

When I read smart, thoughtful posts like Hugh Rundle’s latest over at It’s not about the books, I get inspired to blog. Usually, I have a lot of trouble converting that inspiration into action. I’m not short on ideas, and I’m definitely not short on opinions. But I am short on time and I’m also the kind of crazy perfectionist who labours over every post before hitting send. So I see these awesome posts on topics that really interest me, and I want to respond… or I just get inspired to blog in general… but then, you know. Life happens.

This time round, though, Hugh’s post came just before #blogjune. Inspiration doubled. So here I am.

In other years, I’ve done this #blogjune thing to kickstart my blogging. This year, I’m just doing it for a bit of fun, because I’ve learned from experience that blogging every day for a month isn’t going to turn me into a regular blogger after the month is out.

So over the next month, I’ll be blogging here and over at the NLS6 blog, and hopefully a bit at my totally neglected food blog, fodmapfriendly.com. And the NLS6 crew are going to be blogging almost every day this month too, so make sure you head over to the site and subscribe! </end shameless plug>

© 2013 virtually a librarian Suffusion theme by Sayontan Sinha