@o_guest cc'ing you because I thought of you when writing this :D
I'm not saying you have to but putting something out there without checking isn't good practice IMHO.
-
-
ok but which supervisor rereads the program of a phd student, checking for programming bugs
-
Mine did during my phd but that's actually not how any software testing is done. Either way if you put something out there it's important
-
for science and your reputation to check. I can't force you to do this obviously.
-
but no one re-reads my program. we share a lot of code though, so that's how we discover bugs
-
I'm confused because you said "but which supervisor rereads the program of a phd student, checking for programming bugs" I assumed you meant
-
that checking for bugs is equal to reading somebody's code. Both are useful but not synonymous.
-
Regardless, I am convinced that if you releave a preprint or anything online with your name on it you should check it for bugs as well as
-
check the whole project is OK. I think it's natural to do this, but yes, of course, it's time-consuming.
- 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
