https://latini.dev/tags/slo/Recent content in Slo on F. Latini - IT EngineerHugoenThu, 23 Jul 2026 08:00:00 +0000https://latini.dev/posts/the-error-budget-nobody-spends/Thu, 23 Jul 2026 08:00:00 +0000https://latini.dev/posts/the-error-budget-nobody-spends/<p><strong>TL;DR</strong> - An SLO without an error budget you actually spend is a number on a wiki, not a reliability practice. The error budget is the whole point: it is a pre-agreed trade between reliability and velocity, decided while everyone is calm, so that when the budget runs out the answer - stop shipping features, fix reliability - is already made. Almost nobody spends it. Teams set a target from ambition instead of user need (often a heroic 100%), measure the wrong thing (host uptime, not the user&rsquo;s journey), page themselves at 3am on the raw threshold, and then blow through the budget without changing a single plan. This is the four moves that turn an SLO from decoration back into a decision, and the honest cases where you don&rsquo;t need one at all.</p>