<?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 Danilo Falcão da Silva</title><link>https://falcao.org/tags/reliability/</link><description>Recent content in Reliability on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 24 May 2026 22:50:00 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/reliability/index.xml" rel="self" type="application/rss+xml"/><item><title>SLA, SLO, SLI, and Error Budgets: A DevOps Reality Check</title><link>https://falcao.org/posts/sla-slo-sli-error-budget-devops-practical-guide/</link><pubDate>Sun, 24 May 2026 22:50:00 -0300</pubDate><guid>https://falcao.org/posts/sla-slo-sli-error-budget-devops-practical-guide/</guid><description>&lt;p>Most teams get SLAs, SLOs, and SLIs wrong. Not because the concepts are hard, but because they treat them as compliance paperwork instead of operational tools. The result is dashboards nobody trusts, targets nobody chose deliberately, and on-call rotations that burn people out chasing noise.&lt;/p>
&lt;p>This post is a field guide for teams that actually run production systems and want reliability engineering to work as an engineering discipline — not a slide deck exercise.&lt;/p></description></item></channel></rss>