For me, it's the opposite. This is one of my favorite things about doing pomodoros.
I hate to be the tactibro who sources inspirational quotes from special forces influencers, but I worked with a guy who introduced me to the phrase "go before you're ready," and I really took it to heart as a check against my natural tendency to leave problems alone and wait for them to get easier. I got this tendency from studying math in school, where I fell in love with the magic of getting stuck on a hard problem, putting it aside, and having the solution come to me hours later while I was thinking about something else.
That approach works when my subconscious has everything it needs to work on the problem, like when writing proofs for a math class, but at my job I'm usually working in a different way, where the solution depends on concrete details that I'm in the process of learning, such as a new part of a codebase, a new library, a new API, etc. I can't delegate that kind of work to my subconscious, because my subconscious isn't going to read documentation and write exploratory code. But my brain keeps whispering, "You're stuck. Take a break."
Because of this, I love the "go before you're ready" aspect of doing Pomodoros.
90% of my inability to start something is procrastinating because I don't know the full picture yet, but every time I get started I figure it out. Just have to go before you're ready
In practice I'll happily ignore the "take a 5 min break" part of the Pomodoro method but I definitely take real breaks every hour or two.
People used to being interrupted either get nothing done or weave practices into their routine that help them remember where they left off. Used to be when I was young and an enthusiastic proponent of Flow state (neither of which are true anymore), I would pretty confidently pull on threads until I had six or seven things on my todo list, and manage to almost always remember all of them.
But these are moderately large rewrites pretending to be refactoring by misusing the tools and ignoring the goals and values. So these days I tend to use that mental model to do more reading and trying to get closer to the crux of the issue instead of starting to type and hoping for my brain to catch up with my fingers within a few dozen lines of code, which isn't happening if we've arrived at the adjective "large".
I haven't articulated this before so I don't really have a handy list of all of the tools and tricks I utilize for this, but I can say that conditional breakpoints are one of the ways I augment that memory. Even if I get pulled off into a production issue, these breakpoints are a much better reminder of what I was thinking about than a simple breakpoint.
I've been using pomodoro for many years. Not continuously though because I find that my productivity level is extremely high while doing it and I start to get burned out because the intermittent breaks are not enough.
You might be interested in something called the domino technique to help with getting started / getting into flow. Basically you do something that is difficult but short that you can do to get a meaningful psychological "win" in a short period of time (5 minutes) to kick start your motivation / flow. I would post a link but I don't have a good reference on hand.
It doesn't work for me though because I'm really independent and totally not competitive. I just don't care about my peers. I hate team sports also for this case because I'll always get kicked out for not caring about the team's goals.
It's a bit difficult sometimes because all companies think they only need 'team players'. I can be extremely loyal to people I care about but I need to build up that care naturally, them being part of some arbitrary 'team' doesn't work for me. Hard to explain :)
And as I notice, my problem at times is that my tasks are like "You are a Roman General. You have 3 Legions. Conquer Europe north of this line."
For me personally, it's better to have a task like "Alternate pick the A-Minor scale on the bass 2 times up and down at 120bpm". Easy and simple to do I'd say. And then you realize that other thing. And then that other thing. And then you watch some Vids from Ola, Bernth, Glenn. And suddenly you've noodled 2 hours on the guitar.
Since we all know how this goes, I would say procrastination is a survival instinct.
Some days when I don't use it I end up working for many hours without a break, and my productivity would've been higher with regular breaks. I also find myself drifting to tasks which seem important but aren't, like a random refactor. Pomo helps me be conscious every half hour about what I want to work on
If you don't have those problems, it probably won't offer you anything
Sometimes it is mostly a trick to get me started (ok, I need to do this only for $n minutes, I could do that) and then I ignore the pause, because the clock is not the boss of me and I am in the flow