<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://www.dadishimwe.com/</id><title>Dadi Ishimwe</title><subtitle>Full Stack Developer and Network Engineer specializing in web development, networking infrastructure, data science, and innovative technology solutions. Explore projects, tutorials, and insights on OpenWRT, Peplink, Starlink, Python, FastAPI, and more.</subtitle> <updated>2026-02-24T12:54:42+06:00</updated> <author> <name>Dadi Ishimwe</name> <uri>https://www.dadishimwe.com/</uri> </author><link rel="self" type="application/atom+xml" href="https://www.dadishimwe.com/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://www.dadishimwe.com/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Dadi Ishimwe </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Building a CLI Tool That Hides Complexity: Making APIs Accessible to Non-Technical Teams</title><link href="https://www.dadishimwe.com/posts/building-a-cli-tool-that-hides-complexity/" rel="alternate" type="text/html" title="Building a CLI Tool That Hides Complexity: Making APIs Accessible to Non-Technical Teams" /><published>2025-11-13T14:00:00+06:00</published> <updated>2025-11-13T14:00:00+06:00</updated> <id>https://www.dadishimwe.com/posts/building-a-cli-tool-that-hides-complexity/</id> <content src="https://www.dadishimwe.com/posts/building-a-cli-tool-that-hides-complexity/" /> <author> <name>dadishimwe</name> </author> <category term="English" /> <category term="Programming" /> <category term="API Journey" /> <summary> Disclaimer: This story is fictionalized and based on common patterns and challenges encountered in API integration and CLI tool development. While inspired by real-world scenarios, specific details, clients, and situations have been altered to protect sensitive information and illustrate general principles. How I turned a complex enterprise API into a simple command-line tool that anyone o... </summary> </entry> <entry><title>The Day I Realized My Data Was Doubling: A Cautionary Tale About API Data Management</title><link href="https://www.dadishimwe.com/posts/the-day-i-realized-my-data-was-doubling/" rel="alternate" type="text/html" title="The Day I Realized My Data Was Doubling: A Cautionary Tale About API Data Management" /><published>2025-11-10T14:00:00+06:00</published> <updated>2025-11-16T02:41:15+06:00</updated> <id>https://www.dadishimwe.com/posts/the-day-i-realized-my-data-was-doubling/</id> <content src="https://www.dadishimwe.com/posts/the-day-i-realized-my-data-was-doubling/" /> <author> <name>dadishimwe</name> </author> <category term="English" /> <category term="Programming" /> <category term="API Journey" /> <summary> Disclaimer: This story is fictionalized and based on common patterns and challenges encountered in API data management. While inspired by real-world scenarios, specific details, clients, and situations have been altered to protect sensitive information and illustrate general principles. How a simple oversight led to duplicate data, and the technical journey to fix it The Discovery It w... </summary> </entry> <entry><title>The Docker Deployment Saga: From Local Development to Production</title><link href="https://www.dadishimwe.com/posts/docker-deployment-saga/" rel="alternate" type="text/html" title="The Docker Deployment Saga: From Local Development to Production" /><published>2025-10-22T14:00:00+06:00</published> <updated>2025-10-22T14:00:00+06:00</updated> <id>https://www.dadishimwe.com/posts/docker-deployment-saga/</id> <content src="https://www.dadishimwe.com/posts/docker-deployment-saga/" /> <author> <name>dadishimwe</name> </author> <category term="English" /> <category term="DevOps" /> <category term="Murugo Journey" /> <summary> The Docker Deployment Saga: From Local Development to Production The journey from a working application on your local machine to a live, production-ready system is often fraught with unexpected challenges. For Murugo, Docker was the tool that promised to make this transition seamless, but the reality was far more complex. This is the story of our Docker deployment saga. The Promise: “It Works... </summary> </entry> <entry><title>Session Security for Financial Apps: Why Standard Security Wasn’t Enough</title><link href="https://www.dadishimwe.com/posts/session-security/" rel="alternate" type="text/html" title="Session Security for Financial Apps: Why Standard Security Wasn’t Enough" /><published>2025-10-13T14:00:00+06:00</published> <updated>2025-10-13T14:00:00+06:00</updated> <id>https://www.dadishimwe.com/posts/session-security/</id> <content src="https://www.dadishimwe.com/posts/session-security/" /> <author> <name>dadishimwe</name> </author> <category term="English" /> <category term="Security" /> <category term="Murugo Journey" /> <summary> Session Security for Financial Apps: Why Standard Security Wasn’t Enough When you’re building a platform that will eventually handle payments and sensitive user data, standard security measures are just the starting point. For Murugo, I knew that I needed to go above and beyond to protect our users. This is the story of how I hardened our session security to meet the demands of a modern, finan... </summary> </entry> <entry><title>Navigation Nightmare: How We Solved Desktop Clutter and Mobile Responsiveness</title><link href="https://www.dadishimwe.com/posts/navigation-nightmare/" rel="alternate" type="text/html" title="Navigation Nightmare: How We Solved Desktop Clutter and Mobile Responsiveness" /><published>2025-10-12T14:00:00+06:00</published> <updated>2025-10-12T14:00:00+06:00</updated> <id>https://www.dadishimwe.com/posts/navigation-nightmare/</id> <content src="https://www.dadishimwe.com/posts/navigation-nightmare/" /> <author> <name>dadishimwe</name> </author> <category term="English" /> <category term="User Experience" /> <category term="Murugo Journey" /> <summary> Navigation Nightmare: How We Solved Desktop Clutter and Mobile Responsiveness A great navigation bar is like a good joke: if you have to explain it, it’s not that good. In the early versions of Murugo, our navigation was no laughing matter. It was cluttered, unresponsive, and a constant source of user frustration. This is the story of how we tamed the navigation nightmare. The Problem: A Tale... </summary> </entry> </feed>
