<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Post-Mortem on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/post-mortem/</link><description>Recent content in Post-Mortem on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 19 Oct 2026 17:18:05 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/post-mortem/index.xml" rel="self" type="application/rss+xml"/><item><title>Knightmare: A DevOps Cautionary Tale (2014)</title><link>https://curadevops.metacog.co.kr/insights/2026-10-19-knightmare-a-devops-cautionary-tale-2014/</link><pubDate>Mon, 19 Oct 2026 17:18:05 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-19-knightmare-a-devops-cautionary-tale-2014/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> The Knight Capital incident is a foundational reliability case study illustrating how a deployment error can cause catastrophic, irreversible production failures — useful for grounding runbook and rollback design.&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> The incident&amp;rsquo;s root cause was a flawed deployment process with no automated rollback, making it a canonical reference for why pipeline safeguards, feature flag hygiene, and staged rollouts matter.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A classic cautionary tale about organizational deployment risk at scale — useful context for briefing leadership on why investing in release engineering controls and incident response is non-negotiable.&lt;/li>
&lt;/ul></description></item></channel></rss>