<?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>Engineering-Culture on 매일 영어 일기</title><link>https://diary.metacog.co.kr/tags/engineering-culture/</link><description>Recent content in Engineering-Culture on 매일 영어 일기</description><generator>Hugo</generator><language>ko-kr</language><lastBuildDate>Wed, 30 Sep 2026 10:17:52 +0900</lastBuildDate><atom:link href="https://diary.metacog.co.kr/tags/engineering-culture/index.xml" rel="self" type="application/rss+xml"/><item><title>2026-09-30 실패를 공개하는 엔지니어들의 문화</title><link>https://diary.metacog.co.kr/posts/2026-09-30-diary-2/</link><pubDate>Wed, 30 Sep 2026 10:17:52 +0900</pubDate><guid>https://diary.metacog.co.kr/posts/2026-09-30-diary-2/</guid><description>&lt;h2 id="오늘의-문장"&gt;오늘의 문장&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;engineers publish honest accounts of their own outages&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="일기-diary"&gt;일기 (Diary)&lt;/h2&gt;
&lt;p&gt;I spent part of my afternoon reading tech blogs, and one post really stuck with me. It was about how engineers publish honest accounts of their own outages, including every mistake they made along the way. At first I thought it was strange to admit failures so publicly, but then I realized how much I learned just from reading one post-mortem. The writer explained exactly what went wrong, why the team missed it, and what they changed afterward. It was more useful than any tutorial I&amp;rsquo;ve read this month. I think there&amp;rsquo;s something quietly brave about that kind of honesty. I want to bring the same attitude to my own mistakes.&lt;/p&gt;</description></item></channel></rss>