The news wires and social media feeds were full of public library news today.
Quite properly, Ian Anstice's Public Library News provides the best summary of events.
Being a collection of ramblings on divers bits of library service development.
Wednesday, 30 March 2016
Monday, 28 March 2016
Experience isn't what happens to you…
One of the mantras I trot out with alarming regularity is: "Experience isn't what happens to you, it's what you do with it." Experience is one of those nebulous things that everybody sort-of understands but can’t quite nail down consistently. It’s what makes you reach for a pencil instead of a tortoise when you want to write a shopping list or makes you remember to put a rubber glove on before poking round in the back of “that” drawer in the kitchen.
Experience is confused with occurrence. It’s also often confused with wisdom. Experience is the “understanding-level” derivative of occurrence the same way that wisdom is the “understanding-level” derivative of data:
Too often experience is code for “time served,” as in the common person specification: “Must have x years’ experience.” This is a lazy way of saying: “We want this person to have some idea of what they’re doing from day one.” It’s also wrong-headed: while it’s true that it’s easy enough to assess whether or not somebody’s done that amount of time doing something it isn’t necessarily true that they’ve done it the same way or with the same tools. This lack of applicable context bites even deeper when you think about what those years of “experience” might really be. Some people have 20 years’ worth of repetition of the same working week.
If you ever see "experience" in a person specification don’t be put off if you want the job: think about what might be required that would need “x years’ experience” to do. You might already have done it!
Experience is confused with occurrence. It’s also often confused with wisdom. Experience is the “understanding-level” derivative of occurrence the same way that wisdom is the “understanding-level” derivative of data:
Wisdom | Experience |
Knowledge | Repetition |
Information | Record |
Data | Occurrence |
Too often experience is code for “time served,” as in the common person specification: “Must have x years’ experience.” This is a lazy way of saying: “We want this person to have some idea of what they’re doing from day one.” It’s also wrong-headed: while it’s true that it’s easy enough to assess whether or not somebody’s done that amount of time doing something it isn’t necessarily true that they’ve done it the same way or with the same tools. This lack of applicable context bites even deeper when you think about what those years of “experience” might really be. Some people have 20 years’ worth of repetition of the same working week.
If you ever see "experience" in a person specification don’t be put off if you want the job: think about what might be required that would need “x years’ experience” to do. You might already have done it!
Friday, 25 March 2016
Upon hearing the first English public libraries consultation of Spring
DCMS have issued a consultation on the "draft Ambition document" "Libraries Deliver: Ambition for Public Libraries in England 2016-2021."
It isn't a bad document and has lots of the right stuff in it. Perhaps I'm just jaded with it all.
It isn't a bad document and has lots of the right stuff in it. Perhaps I'm just jaded with it all.
Tuesday, 1 March 2016
Parliamentary Report on Libraries
The House of Commons Library recently published a Report on Public Libraries, an update to the report published five years ago. It's caused a bit of a kerfuffle.
See what you think.