<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Postmortem on Kuldeep Pisda</title><link>https://kdpisda.in/tag/postmortem/</link><description>Recent content in Postmortem on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 06 Oct 2026 08:30:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/postmortem/index.xml" rel="self" type="application/rss+xml"/><item><title>Firebase's Kill Switches Shipped Globally, and a Two-Line Cleanup Crashed iOS Apps</title><link>https://kdpisda.in/firebase-config-cleanup-orphaned-flag-kill-switch-crash/</link><pubDate>Tue, 06 Oct 2026 08:30:00 +0530</pubDate><guid>https://kdpisda.in/firebase-config-cleanup-orphaned-flag-kill-switch-crash/</guid><description>&lt;p&gt;Firebase&amp;rsquo;s postmortem for the September 28 iOS outage contains one sentence that explains most of it: the flags the Google Analytics for Firebase SDK uses as kill switches are themselves &amp;ldquo;released globally&amp;rdquo;. A kill switch is supposed to be the safe, fast path for turning off a bad feature. Here the path that carries it had no staging, so the bad value went out to a wide population of apps.&lt;/p&gt;</description></item></channel></rss>