My opinion is that it's a good idea when/if the project is well-written up and the student and advisor are confident in the work.
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.
-
But that's just my advice and opinion, you don't have to do it — but I think it's a good thing to do esp. since student's depend on advisor
-
for guidance and help. I know an undergrad who published with his supervisors and the paper had to be retracted. I think that's a horrible
- 2 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.