<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kaizen on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/kaizen/</link><description>Recent content in Kaizen on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 02 Jun 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/kaizen/index.xml" rel="self" type="application/rss+xml"/><item><title>Product Thinking (4): Self-Healing Systems — Teaching Machines to Fix Themselves</title><link>https://www.chenk.top/en/product-thinking/04-self-healing/</link><pubDate>Tue, 02 Jun 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/product-thinking/04-self-healing/</guid><description>&lt;h2 id="the-bug-that-fixed-itself" class="heading-anchor">The Bug That Fixed Itself&lt;a href="#the-bug-that-fixed-itself" class="heading-link" aria-label="Permalink to this section" title="Copy link to this section">#&lt;/a>
&lt;/h2>&lt;p>One morning in late May 2026, I woke up to a DingTalk notification from my research agent system:&lt;/p>
&lt;blockquote>
&lt;p>&amp;ldquo;self_heal Rule 37 triggered: restarted research-pipeline after 3 consecutive OOM kills. Root cause: scanner thread retained full PDF buffers across iterations. Applied patch: explicit &lt;code>del&lt;/code> after extraction. Validation: 45 minutes post-patch, RSS stable at 1.2 GB (was 2.4 GB pre-patch).&amp;rdquo;&lt;/p></description></item></channel></rss>