Code for Thought Is Research Software A Tangled Mess?
Sometime in early 2021 there was a bit of excitement on the Research Software Engineering Slack channel. It was all about a blog post called: "Research Software code is likely to remain a tangled mess". The author, Derek Jones, is quite critical of what we are doing with software in research. I accept that not everybody is a fan of Research Software Engineering and I reached out to Derek, who kindly agreed to talk to me for this episode.
In our discussion we touch on a number of subjects, from sustainability, best practices to testing.
Links:
http://shape-of-code.coding-guidelines.com/2021/02/21/research-software-code-is-likely-to-remain-a-tangled-mess/
Derek's book on Evidence Based Software Engineering
http://www.knosof.co.uk/ESEUR/
Leprechauns of Software Engineering (mentioned in the discussion)
https://leanpub.com/leprechauns
Thank you for listening! Merci de votre écoute! Vielen Dank für´s Zuhören!
If you're like to support this show, you can leave a little tip at
https://en.tipeee.com/code-for-thought-podcast/
Contact Details/ Coordonnées / Kontakt:
- Email mailto:peter@code4thought.org
- UK RSE Slack (ukrse.slack.com): @code4thought or @piddie
- US RSE Slack (usrse.slack.com): @Peter Schmidt
- Mastodon: https://fosstodon.org/@code4thought or @code4thought@fosstodon.org
- Bluesky: https://bsky.app/profile/code4thought.bsky.social
- LinkedIn: https://www.linkedin.com/in/pweschmidt/ (personal Profile)
- LinkedIn: https://www.linkedin.com/company/codeforthought/ (Code for Thought Profile)
This podcast is licensed under the Creative Commons Licence: https://creativecommons.org/licenses/by-sa/4.0/