Before trying it for the third time, this time with much more determination to continue it alteast for 30 days, wanted to get some opinion if you have found it useful/ not useful for software development. Also, if there are some tips to share to make this work, they would be very helpful.
Thank you.
I would like to suggest another tool or option for you to try though this is not about pomodoro technique but if you wanted to be productive, you might want to read this book:
The Power of Concentration
https://www.amazon.com/Power-Concentration-Theron-Q-Dumont/d...
There is a free audiobook in librivox:
https://librivox.org/the-power-of-concentration-by-theron-q-...
Wanted an opinion if it is effective or not for experienced developers. Do the frequent breaks assist or hinder concentration and creativity?
[0] - One of my favorite comment on HN: https://news.ycombinator.com/item?id=1888971
[0] - http://doc.norang.ca/org-mode.html#Clocking [1] - http://doc.norang.ca/org-mode.html#TimeReportingAndTracking
An unexpected benefit is sometimes I don't need to start a session. I can catch a glimpse of the hourglass out of the corner of my eye and immediately enter a productive zone.
You may find the common 20 or 25 minute sprint lengths too short to get into flow. But on a day when you're having trouble getting started at all, they're a good way to get your butt in gear. If you're focused, nothing forces you to stop at the end of the sprint.
When I'm ready to buckle down on a big chunk of work, I'll more often set myself a 50-min sprint, though. And if you do work through the "break" period and into another sprint, just make sure you take a nice long brain break once you hit a stopping point. Part of the purpose of those breaks is to keep you refreshed so you can continue to concentrate.
Fifty plus year's ago an economist,Cyril Northcote Parkinson, coined "Parkinson's law", it says, "work expands so as to fill the time available for its completion." In someways it seems obvious but the reality is that it's not so obvious since we don't recognize it until someone points it out.
Parkinson's law is what the Pomodoro technique is trying to manage for the individual as Agile is for project management. It does help but it's just hard to maintain over time.
The way to stick to it is to make it a habit. Start by making it a game such as how long can I last without failing. By the way you will fail. Track the time you lasted and then try to increase it for next time. Also note why you failed and find something to counter that so you're ready for the next time. Repeat until you no longer think about the process but it becomes part of your everyday.
I use an inexpensive mac app from the appstore that seems to help as you can look up and see how much time you have left. For the breaks I'll check email, news or play a quick round of a turned based game.
https://itunes.apple.com/us/app/tomato-ticker-pomodoro-timer...
Or if I'm making progress on something I'll just keep going.
For being productive I've found knocking out a small task to get started in the morning or when starting back to begin a long stretch of development helps.
I also listen to upbeat music with minimal lyrics while I work.
And if you find a song that you're really productive listening to I'll even listen to it on repeat and that seems to help me stay in the zone.
Good luck.
Edmond's definition of leverage = Impact Produced/Time Invested
You can read the book for more on Edmond's definition of leverage, but this seemingly simple idea did absolute wonders for my productivity.
I realized the Pomodoro technique was most effective for me for the lower leverage tasks, and not so much for the higher leverage tasks. As a result, over time I sort of moved away from using it.
Planning out what you are going to work on the night before is a huge help. I think getting good at knowing what you can fit into a 25 minute slot takes some practice.
Staying focused, not reading emails or posting on HN takes serious practice.