<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TOCTOU on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/toctou/</link><description>Recent content in TOCTOU on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 31 May 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/toctou/index.xml" rel="self" type="application/rss+xml"/><item><title>Product Thinking (2): Security Engineering — Defense Without Paranoia</title><link>https://www.chenk.top/en/product-thinking/02-security/</link><pubDate>Sun, 31 May 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/product-thinking/02-security/</guid><description>&lt;h2 id="the-kind-of-security-that-disappears" class="heading-anchor">The Kind of Security That Disappears&lt;a href="#the-kind-of-security-that-disappears" class="heading-link" aria-label="Permalink to this section" title="Copy link to this section">#&lt;/a>
&lt;/h2>&lt;p>I used to think security was something you bolted on: a checklist before release, a penetration test once a quarter, a code review with &amp;ldquo;security&amp;rdquo; in the title. I was wrong. The systems I have built over the past two years taught me a different lesson — the best security is the kind you forget about because it is already woven into the system itself.&lt;/p></description></item></channel></rss>