software design

code4lib Program Proposal

I’d be excited just to be a fly on the wall at code4lib, but I’m on a bit of a mission to change the architecture of our library software — to make it more hackable, and make those hacks more sharable — so I had to propose a talk. Title: What Blog Applications Can Teach […] » about 300 words

Raging Arguments About The Future Of The ILS

I hadn’t seen Ryan Eby’s post at LibDev that connected ILSs with WordPress before I posted that library catalogs should be like WordPress here. It connects with a my comment on a post at Meredith Farkas’ Information Wants To Be Free. My comment there goes in two directions, but I’d like to focus on the technology side now.

Our vendors will inevitably bend to our demands and add small features here and there, but even after that, we’ll still be stuck paying enormous amounts of money for systems that remain fundamentally flawed. Technology marches on, and inevitably we’ll find some new way to use our catalog data. John Blyberg is talking about this in his ILS customer bill of rights post, and that’s what I was getting at when I say the catalog should be like WordPress.

Meredith asks for more programmers, but as a programmer, I’m asking for her help in demanding smart software design from our vendors.