I don’t consider myself a techie. I don’t function well with the details of doing code but I think that curiosity is really important. On my database management notebook I wrote down this somewhat cliche phrase that I read on lifehack . “I wonder how that works.” Really isn’t that it? Even if class taught us more xml, css, sql, it would be up to us to play and make and break things on our own.

a library student friend of mine always says that he is happy when he hears about people like your “never used email” student. More jobs for us.

At one point Candy and I sat down and brainstormed a list of “techie skills librarians should know something about.” It was a long list (and could probably be pared down.) But it pointed to the number of things we don’t cover in a systematic way.

I think if you’re motivated you can get a pretty good technology background at Simmons — it’s just that not everyone is that motivated. Some people still come to library school (and I include my compatriots in the Archives program) with nostalgic visions of a computerless world — they have dreams of living a monastic life amidst books and documents. But the fact is that to do a good job in today’s library world, you have to be good at tehcnology. (Just like you have to be good at dealing with people, managing conflict and change, etc.)

I also think you’re right about the ALA. For better or worse, I think it tends to have a very “public library, frontline service” approach that doesn’t emphasize systems management as a key part of librarianship. Sure banned books and freedom to read are important, but so is making sure librarians can still provide access to information when more and more of it is digital.

my MLIS never even evaluates different OPACs, let alone require that you take anything more than the standard tech class (create databases using InMagic, evaluate Dialog vs Google). some advanced classes are offered, but those tend to have more of a records management focus.

and students who grumble about not being prepare for the “real world” need to take some responsibility for that. this is your career people, not some shmo job. it’s going to involve more than just going to class and getting a piece of paper – you’re going to have to take some initiative. (i spend my spare time reading blogs and playing with a variety of different tech tools so that i won’t be a totally useless employee tech-wise.)

But the structures and mindset these hopeful newbies (of any age) are walking into are not propitiatory.

The problem is also in the funding available to library schools, and in the crop of professors they have to draw from. The sad fact is that most people doing current (not even cutting edge! just current!) work at the intersection of libraries and technology can make much more money with much less hassle doing just about anything except teaching in a library school.

I think I’m approaching that line where a comment becomes its own blog post, so why don’t I just go write that? Great blog, Laura K. I’ll be a regular reader know that I know about you.

Takes two to tango, and the fault isn’t entirely at library schools’ doors.