I’ve discovered I’m much more in touch with my mental and emotional state and even a five minute break will really relieve some of the pressure you put on your mind and body. Also because it’s just for 25 minutes anyway, it’s much easier to get started again, even with unfun work.
Edit: In case you’re worried this will make things worse, because of the regular interruption, I’ve found it to not be so bad with the exception of some types of debugging. The mind is pretty good at mulling over the problem while you’re taking a break and often I’m more effective afterwards. But the 25/5 isn’t a hard requirement and should be changed depending on preference and type of work.
My channel has a short talk recommending Pomodoro for engineers, including using it with Agile. The methods are extremely similar. https://www.youtube.com/channel/UC0PGaH-sVPGIdFUC88FgMmw
Starting a new job and that may finally be enough of a change to trigger me actually trying this after all these years of hearing about it.
I'm reminded of a scene from the movie 'Never Cry Wolf' where the bush pilot, while flying the plane, puts himself into a state of rage before stepping outside to fix the problem.
Like when you need to spend some time in a dark silent room before filling like having fun or do house chores or do the cooking.
That resonated, and it's the best example for me to come to grips with this.
Nice way to put it.
What I am facing however, is a related issue. Perhaps because I have not been doing much programming lately, I find it increasingly difficult to actually get and be in the zone. When I go in, I go all in, and enter a kind of fugue state where the hours slip away. While for some this may sound advantageous, in the past, it has been associated with some bad physical and psychological health outcomes. Now, I actually have anxiety about going into such a state, and try to piece meal my problems, and focus on the non-programming work and thinking.
Situations change, and I am about to be in one where I do really need to perform a lot of coding myself. I suppose I am answering my own question, but I need to split up my work and take notes to reduce the numbers of abstracted layers upon which I am working. Take more breaks with confidence I can return.
I suspect this technique can help ease the burdens of interruptions as well, but it does come at a cost in time. For me, the severe crunch time requirements and gained insane last minute skills should still be less necessary for some time. This is likely called being in a startup and getting older and, well, recognizing long-term limitations.