hammock-driven development

Created: Feb 27, 2021Published: Mar 28, 2023Last modified: Apr 05, 2023
No tags
Word count: 126Backlinks: 5

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


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!

I love streaming for a bunch of reasons, but one thing that comes along with it: the opportunity to create video content. I've not yet carved out a process for handling the stream content, but I feel like there is some plenty of low hanging fruit.

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

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.

The goal is aha moments