<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reliability on Ilyas Hamdi</title><link>https://ilyashamdi.com/tags/reliability/</link><description>Recent content in Reliability on Ilyas Hamdi</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 26 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ilyashamdi.com/tags/reliability/index.xml" rel="self" type="application/rss+xml"/><item><title>The 100% reliability targets fallacy</title><link>https://ilyashamdi.com/writing/slo-100-percent-fallacy/</link><pubDate>Thu, 26 Mar 2026 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/slo-100-percent-fallacy/</guid><description>100% SLOs aren't just impractical. They're logically indefensible, and they corrode every reliability conversation that follows.</description></item><item><title>The error budget mindset</title><link>https://ilyashamdi.com/writing/error-budget-management-infrastructure/</link><pubDate>Tue, 22 Apr 2025 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/error-budget-management-infrastructure/</guid><description>The mechanism is the easy part. The willingness to slow shipping when the budget is exhausted is the hard part, and the part most programs skip.</description></item><item><title>Shaping architecture with SLOs</title><link>https://ilyashamdi.com/writing/slo-driven-infrastructure-architecture/</link><pubDate>Tue, 04 Mar 2025 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/slo-driven-infrastructure-architecture/</guid><description>SLO-driven architecture treats the SLO as upstream of the design. If your SLO has never caused you to ship later, it isn't doing the work.</description></item></channel></rss>