Hammock Driven Development - Rich Hickey

That and Hammock Driven Development: [VIDEO] Both of these talks are in my top 5. Edit (okay, here are the other 3): * All the Little Things by Sandi Metz [LINK] * Programming is terrible—Lessons learned from a life wasted. [LINK] * Some talk I saw by Dan McKinley on making Data-Driven decisions. I can't find the original video, but here's a really similar one: [LINK]

This is a classic and hilarious series of posts on the foolhardiness of the TDD approach to software design: [LINK] Personally I prefer Rich Hickey's "Hammock Driven Development": [VIDEO]

"don't get stuck" reminds me of the feynman method of problem solving: 1. Write down the problem. 2. Think very hard. 3. Write down the answer. Rich Hickey's Hammock Driven Development, [VIDEO] , is IMO very good for actually not getting stuck in a bad place problem solving.

This is very similar to what Rich Hickey (creator of Clojure) talks about when he talks about Hammock Driven Development, I recommend watching him talking about it here: [VIDEO]

I was searching for exactly the same stuff yesterday, and I found this: [LINK] I usually keep notebooks, but I am ever more convinced of using one because of Rich hickey's talk: [VIDEO] and we have a better chance of remembering something if we write than type. [LINK] . I have previously read that people like Martin Gardner had an awesome system of keeping notes. I would love to know more about your tips. How do keep your notes? How do you organize stuff, while retaining the freedom to doodle. How do you find stuff again(which is the killer feature for typed notes). Would love to learn from the masters - do you have any books to recommend?

I have loved this talk for some time and have forced everyone at my company to watch the video. I found a lot of parallels with this "Hammock Driven Development" talk by Rich Hickey: [VIDEO] They both seem to suggest that you have to put in the effort, do the hard work and dig into the problem deeply. But then when you hit a wall, you should take a break. Relax. Play. Sleep. It is often during this "open" minded stage when the solution comes.

I like this kind of development also. But I don't think it is for everyone (the person has to keep thinking on the problem for long time). A good talk about It, from the creator of clojure: [VIDEO]

This makes me think of Rich Hickey's Hammock Driven Development: [VIDEO] - "Stay away from the computer" - Start by asking: "what is the problem?"