ralph-loop Coffee Codex: Spec → Plan → Implement — From Idea to Execution In the last post, I said something that sounds simple, almost trivial: Code is cheap. Thinking is the bottleneck. And the loop is straightforward — spec → plan → implement. This post is what happens when you stop agreeing with that idea intellectually and actually run it, end to end, across real features,
vibe-coding Coffee Codex: When Code Is Cheap, Thinking Becomes the Bottleneck Some ideas stay unfinished. Not because they’re bad ideas. But because the timing isn’t right. Years ago, I explored a small concept called Coffee Codex — a place to document coffee beans, tasting notes, and brewing experiments. At the time it was mostly curiosity and conversation. Interesting to talk
Motion vs Action: Staying in the Driver Seat in the AI Era I've not been a consistent reader, but in the spirit of the new year, perhaps it's worth revisiting some old resolutions. I recently read a chapter from Atomic Habits about motion versus action. The explanation wasn’t new to me, but the author articulated it in
About Helmi I design software systems that have to hold up under real-world pressure — changing requirements, imperfect information and decisions that can’t be undone easily. Most of my work sits around microservices, event-driven architecture, CQRS and DDD, primarily in the .NET ecosystem with Angular and Kafka. Over time, I’ve learned
