<?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>Work-Trouble on 매일 영어 일기</title><link>https://diary.metacog.co.kr/tags/work-trouble/</link><description>Recent content in Work-Trouble on 매일 영어 일기</description><generator>Hugo</generator><language>ko-kr</language><lastBuildDate>Wed, 19 Aug 2026 07:40:35 +0900</lastBuildDate><atom:link href="https://diary.metacog.co.kr/tags/work-trouble/index.xml" rel="self" type="application/rss+xml"/><item><title>2026-08-19 우리를 곤란하게 만든 그 지점</title><link>https://diary.metacog.co.kr/posts/2026-08-19-diary/</link><pubDate>Wed, 19 Aug 2026 07:40:35 +0900</pubDate><guid>https://diary.metacog.co.kr/posts/2026-08-19-diary/</guid><description>&lt;h2 id="오늘의-문장"&gt;오늘의 문장&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;Where this bit us&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="일기-diary"&gt;일기 (Diary)&lt;/h2&gt;
&lt;p&gt;We had a rough morning at work today. The deployment failed right before the client presentation, and the whole team was scrambling to figure out what went wrong. It took us about an hour, but we finally pinpointed where this bit us — a config file nobody had updated after the last merge. Honestly, it was such a simple oversight, but the timing could not have been worse. We ended up postponing the demo by thirty minutes. Next time, I am going to insist we run a full checklist before any production push.&lt;/p&gt;</description></item></channel></rss>