Skip to content

Instantly share code, notes, and snippets.

@kot-behemoth
Last active April 5, 2019 11:48
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save kot-behemoth/5560ae782e642b6ecb7f14140c5a767c to your computer and use it in GitHub Desktop.
Save kot-behemoth/5560ae782e642b6ecb7f14140c5a767c to your computer and use it in GitHub Desktop.
Hammock-driven Development

Hammock-Driven Development Summary

Solve problem vs create features

  1. state the problem
  2. understand: facts, context, constraints
    • what don't you know?
    • related problems out there?
  3. be discerning
    • problems & tradeoffs in your solutions: technical, logical - solve
    • there should be questions tradeoffs: you need at least 2 alternative solutions to compare
  4. focus
    • get away from computer
    • tradeoffs: balls will be dropped
  5. two minds
    • waking mind: tactical/analytical
      • make it feed background mind
      • analyse background mind output
    • background mind: synthesis, strategy, abstractions
      • only can feed it, not direct it
      • make a problem a days' agenda to feed it into your background
  6. 7+-2
  7. hammock time: NO INPUT! close your eyes - recall the problem in your imagination
  8. wait - at least overnight or over month
    • switch to another things (not withing a day), don't stuck
    • capture idea when it appear
    • try it
      • type sparingly - small solution is good
      • feedback is important - don't lean on it
    • you may be wrong
      • don't be afraid of being wrong

(from Alexey Tarasevich's comment https://www.youtube.com/watch?v=f84n5oFoZBc&lc=UgjVIsHMLnIJNHgCoAEC)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment