Curious about Aider

Someone I rather respect (both as a programmer and as a librarian) recently described the period of time after he got properly set up with LLM-enhanced coding tools as “the most productive two weeks of my life.” In a fit of enthusiasm, he completed a ton of previously unfinished projects in very quick succession. Despite my skepticism of vibe coding, because of my respect for this person this is a hard claim to ignore.

I had sought his guidance on tooling for working with LLMs with code. I am not up to speed on this, and was honestly a bit curious. I really had no idea of the workflows, which made me a bit uncomfortable. Aside from kicking the tires of GitHub Copilot back in 2023, the last time I had looked at LLMs — which I admit was quite a long time ago — it seemed like I wasn’t going to get anywhere because I didn’t know linear algebra. Anyhow, things have changed. There are APIs.

So this afternoon, after absorbing some of my coworker’s enthusiasm, I spent some time reading the docs for Aider. It works at the command line, and with vim, which I appreciate. Is it going to help my workflows? I have no idea. My plan is to set it up over the weekend and try. My skepticism remains, but I will let you know what I learn.

Posted in ai, aider | Comments closed

Against IMRaD

In my opinion, the scholarly literature of librarianship has an IMRaD problem. IMRaD is an acronym that stands for “Introduction, Methods, Results and Discussion.” Along with some variants, it is the standard paper structure for much of the sciences and social sciences. Wikipedia includes a visualization of IMRaD that looks like this:

A visualization of a classic scientific paper, with Introduction, Methods, Results and Discussion stacked to show typical paper structure. The middle sections are labelled 'Central report section'
To be fair, there’s nothing wrong with IMRaD papers. They are a specific — and effective — form of scholarly communication. But what rankles me is when people insist (as a peer reviewer did to me recently) that this is the only format for communicating paper-length ideas in librarianship, as though this was a matter of fact, not of (very human, imperfect) negotiation.

There are plenty of other methodologies that can inform librarianship, and some of these have nothing to do with IMRaD papers. Some library journals allow case studies. But beyond that, the humanities are a (rather massive) area of study that basically ignores the IMRaD format altogether. Are we going to exclude all of that methodological knowledge from librarianship? And if so, why?

Some “explanatory pluralism”, to use the felicitous phrase of Robert McCauley[1], would only improve our field. There’s room for many approaches to librarianship. This is part of the reason why we’re starting a new journal. There is an opportunity here to publish useful work in librarianship that isn’t IMRaD.

[1] McCauley, R. (2013). Explanatory Pluralism and the Cognitive Science of Religion: Why scholars in religious studies should stop worrying about reductionism. In W. W. McCorkle & D. Xygalatas (Eds.), Mental culture: classical social theory and the cognitive science of religion (pp. 11–32). Acumen.

Posted in journal, methodology | Comments closed

🚨 Call for editors 🚨

Apply by September 15th, 2025

Humanities Methods in Librarianship – a new, no-fee, open access journal – is looking for editors to join our talented editorial team! The journal publishes high quality, peer-reviewed research, creative works, and book reviews. We aim to broaden the scholarly conversation by encouraging submissions that deploy methods from the humanities to address current or salient issues in the library profession.

If you are interested in being an editor, irrespective of your academic background, we’d love to hear from you!

Please fill out the form here, and we will reach out to you to start a conversation!

Posted in journal | Comments closed

New journal: Humanities Methods in Librarianship

My collaborators and I are very happy to announce this project, which has been brewing for a few months now. We’re launching a journal called Humanities Methods in Librarianship. In the next few months, we’ll put out a call for editors and peer reviewers, launch an instance of PKP’s Open Journal Systems, and ultimately put out our first call for papers.

The motivating idea behind this project is that most academic journals in librarianship take a strongly social science approach to our field, which does not suit all librarians or all library papers. Many of us are trained in the humanities, and we find ourselves having to shoehorn our papers into social science frameworks to get them published. This is not ideal. There should be a venue for addressing librarianship from humanities perspectives, and this journal intends to fill that need.

I’ll follow up here (and elsewhere) with our calls for editors and peer reviewers. We hope you’ll consider contributing in whatever way you’d like. In the meantime, if you’d like to reach out to the editors, you can find us at [email protected].

Posted in journal | Comments closed

Return to XPS 13

In a previous post, I talked about reviving an old Dell XPS 13 9360 that I had accidentally smashed several years ago. I am glad I revived it; it is a lovely machine, though very obviously showing its age, as it is almost 10 years old now. It now runs Debian serviceably, and I’ve been using it to carry around — to work, to the coffee shop, and so on — as I’m not too worried about banging it up at this point.

But I also wanted a new laptop. With the exception of a cheap Chromebook that I bought in a panic a few years ago, I haven’t bought a computer since the 9360, in 2016. I wanted something similar to the 9360; fortunately for me, Dell still produces a very similar XPS 13 9350.

One of the nice things about Dell is that their new machines are very customizable prior to delivery, which is a very different experience than you’ll get walking into the Apple store, or Best Buy, or whatever. Maybe not quite as customizable as Framework computers (which I did consider), but nonetheless the customizability allowed me to focus on the features I wanted (yes to Ubuntu, and to more cores and RAM; no to more disk space and a touchscreen).

Anyhow, I’m now provisioning it with what I want, which is always a thoroughly enjoyable thing to do.

Posted in dell, xps | Comments closed

DNS, part 2

Earlier this week, I wanted to set up a root domain to point at a subdomain. The obvious reason for this is that I wanted a page to load whether a user types in example.org or www.example.org. I had tried this back in 2019 with my projects page, albeit with no success. This may have been due to my own lack of knowledge, or my impatience, or the lack of affordances of GoDaddy; whatever it was, I could not get it to work.

Fast forward six years and I need to do this again, but this time it’s a bit higher stakes because it’s for a work project. In the meantime, I had moved on from GoDaddy to Namecheap, mostly because of discussions on the Code4Lib Slack, where the preferences for Namecheap were clear. Namecheap also allows for ALIAS records, whereas GoDaddy does not. I ultimately used an ALIAS record on the root domain to make the whole thing work.

Setting this up took me about three hours altogether. Much of this time was spent with refreshing the page and wondering if it was propagating. Usually it was not; instead I had made some mistake or another.

In order to get https traffic to redirect from the root domain, I set up a small Flask application there to handle the redirects. This is an improvement on simple forwarding, which is not able to handle https.

Posted in dns | Comments closed

Blogroll

Inspired by @fsvo, I’ve added a “Blogroll” tab to the top of these blog pages. Blogrolls were a popular late 1990s/early 2000s way to recommend content. The idea is that you include a list of links to other blogs on your own blog, so that people can discover new, related content. It’s basically low-tech relevance recommendations.

These seem to have fallen out of favor. But I’d like to suggest that we need to actively encourage alternate means of content discovery. Web search isn’t great these days, and neither are LLMs. Hierarchical directories like Yahoo and DMOZ are long gone, and (in my opinion) were never that helpful in the first place. But it’s useful to have a diversity of ways to find content. It precludes capture by one or a handful of companies. It may be low tech, and very smol web, but it’s valuable.

Posted in blog, smol | Comments closed

Hardware necromancy

I had an old, broken Dell XPS 13 9360 sitting around for quite some time. It was a computer that I really liked, but I dropped it off a table at one point, and the hinge of the monitor broke so badly that it became unusable. Anyhow, I didn’t want to throw it away, because aside from the case, it was perfectly fine.

What I did was buy a second broken Dell XPS 13 9360 on eBay for $161. This sat on my nightstand unopened for quite a while, waiting for me to find a chance to roll up my sleeves and mess with the hardware. I finally got around to tackling this last night.

The first thing I did was try to put the SSD from the original machine into the new one (which came with no hard drive). This may have worked, but I didn’t get to find out, because the fan wasn’t working. The machine wouldn’t boot, and complained loudly and angrily about the fan.

Replacing the fan was a bigger task. I first had to take out the battery (pretty easy) and the motherboard (less easy). I ultimately reassembled the laptop using the battery, fan and motherboard from the old machine, which I had more confidence in. I wired it all up again and expected it not to work :) But it booted!

But at this point the rebuilt machine didn’t recognize the SSD. I’m not sure why. Perhaps because I restored the factory settings in the BIOS? (I may be totally wrong about this; it is just a guess.) Anyhow, I was able to boot into an initramfs recovery shell, and I could get the SSD working again by running fsck (file system check) from the shell. I could then install Debian 12 from a USB drive and my “new” machine was up and running!

Posted in hardware | Comments closed

On my occasional disavowals of coding

Every once in a while, I write a post talking about how I’m going to (more or less) walk away from coding. But nonetheless, the coding projects continue, and this blog endures. This speaks to the compelling power of writing code, even when work and/or life pulls in other directions. Programming, as many people will attest, is enchanting.

Partly this perennial interest on my part is also due to the positive reinforcement loops that can occur between programming and academic work, which I’ve talked about elsewhere. And code is a very versatile tool that can tackle many kinds of tasks in libraries, giving it an evergreen utility.

I started with Python v3.3, which was a long time ago now, and over the years I’ve run through a wide range of emotions and dispositions toward coding. Longtime readers of this blog will perhaps see a pattern, or maybe some cycles. This post is perhaps best read as another marker on that (iterative?) journey.

Posted in meta, writing | Comments closed

OJS, part 2

In a previous post, I described my recent install of PKP’s OJS. This week, I followed up by doing a run-through of a sample publication workflow on my localhost version. In brief, it was great. Without consulting the documentation, and without very much confused clicking around, I was able to peer-review and publish a sample issue of one article. This was a big victory. While it would take a lot of configuration to adapt the tool to a real-world scenario, the fact that it was so intuitive was remarkable. I am very impressed!

Posted in ojs | Comments closed
  • Subscribe to this blog via email

Skip to toolbar