I use a similar pattern, but instead of 30/30, I do 75/30, here are the reasons, 1. I need at least 5 to 10 mins to pick up what's left. 2. Work without distra

I use a similar pattern, but instead of 30/30, I do 75/30, here are the reasons, 1. I need at least 5 to 10 mins to pick up what's left. 2. Work without distraction never happen(people talk to you, have to open the door for someone, answer the office phone etc). If that happens, I need another 5 mins just to remember I was doing. 3. My productivity picks up after the initial 20mins, and it lasts about 45 to 60 mins. 4. A few things could happen after 75mins of coding a) feature done or bug fixed - checkin code, git push. done take a break b) encounter a problem, internet searching - stop and take a 30 mins break, helps a lot. c) starting checking facebook, hacker news, email etc - stop and take a break. d) feature is not done, and I have not encountered a problem - this is the only time I might not take a break, but every time I didnt, I found myself ended up checking email and facebook a lot :) 30/30 sounds great, for me, 75/30 give me enough time to finish a feature or fix a bug. 4.