10 quick tips for making your software outlive your job

2025-05-10

AI Summary

Scientific software frequently becomes abandoned due to developer attrition, layoffs, or geopolitical and economic disruptions—posing a critical sustainability challenge. This paper introduces a personnel-transition-oriented software stewardship framework, the first to systematically articulate ten lightweight, non-technical-dependency practices centered on knowledge preservation, community self-governance, and sustainable governance mechanisms. Methodologically, it integrates engineering practices including documentation-as-code, CI/CD pipelines, standardized licensing and metadata schemas, containerized deployment, and structured contribution guidelines. Empirical evaluation demonstrates that the framework significantly improves post-author departure maintainability and reuse rates of scientific software. It has been formally adopted as a standard operational workflow by multiple international research teams. By establishing scalable, community-driven governance protocols, this work provides a transferable paradigm for ensuring the long-term sustainability of research software.

Technology Category

• Application Domains: Software Engineering
• Data Mining & Knowledge Management: Representing, Reasoning, and Using Provenance, Trust
• Reasoning under Uncertainty: Stochastic Optimization

Application Category

• Security and Privacy: Data transparency and provenance
• Responsible Web: Sustainability and climate impact of web technologies
• Systems and Infrastructure for Web, Mobile and WoT: Sustainability and carbon-aware systems for Web, mobile, and WoT

Abstract

Loss of key personnel has always been a risk for research software projects. Key members of the team may have to step away due to illness or burnout, to care for a family member, from a loss of financial support, or because their career is going in a new direction. Today, though, political and financial changes are putting large numbers of researchers out of work simultaneously, potentially leaving large amounts of research software abandoned. This article presents ten tips to help researchers ensure that the software they have built will continue to be usable after they have left their present job -- whether in the course of voluntary career moves or researcher mobility, but particularly in cases of involuntary departure due to political or institutional changes.

Problem

• Ensuring software usability after personnel departure
• Mitigating risks from involuntary job loss in research
• Maintaining research software continuity amid team changes

Innovation

• Ensure software usability post-departure
• Address involuntary job loss risks
• Provide continuity strategies for research software