https://farokhpakbaz.github.io/Recent content in Home on Mehdi Hasanzadeh Samadi (Farokh) — DevOps EngineerHugoen-usTue, 18 Aug 2026 00:00:00 +0000https://farokhpakbaz.github.io/notes/building-this-site/Tue, 18 Aug 2026 00:00:00 +0000https://farokhpakbaz.github.io/notes/building-this-site/<p>Personal websites are a rare chance to design without a conversion funnel. They can be small, specific, and unmistakably human. This one began with a simple constraint: make it feel like a focused workspace.</p> <h2 id="start-with-atmosphere">Start with atmosphere</h2> <p>The visual system borrows from code editors without pretending to be one. Monospaced type, syntax-like colors, line numbers, and compact metadata create the atmosphere. The hierarchy still behaves like a conventional editorial site, so the interface stays legible and familiar.</p>https://farokhpakbaz.github.io/notes/clarity-is-a-feature/Tue, 11 Aug 2026 00:00:00 +0000https://farokhpakbaz.github.io/notes/clarity-is-a-feature/<p>People rarely experience a product as a list of features. They experience a sequence of questions: Where am I? What can I do? What happened? What happens next?</p> <p>An interface feels clear when it answers those questions at the moment they appear. This is less about minimalism than about information arriving in the right order.</p> <h2 id="make-state-visible">Make state visible</h2> <p>Systems know far more about their state than they usually communicate. A small status label, a useful empty state, or a precise error can prevent a user from forming the wrong mental model.</p>https://farokhpakbaz.github.io/notes/small-systems/Mon, 03 Aug 2026 00:00:00 +0000https://farokhpakbaz.github.io/notes/small-systems/<p>A small system can be understood end to end. You can see where data enters, how it changes, and what comes out. That visibility makes maintenance less mysterious and decisions more reversible.</p> <p>Small systems still solve serious problems. Their advantage is that complexity is introduced in response to evidence, instead of being prepaid for a future that may never arrive.</p> <blockquote> <p>The right amount of architecture is enough structure to make the next change unsurprising.</p>https://farokhpakbaz.github.io/about/Mon, 01 Jan 0001 00:00:00 +0000https://farokhpakbaz.github.io/about/<p>I’m Mehdi Hasanzadeh Samadi—usually Farokh—a DevOps engineer based in Tehran. I build reliable, scalable, and automated infrastructure, with a focus on Kubernetes, Linux, cloud-native platforms, and distributed systems.</p> <p>My background began close to the operating system: Linux administration, networking, storage, virtualization, and practical troubleshooting. That foundation still shapes how I approach modern platforms—I want to understand what is happening below the abstraction, not only how to operate the abstraction itself.</p>