Transform-to-Open-Science
Transform-to-Open-Science copied to clipboard
nasa
OS 101 module 1 lesson 4: additional fear
An additional fear that is common in not sharing software is embarrassment about the quality/style of the coding (not that the code doesn't do what it should, but just how it is written)
@bressler95tops - Although this may be true, this does not require a change in the content at this time.
It's clearly up to you to decide what to include, but I will say that this is one of the top fears that's shown up in surveys about why people don't share their software
@danielskatz - Apologies, to clarify, we meant that there is no change to the content via GitHub at this time. Because the information is laid out in a table, this will have to be added separately. We can include another row in the table to show something like "lack of confidence" as an example fear. Sorry for the confusion - we can fix this, just not via GitHub directly.
@danielskatz and @bressler95tops - Thank you for your patience as the OS101 Team has revisited this issue. We have reviewed and discussed a new addition of simple text, into the existing table. As we recently realized that this is a simple table and not a complex graphic. :) @bressler95tops - within the "What if my code is wrong?" section, please change the text to "What if my code is wrong or inelegant?". Also change the text in the corresponding paragraph to "It can be intimidating to share your research materials publicly, because someone might find a mistake or inefficiency. But isn’t it better for science if we can quickly find and fix mistakes or improve quality? Peer review is a core pillar of the scientific method, and is a mechanism for others to help find and correct mistakes and make improvements. To make this work, we will need to be more open to finding and fixing mistakes or inefficiencies. It’s true that in many science communities, a mistake is considered a failure, or a certain style may be considered lackluster. However, open science policies aim to change the perception of mistakes from that of failure to a step in the discovery process that can be aided with open community feedback.
Thanks @katblanchette. One minor thing, I noticed that the original phrasing is actually "What if my work is wrong?" and the rest of the section also speaks generally about work and not necessarily code even though it can certainly apply to code. So I changed the new title as 'What if my work is wrong or inelegant?'.
Minor tweak but let me know if you think it should still be code and I can swap it. Otherwise, I have made the change with the title and definition. You can view the PR that addresses this in PR #826, and MOOC developers can view this in the 'files changed' tab. Let me know when the MOOC developers are able to get this fix added.
