提交最终稿,而非初稿
提交最终稿,而非初稿
第一次就做对根本不重要。最后一次做对才至关重要。
— Andrew Hunt 和 David Thomas,《程序员修炼之道》
这是”提交前校对并仔细检查论文”的推论。
如果你在阅读论文时仍在发现排版错误或其他错误,或者仍在为论文添加结果和评论,那么现在还不是将论文提交给期刊的时候。
即使你出于某种原因急于发表论文,准备不充分的论文被拒的可能性更大,可能会招致重大修改的要求,并且通常会减慢论文的处理速度,以至于等到论文形式更完善再提交反而会更快。
出于类似的原因,如果你要将论文副本发送给同事,那么将一份已经校对过并且已经在改进表述方面投入了大量工作的论文版本发送给同事,而不是可能需要占用同事更多阅读时间的早期草稿,将是体贴的做法。
Submit a final draft, not a first draft
It’s not at all important to get it right the first time. It’s vitally important to get it right the last time.
— Andrew Hunt and David Thomas, “The pragmatic programmer”
This is a corollary to “Proofread and double-check your paper before submission.”
If you are still finding typographical or other errors in the paper while reading it, or if you are still adding results and commentary to the paper, then it is not yet time to submit the paper to a journal.
Even if you are for some reason in a hurry to publish your paper, a poorly prepared paper will have a greater chance of rejection, may incur demands for major revisions, and will in general slow down the processing of your paper to the extent that it would have been faster to wait until the paper was in a more final form before submission.
For similar reasons, if you are sending a copy of your paper to a colleague, it would be considerate to send that colleague a version of the paper that already has been proofread and to which a significant amount of work has already gone into improving the exposition, rather than an early draft which may take up more of your colleague’s time to read.