How are feeling about not getting into the flowstate when using pomodoros of 25min?
That is at least something that I've experienced when I was trying out the pomodoro method. It was just too short to have a proper flow state to solve the frog problems as you have named them.
The short breaks (5 minutes) doesn't remove my flow. I just have time to breath, to walk and after that focus on my task again. Normally, the flow is not lost.
But, in my article on Medium about the Pomodoro Technique I also mentioned two other experiment with the length: levelup.gitconnected.com/manage-yo...
They experienced the best if you use 52-17 or 90-30. Both are really nice. I prefere 52-17 for bigger tasks where many preconditions are needed to start.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice ideas in there! Thanks for sharing.
How are feeling about not getting into the flowstate when using pomodoros of 25min?
That is at least something that I've experienced when I was trying out the pomodoro method. It was just too short to have a proper flow state to solve the frog problems as you have named them.
I personally can get into the flowstate :)
The short breaks (5 minutes) doesn't remove my flow. I just have time to breath, to walk and after that focus on my task again. Normally, the flow is not lost.
But, in my article on Medium about the Pomodoro Technique I also mentioned two other experiment with the length: levelup.gitconnected.com/manage-yo...
They experienced the best if you use 52-17 or 90-30. Both are really nice. I prefere 52-17 for bigger tasks where many preconditions are needed to start.