  Ascertaining reproducibility of scientific experiments is receiving increased
attention across disciplines. We argue that the necessary skills are important
beyond pure scientific utility, and that they should be taught as part of
software engineering (SWE) education. They serve a dual purpose: Apart from
acquiring the coveted badges assigned to reproducible research, reproducibility
engineering is a lifetime skill for a professional industrial career in
computer science. SWE curricula seem an ideal fit for conveying such
capabilities, yet they require some extensions, especially given that even at
flagship conferences like ICSE, only slightly more than one-third of the
technical papers (at the 2021 edition) receive recognition for artefact
reusability. Knowledge and capabilities in setting up engineering environments
that allow for reproducing artefacts and results over decades (a standard
requirement in many traditional engineering disciplines), writing semi-literate
commit messages that document crucial steps of a decision-making process and
that are tightly coupled with code, or sustainably taming dynamic, quickly
changing software dependencies, to name a few: They all contribute to solving
the scientific reproducibility crisis, and enable software engineers to build
sustainable, long-term maintainable, software-intensive, industrial systems. We
propose to teach these skills at the undergraduate level, on par with
traditional SWE topics.
