Ten Simple Rules for Catalyzing Collaborations and Building Bridges between Research Software Engineers (RSEs) and Software Engineering Researchers (SERs)

Which rule resonates most? Which is most challenging to enact? Vote with a sticker or through our QR linked survey Plus, the QR code will help you find our paper in Computing in Science & Engineering! Secure Institutional Support All parties should seek funding, advocate for institutional recognition of RSE and SER roles, and promote frameworks that support collaboration (e.g., joint appointments and recognition programs). Maintain Vigilance and Recognize When Collaborations Are Off Course To sustain a win-win relationship, SERs and RSEs must regularly review progress and concerns. Actively Advocate for Each Other RSEs and SERs should showcase one another’s work to demonstrate respect and the value of collaboration. Maintain an Open Mind Toward Emerging Challenges Collaborators should be adaptable and ensure continuous dialogue to identify new challenges and solutions. Ensure Mutual Benefit in Collaboration Both parties must earn immediate and long-term value. Incentive schemes must be understood. Authorship and leadership responsibilities should be explicitly addressed. Recognize The Two Communities Are Different RSEs and SERs must appreciate one another' s unique roles and cultures, celebrate their strengths, and avoid assumptions. Identify the Intersection of Shared Research Software Challenges Collaborations must address common challenges that are practically significant and academically valuable. x SERs Must Engage with RSEs in Their Professional Environments SERs should appreciate RSEs’ institutional obligations and resource constraints. SERs can gain these insights and build trust by attending RSE conferences, workshops, and talks. Define Clear Goals and Outcomes Open discussion, measurable and well documented objectives, and regular check-ins ensure progress, though flexibility is needed too. Acknowledge Collaboration Is Not Going to Just Happen Partnerships must be deliberate; proactive initiation, inquiry into mutual goals, and consistent investment are needed. Images generated with ChatGPT. Ten Simple Rules for Catalyzing Collaborations and Building Bridges between Research Software Engineers (RSEs) and Software Engineering Researchers (SERs) Nasir U. Eisty, University of Tennessee, Knoxville, TN, USA Jeffrey C. Carver, University of Alabama, Tuscaloosa, AL, USA Johanna Cohoon, Lawrence Berkeley National Laboratory, Berkeley, CA, USA Ian A. Cosden, Princeton University, Princeton, NJ, USA Carole Goble, University of Manchester, Manchester, U.K. Samuel Grayson, University of Illinois at Urbana-Champaign, Urbana, IL, USA 1 2 3 4 5 6 7 8 9 10