I think this is definitely valid and real, but there also is a danger of pretending you're in this situation when you're not.
For example, suppose you have some electronic item you want to repair but you're horrible at soldering, so you put it off because you don't want to face the negative feelings of failing at soldering again or the negative feelings of destroying that item you think you should have been able to repair. You could get past this by watching some videos on soldering, getting some better equipment, or practicing with a friend who's actually good at soldering. Once you don't suck at soldering, the negative feelings around fixing your electronic item are gone, and you can stop procrastinating. (And you can do it faster and better.)
On the other hand, maybe you need to write a complicated and annoying SQL query that is going to be tricky to get right, and you already know SQL, but you go off on a huge tangent reading SQL documentation looking for a function or trick that will make it easier when there really isn't one. Pretty soon you're just learning about esoteric SQL functions that don't have anything to do with your problem. But maybe one of them could if you read long enough, so you keep reading and reading.
For example, suppose you have some electronic item you want to repair but you're horrible at soldering, so you put it off because you don't want to face the negative feelings of failing at soldering again or the negative feelings of destroying that item you think you should have been able to repair. You could get past this by watching some videos on soldering, getting some better equipment, or practicing with a friend who's actually good at soldering. Once you don't suck at soldering, the negative feelings around fixing your electronic item are gone, and you can stop procrastinating. (And you can do it faster and better.)
On the other hand, maybe you need to write a complicated and annoying SQL query that is going to be tricky to get right, and you already know SQL, but you go off on a huge tangent reading SQL documentation looking for a function or trick that will make it easier when there really isn't one. Pretty soon you're just learning about esoteric SQL functions that don't have anything to do with your problem. But maybe one of them could if you read long enough, so you keep reading and reading.