Having just submitted a paper on Friday (yay!) I thought I would write this week about the process of letting go. This paper has been a long time in the making (it is based on my Ph.D. work, and as some people have recently pointed out, epsilon is not all that small anymore). There were many reasons it took me so long to submit, but one of the main ones is that the paper still felt like it wasn’t done. This is why I say that we let go of papers, we don’t really finish them. <\/p>\n
For accomplishing many things in life, it helps to have a deadline. I was thinking of submitting my paper to Journal X. Every week that I worked on it, I decided it wasn’t “finished”, and I would tell myself\u00a0 “It’s OK, I can just work on it for one more week and then submit”. If you’re not careful, this can span years of your life (like with yours truly). So give yourself a deadline. Just make a date up, pretend like you’re going to be fired from mathematics if you don’t finish (eventually you will be, right?). In my case, I decided to apply to a conference instead (with some encouragement from people at a conference I’m currently attending). Publishing in a conference proceedings volume is usually not as prestigious as in a journal, although of course that depends on the journal and the conference. In the case of computer science, for example, proceedings volumes are the normal place to publish your work. Since the work I did was computational and the conference is modeled after computer science conferences, people have told me this should be counted (if accepted) as a good publication. The advice I have gotten, with respect to presenting this publication (again, if accepted) to a personnel committee, is to add to my tenure dossier all of this information. You need to make your case for tenure, so explaining how Journal X or Conference Proceedings Y rank in your area is always a good idea. At any rate, if not accepted, the paper is much closer to finished than it was a week ago, and I will get a chance to incorporate the feedback from the referee.<\/p>\n
Another thing that is good, in life and in math, is asking people for help. My Ph.D. advisor helped me a lot with the earlier drafts. I radically changed much of what was in the paper thanks to his comments, and I agree that it makes a lot more sense now. As I said earlier, this past week I have been at a conference, and one person here took it upon herself to be my cheerleader\/proofreader, which made a huge difference. Just having someone read your writing and tell you about how to use the DeclareMathOperator command in LaTeX<\/a> so your operators are not italicized is amazing, but even better is the fact that they are also telling you if a definition is not clear or whether you really need to write the proof of Lemma A. She definitely gets a big acknowledgement in the paper. But this is not the only way to get help. One thing I haven’t done but many people do is to post an almost finished version on the Arxiv<\/a>. People do read these papers and give feedback sometimes, but it’s not a sure thing.<\/p>\n A big source of feedback is also the referee report, although that may be tainted by feelings of rejection (if the paper is rejected). But still, you cry about it for a day, and then you have some potentially useful information (unless you are told, like a friend of mine did recently, to enlist the help of a “native English speaker”, being one herself). In general, you will have a better idea of what is not clear, whether there are gaps in your arguments, and sometimes you might even find out you are wrong. These are all good things to know! Hopefully, instead of the paper being rejected, you get a “review and resubmit”, which is another step towards getting your paper to that “finished” form.<\/p>\n So now I open this up for discussion, since I’m sure there are wiser, more experienced mathematicians who could give some great advice. How do you motivate yourself to finish\/submit a paper? Where and who do you send it to? Is there a process you follow that you find is efficient?<\/p>\n <\/p>\n <\/p>\n