
  <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/domain-knowledge/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/career/2026-08-15-career-skills-domain-knowledge.en</guid>
    <title>Why Domain Knowledge Is a Defensible Line — The Engineer Who Knows the Business</title>
    <link>https://www.youngju.dev/blog/career/2026-08-15-career-skills-domain-knowledge.en</link>
    <description>Domain knowledge is not in the code and usually not in the docs; it lives in people and in organizational habit. That makes it the single largest contributor to the verification cost this series has been tracking, and the reason people who carry it stay hard to replace. This piece covers what an engineer who knows the business does differently with questions, exceptions, and requirement interpretation, what breaks when the words used in meetings and the names in the code diverge, a six-step procedure for learning a domain, and the honest limit that domain knowledge does not transfer. The final part, 10 of 10, of the What Stays Expensive series.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>career</category><category>skills</category><category>domain-knowledge</category><category>ddd</category><category>ontology</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/career/2026-08-15-career-skills-domain-knowledge.ja</guid>
    <title>ドメイン知識はなぜ防衛線なのか — 業を知るエンジニアと技術だけのエンジニア</title>
    <link>https://www.youngju.dev/blog/career/2026-08-15-career-skills-domain-knowledge.ja</link>
    <description>ドメイン知識はコードにも無く、文書にもたいてい無く、人の記憶と組織の慣行だけにあります。だからこのシリーズが追ってきた検証費用を最も高くする要因であり、それを担える人が残る理由でもあります。この記事は、業を知るエンジニアが問いと例外と要求の解釈で何を違えるのか、会議で使う言葉とコードにある名前がずれると何が壊れるのか、ドメインを身につける六段階の手順、そしてドメイン知識が持ち越せないという限界を扱います。高いまま残る技術シリーズの最終回、第10回です。</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>career</category><category>skills</category><category>domain-knowledge</category><category>ddd</category><category>ontology</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/career/2026-08-15-career-skills-domain-knowledge</guid>
    <title>도메인 지식이 왜 방어선인가 — 업을 아는 엔지니어와 기술만 아는 엔지니어</title>
    <link>https://www.youngju.dev/blog/career/2026-08-15-career-skills-domain-knowledge</link>
    <description>도메인 지식은 코드에도 문서에도 없고 사람과 관행에만 있습니다. 그래서 이 시리즈가 말해 온 검증 비용을 가장 비싸게 만드는 요인이자, 그 비용을 감당할 수 있는 사람이 남는 이유입니다. 이 글은 업을 아는 엔지니어가 질문과 예외와 요구 해석에서 무엇을 다르게 하는지, 회의에서 쓰는 말과 코드에 있는 이름이 어긋날 때 무엇이 깨지는지, 도메인을 익히는 여섯 단계 절차, 그리고 도메인 지식이 이월되지 않는다는 한계를 다룹니다. 비싸게 남는 기술 시리즈의 마지막 10편입니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>career</category><category>skills</category><category>domain-knowledge</category><category>ddd</category><category>ontology</category>
  </item>

    </channel>
  </rss>
