Episode 02 / Should Librarians Learn How To Code?
HELLO AND WELCOME. you are. Are you Gillian or are you Gill. Jill with a J. The name gets shorter as the time stretches. John's mother has sonorous instincts. Child chiding. Never Johnny. Scheduled banter. Semi-professional accounts without names as handles. 2007 as a less robust time. Traveling with Sue Fahey. Shiny objects. Went to Thailand. You're looking for the Red Girl. RED GIRL, OVER THERE. Ohhhh, *that* red. Ahhh sigh. It's called "Humanizing". Computery stuff. John gives a boring talk about a computer and operating system nobody cares about anymore. Process Names. Forgetting about resetting. It's literally the story. Nerdo computer topics. SHOULD LIBRARIANS LEARN TO CODE? No. No. Show's over. Can we unpack this. "Build an Access Database" as a course which is always going to be horrible. Why do people even *say* librarians should learn to code. Shorthand for technology context. Technology skills enjoy a continuing boom. Programming makes us cooler. Lionizing is a cool word. Shiny. Tech literacy is wide ranging. John doesn't know HTML or Access. Librarians do have to be technologically literate. Smell when people pull things over. ILL, how does it work? What is the specific problem. This aspect of this. ILL arose before shared cataloguing and pre-OCLC. Serials or cereals? BREAKFAST CEREALS OH MY GOD. Complex. Things that bug on a conceptual level. 5 systems with a user database. Why doesn't stuff talk. The Rolling of the Eyes. The same system for every library. Someone on III, someone on Sirsi-Dynix, someone on this someone on this. RACER as usability nightmare. Maybe not a better version of RACER but a better version of sharing. Net lenders vs. net borrowers. Single system vs. single set of policies. Invoicing every library every time someone borrows something is too expensive. FTE of 157. Many hours of meetings. Large transactions of money are a pain. We're supposed to be talking about learning to code! Downsview project. Well oiled retrieval is important. Pushback to offsite storage. Sonoma State's Onsite Offsite Retrieval. Robot dumping. Snoopy Retrieval Robot. Back to the actual subject that we're actually supposed to be actually talking about. Coding accessibility. Who has the time and access. Fluff. You gotta show INITIATIVE to get BY in this world. Can't force people I guess mostly? Sam Popowich, call in to the non-call-in show. John can't learn unless there is an actual project. Vendor relation courses????? Will they lie to you to make more money? There is no incentive to tear down and rebuild. Big holes. Ten systems. Glue programs. The problem with systems department. Org culture. The production mindset. Reductive. Back to Sam. Ryerson bookfinder The problem with systems department. Org culture. The production mindset. Reductive. Back to Sam. Ryerson bookfinder. The Nuance that Lies Underneath. Sorry Sam. The Sam Popowich Radio Hour. Code is not just code. Programming is not just programming. Wouldn't be a show without bonking the table. Delightful dancing around the topic. Medium-to-large-size-yes. Easier to teach programmers library stuff than to teach librarians programming stuff. Writing librarians off as a lost cause? Teamwork. Having one doesn't negate the other. Programming as special skillset. Monetarily challenges. The salaries of programmers. Technology hiring is hard. Hiring is hard. All smiles all the time. It's 38 minutes. John is passionate and enthusiastic to talk about mandatory happiness and enthusiasm. Edit-schmedit. Looking at the numbers. Passion and higher ed. Hiring Librarians. Policing professionalism. "Fit". Emily Weak's approaches. You're too "X", can you handle it. We're not hear to assess people's motivations. Don't talk about what might be behind. Internal drivers vs. external drivers. Reacting to brash people. Rife with baggage. People are adaptable. The one-shot. Frank is awesome. It's democracy, it's the worst thing except everything else. Massive issues with interviewing. "Fiiiii---iiiiit". Doing a shout-out. Hemmed in by numbers. Crushed by entry level liaisons. Flinging motions. John's dumb answer for everything. Let’s leave it there.