
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, and data engineering — plus mindset essays on confidence, routines, health, and sport psychology.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Sat, 15 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/기술문서/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/architecture/2026-08-15-guide-design-docs.en</guid>
    <title>The Complete Guide to Design Docs: Documents That Preserve Decisions and Documents That Vanish</title>
    <link>https://www.youngju.dev/blog/architecture/2026-08-15-guide-design-docs.en</link>
    <description>This guide treats design documents as a team decision-making infrastructure rather than a writing skill. It covers which of the four formats (1-pager, design doc, ADR, RFC) to use when, how to run the review as a process, how decisions expire, and the eight ways documents fail.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>설계문서</category><category>adr</category><category>rfc</category><category>design-doc</category><category>기술문서</category><category>의사결정</category><category>아키텍처</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/architecture/2026-08-15-guide-design-docs.ja</guid>
    <title>設計ドキュメント完全ガイド: 決定を残す文書と消える文書</title>
    <link>https://www.youngju.dev/blog/architecture/2026-08-15-guide-design-docs.ja</link>
    <description>設計ドキュメントを文章術ではなくチームの意思決定インフラとして扱います。1-pager・設計ドキュメント・ADR・RFC のどれをいつ使うか、レビューをどう運用するか、決定がどう期限切れになるか、そして文書が失敗する八つの形を整理します。</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>설계문서</category><category>adr</category><category>rfc</category><category>design-doc</category><category>기술문서</category><category>의사결정</category><category>아키텍처</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/architecture/2026-08-15-guide-design-docs</guid>
    <title>설계 문서 완전 가이드: 결정을 남기는 문서와 사라지는 문서</title>
    <link>https://www.youngju.dev/blog/architecture/2026-08-15-guide-design-docs</link>
    <description>설계 문서를 글쓰기 기술이 아니라 팀의 의사결정 인프라로 다룹니다. 1-pager·설계 문서·ADR·RFC 중 무엇을 언제 쓰는지, 리뷰를 어떤 절차로 운영하는지, 내려진 결정이 어떻게 만료되는지, 그리고 문서가 실패하는 여덟 가지 방식을 정리합니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>설계문서</category><category>adr</category><category>rfc</category><category>design-doc</category><category>기술문서</category><category>의사결정</category><category>아키텍처</category>
  </item>

    </channel>
  </rss>
