The next Byte-sized RSE session, covering code style and linting, will take place on Tuesday 28th February, 13:00-14:30 GMT.
SSI Fellow Jannetta Steyn tells us about the exciting work she and others have done to create and test CarpentriesOffline, a version of The Carpentries workshops that uses a Raspberry Pi (RPi) computer to take the lessons offline when there is limited or no access to the internet.
The next Byte-sized RSE session, covering continuous integration, will take place on Tuesday 17th January, 13:00-14:00 GMT.
The next Byte-sized RSE session, covering testing your python code, will take place on Tuesday 13th December, 13:00-14:00 UK.
Photo by KOBU Agency
After the success of last year’s pilot, the Society of RSE’s mentoring scheme has been launched fully for 2023.
Following the success of the first Byte-sized RSE session in October, session 2, covering collaboration and code review via GitHub will take place tomorrow (Tuesday 15th November), 14:00-15:00 GMT.
Today (13th October 2022) marks International RSE Day, organised by the International Council of RSE Associations. This is a fantastic opportunity to celebrate the contribution of research software engineering (RSE) to UK science. Software is used everywhere in science, from modelling COVID-19, forecasting our future climate and analysing vast quantities of social media data.
Byte-sized RSE is a new series of short interactive tutorial sessions where you can learn key skills to improve how you write and manage your research software in just 1 hour! The first session will take place on Tuesday 18th October at 13:00 BST on Zoom.
By Mike Jackson, Software Architect.
First published on 23/11/17. Updated on 08/09/22.
This guide is the first in the Unit Testing for Scale and Profit series. In a project where changes are frequently made to research software, it is helpful to know that the code still works as expected. In our last two episodes, we looked at the benefits of having a set of unit tests and how we can use test parameterisation to write numerous tests efficiently. However, particularly with projects involving more than one contributor, it would be good to have assurance the software still works without everyone having to pull down all the changes and test them. In this guide, we'll be looking at…