Care Work in Software

While tooling around with some prototype spaces for “Project Lunfardo” (still a provisional name, I’m sure!) I was thinking about some of the unspoken or under-acknowledged tasks that must exist in the realm of DH scholarly software. I see a lot of discussion about the various roles like project management, design, development, outreach, etc., but references to things like maintenance and deployment tend to be more oblique. This was a topic I was playing with yesterday over on BlueSky. Today I’m connecting it more explicitly to care work, which our society tends to feminize and therefore devalue. We need only look at the twin mantras of “move fast and break things” (Facebook’s previous motto) and “it is better to ask forgiveness than permission” (a particular kind of misquote of a popular saying later attributed to Admiral Grace Hopper) to understand how acting over caring functions.

Personally, I’ve found a good deal of satisfaction in improving a piece of software and keeping it running. And that sort of care is necessary even if no actual functionality changes. Software is subject to entropy just like anything else, so it’s vital to keep its dependencies up to date, which will occasionally require code changes as deprecations creep in. This isn’t a post about good software practices, though it certainly could be. Instead, it’s a bit of a meditation on how/why to use the power of institutions to keep the lights on. I assume that when we make something that is supposed to serve a scholarly purpose, we want it to last beyond peer review. Perhaps it’s not always necessary, but I’m guessing we don’t undertake a DH project with the idea that the software will go offline and become more internet ephemera. That said, we also do well to remember that software has lifecycles, so there’s a balance here.

Making it available online in the first place is also a job that often ends up being thrown over the proverbial wall. I came to software via systems administration, having labored for years under that sort of “well, it’s someone else’s job to figure out how to deploy it” mentality, where developers would make something someone else would deploy it and keep it running. That someone else was me. A result is that I keep both the development and deployment contexts close together, because I don’t think you can really separate them.

At the very least, you need several things to put something online and keep it there. You need a domain name, an SSL certificate, and a place to host the code and the database. The smaller the system and the less traffic it’s intended to serve, the lower the overall requirements. Most systems will need to scale, however, and some will require the ability to send email (to register users, send password resets, and otherwise generate useful notifications). And finally, keeping them up to date is necessary to keep them online. These additional constraints benefit from institutional support, even though they can be supported by an individual or small team depending on their complexity.


NB: On the topic of “ask forgiveness vs ask permission”, the actual saying was that it is easier to ask forgiveness than permission. In my mind, this is very different from asserting that it is better to do so. Imagine for a moment that one works in a large bureaucracy. It’s long been my assertion (yes, that’s me) that the main function of bureaucracy is to deny access to scarce resources. To say “no”, in other words. In such a system, asking to do something within the bounds and via the methods of the bureaucracy (asking permission) is virtually guaranteed to result in denial. After all, if you could do it already, you wouldn’t need to ask permission; and if you couldn’t do it already, there’s a reason. Hence it’s easier to ask forgiveness here than permission simply because asking permission entails a process or requires that one be invented. But it’s not better, per se, because it’s risky. Turning the phrase to suggest it’s better to ask forgiveness than permission is to say that none of the regulatory structure on which bureaucracy functions matters. You are, in fact, likely to break something.

 

Naila’s Skilllset

Hello everyone. I was excited to see that almost everyone from last semester’s DH Intro is now in DH Methods and Practices as well! Just a bit about me: My undergraduate degree is a Bachelor of Science in Professional and Technical Writing. I am very comfortable and adept at using and learning new technical skills. In my current position at the CUNY City Tech Writing Center, I’ve had the opportunity to take on many roles and work on various projects. I have created a variety of digital materials and content for the center and worked on outreach to increase overall visibility. I also have experience organizing and analyzing key data to build our reports and narratives, which helps us secure funding to continue serving our students.

Here’s a bit about the various types of skillsets and my proficiencies, as well as areas I’d like to build on:

Development
This has always been an area of interest for me, and I’m most eager to continue expanding my skill sets in coding and development. I have a solid foundation in HTML and CSS to start building out projects. I have dabbled with JS on a recent project, but I hope to work on more projects to gain a better proficiency (p5.js, too). I think I have also built a solid foundation in Python after taking the Python for Researchers class last semester and working on two Python-heavy projects. So Python is something that I’m also interested in building on. Basically, anything coding is a yes for me.

Graphics Design, Visual Design, UX/UI
I have a lot of experience creating visual assets and materials, and I love any opportunity to create visual content for projects. This can range from creating UI elements such as buttons, containers, and navigational components to image and video editing, curating a color palette, typography, logo design, and more.

Data Visualization
I have some experience with data visualization from my current job, but I feel like I’m expanding this skill set more and more throughout the DH program. I am interested in working on projects that employ creative data viz practices. This is an area I feel comfortable in, but I definitely would like more experience and tools under my belt.

Project Management
In my current position, I have led various collaborative project initiatives. One of my favorite projects was directing and producing a welcome and informational video to highlight who we are and what services we provide. This was part of a 3-month project with very limited resources, but I found it valuable in my overall professional development. I’ve also held many leadership roles that involved project management throughout my academic career. Though if project management were to be defined as a role in a project, it’s probably the role I’d be least likely to want to take on. I’m happy to collaborate on establishing workflows, but I’m always a bit nervous about being assigned as the “lead” project manager on the team.

Documentation
I enjoy writing various types of documentation. I have experience writing technical documents such as handbooks and manual type things. I wouldn’t mind supporting the team by writing methodology documents or other required documentation.

Research
I would like to say I’m experienced in this area. It’s not the most fun, but research methods and practices are pretty much second nature to me across academia and in my professional career. I find it foundational for almost everything. Even if my main role isn’t research, I think it’s inevitable, and I’ll probably find myself doing some research to familiarize myself with the project and gain insight into different methods and approaches for my respective role(s).

Social Media
I have done a bit of content creation and managed a social media account with a rather small following (~200ish). I’m not really a huge fan of social media though. I kind of like the idea of microblogging or a Subreddit as a public platform to share updates of our project timeline, but that, of course, depends on the project and team preferences. I’m happy to assist with the content and writing in this area.

Skillset: Chris

My skills are mostly developed from undergraduate research experiences and personal efforts in figuring out how to leverage digital technologies in historical studies. Professional experiences are few but have contributed to improving my abilities to uphold objectives consistent in developing scholarly research projects. 

 

 

Historical Transcription: 

This term describes the act of reading historical documents produced in their original form. In other words, looking at sentences that were printed in primitive styles of cursive before making them legible for others. I transcribed journals, letters, and newspapers that were produced in the late-19th and early 20th centuries for my undergraduate senior thesis, as well as in the recent semester. Moreover, for practice, I interacted with and transcribed a few preserved documents on the National Archives website (one of which was from the U.S. Navy). 

 

 

Data Visualization: 

I gained many experiences in data visualization across unique academic settings, as well as by learning to use different tools. There are two instances when I helped a student and a coworker in producing data graphics on Google Sheets; one in a high school statistics class, and another at an environmental research internship. Studying some Physics at DePauw University entailed the usage of Microsoft Excel to record lab results; additionally, building codes in R to create charts representing the same information. Two data visualization courses introduced me to Tableau, which gave experimental assignments and opportunities to evaluate transit systems and railways in the United States. On a final note, after being introduced to Voyant this past semester, I hope to continue learning about new data visualizing software and getting chances to apply them in unique settings.  

 

 

Digitization: 

In a historical sense, digitization is taking photocopies of a letters written by the wife of a French merchant company, then converting those images into PDF pages. It also includes transferring physical audio recordings (such as interviews) into computer audio files that online users can listen to and study. I do not have direct experience in digitizing historical material, though I have converted more than 300 documents for the MTA by putting physical safety information into digital databases. Furthermore, I am certain that I have enough technical knowledge to figure out how to make physical details viewable on screens. 

 

 

Research: 

Completing research to produce history papers within and outside my senior thesis had, overall, similar objectives and approaches regardless of the unique challenges that emerged from each study. Tasks mostly include navigating various library systems (physical and online), scheduling appointments with guides to receive help with citations and finding desired sources, and exploring many different online resources to discover potential networks and locations that would lead desired results. From a personal standpoint, research is an opportunity to produce knowledge and perspective while exploring extra details that may or may get written into published work. These interests influence me to make notes of such details, regardless of getting published or not. With that in mind, I am happy to bring these attributes into a project.  

Project proposal for a *pretty* terrifying interpretative data website on feminist themes prevalent in horror video games

Last semester, the initial goal of the horror_games_feminist_themes project was to create a curated dataset by scraping the “Category: Horror video games” tree on Wikipedia to classify keywords from horror video games that feature a female or LGBTQ+ protagonist. Here’s a spreadsheet of the output .CSV file for convenience. This was my first time constructing a dataset, and my hope was to create one that could eventually help identify and analyze recurring feminist themes, patterns, and harmful tropes within the horror video game genre. I chose to scrape, curate, and then manually review Wikipedia pages because video games involve a wide range of elements, from gameplay mechanics to visual design; it would be nearly impossible to begin an analysis on gameplay alone. Starting with Wikipedia seemed like a feasible place to start. 

So now what?

The project I propose aims to build a website that brings the dataset to life. The creation of a public-facing website that translates a dataset into an accessible and interactive experience, one that can make invisible structures visible by dissecting feminist themes from a medium that is not often analyzed in such a way. I envision that there will be playful design choices to lighten the load of this sort of gruesome topic–something fun and feminine as an entry point to make sense of the genre and medium where patterns can be analyzed and challenged.

Here are some data viz examples from https://pudding.cool/ that I was inspired by while doing a brainstorm scan: 

What question or problem will this project answer? Horror studies is typically centered around film, and video games are often underexamined as cultural artifacts. Scholars like Barbara Creed highlight themes of female monstrosity, embodiment, and patriarchal structures in horror films. For example, the horror genre historically frames female bodies and the reproductive system as something monstrous or abject (Creed, 1993), and this is one of the themes that I have also noticed when sifting through reviewing keywords for my dataset. I’d like to build from these frameworks to examine horror video games as cultural artifacts that expose similar structures and themes, such as patriarchy and embodiment. 

What audience will this serve?

  • People who are interested in games, horror, and feminism.
  • Students who are interested in media/game studies and/or gender studies
  • The (female and LGBTQ+) gaming community(?)
  • This project contributes to DH by applying feminist principles of DH not only to interpret “data as capta” (Drucker, 2011) but also to design a project that analyzes the medium of video games, which, as mentioned previously, is often difficult to dissect and comprehensively analyze compared to other media.  

Tentatively…

the final product is some sort of data viz website, but we might need to refine the data a bit more. This may include refining the keywords and classifiers, or scraping more titles. We might need to narrow down the scope. One thing I found particularly interesting while constructing the dataset was the differences between horror games published in the 90s to early 2000s versus more recent titles. This could be one of the ways to help centralize and narrow the scope of this project. 

Tools, skillsets, and various roles I envision us needing:

Some of these roles may be merged, shared, or rotated amongst other team members (based on individual preferences) through the different stages of the project!

  • Web-developer:
    • HTML/CSS/JS 
    • Build out the site
  • UX & visual designer
    • Design the site’s color, typography, and layout
    • Tools tbd.
  • Data curator & researcher
    • Python (for pulling data)
    • Review Wikipedia pages and validate keyword entries
    • Refine thematic keywords/classifiers
    • Help document interpretative decisions
  • Writer & content development
    • Draft and edit website textual content
    • Help shape the project’s voice and tone
    • Content creation for the chosen social media platform

Potential barriers and questions:

  • Wikipedia bias: I want to acknowledge that creating a dataset using keywords pulled from Wikipedia can have its limitations and biases. 
  • How can the interface be used to display data and invite engagement without minimizing gendered-violence, trauma, or harm?

 

A Digital Intertextual Concordance of Female Epics

NB: When I saw all the great proposals at the end of last semester, I wasn’t sure I would pitch mine this semester, not because I don’t believe in my proposal, but because I wanted to work on everyone else’s projects too! I’m pitching it now both because I still want to do it, and perhaps to prompt others to pitch their projects.

This is an extract, cleaned up to incorporate the feedback I received, of my Fall Semester proposal, comprising the Abstract, the Enhancing the Humanities portion of the Narrative, a brief Environmental Scan, and the Final Product.


My project seeks to compile and exhibit a digital intertextual comparative concordance of themes that occur in epics authored by or attributed to women authors. The initial phase will focus on a small corpus comprising three themes (death, love, and vengeance) across each of three female epics, with later phases covering more themes and epics. Leveraging the work in Approaches to the Anglo and American female epic, 1621-1982, edited by Bernard Schweizer, it analyzes Telemachus by Anna Seward (unfinished as of 1809, officially published in 2016), Psyche by Mary Tighe (1805), and Aurora Leigh by Elizabeth Barrett Browning (1856) and facilitates questions of if or how the language used by women writing in traditionally male spaces to express these themes reflects feminist perspectives, as well as any insights that can be gained by comparative digital analysis.

The project has three main digital outputs: a toolset for extracting and documenting specified themes, a dataset comprising the extracted themes, and a Web-accessible display of those themes. The creation of this toolset, dataset, and Web-accessible presentation layer will further allow for future expansion, via, for example, text selections in other languages, additional translations, and selection of additional epics. While it aims to be neither a comprehensive collection of female epics nor a primary source for the epics it does include, the project nevertheless highlights the relative absence of such digital collections and serves as a thematic reference for scholars of epic literature, especially those interested in female epic literature.

Enhancing the Humanities

Historically, concordances have been laborious creations made for intense scholarship of works that, because of their cultural importance, were read and re-read, such as religious texts. Father Busa’s Index Thomisticus, created with the assistance of digital computers, is generally regarded as the beginning of digital humanities as a discipline. In the intervening years, more powerful computing technologies have made the creation of concordances per se easier, and at the same time, the rise of natural language chatbots and fuzzy searches based on statistical sampling presents us with the foregone conclusion that concordances lack comparative value in the face of powerful modern search technologies. Looking beyond the marketing terminology, however, we see that mere statistical correlations yield decontextualized results arranged according to internal algorithmic relevance. Concordances, as tools positioned specifically for textual and intertextual comparison and interpretation, remain vital parts of the landscape for examinations of the use of language to convey concepts, and digital concordances offer a chance to be more deliberate in building human-scale searches. The central questions afforded by this concordance are exploratory, focusing as it does on what we should automate, but the relative scarcity of scholarship focused here underscores the importance of conducting the scholarship in the first place.

In his introduction to Approaches to the Anglo and American Female Epic,1621-1982, Bernard Schweizer suggests that the epic is perhaps the most male-coded genre of literature, “so much so that epic and masculinity appear to be almost coterminous” (Schweizer et al 1). This gender assumption is apparent from several standpoints: first, of who has historically produced epics; second, who defined and formed the body of the genre’s critics; and third, the genre’s main characters. A fourth standpoint could be the themes of epics, but this question is afforded in part by the outputs of this project. And yet, as Schweizer and his contributors demonstrate, British and American women have been producing epics at least since the 17th century. Production of epics by women authors is not limited to modern American and the United Kingdom, however. At his blog, Interesting Literature, Dr. Oliver Tearle lists the Sumerian poem The Descent of Inanna, attributed to the high priestess Enheduanna, as a particularly early example of the female epic, suggesting that “if Enheduanna was the author of this poem, … that makes it the oldest work of poetry written by any named poet, male or female” (Tearle). His article goes on to list six other epic poems, half of which, had they all been published at the time of their writing, all should be in the public domain. There are likely to be others that have either been misattributed or forgotten, awaiting rediscovery.

Centering women-authored and attributed texts in Digital Humanities scholarship will bring more attention to these works, elevating them in the public consciousness, as well as the other non-epic works by the included authors. Additionally, it allows scholars interested in the use of figurative language a ready platform to explore how or even if the use of such language in female epics may differ from that used in male epics. 

This project focuses on three of the epics identified by Schweizer. The first, and most problematic from a sourcing standpoint, is Anna Seward’s epic poem Telemachus. In her introduction to The Collected Poems of Anna Seward, editor Lisa L. Moore writes that Seward had arranged with Walter Scott to publish a complete collection of her poems. Among the collection was one unpublished poem, an epic she considered her masterpiece, and which she “took special care to recommend … to Scott’s attention.” (Seward 37). When he published the collection in 1811, two years after Seward’s death, he had excluded Telemachus with no explanation. The poem would not appear in print until Moore laboriously transcribed it from the original manuscript and included it in her 2016 collection of Seward’s poems. What this means for scholars is that unlike the other epics in the selection, there is a question about copyright for Telemachus, and there is no public domain source from which one can acquire it. Careful attention is paid in this project to avoid full replication of the text, arguing that extractions of the text for concordancing and other search purposes constitutes a Fair Use claim.

The second and third epics included, having been published in 1805 and 1856 respectively, are firmly in the public domain. Mary Tighe’s Psyche, a six canto allegorical poem written in Spenserian stanzas, and Elizabeth Barrett Browning’s Aurora Leigh. As these were chosen specifically because of their treatment in Approaches to the Anglo and American Female Epic,1621-1982, they are naturally limited in their linguistic and temporal representation. Further, they were chosen because, with the exception of Telemachus, of their publication dates. This places some constraints on the broad applicability of the project and its tools and outputs in their initial phases, but an output of the project includes support to locate and process additional texts from beyond this immediate set.

This project naturally raises questions about what could potentially be included in the future. While it proposes eventually to encompass all female epics, a main question is what counts as an epic? Is it limited to poetry, or are prose works also applicable? If so, the field expands again, but a key consideration is to maintain some boundaries on the genre to keep the overall scope constrained. As the project grows, other types may be added, but the continuing mission will be to maintain sufficient constraint to demonstrate the related concepts. Additionally, the issue of copyright vis-a-vis translations of older, especially ancient and antique works, may impact selection even while the existence of multiple translation offers interesting opportunities to compare interpretations of figurative language from translator to translator. To account for this, the project will review concepts in the concordance annually, new works will be added when possible, and the project will maintain a registry of desired works that are unavailable because of copyright constraints. Additionally, the project is committed to obtaining permission from translators for less available texts.

A final consideration is the methodology. Existing digital concordances facilitate keyword searches for words, word forms, or phrases that occur in the works included. In most cases, the searches are limited to a single work. While a broad keyword search is possible and perhaps desirable, this project proposes both a curated approach focused on thematic subjects that are known to occur in the included works, and a fully intertextual display of those occurrences across all included works. By curating the theme selection, the intent is not to limit the possible explorations afforded by the texts and interface, but rather to help orient users to examine major themes that occur in the works. The selection of three initial themes (love, death, and vengeance) speaks to some of the timeless aspects of epic literature, but in no way is it asserted that these epics are limited to or even mainly about these subjects. They are mere starting points for additional analysis, and it is the intention of this project to set the basis for additional curated theme selections even as more works are identified for inclusion. During the execution of the project, the thematic selection may be adjusted to accommodate what the project team discover, but only if this has no impact on delivery.

Brief Environmental Scan

In the interest of brevity from here, I will just list the projects that informed mine.

  • The Index Thomisticus
  • Open Source Shakespeare
  • The Electronic Dictionary of Armenian Bibliography
  • The Chinese Text Project
  • The Hyper-Concordance at the Victorian Literary Studies Archive
  • Skovoroda Online Concordance
  • PHI Latin Texts
  • Intertextual Dante at the Digital Dante Project
  • The Women Writers Project at Women Writers Online

Final Product and Dissemination

The final output of the project will live in GitHub as a code repository containing the extracted themes properly annotated with the designed metadata schema, the tools and scripts used to generate the extractions, and the website, including all narrative content, that exhibits the Concordance. Additionally, the site itself will be hosted online at a location to be determined and secured by the project team. In addition, the project lead and co-lead will share links to the final project via their various social media accounts, namely BlueSky, as well as the DH program lighting talks, the CUNY IT Conference, and potentially other conferences. 



Sasha’s Skill Set

Hey everyone, Sasha here. My background is heavily tech-focused (computer science and data analytics). My interests center on applying technical methods to questions in the humanities. I’m still refining my specific niche, but that intersection is where I’m most engaged.

Project Management: This depends on my familiarity with the project. I’m organized and generally reliable with deadlines. I work best as a collaborator rather than the sole project manager, though I can step into that role when needed.

Development: This is my strongest area. I’m comfortable with Python, web development (HTML, CSS, some JavaScript), GitHub-based collaboration, and data visualization tools such as Tableau and QGIS.

Design / UX: I have a basic foundation and am comfortable learning as projects evolve.

Outreach / Social Media: This is my weakest area. I have very limited experience with social media or outreach strategies.

Documentation: Not my favorite task, but I can produce clear, effective documentation when required, especially for any solo work done.

Research: I’m still developing my skills in self-directed research through the DH program and would welcome opportunities to collaborate with more research-focused teammates.

Project Proposal: The Humanities AI Hallucination Database

Brief Project Overview: This project will build a public-facing, interactive web archive for the Humanities AI Hallucination Database. We are starting with a significant advantage: a pre-generated seed dataset of 100 records documenting AI hallucinations related to Black histories. However, our goal this semester would be to expand this scope to document algorithmic erasures in Latinx, Asian-American, and white American histories as well. We aim to create a comparative dataset that reveals how generative AI distorts knowledge across different identities.

The Problem: AI chatbots are fast becoming de facto historians for students. However, these models often invent figures, misattribute theories, or erase narratives. Failures that disproportionately affect marginalized groups. The gap: There is no centralized, standardized repository that educators can use to show students specifically how these models fail across different cultural contexts. We need empirical data to verify if, for example, AI “hallucinates” Asian-American historical figures differently than it does Black feminist scholars.

Intended Audience

  • Educators & Librarians: Seeking diverse examples for teaching source evaluation and information literacy.

  • Ethnic Studies Scholars: Researchers analyzing comparative patterns in algorithmic bias.

  • Students: CUNY undergraduates learning to navigate generative AI tools critically.

Contribution to DH & Potential Impact This project contributes to Intersectional Digital Humanities and Critical Data/AI Studies. By moving this data from a spreadsheet to a public web interface, and expanding it to include Latinx, Asian-American, and white American histories, we are creating a vital Open Educational Resource (OER). Team members will help build a tool that operationalizes “epistemic justice” for multiple communities, giving educators the concrete evidence they need to challenge algorithmic authority in the classroom.

Final Product (What we will build) We will build a searchable, scalable web archive.

  • The Web Archive: A website where users can filter hallucinations by demographic (e.g., “Black History,” “Latinx History,” “Asian-American History”) and error type.

  • The Expanded Dataset: We will clean the existing 100 records and generate/verify 20-30 new records for Latinx and Asian-American topics to demonstrate the database’s capacity for growth.

  • Data Visualizations: Charts comparing error rates or types across different demographic categories.

Feasibility Assessment

  • Current Status: High feasibility with room for growth. We have a “Day 1” dataset (100 records) to start building the site immediately. The expansion into new histories provides a meaningful research task for the semester without overwhelming the team.

  • Skills Needed:

    • Frontend Dev: To build the site structure and search interface.

    • Research Leads (Crucial): To generate and verify new prompts regarding Latinx, Asian-American, and white American history (using JSTOR/Library of Congress, etc.).

    • Data Curator: To ensure metadata standards match across different historical categories.

  • Barriers: The main challenge is verifying new data accurately.

Skillset: Michael

Whenever I am asked what are my “skills”, I’ve always struggled to pinpoint the areas I excel in. Throughout my years,  I learned a lot of random things, but nothing was mastered. Nevertheless, I would say my most developed skill sets revolve around educational technology and accessibility.

Project Management:
As part of my daily work, I manage several projects over 3-6 month stretches with small teams. Helping to manage things like scheduling, roadmap planning, deadlines, etc., and all the fun stuff in between. It is something that, over the years, has become almost second nature to me in most cases.

Development:
I do occasionally use HTML and CSS fairly often at my job. It isn’t something I’d say is my speciality, but rather something I picked up along the way as a foundational understanding. I do, however, possess a fairly developed skillset of multimedia creation. I’ve created videos, images, icons, banners, etc., and still do semi-often.

Documentation:
Oddly, I do like writing instructions and technical/process documentation. I have a good amount of experience in this area and don’t mind assisting with this. The documentation preparation I do most often involves writing methodological processes and ideas.

Research:
This is something that I “should” be good at, but could use a lot more development in. Digging through academic/scholarly journals, archives, and books has always seemed daunting to me. While I have done it in the past, I am far from an expert in it. Many times when doing academic research, I feel like I am searching blindly and just hoping for the best. It is something I am willing to learn more about and expand better.

Social Media:
While I understand how beneficial it is within our field, I tend to stay as far away as possible from social media. I believe I have an account for most platforms, but my presence on them is nearly non-existent. I do try to leave as little of a digital footprint as possible for my own personal reasons. I would prefer to leave this area to someone else.

Skillset: Aaron

I am just shy of 30 years of full time experience as an information systems professional. Currently I manage a development team at the United Nations Dag Hammarskjöld Library, which means I mainly develop library information systems, but I’m also responsible for IT security, DevOps, and cloud infrastructure.

I’ll use a rubric similar to what others are using, but especially with information systems, as I’m fond of saying, I don’t even really know at this point what I know.

Project Management: While I’m not certified in any particular methodology, I have been practicing project management for many years now. I am comfortable breaking down tasks and structuring work according to known parameters, such as when building tools and platforms that leverage common patterns, or when aiming for clearly defined outcomes. That said, I wouldn’t consider myself particularly good at this, especially when the scope is less well defined.

Development: This is a strong point for me. My current development stack includes Python, HTML, JavaScript (both server side and client side), and CSS, backed by various databases: MongoDB, Ontotext GraphDB, and Postgres. I’m also familiar with integration of search engines.

Design/UX: Because of the size of my team, I have to moonlight as a UX professional. I have a basic grasp of design and UX concepts, but this is certainly not my strength. That said, I learned HTML programming in the 90s like many others did, by looking at sites I liked and trying to copy them. That same sensibility has served me well enough to date…

Graphics Design and Art: I am capable with digital image creation and basic editing, and I like to make logos, art, and such. Who knows if we’ll need any, but I thought I’d throw it out there.

Infrastructure and Deployment: This is an aspect that I haven’t seen covered as often as other aspects. I have a strong grasp of the components necessary to deploy web applications, keep them online, and ensure they can be maintained, especially on a budget.

Outreach/Social Media: I consider myself chronically allergic to publicity of any kind, which may seem like a funny thing to hear from someone who has been blogging publicly for many years, posts plenty on social media, and even publishes things for people to buy. All that’s to say I haven’t the first clue how to actually market anything. I could stand to learn!

Documentation: Since I do like to write, I also like to explain things. I’m always eager to help structure documentation that serves different audiences, though I am not always as diligent in filling it in.

Research: I like to think this is something I know how to do, but so far in my Digital Humanities journey, I have found that research in a humanities context feels substantively different from what I had done many years ago in my Information Systems MS, even while the methods themselves are basically the same. That said, I feel pretty confident in my research skills.

Skillset Post – What I can (and can’t, but want to) do

I am a writer and an editor, with a focus on internet and digital cultures, and art. My skills include:

Copy writing: I can write anything — web copy, social media copy, newsletters. Essays, presentations, critical papers, white papers. Anything! In English and Spanish (and French if I have a dictionary.)

publicity + social media management: I’ve been working in media for over seven years. I know the ins and outs of getting media coverage and fitting into the “discourse.” My specialty (and years of contacts) are deeply tied to all things art, culture and technology. I know the landscapes well and am confident I have the insights and contacts to help our project reach the people who would be most-interested in it. While I doubt we’d ever pursue media coverage in a traditional sense, I know how to build a community using social media and am familiar with all the platforms and alternatives ways of building engagement.

publishing: Newsletters, zines, printed matter. Social media is great but publishing is sometimes a more effective means of creating a community around a project and putting it in people’s hands. I know how to produce small-runs of printed matter as well as set up digital zines, newsletter platforms etc.

project management: I have experience managing groups and intricate workflows.

Research: I am working journalist (and budding academic), and I feel confident in my research skills: courthouses, archives, libraries, social media rabbit holes.

Development: Not very robust here, I know the bare minimum of HTLM, CSS, etc. I can read through a GitHub and get the gist of whats going on. Would love to develop these more in an assistive capacity. Don’t have the knowledge to lead anything here but I am eager to refine these skills and be of substantive assistance. I am particularly looking to get close to any data cleaning, dataset-curating, or database-related projects.