<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Emergency-Preparedness on 매일 영어 일기</title><link>https://diary.metacog.co.kr/tags/emergency-preparedness/</link><description>Recent content in Emergency-Preparedness on 매일 영어 일기</description><generator>Hugo</generator><language>ko-kr</language><lastBuildDate>Thu, 27 Aug 2026 12:17:54 +0900</lastBuildDate><atom:link href="https://diary.metacog.co.kr/tags/emergency-preparedness/index.xml" rel="self" type="application/rss+xml"/><item><title>2026-08-27 비상 상황에 대비하는 법</title><link>https://diary.metacog.co.kr/posts/2026-08-27-diary/</link><pubDate>Thu, 27 Aug 2026 12:17:54 +0900</pubDate><guid>https://diary.metacog.co.kr/posts/2026-08-27-diary/</guid><description>&lt;h2 id="오늘의-문장"&gt;오늘의 문장&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;break-glass&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="일기-diary"&gt;일기 (Diary)&lt;/h2&gt;
&lt;p&gt;Today at work, we had a full system outage right before a major client demo. Nobody could log in, and the whole team started panicking. Fortunately, our senior engineer remembered we had a break-glass account set up for exactly this kind of emergency. She pulled up the credentials, we got back in, and somehow pulled off the demo without the client noticing anything was wrong. It felt like one of those movie moments where someone smashes the little red box on the wall. I learned today that having a break-glass plan isn&amp;rsquo;t paranoia — it&amp;rsquo;s just being prepared.&lt;/p&gt;</description></item></channel></rss>