so it's only a good idea if the supervisor takes responsibility for vetting the work (which is a lot to ask, but would be great mentorship)
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
-
way to start publishing as a student.
- 1 more reply
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.