Clojurians Log v2
clojuredesign-podcast
Hi @neumann@nate, I just wanted to share that I've been thinking a lot these past days about the tracer-bullet approach that you kept mentioning in the podcast. I'm looking into https://data-star.dev/ these days and for that I needed a server-sent-event endpoint. I've never built one, so I thought to start with a super embarrasing and leaky 😅 tracer-bullet and it helped me significantly to move forward. I thought to use writing as well next to that and the combo of writing + tracer-bullet worked really well. I think without the tracer-bullet approach, I'd be stuck in writing, I'd never be able to write anything close these posts. But with the tracer-bullet, stopping with an embarring solution felt ... productive. So thanks a lot 🙏 • https://krcah.com/building-sse-endpoint-in-clojure-ring-core-async • https://krcah.com/building-sse-endpoint-in-clojure-ring-core-async-part-2
I keep thinking about Alberto Brandolini & DDD saying that: "software engineering is a learning process, working code is a side-effect", with trace-bullets there to maximize learnings, especially in those fuzzy beginnings
I love that! That’s exactly it! It’s a learning process. Working code is the manifestation and application of the learned knowledge.
@marcel187 That's awesome! Thanks for sharing! I have to thank @nate for the tracer bullet approach. He was the one that introduced me to that idea. I tend to overthink, and he's fantastic at pulling me out of it! I underestimate how much I get out of a tracer bullet. I'm still surprised by the emergence of vital information from being concrete. I always discover things I would have never thought of! I'm so glad you wrote up your experience! Thank you again for sharing the links.
That's such an awesome story! Thanks for letting us know. Great idea to add writing to the mix. I've done that as well to great effect. It can also help get teammates unstuck and on to the next better iteration of the solution.
Get to that first rewrite as fast as you can. The first iteration is always messy and imperfect, so make it messier and less perfect so that you can learn faster.
It's something that's rather counter-intuitive, especially as you gain experience. I just had to remind myself of this principle in my current task at work. Make it messy and then make it right.