<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SRE on Jason Lee Miller · DevOps &amp; Cloud Security Engineer</title><link>https://www.jasonmiller.cc/tags/sre/</link><description>Recent content in SRE on Jason Lee Miller · DevOps &amp; Cloud Security Engineer</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 14 Apr 2026 19:00:29 -0700</lastBuildDate><atom:link href="https://www.jasonmiller.cc/tags/sre/index.xml" rel="self" type="application/rss+xml"/><item><title>Killing the Hero Culture</title><link>https://www.jasonmiller.cc/blogs/killing-the-hero-culture/</link><pubDate>Tue, 14 Apr 2026 19:00:29 -0700</pubDate><guid>https://www.jasonmiller.cc/blogs/killing-the-hero-culture/</guid><description>&lt;h2 id="killing-the-hero-culture-why-i-build-systems-that-dont-need-me">Killing the Hero Culture: Why I Build Systems That Don’t Need Me&lt;/h2>
&lt;h3 id="stage-1-the-psychology-of-the-hero-vs-the-architect-of-systems">Stage 1: The Psychology of the Hero vs. The Architect of Systems&lt;/h3>
&lt;p>In the landscape of modern enterprise technology, there is a recurring character often celebrated in post-incident reviews and all-hands meetings: the &amp;ldquo;Hero.&amp;rdquo; This is the engineer who spends 48 consecutive hours awake during a critical production outage, the one who knows the specific, unwritten command to revive a legacy database, and the one who ultimately &amp;ldquo;saves the day.&amp;rdquo; While this individual’s dedication is admirable, their necessity is a glaring indictment of the system’s architecture.&lt;/p></description></item></channel></rss>