Publishing our code and data is an important Open, Reliable, and Transparent practice to ensure the reproducibility of research. To facilitate the production and reviewing of code, Arthur Rodrigues and Natalie van Dis hosted the Code Club meetings of October and November with a Hackathon aimed at Creating a Code Standard.
Code Club returned from midyear break with a training session on local Open Science meet-ups. Kaija Gahm shared her experiences with running weekly “Hacky Hours” in her department at the University of California, Los Angeles, which serves as a collaborative coding and working space. We discussed the value of such local Open Science meet-ups and how to organize them.
In June’s Code Club session, Steffi LaZerte hosted a workshop on how to code our own website. By walking participants through the code underlying her own website, she showed us how to use Markdown and Quarto to create and host a website on GitHub.
In May’s Hacky Hour, we did a code review exercise using the 17-step checklist for Ecology and Evolution. Participants reviewed each other’s code or that of already published papers and discussed what would constitute the “perfect” piece of Open, Reliable and Transparent (ORT) code.
In this month’s Training Session, Stefan Vriend, Freddy Hillemann and Joey Burant hosted a workshop on how to code review a manuscript, using a checklist they developed for Ecology and Evolution.
The Member Engagement Committee runs Code Club every third Tuesday of the month. Time can vary depending on the host and will be announced at least two weeks in advance on SORTEE’s Slack. In this month’s Hacky Hour, 9 participants shared their code mistakes, starting up the SORTEE library of code mistakes! The goal is twofold: the normalization of coding errors and building a resource of (common) code mistakes that you can use during code review.
Copyright (c) 2024, SORTEE; all rights reserved.
Website by M. Lagisz and by R.E. O'Dea. Logo design by Szymek Drobniak. Template by Bootstrapious. Ported to Hugo by DevCows.
