You know, I'm fairly sure that there is more than just procrastination at play. This feels like some human mal-adaptation where we do anything (or nothing) to avoid dealing with That One Terrible Thing, whatever it may be.
Throughout my career I've had this feeling or state of thinking multiple times, whether I had to work with legacy code, uncooperative individuals, or just a week ago, work with a bad DB schema and write complex queries against it.
In my case, procrastination was just a consequence of wanting to do something but I very clearly also remember just sitting and staring at the task at hand, doing absolutely nothing, because I couldn't stomach how bad everything about the task that needed to be done was - bunches of redundant tables, illogical linking of data, lots of overcomplication, no documentation and no examples of helpful queries whatsoever.
> If you're not just making slow progress but literally unable to make a single bit of progress, my goto strategy is similar to what writers call a vomit draft.
In the end, just forcing myself to get started, writing out the dozen of different things I needed as a part of the query and then working backwards through everything, was what worked. It took hours of uninterrupted work, I felt miserable throughout it, but I got things done in the end, all because of that decision to actually work on it and deal with the pain and suffering, very much how someone would need to make the leap to dive into legacy code, or an issue for a project that doesn't have monitoring or instrumentation, or writing a thesis.
I think that's why techniques like Pomodoro also get recommended, because if you trick yourself into saying that you'll only do a bit of suffering (work on the horrible thing) now and will take a break later, it's more tolerable: https://todoist.com/productivity-methods/pomodoro-technique
I'm just writing this because to me it feels different from how people commonly view procrastination: just getting distracted and wanting dopamine, as opposed to being able to stare at the computer for an hour without doing anything, just because doing the thing would be horrible. The latter feeling makes you want to quit your academical program (which seems like what the author is dealing with a little bit), or maybe draft your resignation and leave the job market for a bit instead of dealing with the codebase or whatever (which I did, albeit for different and less negative reasons in my case).
I'm also experiencing this currently. I can sit in front of my thesis and stare into the screen for a whole good day. I also can distract myself with a smartphone but that's merely a distraction from the boredom.
Around the topic of procrastination, I read "doing the thing would be horrible" for the first time and it just rings so true.
Doing this thing (this kind of work) feels horrible and I know I'll need to do it for many, many more days and weeks and these will all be horrible. There's no way around it. I often subconsciously try to make this time less horrible by experimenting with listening to music, have the TV running in the background or other things. This never really works. Or I just haven't found what I need.
At the end, whenever I do get a good chunk of work done, I feel really good about it. But I also acknowledge that it was horrible and I need rest now. And some dread builds up, reinforcing that the work is indeed horrible and the next chunk will require me to go through it again. The good feeling of getting work done does absolutely nothing to knowing that the work is horrible while you are doing it. It's the type of work (writing, editing) that I detest, not so much the content/topic.
I have no idea what strategy can help here (I welcome suggestions!).
Strategies such as Pomodoro do not help me. A 5min break doesn't change that the work is horrible and I'll be doing countless Pomodoros throughout the days/weeks anyway. The amount of horrible work is not reduced and the little breaks don't make it less horrible, so it doesn't help me.
What works for me sometimes is tricking me a bit. Just change this one sentences here and... this one also looks really bad... and when I'm at it, this figure there could use an overhaul... and suddenly you are working on your thesis. Key point here is - I think - that you don't go at it with the intention of doing actual work (which you know is horrible). You just change this stupid sentence there because your inner perfectionist wants you to. Thinking about it like that, the horribleness associated with the work may be a state of mind I can work on. No idea how to though.
Throughout my career I've had this feeling or state of thinking multiple times, whether I had to work with legacy code, uncooperative individuals, or just a week ago, work with a bad DB schema and write complex queries against it.
In my case, procrastination was just a consequence of wanting to do something but I very clearly also remember just sitting and staring at the task at hand, doing absolutely nothing, because I couldn't stomach how bad everything about the task that needed to be done was - bunches of redundant tables, illogical linking of data, lots of overcomplication, no documentation and no examples of helpful queries whatsoever.
> If you're not just making slow progress but literally unable to make a single bit of progress, my goto strategy is similar to what writers call a vomit draft.
In the end, just forcing myself to get started, writing out the dozen of different things I needed as a part of the query and then working backwards through everything, was what worked. It took hours of uninterrupted work, I felt miserable throughout it, but I got things done in the end, all because of that decision to actually work on it and deal with the pain and suffering, very much how someone would need to make the leap to dive into legacy code, or an issue for a project that doesn't have monitoring or instrumentation, or writing a thesis.
I think that's why techniques like Pomodoro also get recommended, because if you trick yourself into saying that you'll only do a bit of suffering (work on the horrible thing) now and will take a break later, it's more tolerable: https://todoist.com/productivity-methods/pomodoro-technique
I'm just writing this because to me it feels different from how people commonly view procrastination: just getting distracted and wanting dopamine, as opposed to being able to stare at the computer for an hour without doing anything, just because doing the thing would be horrible. The latter feeling makes you want to quit your academical program (which seems like what the author is dealing with a little bit), or maybe draft your resignation and leave the job market for a bit instead of dealing with the codebase or whatever (which I did, albeit for different and less negative reasons in my case).