@MCDuncanLab @Drugmonkey Sorry, strong disagreement on a couple of points. Before that, I’ll just say that Tom Dietterich is a well-known and highly respected scientist and Prof. Emeritus of Computer Science. He is the kind of person I would 100% trust to get it right on a co-authored paper and his conduct is unimpeachable. He sets a high bar, yes, but it is also consistent with excellence in the conduct of science.
If you co-author a paper with someone who is very junior or less than stellar in their scientific methodology or standards of writing a scientific paper, that’s on you because you made the decision to delegate more to them than was reasonable. I’m not saying you must avoid working them, only that you hold them to AT LEAST the standards you follow yourself.
For junior collaborators, finding bugs in their reports is a mentoring opportunity. For senior co-authors who provide slipshod work, it is an opportunity for you to take corrective action to protect your own reputation and also to reconsider the collaboration. Collaborators don’t need to be experts in each other’s area, but they do need to be able to interrogate each other’s contribution. From the readers’ perspective, co-authors are judged together on the content.
Can we all agree that citations must not be fabrications? That is easy enough to check. Accuracy and relevance are harder if you don’t know the subject matter, and this is where it gets dicey. People have different ideas about what to include and that is to be expected. It is fair to say that there is some burden on the reader to make this judgement. As a minimum, citations ought to be useful in some way, especially if they are not discussed in the body of the paper.
Finally, if somebody has not made an original and substantive contribution to the work described in a paper, they should not be a co-author. The responsibility is on them as well to decide if they should be listed or not. Padding their resume is not a good justification.