|
| 1 | +--- |
| 2 | +layout: post |
| 3 | +title: "Writing rigorous math papers is very time consuming" |
| 4 | +categories: research |
| 5 | +--- |
| 6 | + |
| 7 | +Once again, it has been about 6 months since my last blog post. |
| 8 | +I really need to work on posting incrementally about research in progress, |
| 9 | + otherwise this blog will frequently have large gaps when I'm working on longer projects. |
| 10 | +Also, the isolation from the coronavirus pandemic has caused me to reflect a lot more on career problems and plans, |
| 11 | + and the views expressed in [my previous post]({% post_url 2020-03-27-career-hopelessness %}) |
| 12 | + have undergone some important revisions. |
| 13 | +I will blog about that some more in the near future. |
| 14 | + |
| 15 | +This post isn't about a new project or paper, |
| 16 | + but rather the revisions to the low-rank approximation paper that I submitted for publication towards the end of 2019 |
| 17 | + and [blogged about]({% post_url 2019-09-16-cauchy-kernel-triage %}). |
| 18 | +Much to my surprise, I got the reviews back for the paper in late January. |
| 19 | +The timescale of mathematical publication is notoriously slow, |
| 20 | + so I didn't expect to hear from the journal for at least 6 months. |
| 21 | +I was initially given until the end of March to revise the paper, |
| 22 | + but I didn't even start the revision process until after I finished my last paper for the 2020 APS March Meeting. |
| 23 | +I was able to get multiple extensions from the journal, but eventually they gave me a hard deadline on October 1st. |
| 24 | +It has been a long and tiring journey from the first to the [second version of this paper](https://arxiv.org/abs/1909.06911), |
| 25 | + and I feel like I've grown as a mathematician in the process. |
| 26 | + |
| 27 | +As I previously discussed, the first version of this paper was heavily restricted in scope compared with my original plans for it. |
| 28 | +There were three intended applications that were dropped, and the central proof of the paper was a touched-up version of a proof |
| 29 | +that I wrote several years ago. |
| 30 | +My focus in preparing that proof for publication was correctness rather than clarity, |
| 31 | + and it resulted in a terse and hard to understand final product. |
| 32 | +Also, part of that terseness was minimizing the amount of time devoting to discussing external results that the proof relied upon, |
| 33 | + partly because I did not fully understand those external results. |
| 34 | +While it was a much better proof than every previous attempt I had made, |
| 35 | + it still wasn't very good in any objective sense, but it was the best outcome I could produce with the effort I could afford to expend on it. |
| 36 | + |
| 37 | +If I thought it was appropriate, I would post the two referee reports that I received. |
| 38 | +However, referees retain copyright, and it would be inappropriate for me to post them without permission, |
| 39 | + which I simply cannot obtain from anonymous referees. |
| 40 | +What's important is that I consider them to be fair mathematical assessments of the paper. |
| 41 | +They were intrigued by the central theorem of the paper, found the central proof very difficult to understand, |
| 42 | + and were not that interested in the remaining content of the paper outside of the central theorem and proof. |
| 43 | +I felt like I had a strong opportunity to obtain the approval of these referees |
| 44 | + if I reworked the central proof into a more readable form, |
| 45 | + and I enthusiastically embarked on paper revisions after the 2020 APS March Meeting. |
| 46 | + |
| 47 | +Revising this paper also meant revising my expectations on what constitutes good mathematical writing. |
| 48 | +According to my previous expectations, the original version of the paper was "good enough", |
| 49 | + and whatever my new expectations were to be, that paper could no longer be "good enough". |
| 50 | +There were completeness, notation, and organizational problems. |
| 51 | +The original, terse version of the proof made some terse arguments that would actually take a lot more space to justify thoroughly. |
| 52 | +For example, I defined optimization problems over closed domains that I could explicitly solve for most but not all elements in the domain. |
| 53 | +I decided to simply remove the problematic elements, since their contributions to the set of possible optimizers could be recovered |
| 54 | + from limiting arguments - "nearby" elements would contribute very similar values to the set of possible optimal values. |
| 55 | +However, a truly rigorous proof would either have to show that the contribution of these discarded elements were recovered |
| 56 | + or at least cite something that showed this to be true for a general enough class of problems that this specific case was covered. |
| 57 | +When considering the amount of space such an argument would take, that no longer seemed like a good proof strategy at all. |
| 58 | +Also, I got way too eager to define a zoo of auxiliary variables and didn't clearly explain what they were useful for. |
| 59 | +However, the trickiest aspect of the revision was deciding how to break up the proofs using intermediate lemmas. |
| 60 | +This is a canonical aspect of mathematical writing - breaking up a complicated argument into smaller, technically distinct pieces |
| 61 | + to make the argument more understandable. |
| 62 | +Sometimes those intermediate steps are interesting and useful in their own right, and sometimes they are just a means to an end. |
| 63 | +I struggled with this the most, as I had to work through trial proofs for each of the possible intermediate lemmas that I considered, |
| 64 | + and it took many attempts to find one that made the cleanest separation between the lemma's proof and the central theorem's proof |
| 65 | + that would depend on the lemma. |
| 66 | +Right now (pending further revisions to my math writing expectations), I'm quite happy with the end result, |
| 67 | + but I'm not happy with just how long it took to get there. |
| 68 | + |
| 69 | +I'm not completely happy with everything in the revised paper. |
| 70 | +The paper is about an optimization problem, |
| 71 | + and I strengthened up the formal results of the paper to rigorously characterize optimal solutions. |
| 72 | +This made it feasible to solve the optimization problem numerically, |
| 73 | + and I dived into writing a numerical solver to add to the paper. |
| 74 | +Unfortunately, that was its own time sink. |
| 75 | +With priority given to cleaning up the theorems and proofs, I didn't give the numerical solver the time it needed to develop fully. |
| 76 | +What ended up in the paper is the third completed version of a numerical solver, |
| 77 | + which was a massive improvement to the previous two versions, |
| 78 | + but just managed to stumble into an uncanny valley where it was just good enough to clarify what the remaining technical problems were |
| 79 | + without actually being able to solve them. |
| 80 | +Unfortunately, I just ran out of time for a fourth version, so I cleaned up what I had before the resubmission deadline. |
| 81 | + |
| 82 | +With this experience behind me, I feel like the revised paper is now legitimately my "first" math paper, |
| 83 | + but that feeling might not survive the next round of the review process. |
| 84 | +Outside of further revisions, I'm done with math research for the foreseeable future. |
| 85 | +While I have unfinished math projects and plans for future math research, |
| 86 | + I just don't have the time to pursue this kind of work right now. |
| 87 | +A lack of research resources has consequences, even for theorists. |
| 88 | +If you don't financially support an experimentalist, then they just can't afford to run a lab, and all research quickly grinds to a halt. |
| 89 | +With theory work, the most valuable resource is a theorist's time. |
| 90 | +I want to spend as much of my time as possible on research, but my full-time job is not a research job, |
| 91 | + and it has obligations that frequently divert my time and attention from research. |
| 92 | +I can pretend that I can effectively carry out two full-time jobs, but in reality everything suffers as a result. |
| 93 | +I wish that I could afford to focus exclusively on research right now, but I simply can't, |
| 94 | + or at least not without throwing away my financial future. |
| 95 | + |
| 96 | +So, what comes next? |
| 97 | +I'm trying to escape the death spiral of my research career. |
| 98 | +So far in my career, none of my research has generated enough interest to expand my future resources and opportunities, |
| 99 | + which has lead to a negative feedback loop of dwindling resources and opportunities. |
| 100 | +For example, this math project and paper originated from my personal interest in a problem |
| 101 | + and my beliefs about its future utility to my research. |
| 102 | +It wasn't some big open math problem that lots of people cared about, |
| 103 | + and very few people are going to care about it or understand it. |
| 104 | +Unfortunately, I now see that such research predilections are quite fatal in the long run to a research career, |
| 105 | + and my run has been long enough that I can really feel it dragging me down to the bottom now. |
| 106 | +Next, I'm going to try something different for a while. |
| 107 | +I'm going to prioritize research based on how I think others might value it. |
| 108 | +Specifically, I'm going back to quantum computing research, which I consider to be overhyped and overvalued. |
| 109 | +My plan is to patent new quantum error correction (QEC) protocols that will be essential to future digital quantum computers. |
| 110 | +Of all my research interests, this is the one with the most immediate and explicit possible value. |
| 111 | +For once, I'll attempt to play into excessive hype and overvaluation by trying to sell something for more than it is truly worth. |
| 112 | +In upcoming blog posts, I will rant some more about career issues, |
| 113 | + offer my somewhat negative perspective on quantum computing in general, |
| 114 | + and discuss these QEC plans further. |
0 commit comments