This week in RCDH, we focused our reading and discussion around algorithms. As I mentioned last week, the topic felt kind of transitional for me—databases, archives, and metadata blend together fairly well (for me, at least), and they’re not topics that feel overwhelmingly technological for people. Whether or not we work on the back ends of those kinds of projects, the concepts themselves are not immediately intimidating, I don’t think.
That changes a bit with the shift to algorithms, which have a more machinic flavor. Whether that’s actually the case is something I was thinking about in class, and it’s persisting with me this morning. One of the things that I said last night is that, at heart, algorithms are simply procedures, and we spent a healthy chunk of our time trying to put that into practice.
Last week, we used a couple of pages from an old MLA job list, and brainstormed as complete a catalog of metadata as we could. Before class yesterday, I took that list and converted it into “variables,” such that Rank, for example, became a class with potential values like Assistant, Associate, Full, Open, Fixed Term, etc. I brought copies of that list of variables to class with me, and had the students write “programs” for evaluating job advertisements. We didn’t focus too heavily on programming languages or anything—I wanted to keep it as light as possible. The goal of the program was to generate a score S(n) for each of the …