<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel>
        <title>Alex Rowan / Blog</title>
        <link>https://www.benbaert.com</link>
        <description><![CDATA[Notes on engineering, systems, and product craft.]]></description>
        <atom:link href="https://www.benbaert.com/rss.xml" rel="self"
                   type="application/rss+xml" />
        <lastBuildDate>Fri, 11 Apr 2025 00:00:00 UT</lastBuildDate>
        <item>
    <title>Building Sustainable On-Call Rotations</title>
    <link>https://www.benbaert.com/blog/sustainable-oncall/index.html</link>
    <description><![CDATA[<p>On-call design is organizational design.</p>
<p>Teams that run resilient rotations do three things well:</p>
<ol type="1">
<li>Keep alert quality high.</li>
<li>Hold blameless, actionable incident reviews.</li>
<li>Budget dedicated reliability work each cycle.</li>
</ol>]]></description>
    <pubDate>Fri, 11 Apr 2025 00:00:00 UT</pubDate>
    <guid>https://www.benbaert.com/blog/sustainable-oncall/index.html</guid>
    <dc:creator>Alex Rowan</dc:creator>
</item>
<item>
    <title>Writing Engineering RFCs People Actually Use</title>
    <link>https://www.benbaert.com/blog/writing-clear-engineering-rfcs/index.html</link>
    <description><![CDATA[<p>Clear RFCs make tradeoffs legible. They should explicitly answer:</p>
<ul>
<li>What outcome matters?</li>
<li>Which options were rejected and why?</li>
<li>What migration path is expected?</li>
</ul>
<p>When documents answer these questions, review quality improves dramatically.</p>]]></description>
    <pubDate>Sat, 22 Mar 2025 00:00:00 UT</pubDate>
    <guid>https://www.benbaert.com/blog/writing-clear-engineering-rfcs/index.html</guid>
    <dc:creator>Alex Rowan</dc:creator>
</item>
<item>
    <title>Platform as Product, Not Internal Ticket Queue</title>
    <link>https://www.benbaert.com/blog/platform-as-product/index.html</link>
    <description><![CDATA[<p>A platform team creates leverage when it owns a real roadmap, explicit customer segments, and measurable adoption goals.</p>
<p>Without this, internal tooling becomes reactive infrastructure work with weak strategic impact.</p>]]></description>
    <pubDate>Wed, 05 Mar 2025 00:00:00 UT</pubDate>
    <guid>https://www.benbaert.com/blog/platform-as-product/index.html</guid>
    <dc:creator>Alex Rowan</dc:creator>
</item>
<item>
    <title>Notes on Technical Leadership in Growth Stages</title>
    <link>https://www.benbaert.com/blog/notes-on-technical-leadership/index.html</link>
    <description><![CDATA[<p>As organizations grow, ambiguity compounds faster than headcount. Technical leadership must shift from direct execution to operating systems:</p>
<ul>
<li>explicit decision records</li>
<li>architecture reviews with clear ownership</li>
<li>predictable planning rituals</li>
</ul>
<p>These mechanisms improve speed by reducing rework.</p>]]></description>
    <pubDate>Sun, 16 Feb 2025 00:00:00 UT</pubDate>
    <guid>https://www.benbaert.com/blog/notes-on-technical-leadership/index.html</guid>
    <dc:creator>Alex Rowan</dc:creator>
</item>
<item>
    <title>Designing for Observability From Day One</title>
    <link>https://www.benbaert.com/blog/designing-for-observability/index.html</link>
    <description><![CDATA[<p>The cheapest time to make software observable is before interfaces harden.</p>
<p>When teams define key business and platform signals while designing a service boundary, they ship faster and recover faster.</p>]]></description>
    <pubDate>Mon, 27 Jan 2025 00:00:00 UT</pubDate>
    <guid>https://www.benbaert.com/blog/designing-for-observability/index.html</guid>
    <dc:creator>Alex Rowan</dc:creator>
</item>
<item>
    <title>Shipping AI Features Without Shipping Chaos</title>
    <link>https://www.benbaert.com/blog/shipping-ai-products/index.html</link>
    <description><![CDATA[<p>Most AI roadmaps fail in the handoff between a promising demo and a reliable product surface.</p>
<p>Three habits close that gap:</p>
<ol type="1">
<li>Define model behavior contracts early.</li>
<li>Design graceful fallback behavior first.</li>
<li>Instrument quality feedback loops before launch.</li>
</ol>
<p>Treat AI work as product engineering, not isolated experimentation.</p>]]></description>
    <pubDate>Thu, 09 Jan 2025 00:00:00 UT</pubDate>
    <guid>https://www.benbaert.com/blog/shipping-ai-products/index.html</guid>
    <dc:creator>Alex Rowan</dc:creator>
</item>

    </channel>
</rss>
