Codecheck each others work (before submission or before sharing code online)
Codecheck benchmarks (and share the frustration)
Immediate use for your own research
Use existing facilities
Could be done before submission
Convincing colleagues can be difficult
More work beforehand, focus might shift from content to skill
Join the discussion: #TeachingByReprohacking on Twitter and the dedicated Teaching Channel on our Slack
Focus on one domain (more or less broadly)
Similar data (size, privacy issues etc)
Similar scripting and programming languages
Get to network with peers outside your lab
Requires a bigger organizing team
Interdisciplinary fun!
Share with people with similar enthusiasm
Meet people that are in different communities (E.g. ReproducibiliTea)
Keep it to one programming language and interdisciplinary
Cluster around one research topic across domains
be creative and make this format your own!
Slides used for community call: https://docs.google.com/presentation/d/1dzNo0w1a1Aug7OvkeyZygAuUlHK8dgYyv8X-FXgYj5w/edit?usp=sharing
Collaborative Notes of the Community Call: https://hackmd.io/@DGawehns/Sk5K1GYa8/edit