Ask HN: How to reduce inertia in Hammock Driven Development
I've been a software engineer for almost a decade now, and I enjoy working in this field a lot. One of the most influential talks in my career has been Rich Hickey's talk on Hammock Driven Development [1]. It's helped me complete projects with such a simple approach that fits well with how my brain works. I'm a very pensive person and for the most part, everything from initial concept to system architecture I do in my head or on a chalkboard. The hardest part for me, still, is going from the chalkboard to code. In Hickey's talk, this step only takes up one bullet point on one slide, but it's easily the most difficult part of the process for me. I'm a competent coder, and know I am capable of writing the code I need to write. Sometimes, however, I spend a lot of time just staring at a keyboard, unable to type what I want to type. There are a lot factors making me this way, outside of the realm of software engineering, that I'm working on. But in the short term, I was hoping to hear about any strategies employed by people who work in a hammock-driven fashion, or anything similar, to actually take the concepts and systems they design in their head and on paper, and put them into a source file for execution.