I was using the pomodoro technique while programming. The Pomodoro timer finished and I was just in the middle of adding a new parameter to a function and was refactoring my code to make sure that the new parameter is propagated everywhere.
According to the technique, I'm suppose to drop everything and stop. But with programming (and with other tasks), when you're in a zone...keeping variables and logic in short term memory, I think it's actually counter productive to stop right when the Pomodoro rings. I feel like one should finish that last thought or unit of work before stopping. Otherwise, after you take a break, you need to reestablish context for your task and you'll basically be wasting some time at the beginning of the next Pomodoro to do this.
Can I extend the Pomodoro just so I can come to a good stopping point?