
  <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 tech blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, distributed training, and data engineering.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Fri, 12 Jun 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/design-docs/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-06-12-technical-writing-design-docs-adr.en</guid>
    <title>The Developer Who Works in Writing — Design Docs, ADRs, and Persuasive Technical Writing</title>
    <link>https://www.youngju.dev/blog/culture/2026-06-12-technical-writing-design-docs-adr.en</link>
    <description>Why writing is the senior engineer leverage skill, practical templates for design docs and ADRs, the craft of documents that survive review, bad-writing before/after fixes, and how to use AI for writing without losing your own thinking. A technical writing guide for an era where docs get evaluated before code.</description>
    <pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>technical-writing</category><category>design-docs</category><category>adr</category><category>documentation</category><category>career</category><category>culture</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-06-12-technical-writing-design-docs-adr.ja</guid>
    <title>文章で働く開発者 — デザインドック、ADR、そして説得するテクニカルライティング</title>
    <link>https://www.youngju.dev/blog/culture/2026-06-12-technical-writing-design-docs-adr.ja</link>
    <description>文章力がシニアエンジニアのレバレッジである理由から、デザインドックとADRの実践テンプレート、レビューを通過するドキュメントの技術、悪い文章のビフォー/アフター、AIを書くことに活用する方法と限界まで。コードより先にドキュメントが評価される時代のテクニカルライティングガイドです。</description>
    <pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>technical-writing</category><category>design-docs</category><category>adr</category><category>documentation</category><category>career</category><category>culture</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-06-12-technical-writing-design-docs-adr</guid>
    <title>글로 일하는 개발자 — 디자인 독, ADR, 그리고 설득하는 테크니컬 라이팅</title>
    <link>https://www.youngju.dev/blog/culture/2026-06-12-technical-writing-design-docs-adr</link>
    <description>글쓰기가 시니어 엔지니어의 레버리지인 이유부터 디자인 독과 ADR의 실전 템플릿, 리뷰 받는 문서의 기술, 나쁜 문서 비포/애프터, AI를 글쓰기에 활용하는 법과 한계까지. 코드보다 문서가 먼저 평가되는 시대의 테크니컬 라이팅 가이드입니다.</description>
    <pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>technical-writing</category><category>design-docs</category><category>adr</category><category>documentation</category><category>career</category><category>culture</category>
  </item>

    </channel>
  </rss>
