Jay_millerjay Categories Science
7 days
30 days
All time
Recent
Popular
It was great to talk about reproducible workflows for @riotscienceclub @riotscience_wlv. You can watch the recording below, but if you don't want to listen to me talk for 40 minutes, I thought I would summarise my talk in a thread:
My inspiration was making open science accessible. I wanted to outline the mistakes I've made along the way so people would feel empowered to give it a go. Increased accountability is seen as a barrier to adopting open science practices as an ECR
It also comes across as all or nothing. You are either fully open science or your research won't get anywhere. However, that can be quite intimidating, so I wanted to emphasise this incremental approach to adapting your workflow
There are two sides to why you should work towards reproducibility. The first is communal. It's going to help the field if you or someone else can reproduce your whole pipeline.
There is also the selfish element of it's just going to help you do your work. If you can't remember what your work means after a lunch break, you're not going to remember months or years down the line
Thank you again @JamesEBartlett for a fantastic talk (with a really nice personal touch) on reproducible workflows!
— RIOT Science Club Wolverhampton (@riotscience_wlv) February 16, 2021
Thanks especially for the co-leads @IMLahart for co-hosting and @DrManiBhogal for nabbing James!
Slides: https://t.co/CNqxzOhch1
Video: https://t.co/YjHEHuRJlz
My inspiration was making open science accessible. I wanted to outline the mistakes I've made along the way so people would feel empowered to give it a go. Increased accountability is seen as a barrier to adopting open science practices as an ECR
It also comes across as all or nothing. You are either fully open science or your research won't get anywhere. However, that can be quite intimidating, so I wanted to emphasise this incremental approach to adapting your workflow
There are two sides to why you should work towards reproducibility. The first is communal. It's going to help the field if you or someone else can reproduce your whole pipeline.
There is also the selfish element of it's just going to help you do your work. If you can't remember what your work means after a lunch break, you're not going to remember months or years down the line
Why are lunch breaks important for #code?
— Dr Rebecca Hirst (@HirstRj) February 11, 2021
If you can't remember what your variable names refer to after lunch, you sure as hell won't remember in 3 months.
