Of all my training challenges, developing a keynote is always tough. The one I’m trying to develop for Code4Lib for my keynote is giving me conniptions. Do you hear an echo somewhere? That’s my brain.
I’m feeling more self-critical than usual because I feel my keynote in South Africa last fall was weak, largely because I was all tuckered out from presenting the previous day… it was a worthy endeavor, but the first day got most of my energy… and yet I felt it falling flat, and that’s hard.
I’m also speaking with a very technical crowd. I’m not intimidated by this crowd’s acumen; in fact, the real challenge to this presentation will be to get them to see past their code–to reimagine their work from the user’s point of view, and to see that code is simply an ingredient in a much larger recipe.
If you had a chance to speak with a library software developer, what would you say?
What should they know that perhaps they don’t?
What should they know about library users or library staff–two very different groups who both need to use their software, albeit for different purposes?
What can I tell them about talking to non-techies?
How can we challenge our developers?
What should they be proudest of? Most concerned about?
What can they do, as developers and human beings, to help librarianship survive this most tenuous of eras?
Posted on this day, other years:
- Between an ebook and a hard place - 2012
- Heading to Code4Lib, Prepping for Evergreen 2009 - 2009
- Reviews Resumed - 2006
- The Art of the Personal Essay : An Anthology from the Classical Era to the Present - 2006
- Steve Lawson's Batch of Feeds for Computers in Libraries - 2006
- Code4Lib Conference Notes Up - 2006
- Treadmill of Craft - 2006
- FRL's Library - 2006
- Media Bloggers Association to the Rescue - 2005
- Blogging at PLA: Any Insights? - 2004
Karen, as far as users go, whether they are librarians or library customers, I’d say that all they’re concerned about is having software that works. They don’t care what language it’s written in, they don’t care if it’s proprietary or open source, they just want something that works and helps them achieve their objectives. I’m sure that Kathy Sierra has said something about this much better than I can – her blog is at http://headrush.typepad.com/creating_passionate_users/ – she’s always inspirational, even if it’s sometime hard to relate what she says to libraries.
Oh, I would LOVE this opportunity — to be a respected speaker with those ears trained on me. What a gift!
I don’t have library-specific topics to suggest, but in general, I’d tell geeks to remember that there is likely something out there that they do not understand, but someone else does. Someday they’ll need that explained to them — a medical issue, how to get somewhere in a country where they don’t speak the language, what their options are for the sinking foundation of their house — and they should be talking to their clients in the way they’ll want someone else to explain the unknown to them. It’s a simple thing to say, but I think developers really do forget this. They need the reminder that they are not always going to be sitting on that side of the table.
In other words: for heaven sakes, LISTEN and BE NICE!
I have no specific suggestions, but in general I’d remember my creative nonfiction training and start with a couple of scenes.
Specifically, I’d paint two scenarios of library users that remind the audience that their customers’ customers are their customers – that the quality of the experiences of ordinary library visitors is their ultimate concern as developers. One scenario would show how something about library software made for a excellent experience and the other would show an unsatisfactory one.
>
That a little trust can go a long way. We are not all idiots who need a locked down computer. Let us prove our worth and do not make rules that constrict us because of one User and their User Error.
I’ll be one of the listeners (and looking forward to it) so it might be a little strange saying what I think you should say, but I liked Debi’s point a lot. I think the issues involved with successful communication (and being wary of context) would be good topics.
It would also tie in nicely, in my opinion, with code4lib’s collaborative thread (essence? being?) After all, sometimes we give and sometimes we take… being able to recognize the importance of each and shift contexts successfully (as givers or takers in different environments) certainly is a great skill… one most people (myself included) would do well to develop and refine.
I also agree that being able to listen is a key component to being able to successfully and gracefully shift contexts. And, of course, you can’t go wrong with, “BE NICE!”
Karen – Just my 2 cents, but I don’t think that your audience at code4lib is going to be a crowd of code-junkies who don’t understand the greater context; the opposite, in fact, most will be librarians, and most are very user-focused – I would even venture that one of the reasons this community exists is due to the lack of user-focused applications from our venders.
I may be wrong, but the way you phrase your post sounds very ‘me vs. them’, and I’m a bit worried about that.
Ah, yes, Steven… open in scene. Always good advice!
I agree with Jeremy.
I got my ALA-accredited degree 10 years ago and have mostly been working in the area of user experience design since then. I can’t write the even most basic script from scratch.
But I’ve found the code4lib community pushes the envelope in terms of user-centered design in libraries. There is no LibraryUX conference or community (only a low-traffic USABILITY4LIB listserv) but my experience via last year’s conference and the mailing list (I don’t do the IRC channel), is that code4lib fills that need quite well.
Here’s my suggestion; take it for what it’s worth.
It’s pretty clear, Karen, that you don’t have much faith in software of *any* stripe, nor in the people who create it. How did that happen? Why is it widespread in librarianship? (‘Cuz you’re hardly the only one.)
Crucially — what can librarians who are also creators of software do to earn your trust (and by extension, the trust of librarianship in general)? What about creators of software who are not librarians, and who (often with justification) feel shoved aside by the MLS crowd?
It’s a sticky subject (she wrote, as the bucket of litotes overflowed in a glutinous mess on the floor). I’m very likely the wrong person to bring it up in this context, as it’s well-known that I completely lost confidence in code4lib as a force in librarianship some time ago. But I think it’s a valuable topic, one you could speak to very effectively, and one that might allow both sides to get past some defensiveness and start thinking and talking together.
(*resists near-overpowering urge to sing “The Refdesk and the Techies Should Be Friends,” Oklahoma-style*)
Actually I can point to a lot of software I love, Dorothea. Excel, for one. Refworks. Google. LibraryThing. Flickr. Kodak EasyShare. Amazon (to the extent I’m interacting with software when I use it).
I also have great fondness for good developers. I really grooved on the developers at Siderean that I worked with. Nice product, nice people. I also worked well with our CMS developers, once we got some awful middlemen vendors out of the way.
You may wonder where the questions I developed came from. Actually, not from me. I asked what I could say that could benefit this crowd, and this is what was suggested.
What Karen is too nice to say is that I was the source of the questions. I’m sorry if the questions, or the phrasing of them, makes it sound as if Karen or I question the knowledge or perspective of the C4L community. As a proud member of that community, it would be the last thing I would want to do.
As Jeremy and Steve have pointed out, and I very much agree with, the C4L community tends to be very savvy about user needs. But I still think that someone with Karen’s experience may have a lot to say from which we can learn.
I wanted Karen to apply her unique perspective to the challenges and opportunities that we share and in so doing inspire and challenge us to do better. I regret that if in trying to challenge ourselves to do better it comes off more as an insult or as an “us vs. them” situation. That is not the way in which I intended such questions to be perceived, and I apologize for that.
I’d tell them to treat women and librarians with respect if you’re going to bother to work in the library field.
Signed, a former library software company employee