🤖 AI Summary
As AI coding agents become increasingly prevalent in scientific research, the long-standing assumption that “at least one human understands the intent behind every piece of code” is being undermined, jeopardizing code readability and collaborative maintenance. This study investigates this emerging challenge through contextual inquiry, a survey of over 800 research software developers, case studies, and empirical analysis of version control logs. We introduce the concept of “landmarking strategies,” revealing how researchers explicitly demarcate human-readable code from agent-specific context. Our findings also uncover non-standard uses of shared infrastructure such as Git, highlighting risks of destandardization in current practices. The work offers critical design implications for improving the maintainability of scientific codebases and enhancing team collaboration in agent-augmented research environments.
📝 Abstract
Scientific research involving code has long rested on the assumption that at least one person understands why the code exists. As scientists adopt coding agents, this assumption is breaking down. Drawing on an ongoing contextual inquiry of scientific programmers working with agentic tools (four cases to date), a survey of over 800 scientific programmers, and my own analysis workflows, this position piece describes how scientists are inventing personal conventions, "landmarking strategies", for marking which artifacts in a codebase are meant for human understanding and which are context for agents. They repurpose shared infrastructure (version control especially) in idiosyncratic ways, and I argue that this quiet de-standardization could complicate collaboration in teams with heterogeneous software practices. Alternatively, teams that explicitly delineate what is human-readable versus agent context will be better able to develop, document, and maintain scientific code.