Notices by Heidi Seibold (heidiseibold@fosstodon.org)

Happy international Day of Women and Girls In Science!

Let's be role models for the next generation of scientists and show that you can be a scientist AND wear a flower skirt 🌸 - if you like.

Does anyone have good storys about why it makes sense to

✅ Get organized
✅ Create useful code
✅ Write code together
✅ Use automation

for research code / software that I could share in training?

Something along the lines of "This one time I forgot to document my code something awful happened..." or "When I got onboarded to this code project it was amazing to see that...".

#RSEng

I am collecting templates for setting up a #FAIR and #reproducible projects.

Here's what I already have:

Research:
🗃️ GIN-Tonic standardized research folder structure: https://gin-tonic.netlify.app/standard/
🗃️ My research project template: https://github.com/HeidiSeibold/research-project-template
🗃️ R analysistemplates: https://github.com/jonas-hag/analysistemplates

Code:
📦 Python cookiecutter template: https://github.com/Materials-Data-Science-and-Informatics/fair-python-cookiecutter
📦 R devtools: https://devtools.r-lib.org/

🔍 Anything missing? 🔎

The full list will be published in an upcoming newsletter post.

Scientific fraud hurts everyone 😱

It hurts the trust in science, it hurts the scientists who build upon problematic research, and of course it hurts the people who were supposed to benefit from the research (think e.g. medical research).

So how do we avoid fraud? In my opinion, #OpenScience can be part of the solution. But Open Science can be so much more: In my opinion it is a good way to improve scientific rigor.

Newsletter post:
https://heidiseibold.ck.page/posts/avoiding-fraud-and-improving-rigor-through-open-science

Most important learning this year:

I won't always be able to finish everything by the end of the day. It will feel shitty, but it is not the end of the world. It is a necessary evil of the type of work I do. I can be super organized and it will happen anyway.

In my version control courses I often get the question:

🤷 "Should I use GitHub or GitLab?" 🤷

If you are a researcher, I think you can answer that question for yourself by answering the following two questions:

🤝 Where is my community?: Go where your community is.

🏠 Does my institution have a GitLab instance?: If yes, it is often a good idea to at least start your project on the institutional instance. Copying to GitHub later on is done in <5 minutes.

Do ya'll agree with my take? 😉

I teach not using spaces in file names as good practice, because it is annoying when coding.

But when I create a duplicate file, the standard on IOS is to name it "duplicate-name 2.pdf".

Why? 🤷

What is the opposite of in-house training?

@geospacedman haha yes, that's exactly what I said and then I learned what an out-house is 🤣

Thanks for the image to support non-native speakers learning new words.

#OpenScienceChallenge

👉 Do you want to become a better researcher?

👉 Do you feel insecure about making your work more open?

Sign up to join us for a month full of
✅ reflections on your career,
✅ discussions about the way we practice science, and
✅ practical steps towards #OpenScience

12 emails 💌 over the course of a month that are designed to help you on your Open Science journey.

https://heidiseibold.ck.page/opensciencechallenge