Finished a new blog post: "My Coworkers Don't Want AI. They Want Macros"

https://ruthtillman.com/post/macros-not-ai/

My Coworkers Don't Want AI. They Want Macros | Ruth Kitchin Tillman

An exploration of how we are using macros in our current system, contrasted with what we're getting pitched by vendors. We want to: enter consistent data, avoid typos, improve system design, add conditional logic, and generally save the user repetitive, mindless work. Right now, that seems to require macros.

Ruth Kitchin Tillman

From the post, to summarize at an abstract level, we are using macros to:

- Enter consistent data
- Avoid typos
- Improve system design
- Add conditional logic
- Save the user repetitive, mindless work

At its best (pattern-recognition), β€œAI” is overengineered for what we need: logic and lookups.

At its worst (predictive text), it’s the opposite of the very concrete and repeated things we want to be able to do.

We want to extend our control over the system and augment it to work for us in our local context. And we're being offered black boxes.
@platypus thanks for this. I’ve been thinking similar thoughts about the way we code: we want to issue commands to the computer in a (more or less) deterministic way - what we *dont* need is some kind of stochastic stuff that is less consistent/predictable.
@platypus this is terrific and I really appreciate you sharing it. Our ILS (TLC Library.Solution) eliminated all macros (along with the ability to directly edit marc records) and I weep when I think about how much time I waste these days!
@platypus I wonder how many of the people that are proposing AI for this kind of work have even talked with people actually doing the work and be around them for a day or two before making those suggestions.
@hectorjcorrea it's actually so simple while also not being something that our systems enable on their own or provide good hooks for. No "select from these linked fields to make your own working page with just the fields you need" even though something similar exists for creating new reports in these systems -- so it kind of exists!
@platypus reminds me of this meme that one of my colleagues used in our slides.

@platypus Thank you for this article. It was a great read.

The place I previously worked at could have benefited from that kind of automation. For example, I was among the staff tasked with putting labels on our serials. Everything had to be done manually, from editing Alma’s default call numbers, to individually pasting those in a custom spreadsheet used as a template for priting labels, to actually putting the correct sheet of paper in the printer. It was a study in repetition.

@via It's a real irony that older systems are more compatible with these macros. It's not that the systems themselves were better designed, but I think it's awesome that library workers figured out (across libraries!) that they could make macros, shared tips, built whole little system improvements at home, and have maintained these.

@platypus
My experience mirrors this in many ways. People need tools so that simple things are simple, and when doing repetitive things they only need to do the minimum operations per iteration, to minimize mistakes. Sharing and flexibility give them power.

AI is entirely the wrong tool: randomness and nonlinearity are core to the technology. Make me an AI without either of those and maybe it'll be helpful.