
  <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>Sat, 11 Jul 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/maintainability/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/2026-07-11-write-code-for-humans.en</guid>
    <title>When an AI Maintains Your Code, Write for Humans Anyway</title>
    <link>https://www.youngju.dev/blog/2026-07-11-write-code-for-humans.en</link>
    <description>On July 10, 2026, Scott Robinson revived an old maxim with a twist: an LLM reads your codebase as its style guide, so every shortcut you merge becomes training data it repeats back at machine scale. We walk through his duplicated access-check example and his line that LLMs are sponges. Then the harder question — does writing for humans still matter when a machine is the next maintainer? It does, because humans still review and debug, and clarity is what makes a diff reviewable.</description>
    <pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ai</category><category>llm</category><category>code-quality</category><category>maintainability</category><category>craft</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/2026-07-11-write-code-for-humans.ja</guid>
    <title>AIがコードを保守する時代でも、人間のために書く</title>
    <link>https://www.youngju.dev/blog/2026-07-11-write-code-for-humans.ja</link>
    <description>2026年7月10日、Scott Robinson は古い格言を一ひねりして蘇らせました。LLM はあなたのコードベースをスタイルガイドのように読むため、あなたがマージしたあらゆる近道は、モデルが機械の規模で返してくる学習データになります。重複したアクセスチェックの例と、「LLM はスポンジだ」という彼の一文を追ったうえで、より難しい問いを立てます。次の保守者が機械であるときも、人間のために書くことは依然として重要か。重要です。人間は依然としてレビューしデバッグし、明快さこそが diff をレビュー可能にするからです。</description>
    <pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ai</category><category>llm</category><category>code-quality</category><category>maintainability</category><category>craft</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/2026-07-11-write-code-for-humans</guid>
    <title>AI가 당신의 코드를 유지보수해도, 그래도 사람을 위해 쓴다</title>
    <link>https://www.youngju.dev/blog/2026-07-11-write-code-for-humans</link>
    <description>2026년 7월 10일, Scott Robinson은 오래된 격언을 한 번 비틀어 되살렸습니다. LLM은 당신의 코드베이스를 스타일 가이드처럼 읽기 때문에, 당신이 병합한 모든 지름길이 곧 모델이 기계 규모로 되돌려주는 학습 데이터가 됩니다. 중복된 접근 권한 검사 예시와 &quot;LLM은 스펀지&quot;라는 그의 문장을 짚은 뒤, 더 어려운 질문을 던집니다. 다음 유지보수자가 기계일 때도 사람을 위해 쓰는 일이 여전히 중요한가? 그렇습니다. 사람은 여전히 리뷰하고 디버깅하며, 명료함이야말로 diff를 리뷰 가능하게 만들기 때문입니다.</description>
    <pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ai</category><category>llm</category><category>code-quality</category><category>maintainability</category><category>craft</category>
  </item>

    </channel>
  </rss>
