procrastinating improves design
Often I procrastinate something I _should_ be doing.
I feel a bit guilty or uncomfortable, because I _should_ dive in and just do it.
But when there's not that clarity about what it is/how to do it... when there's not confidence in the shape of it... it's just not the right time.
Later, when the clarity and confidence hit, it gets done, and done well.
Maybe even with testing!
If you're not sure what to do, I recommend the hammock and sleeping on it.
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: hammock-driven development
The goal is aha moments
Backlinks
Aha! moments - moments of insight that unlock the clarity and confidence while designing and implementing something.
The goal of a Hammock or Procrastination session.
Worth capturing!
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