The next Byte-sized RSE session, covering testing your python code, will take place on Tuesday 13th December, 13:00-14:00 UK.
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.
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…
Code review is known to be an effective way to improve software quality, foster peer learning and develop common ownership of a research software project. In practice, a code review is nothing else than a conversation between the author of the code and somebody else providing feedback on coding practices, readability or other aspects of code quality. If this sounds straightforward, an effective code review routine can be tricky to establish. Here are five tips for you to get started with code reviews, or get more of them.
It's 10 years since the term Research Software Engineer was coined at the Collaborations Workshop 2012 and the RSE movement began!
This guide is the second in the Unit Testing for Scale and Profit series.
As our code increases in size and particularly complexity, we should expect our number of tests to increase too, which means more time writing tests. Fortunately there is something that can help with this burden which we'll look at in this guide: parameterised tests!