
  <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/posix-time/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/2026-07-11-no-leap-second-2026.en</guid>
    <title>No Leap Second in 2026 — and the Negative One No System Has Ever Run</title>
    <link>https://www.youngju.dev/blog/2026-07-11-no-leap-second-2026.en</link>
    <description>On 6 July 2026 the IERS issued Bulletin C 72: no leap second at the end of December 2026. It reads like quiet news, but since Earth started spinning faster around 2016, the first-ever negative leap second is now on the table. This piece explains what a leap second is, why POSIX time cannot represent one, what the real 2012 and 2017 outages taught us, and what engineers should check now — before the whole planet runs, simultaneously, a code path that has never executed in production.</description>
    <pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>leap-second</category><category>utc</category><category>ntp</category><category>distributed-systems</category><category>posix-time</category><category>timekeeping</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/2026-07-11-no-leap-second-2026.ja</guid>
    <title>2026年も閏秒なし — そして誰も動かしたことのない負の閏秒</title>
    <link>https://www.youngju.dev/blog/2026-07-11-no-leap-second-2026.ja</link>
    <description>2026年7月6日、IERSはBulletin C 72で「2026年12月末に閏秒なし」を発表しました。一見静かなニュースですが、地球の自転が2016年頃からむしろ速くなり、史上初の負の閏秒を入れる可能性が現実に出てきました。閏秒とは何か、なぜPOSIX時間がそれを表現できないのか、2012年と2017年の実際の障害が何を教えてくれるのか、そして一度も実行されたことのない負の閏秒の処理経路を前に、エンジニアが今何を確認すべきかを整理します。</description>
    <pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>leap-second</category><category>utc</category><category>ntp</category><category>distributed-systems</category><category>posix-time</category><category>timekeeping</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/2026-07-11-no-leap-second-2026</guid>
    <title>2026년에도 윤초는 없다 — 그리고 아무도 겪어본 적 없는 음의 윤초</title>
    <link>https://www.youngju.dev/blog/2026-07-11-no-leap-second-2026</link>
    <description>IERS가 2026년 7월 6일 Bulletin C 72로 &quot;2026년 12월 말 윤초 없음&quot;을 발표했습니다. 겉보기엔 조용한 소식이지만, 지구 자전이 2016년부터 오히려 빨라지면서 사상 처음으로 음의 윤초를 넣어야 할 가능성이 생겼습니다. 윤초가 무엇인지, POSIX 시간이 왜 이걸 표현하지 못하는지, 2012년과 2017년의 실제 장애가 무엇을 가르쳐 주는지, 그리고 한 번도 실행된 적 없는 음의 윤초 처리 경로를 앞두고 엔지니어가 지금 무엇을 확인해야 하는지 정리합니다.</description>
    <pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>leap-second</category><category>utc</category><category>ntp</category><category>distributed-systems</category><category>posix-time</category><category>timekeeping</category>
  </item>

    </channel>
  </rss>
