
  <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>Wed, 12 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/tech-report/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/ai-papers/2026-08-12-model-internals-reading-a-tech-report.en</guid>
    <title>Reading a Technical Report Critically — What Gets Written Down and What Goes Missing</title>
    <link>https://www.youngju.dev/blog/ai-papers/2026-08-12-model-internals-reading-a-tech-report.en</link>
    <description>How to separate the verifiable from the unverifiable in a model technical report. Covers the limits of self-reported benchmarks, the places where a config and a report disagree, values that could not be read from gated repositories, and the verification procedure used throughout this series, illustrated with real cases.</description>
    <pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ai-papers</category><category>model-internals</category><category>tech-report</category><category>benchmarks</category><category>evaluation</category><category>reproducibility</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/ai-papers/2026-08-12-model-internals-reading-a-tech-report.ja</guid>
    <title>技術レポートを批判的に読む — 何が書かれ、何が抜けるか</title>
    <link>https://www.youngju.dev/blog/ai-papers/2026-08-12-model-internals-reading-a-tech-report.ja</link>
    <description>モデル技術レポートで検証可能な項目と検証不可能な項目を区別する方法を整理します。自己申告ベンチマークの限界、config とレポートが食い違う箇所、ゲートされたリポジトリで確認できなかった値、そしてシリーズ全体で用いた確認手順を実例とともに示します。</description>
    <pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ai-papers</category><category>model-internals</category><category>tech-report</category><category>benchmarks</category><category>evaluation</category><category>reproducibility</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/ai-papers/2026-08-12-model-internals-reading-a-tech-report</guid>
    <title>기술 리포트 비판적으로 읽기 — 무엇이 적히고 무엇이 빠지는가</title>
    <link>https://www.youngju.dev/blog/ai-papers/2026-08-12-model-internals-reading-a-tech-report</link>
    <description>모델 기술 리포트에서 검증 가능한 항목과 검증 불가능한 항목을 구분하는 법을 정리합니다. 자체 보고 벤치마크의 한계, config와 리포트가 어긋나는 지점, 게이트된 저장소에서 확인할 수 없는 값, 그리고 시리즈 전체에서 쓴 확인 절차를 실제 사례로 보여 줍니다.</description>
    <pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ai-papers</category><category>model-internals</category><category>tech-report</category><category>benchmarks</category><category>evaluation</category><category>reproducibility</category>
  </item>

    </channel>
  </rss>
