How did you hear about the CaDiR community?
When I joined the University a couple of years ago, we were exploring how to establish a new community of practice around research software. During this process, Gillian Sinclair (Research IT Relationship Manager), introduced me to CaDiR, suggesting it could be the perfect space for our initiative. We started out via CaDiR and it proved to be a great fit, as it provided us with well-established channels to connect and engage with the broader community – and gave the Manchester Research Software community (MRSC) a strong foundation.
What is your role at the University and how does it interact with the MRSC community?
I am a Research Software Engineer (RSE) in Research IT and a Software Sustainability Institute Fellow. Research software and community engagement lie at the intersection of both these roles, which naturally led to my involvement with MRSC. I had already been planning to focus on community-building as a part of my fellowship, even before joining Research IT – so it worked out perfectly when I was provided support in pursuing this commitment as an RSE.
What would you like to see the MRSC community doing over the next 12 months?
I believe the core idea behind MRSC has always been to create a self-sustaining community. Over the next 12 months, we’re focused on making the community more collaborative by encouraging discussion-based events. My hope is that we can build on this momentum to develop a community that runs smoothly and independently, with minimal friction.
What do you hope to come out of the MRSC community?
I hope we can foster a welcoming and accessible space for people across all fields and experience levels at the University to engage in meaningful discussions around research software. Our goal is to create an environment where members can collaborate, support each other, share ideas and have a place they can turn to for help and advice. We also aim to spark new opportunities for collaborations and networking for our community members as they participate in the events and discussions. Furthermore, it is important for us to build connections and collaborate with other groups at the University doing valuable work such as the Office for Open Research, the Software Sustainability Institute and other CaDiR communities.
How can members of the MRSC community support you / get involved?
I believe the simplest, yet the most important, way to support the community is by engaging with it. This can range from attending meetings and giving talks to starting discussions, asking questions or even posting on the CaDiR space. Spreading the word and inviting colleagues is another great way help increase our visibility. Everyone is welcome to join our meetings, and we’re always happy to involve members in the organising and planning stages.
How did you get into your domain i.e. become an RSE?
I have a background in computer science, and as an undergraduate student, I came across the Princeton Research Computing, which first piqued my interest in research software. I worked as a research fellow there and had the opportunity to explore open-source and research tools in particle physics while working alongside research software engineers. This experience was incredibly impactful for me and made me realise how much I enjoyed being a part of the community. Attending SSI’s Collaborations Workshop was another opportunity that solidified my interest in becoming an RSE, and I joined the University shortly after that.
What does your role as an RSE involve?
As a research software engineer, I wear a few different hats. My primary responsibility is software engineering, where we collaborate with researchers to help develop software as well as provide technical expertise. Another key aspect of my role involves designing and delivering training across the university, ranging from beginner-level Git and Bash courses to more advanced Intermediate Python training. Community engagement and collaboration are also central to my role – this includes supporting the MRSC, working with the SSI, doing outreach, participating in workshops as well as collaborating across the wider UK RSE community.
What do you enjoy most about being an RSE?
The diversity of our work and the possibility of learning something new every day is my favourite part of being an RSE. It’s exciting to work on interdisciplinary projects and have the chance to share expertise with a wide group of people in the form of training and community work.
What is your favourite project you have worked on?
It’s a tough choice to make, as all the projects I’ve worked on have been enjoyable! One project that stood out for me was the Prehab Mobile App, which was designed to extend a study looking at prehabilitation for patients due to surgery. Not only was it incredibly impactful, but it also helped me apply many of the key concepts I had learned as a research software engineer. It was a new experience for me, offering insights into how clinical studies are run, while also advancing my understanding of best software engineering practices.