[iLemming]

I've tried many different things and I finally have a solution that (I think) works for me:

It's Emacs' Org-mode in combination with Org-pomodoro

- First, using org-capture I would create an org heading with a description of the problem. If there's a Jira ticket I would attach the ticket number (I have a trivial elisp function that converts a regular number into a complete jira-ticket link)

- Then I would start a Pomodoro cycle. If I'm on a Mac - it would create an OSX menubar item with the title of the heading (using Hammerspoon). Org will "clock" me in for the task for the next 25 minutes

- I just realized that I can probably even programmatically switch Slack to "do not disturb" mode while Pomodoro is active

- Activated Pomodoro cycle is like a sacred ritual for me. I do not pick up my phone or check email or (if possible) even talk to anyone. After Pomodoro is done I would take a break, check email, get some water, etc. If I can get done 5-7 pomodoros during a day - I consider it a very productive day.

- Org records everything. At the end of the day I know: exactly how long I worked on every single story, the number of pomodoros I did, notes that I took while working on each story. Whenever I changed the status of the story from "todo" to "in progress" and back to "to do" or when I flipped it to "done" or "canceled", reasons why the story was canceled, etc.

And this is all done with a minimal context switching.

[tighter_wires]

Do you ever find that Pomodoro doesn't leave enough uninterrupted time on your task? When you're knee deep do you ever just skip your breaks?

[iLemming]

Sometimes that happens. I try not to skip breaks, they are important part of pomodoro. But Emacs ain't my dad - if I feel like skipping a break or taking one before the end of the current cycle - I just do it. There are days when I simply can't maintain discipline of concentrating focus and taking breaks within intervals then I simply don't use org-pomodoro. I would clock-in on a task and work until I'm tired. I'm not a contractor, I don't need to report my "billable hours" yet clocking in helps me to maintain focus on the task and keep notes. There's a way in Emacs to attach a note onto currently clocked-in task without having to navigate to it.

[Narushia]

I generally find pomodoro’s 25-minute work intervals too short for software development, I prefer the 52/17 method.

[iLemming]

Yeah, everyone is different. I tried experimenting with 20-30-40 minute intervals and decided 25 is the optimal for me. But it really has to be distraction free. I use brain.fm or instrumental music (no lyrics) or I just keep my headphones on so nobody bothers me. It doesn't sound very challenging, but after five pomodoros I truly can feel it, after eight - I am mentally exhausted. Ten pomodoros mean I either cheated or something else.