https://idodo.dev/posts/Recent content in Posts on idodo.devHugo -- gohugo.ioen-usSun, 13 Sep 2026 00:00:00 +0000https://idodo.dev/posts/entra-tui/Sun, 13 Sep 2026 00:00:00 +0000https://idodo.dev/posts/entra-tui/I keep building terminal UIs, because the mouse is a peripheral I resent. entra-tui is the newest one: a k9s-flavoured browser for Microsoft Entra ID that borrows your az login token, never holds one of its own, and gets you to an object in three keystrokes instead of nine clicks. Written entirely in Go — by Claude, with me driving.https://idodo.dev/posts/tftui-0-14/Mon, 07 Sep 2026 00:00:00 +0000https://idodo.dev/posts/tftui-0-14/TFTUI is a terminal UI for Terraform state that I wrote three years ago, mostly by feel. Version 0.14 is a complete rewrite — new internals, 406 tests, CI on three platforms — that Claude Code did in a single day while I drove and reviewed. Here is what changed, what broke, and what the experience actually taught me.https://idodo.dev/posts/apigee-spikearrest/Fri, 14 Aug 2026 00:00:00 +0000https://idodo.dev/posts/apigee-spikearrest/What a 429 means, why equivalent throughput rates can behave differently, and how clients should respond when Apigee SpikeArrest rejects a request.https://idodo.dev/posts/github-repo-watcher/Thu, 30 Jul 2026 00:00:00 +0000https://idodo.dev/posts/github-repo-watcher/<p>GitHub&rsquo;s notification inbox has a design philosophy: tell you everything, and let you sort it out. Someone labels an issue, a bot bumps a dependency, a colleague replies to a thread you commented on eleven months ago — it all lands in the same pile. So most of us do one of two things. We check the pile constantly, or we stop checking it at all.</p> <p><strong>GitHub Repo Watcher</strong> takes a narrower swing. It watches a handful of repos you actually care about and answers one question from your browser toolbar: <em>is anything waiting on me right now?</em></p> <p>Most of the time the answer is a small green dot. When it isn&rsquo;t, you get a number.</p>https://idodo.dev/posts/aws-streaming-architecture/Mon, 13 Apr 2026 07:51:27 +0300https://idodo.dev/posts/aws-streaming-architecture/A technical deep-dive into how bits move from encoder to viewer — and what it costs. Introduction Streaming video at scale is, at its core, a bandwidth and caching problem. Every architectural decision — which AWS services to use, how long your segments are, how much delay you&rsquo;re willing to tolerate — has a direct, calculable effect on your monthly bill. For a hands-on way to estimate these numbers, check out our interactive AWS Streaming Cost Dashboard.https://idodo.dev/posts/vibe-coding-the-last-mile/Thu, 26 Feb 2026 20:39:23 +0200https://idodo.dev/posts/vibe-coding-the-last-mile/Sometimes you don&rsquo;t need to conquer the world or reinvent the wheel — you just need to add the final touch on an already working tool with a blind spot. The Premise There&rsquo;s a certain kind of problem that doesn&rsquo;t get talked about enough in platform engineering: the almost great tool. You&rsquo;ve procured it. It&rsquo;s enterprise-grade. It solves the core problem. It has a support contract and a roadmap and a Gartner Magic Quadrant placement.https://idodo.dev/posts/github-workflows-spend-reduction/Sat, 24 Jan 2026 16:19:19 +0200https://idodo.dev/posts/github-workflows-spend-reduction/In an organization with hundreds of repositories, you wouldn’t expect a single workflow in a single repo to be the primary driver of cost. Yet, in our case, the Pareto principle hit hard: one high-traffic repository was responsible for a staggering 50% of our entire GitHub Actions spend. This is a story about leverage. Most engineering teams try to shave 5% off everything; we saved 50% of the entire org&rsquo;s bill by identifying and fixing the right 1%.