← Public packages
@kentcdodds/the-last-software-engineer
The Last Software Engineer: Kent C. Dodds's React Summit US 2026 talk deck. Judgment and product engineering in an AI era.
Files
<section id="primitives" class="chat-slide" data-title="Think in primitives" data-steps="2">
<h2 data-m="rise">Think in primitives</h2>
<div class="chat" data-m="rise" data-d="200">
<div class="lights" aria-hidden="true"><i></i><i></i><i></i></div>
<div class="bar"><img class="avatar" src="c/img/avatar-cole.webp" alt=""><span class="name">Cole</span><span class="role">Coder</span></div>
<div class="screen" data-until="1">
<div class="msg me" style="--i:1">Also, every time I select a new guide, some of the elements that do not change are still animating and it's distracting.</div>
<div class="msg me" style="--i:3">We should not clear the current docs or experience a flash of loading state when changing routes... make sure we have the <mark>necessary primitives</mark> to make this the <mark>pit of success</mark> path for the future</div>
</div>
<div class="screen" data-at="1" data-until="2">
<div class="msg them" style="--i:0">That flash on docs nav shouldn't happen: launching an agent to audit route transitions app-wide and put the right primitives in the pit of success.</div>
<div class="msg them" style="--i:1">First pass is in: docs keep a persistent page frame, and routes share one loader that keeps the last good content on screen. <mark>20 account/admin routes still hand-roll their loading.</mark></div>
</div>
<div class="screen" data-at="2">
<div class="msg me" style="--i:0">On the loading thing<span class="quote">20 account/admin routes still hand-roll their loading.</span><mark>I want those fixed now</mark></div>
<div class="msg them" style="--i:1">Merged: every hand-rolled account/admin route is on one shared loader with last-good content; <mark>a lint rule bans the old pattern</mark> from routes.</div>
</div>
<div class="input" aria-hidden="true"><span class="circle"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round"><path d="M12 5v14M5 12h14"/></svg></span><span class="ph" data-chrome>Message Cole</span><span class="circle"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><rect x="9" y="3" width="6" height="11" rx="3"/><path d="M5.5 11a6.5 6.5 0 0 0 13 0M12 17.5V21"/></svg></span><span class="circle send"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2.4" stroke-linecap="round" stroke-linejoin="round"><path d="M12 19V5M5.5 11.5 12 5l6.5 6.5"/></svg></span></div>
</div>
<aside class="notes">
<p>First habit: think in primitives. This was a small annoyance. When I switched guides in the docs, things that hadn't changed were re-animating, and there was a flash of loading state.</p>
<p>The implementation fix is easy: patch that one page. But I didn't ask for that. I said this is a general principle: make sure we have the necessary primitives so the right thing is the pit of success for the future.</p>
<p>[click] Cole audited route transitions across the whole app and built a shared loader that keeps the last good content on screen. And it told me 20 account and admin routes were still hand-rolling their loading.</p>
<p>[click] I said: I want those fixed now. And the result wasn't just a fix. It was a lint rule that bans the old pattern, so the next agent, or the next person, can't reintroduce the problem. That's thinking in primitives: you don't fix the instance, you change the system so the instance can't happen.</p>
</aside>
</section>