<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>System Design - Tag - Daily Deep Think</title>
        <link>https://blog.baifan.site/en/tags/system-design/</link>
        <description>System Design - Tag - Daily Deep Think</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>blog@baifan.site (ByF)</managingEditor>
            <webMaster>blog@baifan.site (ByF)</webMaster><lastBuildDate>Mon, 13 Jul 2026 14:00:00 &#43;0800</lastBuildDate><atom:link href="https://blog.baifan.site/en/tags/system-design/" rel="self" type="application/rss+xml" /><item>
    <title>Agent Interview Questions: Who Has Actually Done the Work</title>
    <link>https://blog.baifan.site/en/agent-interview-questions/</link>
    <pubDate>Mon, 13 Jul 2026 14:00:00 &#43;0800</pubDate><author>
                    <name>ByF</name>
                </author><guid>https://blog.baifan.site/en/agent-interview-questions/</guid>
    <description><![CDATA[<!-- more -->
<blockquote>
  <p><strong>Attachment download</strong>: <a href="/files/agent-interview-questions.pdf" rel="">Agent Interview Questions.pdf</a> — handy for printing or offline reading</p>

</blockquote><h2 id="why-would-you-need-multiple-agents" class="headerLink">
    <a href="#why-would-you-need-multiple-agents" class="header-mark"></a>Why Would You Need Multiple Agents</h2><p>An opening question to separate people who have &ldquo;read the articles&rdquo; from people who have &ldquo;actually built one&rdquo;.</p>
<p><strong>The bad answer:</strong> &ldquo;Multi-agent enables parallel processing, which improves system throughput and robustness.&rdquo;</p>
<p>Every word of that is correct, but if you follow up with &ldquo;so after splitting into two agents, did throughput actually double?&rdquo;, they stall. The reality: inter-agent communication has overhead, coordination has complexity, and after the split total throughput may well drop. Adding agents is not like adding CPU cores.</p>]]></description>
</item>
<item>
    <title>AI Psychosis: When MTTR Fanaticism Meets Resilience</title>
    <link>https://blog.baifan.site/en/ai-mttr-mtbf-resilience-psychosis/</link>
    <pubDate>Tue, 24 Feb 2026 14:00:00 &#43;0800</pubDate><author>
                    <name>ByF</name>
                </author><guid>https://blog.baifan.site/en/ai-mttr-mtbf-resilience-psychosis/</guid>
    <description><![CDATA[<div class="featured-image">
                <img src="/pictures/note/ai-mttr-mtbf-featured.svg" referrerpolicy="no-referrer">
            </div><!-- more -->
<p>I have a strong intuition: some companies in the tech industry right now are going through a full-blown AI psychosis, and inside those companies, rational conversation is simply impossible. I&rsquo;m not talking about strangers — I&rsquo;m talking about personal friends I deeply respect. That leaves me worried about how this ends.</p>
<p>This fear has a specific source. I lived through the great MTBF (mean time between failures) vs MTTR (mean time to recovery) debate when infrastructure moved from traditional ops to cloud and cloud automation. Now those exact same arguments are resurfacing in a new costume — only the scope has widened from infrastructure to the entire software industry, and possibly to the whole world.</p>]]></description>
</item>
</channel>
</rss>
