Tech-nos
Sun 17 Feb 2008, 11:09 pm
I read the “TechNot” posts by Rochelle “the Jefe” Hartman (twice!) and Jenna Freedman and Laura Crossett with some interest. I could fairly easily come up with a list of technologies or technology skills that have passed me by:
- Cell phones: Mine is cheap as can be and kept alive via periodic infusions of minutes rather than a monthly plan.
- Computer hardware: Like Laura, I am a lifelong Mac user, and never learned to care about things like video cards, processor speeds, etc., and in fact feel slightly superior to those people who do seem to obsess over such matters. (That completely unwarranted sense of superiority is included with the purchase price of every Macintosh, btw.)
- Programming and scripting: I can cut and paste just like everyone else, but I still have yet to sit down and really understand PHP or JavaScript or the like.
- Databases: I can’t tell if I have trouble with relational databases because it is really pretty simple and self-evident and I’m overthinking it, or if something fundamental continues to escape me.
So why are we interested in compiling such lists? It’s fun to “come clean,” to demonstrate to others and ourselves that everyone has blind spots and tin ears for some technology. But what does it matter if we can’t program a VCR or play a videogame? I think this memelet says something interesting about library bloggers.
We are prone to conflate various interests, tendencies, and proficiencies into one big “techie” category. But we are really talking about at least two different things.
Are we talking about being able to create and maintain interesting and useful technology for digital libraries? Or are we talking about being down with what we think our user population is doing? In other words, would anyone care if it were to come out that John Blyberg didn’t own a cell phone or planet code4lib doesn’t have a World of Warcraft guild? They are too busy actually trying to build useful stuff, right?
Or, on the flip side, would it really matter if Jenny Levine couldn’t use regular expressions or if Stephen Abram was perplexed by phpMyAdmin? These folks don’t set themselves up as hands-on creators of technology, but as popularizers and surveyors of what users are doing and expecting.
I guess part of the anxiety around this subject is that many of us feel caught in between, falling behind on one end of this discussion or the other. For my part, I couldn’t care less about my first two tech-nos on my list. The second two are things I’d like very much to change, if I can find the time and the right project.

I’m trying to think of why I even started this discussion. I think it was because I felt a bit of defensiveness at Michael Stephens’ friendly goofing about me having technolust and I felt I should set the record straight.
I think it also comes from being a public service desk librarian, and being asked by our users about everyday technology that many of us don’t use in our every days. I laughed at your comment about being able to “cut and paste” code “like everyone else.” I wasn’t even thinking about that side of tech when I posted because it is absolutely not part of my job. And, I think the range of responses we’re seeing demonstrates just how broadly we characterize “technology.” I think it’s valid to admit clumsiness with SD cards and cell phones because many of us regularly get questions at the ref (and circ!) about tools and applications. Libraries are starting gadget garages to get staff up to speed on phones, mp3 players, etc. The bigger question is: how far do we go to support technology?
Comment by rochelle — February 18, 2008 @ 8:30 am
I guess my “everybody else” was a pretty small circle of people who like to goof around with web sites, eh?
And now I see that I was coming at this from a completely different angle than you were, mostly due to our different work environments. People really ask librarians about SD cards and mp3 players and cell phones? That’s news to me, because at the small private college where I work, no one would think of asking about those things at the reference desk (and we’d refer them to the IT help desk–or the manufacturer’s help desk–if they did).
Comment by Steve Lawson — February 18, 2008 @ 9:11 am
[...] After reading Rochelle Hartman, Steve Lawson, Jenna Freedman, Dorothea Salo and Laura Crossett’s posts about their “Tech-Nots”, I started thinking about what it means to be tech-savvy. I was once I was eating lunch with some people I just met at a conference and one said “well you must have the new iPhone right?” Even if I did live in a state where I could get an iPhone (which I don’t), I wouldn’t spend the money on the device and the plan for all I’d use it. I’d wanted a mobile device for a while, but it was only because carrying around my laptop hurt my shoulders at conferences. I realized though that I could save lots of money by buying an ultra-mobile PC (UMPC) and my 2 lb., 7-inch, $399 Cloudbook will be arriving tomorrow (woo hoo!). I’m glad I waited for the hardware that actually meets my needs to come out. [...]
Pingback by Tech-NO-lust | Information Wants To Be Free — February 18, 2008 @ 6:20 pm
[...] Like several others who have posted on this meme, I wish I had better programming skills, like Dorothea I learn best when I have a project so it’s a matter of finding something to use as a guinea pig. I did start on Ruby on Rails a while back but never really came up with a solid idea to try out with it. [...]
Pingback by TechNotSavvy at Blisspix.net — February 19, 2008 @ 1:29 am
[...] February 19, 2008 by rudibrarian I’m finding the tech-NOT meme going around to be oddly comforting. I think what I like about it is knowing that I stand pretty firmly in the middle of the pack of folks who stand pretty far ahead of the pack in thinking about new technologies int eh workplace. And I’m really ok with that! [...]
Pingback by Late admission of techno-faux-bia « Deepening the Conversation — February 19, 2008 @ 8:04 am
That is a big difference between a public library public services desk and yours–I do get asked about anything and everything, and there’s a general assumption that if you know about one technology, you know about them all.
It’s difficult, as Rochelle says, because it is hard to know what kinds of things librarians in our positions should be responsible for knowing.
Comment by Laura — February 19, 2008 @ 11:20 am