I will be attending the #SOOCON24 and #stateofopencon and speaking about my work. I will present preliminary research on applying the Do No Harm framework to open source/science interventions.
Grab a ticket - limited free tickets are also available. https://t.co/sgc2KdbF6P.
@ThePSF Maybe it's the sleep deprivation but I don't really understand term 3 of the T&C:
3) Additional Terms. You understand that we may present you with additional terms and conditions ... including on the JetBrains website ...
Can someone explain what this one means?
Applications now open for our next #Neutron Training course in May 2024. This is a practical instrument-base courses for postgrad + post-doc researchers who have little or no experience but whose future research program will make use of neutron techniques. https://t.co/YaOqMgTnT1
@Andrew_S_Rosen Yes one can reimplement from the paper but it delays community benefit, repeats effort on implementation "gotchas" and if code *is* available means wading through complex/irrelevant interfacing details. 2/2
@Andrew_S_Rosen It's so frustrating to see new publicly-funded methods published as a de-facto "exclusive" to one package when it isn't technically necessary. Something has gone wrong with the incentive structure. 1/2
@AndrewBKin@AstroKatie To be clear, by "explanations" I mean "what does this paper say", "what does this figure mean", etc. I think that's a more exciting, open and democratic kind of Sci Comm than the usual "summarise this field in a few easy sentences that make it sound like one man did it."
@AndrewBKin@AstroKatie But then I also see very highly liked/retweeted/viewed posts on LK99 that are much lower quality. Something is incentivising that. The cultists are haunting "For You", not "Following".
@ifndef_define @Andrew_S_Rosen@MaximZiatdinov Here's a cheeky little blog post about bad tests from a @SoftwareSaved event a few years ago! "Five failed tests for scientific software" https://t.co/NdXraAMn5W
@ifndef_define @Andrew_S_Rosen@MaximZiatdinov 70-80% is a good sign. I am slightly wary of code with 95+% coverage as there is a danger Goodhart's Law is at work. It is possible to write tests that technically execute the code branches but don't really stress the problem areas well.
@Andrew_S_Rosen @DrDeCaluwe A _practical_ difference is that when a "unit test" fails it should make it pretty clear where the problem lies and what internal expectation/promise is being violated. Whereas "integration" tests check one path through a lot of code; they are easier to write but harder to fix.