← Public packages
@kentcdodds/closing-the-agentic-loop
Closing the Agentic Loop: Kent C. Dodds's talk and workshop deck. Default short talk; ?event=aie-2026 is the AIE hour cut with a Podium QR; ?format=full adds labs.
Files
<section id="doors" data-title="One-way vs two-way doors">
<style>
@scope {
.cards { display: grid; grid-template-columns: 1fr 1.25fr; gap: 36px; }
.card { padding: 32px 40px; }
.card .t { font: 800 66px var(--font-display); line-height: 1.05; margin-bottom: 18px; }
.two .t { color: var(--green); }
.one .t { color: var(--amber); }
.card p, .card li { font-size: 50px; color: var(--ink); margin: 0 0 12px; }
.card ul { margin: 0; padding-left: 1.1em; }
.flag { margin-top: auto; font-size: 58px; color: var(--ink); }
.flag strong { color: var(--green); }
}
</style>
<h2>One-way vs two-way doors</h2>
<div class="cards">
<div class="card two"><div class="t">Two-way</div><p>Cheap to reverse. Ship it, change it if wrong.</p></div>
<div class="card one"><div class="t">One-way</div><ul><li>First + last name into one field</li><li>Public API contracts</li><li>Deleting user data</li></ul></div>
</div>
<p class="flag"><strong>Feature flags</strong> turn a one-way door into a two-way door.</p>
<aside class="notes">
<p>The Door field on the PR template. In my words: "a two-way means that it's cheap to reverse. If we got something wrong or something, we can ship it and we can change it back." "A one-way door is a lot more expensive to undo."</p>
<p>The examples: you have a first name and a last name and decide to change to just name, so a migration combines them with a space. "That would be really expensive to undo because some people might have a space in their first name." Changes to public contracts: everybody starts using the new API, and their integrations break if you go back. Deleting user data.</p>
<p>"If you've got a one-way door, that's an area where you probably want to do some review and make sure you're doing a lot more manual verification." The template says the same: "spend the review here."</p>
<p>"Feature flags are... how you turn a one-way door into a two-way door for as long as that feature flag exists." Callback when we get to the flags slide in pillar 3.</p>
<p>Product decisions too: "it's so much easier to add new functionality than remove existing functionality," so I start simple.</p>
</aside>
</section>