Core Concepts
Evidence-based practice techniques can benefit research software engineers by promoting career-long learning, professionalization, and better practices in scientific software development.
Abstract
The content discusses the application of evidence-based practice (EBP) techniques, specifically rapid reviews, within a research software engineering team. It highlights the strengths and limitations of rapid reviews, the challenges for RSEs to adopt EBP techniques, and strategies to address these challenges. The study emphasizes the importance of training, incomplete research in RSE contexts, and convincing others to adopt best practices. Recommendations are provided based on experiences and insights from other fields where EBP has been successfully adopted.
Structure:
Introduction to Evidence-Based Practice in Software Engineering
Experience Report on Rapid Reviews in RSE Team
Background on Research Software Engineering Movement
Methodology of Rapid Review Approach
Results on Strengths and Limitations of Rapid Reviews
Challenges for RSEs to Adopt EBP Techniques
Strategies to Address Adoption Challenges
Discussion on Benefits of EBP for RSEs
Threats to Validity Consideration
Conclusion with Recommendations
Stats
"Each rapid review reported in this paper... required 12-20 hours of labor over the course of three to five days to complete."
"Studies suggest that may stem in part from that a lack of shared clarity around roles and expertise."
Quotes
"Rapid reviews help us get unstuck... That kept us from hemming and hawing about it." - Anthony (RR4)
"I found it very useful because you drew attention to papers and topic areas that I wasn’t necessarily aware of." - Henry (RR5)
"If we wanted to explore containerization further... there’s no sense in rolling out a new technology until we’re confident that it’ll work." - Allen (RR4)