One thing I've noticed about a lot of inward-facing HCI topics is that they are very focused on "the code", but that's just a portion of what's involved in common working loops. I spend a lot of time thinking about stuff that surrounds the code, and it's clear that large orgs are starting to as well, if they haven't already, though there is little convergence on the topic. Am I wrong about these topics not being in the literature? Am I not looking for the right topics or terms, or is this not happening at all in academic research? And if it's not happening, how do we draw researchers' attention to it?
What specifically do you want to draw researchers attention to? Can you give an example?
Your example above of "common working loops" and essentially think time around coding has been studied extensively previously. Before making recommendations, I want to first ensure we're on the same page.
Potential keywords (and conferences) are CSCW and CHI.
I'm talking about the secondary work that goes into software, things like environment setup, building artifacts, producing ancillary tooling, and deployment.
I know these might be considered disparate, and I'm intentionally omitting topics that I know are studied, such as formal verification and fuzzing.
I was joking with my spouse, who is a methodologist in medicine, about making a group of researchers set up environments for working on various large open source projects as an example.
Perhaps all of this crosses into operations research?
HCI = Human Computer Interaction[1] for the curious. This is the name for the older research discipline that UX (user experience) grew out of. I'm familiar with the term from reading "An Introduction to Human Factors Engineering" (2004) by Wickens, et al. But wikipedia dates it's first use to a paper by James Carlisle in 1976.
