
  <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>Sun, 09 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/code-navigation/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-09-lookup-cost-decides-what-you-can-read.en</guid>
    <title>Lookup Cost Decides What You Can Read — From Two-Thousand-Year-Old Texts to Code Navigation</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-09-lookup-cost-decides-what-you-can-read.en</link>
    <description>A site has appeared that gathers 1,060 Greek and Latin works and, when you click any word, shows its lemma, its morphological parsing, and its dictionary entry. The impressive part is not the volume of text but that the lookup cost has been driven to zero — because twenty seconds two hundred times over turns a text into one that cannot be read. After checking how the site was built and what limits it declares about itself, we carry the same logic into our own codebases.</description>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>developer-tools</category><category>code-navigation</category><category>ide</category><category>reading</category><category>tooling</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-09-lookup-cost-decides-what-you-can-read.ja</guid>
    <title>参照コストが読めるものを決めます — 2000年前のテキストからコード探索まで</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-09-lookup-cost-decides-what-you-can-read.ja</link>
    <description>ギリシア語とラテン語の原典1,060編を集め、どの単語を押してもその場で見出し語と形態解析と辞書項目が出てくるサイトが公開されました。すごいのはテキストの量ではなく、参照コストをゼロにしたことです。1回20秒を200回やれば、そのテキストは読めないテキストになるからです。このサイトがどう作られ、何を限界として明示しているかを確認したうえで、同じ論理が私たちのコードベースでどう働くかへつなげます。</description>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>developer-tools</category><category>code-navigation</category><category>ide</category><category>reading</category><category>tooling</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-09-lookup-cost-decides-what-you-can-read</guid>
    <title>조회 비용이 읽을 수 있는 것을 정합니다 — 2천 년 된 텍스트에서 코드 탐색까지</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-09-lookup-cost-decides-what-you-can-read</link>
    <description>그리스어와 라틴어 원전 1,060편을 모아 두고 아무 단어나 누르면 원형과 형태 분석과 사전 항목이 뜨는 사이트가 공개됐습니다. 대단한 점은 텍스트의 양이 아니라 조회 비용을 0으로 만들었다는 것입니다. 한 번에 20초씩 200번이면 그 텍스트는 읽을 수 없는 텍스트가 되기 때문입니다. 이 사이트가 어떻게 만들어졌고 무엇을 한계로 밝히고 있는지 확인한 뒤, 같은 논리가 우리 코드베이스에서 어떻게 작동하는지로 이어 봅니다.</description>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>developer-tools</category><category>code-navigation</category><category>ide</category><category>reading</category><category>tooling</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-09-lookup-cost-decides-what-you-can-read.zh</guid>
    <title>查询成本决定你能读什么 —— 从两千年前的文本到代码导航</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-09-lookup-cost-decides-what-you-can-read.zh</link>
    <description>有个网站把 1,060 篇古希腊语与拉丁语原典聚在一起，点任何一个词，词元、形态分析和词典条目就当场浮出来。真正厉害的不是文本量，而是它把查询成本压到了零 —— 因为一次 20 秒、重复 200 次，那篇文本就变成了读不了的文本。我们先看这个网站是怎么做出来的、把什么写成了自己的局限，再把同一套逻辑接到我们自己的代码库上。</description>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>developer-tools</category><category>code-navigation</category><category>ide</category><category>reading</category><category>tooling</category>
  </item>

    </channel>
  </rss>
