Pomodoros
The term Pomodoro refers to a tomato timer, and usually corresponds to working for 25 minutes, then taking a 5 minute break before starting again.
pomodoros, as implemented in Yodo
An encouraged break and a check-in with the time-of-day!
- increases self-awareness Am i tired? Am I working on the thing I want to be working on?
- make sure we're spending time on the right thing
- identify places we're getting stuck increased subconscious problem solving by stepping away from the problem for a moment (see: hammock-driven development )
- wind-down and capture context so that building it back up is easier
suggest structures for pomodoro breaks in the last 5 minutes of a pomodoro
Backlinks
Pomodoros are nice, but what would be nicer is pomodoros that start when you start, notify while you're working, and overall just do-the-thing based on you sitting down to work or walking away from the computer.
See also:
- Pomodoros
- Workrave
Rich Hickey's Hammock-driven development has provided a useful term to thinking.
To "hammock" something now refers to conscious or sub-conscious problem solving.
Take the requisite time and space to understand the problem.
It's ok to wait before writing code - make sure you conceptually understand what it is you need.
It's hard to resist diving into code - it's uncomfortable to sit and admit that you need to think, learn, and comprehend first.
Sometimes i think this is about better planning, sometimes i think it's about Pomodoros.
Note that this does not apply if you haven't sought out info/dug into the problem/done some research/toyed with potential solutions. All that is a pre-req for hammocking.
See also: procrastinating improves design
The goal is aha moments
Starting early today (12:01am)
working through clawe.org, pulling in some content, writing some new ideas
garden tending