Caveat Lector

Well, Michael and Karen and She in Black and their commenters covered a lot of ground, but I still think there’s more, so…

1. Be passive-aggressive. Don’t tell your techie you need help setting up your new widget. Say “Hey, I got a new toy! Wanna come see it?” Because, hey, that way you don’t have to be grateful.
2. Don’t just mention how many real library services you had to give up for all this silly tech stuff (this is Karen’s point 6, I believe). Loudly bemoan how badly your library needs to hire “some real librarians.” Double points if your techie has an MLS.
3. Constantly ask your techie why s/he isn’t making more money in industry. Because of course there’s no way a techie has any intellectual, ethical, or social investment in librarianship.
4. If your techie is female, send her into all the tech-boy locker rooms (IRC chats, locker-room-style tech conferences, and whathaveyou) you can possibly find. Refuse to understand why she might be uncomfortable. By no means accompany her or stand up for her. Pooh-pooh or make excuses for the lads’ behavior; it can’t possibly be that bad. Double points if you know some of the lads. Triple points if you supervise them, or if they respect you.
5. If a project involving technology fails, blame the technology. And hold it against both the techie and technology (not the particular technology employed, but all technology) forever.
6. Cram every technology skill imaginable into your techie job ads. Network installation, database administration, ILS management, web design—it’s all technology, right? They all know how to do everything, right?

I hasten to add that while all the above listings come from personal experience, the experience is largely from library school and job interviews; MPOW and especially the World’s Coolest Boss aren’t implicated in anything serious, calculated, or damaging. Heck, MPOW firewalls IRC, so that one couldn’t possibly be their fault to begin with.