Speaker
Description
Research software engineers often work in environments where priorities shift quickly, projects overlap, and responsibilities are not always clearly defined. There is always another scientist to support, another bug to fix, or another deadline to meet. Early in my RSE career, I have found that surviving the day-to-day work is only part of the challenge. While this work is necessary, so is finding ways to intentionally grow, both individually and as a team, while still meeting the immediate needs of scientific projects.
This talk explores tools and practices I have encountered outside of research software and adapted to navigate that balance. These include setting longer-term and time-bounded goals, improving ownership and knowledge sharing within teams, and advocating for better processes without just adding overhead.
Rather than presenting a universal solution, I will share what I have tried, what has helped, and what questions remain as I continue building my own RSE toolbox. The goal is to start a conversation about how we can move beyond the next sprint while staying responsive to the unpredictable nature of research software.