<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Christian Yongwhan Lim — Working Notes</title>
    <link>https://www.yongwhan.io/writing.html</link>
    <description>Working notes on AI systems, competitive programming, practice, mentorship, and technical education.</description>
    <language>en-us</language>
    <lastBuildDate>Sat, 12 Sep 2026 12:00:00 -0400</lastBuildDate>
    <atom:link href="https://www.yongwhan.io/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Building a technical-talent pipeline that can outlast its builders</title>
      <link>https://www.yongwhan.io/institutional-systems-case-study.html</link>
      <guid isPermaLink="true">https://www.yongwhan.io/institutional-systems-case-study.html</guid>
      <pubDate>Sat, 12 Sep 2026 12:00:00 -0400</pubDate>
      <category>Institutional systems</category>
      <description>A public case study in connecting selection, contribution, mentorship, public products, measurement, shared ownership, and succession.</description>
    </item>
    <item>
      <title>Anatomy of a reliable contest release</title>
      <link>https://www.yongwhan.io/contest-release-anatomy.html</link>
      <guid isPermaLink="true">https://www.yongwhan.io/contest-release-anatomy.html</guid>
      <pubDate>Sat, 12 Sep 2026 11:00:00 -0400</pubDate>
      <category>Contest reliability</category>
      <description>A release-safe field guide to specifications, independent solutions, adversarial submissions, generated data, automation, and human sign-off.</description>
    </item>
    <item>
      <title>A technical leadership playbook</title>
      <link>https://www.yongwhan.io/technical-leadership-playbook.html</link>
      <guid isPermaLink="true">https://www.yongwhan.io/technical-leadership-playbook.html</guid>
      <pubDate>Sat, 12 Sep 2026 10:00:00 -0400</pubDate>
      <category>Technical leadership</category>
      <description>Concrete mechanisms for decision clarity, early risk communication, apprenticeship, sponsorship, recognition, and organizational memory.</description>
    </item>
    <item>
      <title>Problem-Solving Notebook: Increment All Divisors</title>
      <link>https://www.yongwhan.io/problem-solving-notebook.html</link>
      <guid isPermaLink="true">https://www.yongwhan.io/problem-solving-notebook.html</guid>
      <pubDate>Sat, 12 Sep 2026 09:00:00 -0400</pubDate>
      <category>Problem solving</category>
      <description>An annotated AtCoder solution using reverse traversal on the divisibility order, affine operation counts, and a feasible interval.</description>
    </item>
    <item>
      <title>A public-safe framework for production decisions</title>
      <link>https://www.yongwhan.io/production-decision-framework.html</link>
      <guid isPermaLink="true">https://www.yongwhan.io/production-decision-framework.html</guid>
      <pubDate>Fri, 11 Sep 2026 12:00:00 -0400</pubDate>
      <category>Decision systems</category>
      <description>Turn an ambiguous technical question into a reviewable choice across quality, cost, risk, delivery time, and reversibility.</description>
    </item>
    <item>
      <title>How to end a technical system responsibly</title>
      <link>https://www.yongwhan.io/ending-systems-responsibly.html</link>
      <guid isPermaLink="true">https://www.yongwhan.io/ending-systems-responsibly.html</guid>
      <pubDate>Fri, 11 Sep 2026 11:00:00 -0400</pubDate>
      <category>Technical stewardship</category>
      <description>A practical closeout checklist for infrastructure, cost, access, ownership, retained knowledge, and final operating state.</description>
    </item>
    <item>
      <title>What fifteen years in the ICPC changed about how I solve problems</title>
      <link>https://www.yongwhan.io/fifteen-years-in-icpc.html</link>
      <guid isPermaLink="true">https://www.yongwhan.io/fifteen-years-in-icpc.html</guid>
      <pubDate>Sat, 22 Aug 2026 12:00:00 -0400</pubDate>
      <category>ICPC</category>
      <description>Reflections across competing, coaching, judging, organizing, and teaching—and what those roles reveal about the real work of problem solving.</description>
    </item>
    <item>
      <title>How to build a sustainable university competitive-programming community</title>
      <link>https://www.yongwhan.io/building-a-competitive-programming-community.html</link>
      <guid isPermaLink="true">https://www.yongwhan.io/building-a-competitive-programming-community.html</guid>
      <pubDate>Sat, 22 Aug 2026 11:00:00 -0400</pubDate>
      <category>Community</category>
      <description>An entry ramp, durable weekly rituals, leadership succession, and institutional memory matter more than one exceptional team.</description>
    </item>
    <item>
      <title>How I review an ICPC contest with a team</title>
      <link>https://www.yongwhan.io/reviewing-an-icpc-contest.html</link>
      <guid isPermaLink="true">https://www.yongwhan.io/reviewing-an-icpc-contest.html</guid>
      <pubDate>Sat, 22 Aug 2026 10:00:00 -0400</pubDate>
      <category>Coaching</category>
      <description>The scoreboard records outcomes. A useful review reconstructs decisions, failure modes, and team interactions.</description>
    </item>
    <item>
      <title>Coaching without taking ownership away from the team</title>
      <link>https://www.yongwhan.io/coaching-without-taking-ownership.html</link>
      <guid isPermaLink="true">https://www.yongwhan.io/coaching-without-taking-ownership.html</guid>
      <pubDate>Sat, 22 Aug 2026 09:00:00 -0400</pubDate>
      <category>Coaching</category>
      <description>A coach should make reasoning visible and feedback precise—not become the hidden fourth contestant.</description>
    </item>
    <item>
      <title>How to choose problems for deliberate practice</title>
      <link>https://www.yongwhan.io/choosing-problems-for-practice.html</link>
      <guid isPermaLink="true">https://www.yongwhan.io/choosing-problems-for-practice.html</guid>
      <pubDate>Sat, 22 Aug 2026 08:00:00 -0400</pubDate>
      <category>Practice</category>
      <description>A four-stage sequence for isolating weaknesses, varying ideas, testing transfer, and finally adding pressure.</description>
    </item>
    <item>
      <title>From reading an editorial to owning the technique</title>
      <link>https://www.yongwhan.io/from-editorial-to-technique.html</link>
      <guid isPermaLink="true">https://www.yongwhan.io/from-editorial-to-technique.html</guid>
      <pubDate>Sat, 22 Aug 2026 07:00:00 -0400</pubDate>
      <category>Practice</category>
      <description>Turn an explanation into reconstructed reasoning, independent implementation, and evidence of transfer.</description>
    </item>
    <item>
      <title>Reliable voice agents are systems problems</title>
      <link>https://www.yongwhan.io/reliable-voice-agents.html</link>
      <guid isPermaLink="true">https://www.yongwhan.io/reliable-voice-agents.html</guid>
      <pubDate>Fri, 14 Aug 2026 12:00:00 -0400</pubDate>
      <category>AI systems</category>
      <description>The model matters, but the user experiences the entire system: latency, interruptions, tools, state, evaluation, and recovery.</description>
    </item>
    <item>
      <title>Practice that compounds</title>
      <link>https://www.yongwhan.io/practice-that-compounds.html</link>
      <guid isPermaLink="true">https://www.yongwhan.io/practice-that-compounds.html</guid>
      <pubDate>Fri, 14 Aug 2026 11:00:00 -0400</pubDate>
      <category>Practice</category>
      <description>A useful practice session should change how you approach the next problem, not merely add one more accepted solution to a profile.</description>
    </item>
    <item>
      <title>Mentorship is leverage, not a shortcut</title>
      <link>https://www.yongwhan.io/mentorship-is-leverage.html</link>
      <guid isPermaLink="true">https://www.yongwhan.io/mentorship-is-leverage.html</guid>
      <pubDate>Fri, 14 Aug 2026 10:00:00 -0400</pubDate>
      <category>Mentorship</category>
      <description>Good mentorship improves the quality and timing of feedback while leaving ownership of the work with the person being mentored.</description>
    </item>
  </channel>
</rss>
