Let me explain the title.
At last year’s Internet Librarian conference, I made a comment about being a “sparklepony” in your library. What I meant was that if you’re someone who has a special skill that no one else on staff has, you should evangelize on your own behalf, stop downplaying that expertise just to make others feel comfortable or less threatened, and make sure that you use your skills in the service of others.
I mentioned my Sparklepony Theory of Professional Success ™ during a presentation I made to staff last week about the Digital Public Library of America (DPLA) Appfest that I attended last November. Part of DPLA’s mission is to break down the information silos that exist between libraries/cultural institutions and their digitized collections.
These silos also exist in libraries, particularly among library staff who create artificial divisions between “techie” and “non-techie” staff members. I am a web services librarian, and you are a children’s librarian, and neither of us can ever be anything else ever, ever, ever, The End.
During my talk, I made a point of telling the audience that they could break through these silos if they really wanted to by looking for other ways to become involved in technical projects. My own work experiences on this front have been frustrating as all get out, and there were many times I thought about leaving the library. But instead of giving up, I looked for other ways to do the work I wanted to do. I paid for a Lynda.com subscription and took many courses on WordPress, Drupal and PHP, and I’ve made a few introductory forays into the courses on offer through Codeacademy. I taught a couple of courses on WordPress, usability, and human factors, and I read a lot of blogs. I reached out to developers who were affable and approachable, and made contacts with some librarians who were all too willing to answer my annoying newbie questions. I put in the work on my own time, but it paid off.
Here are a few suggestions I made for ways to break through:
- Work on Codeacademy lessons during your lunch break at your desk
- Read bloggers like Andromeda Yelton, Bohyun Kim, Becky Yoose and Lisa Rabey, just to name a few
- Write about your struggles and your successes. GYODB, but comment on others.
- Get on Twitter. Now.
- If you can’t write code, write documentation. It’s every bit as important, and very necessary.
What I most wanted to do in the talk was to convince the staff that there’s a way in for them as well, that the Sparklepony mystique is just a myth. I may be a special unique snowflake in my organization — and that’s hella debatable — but I don’t take any particular pride in it, and they shouldn’t be intimidated by it. I am by no means an expert developer. To call myself a developer would not just be a stretch, it would be a lie. But what I am is code literate. And any librarian who is willing to put in the time, to make connections, and to look for a way in — even on her own time — can do the same.
Being a lone Sparklepony isn’t much fun. I want others around me who can frolic, play, break stuff, and make stuff better.
Join me, won’t you?