If your coding agent keeps producing garbage, better prompting may not fix it. Kent shows how intentional system primitives make agents more reliable, efficient, composable, and auditable.
(00:00) - Bad agent output starts in the system
(00:37) - We are all tech leads now
(01:28) - What is a primitive?
(04:57) - Four moves: create, combine, delete, expand
(06:01) - Create: role-based access control
(07:59) - Combine: downshift and Kody packages
(10:37) - Delete: Instagram and Kody email
(12:22) - Expand: packages subscribe to events
(13:51) - Why good primitives work
(14:43) - Homework for your agent
(15:32) - Keep evolving the system
Better with Kent — durable skills for people who ship software.
If your coding agent keeps producing garbage, the model may not be the problem. Agents are only as effective as the system they work in: the UI components, APIs, data entities, platform tools, workflows, and trust boundaries they can reliably use.
Kent explains four moves for improving that system: create missing primitives, combine overlapping ones, delete rigid or unused ones, and expand the primitives that should cover more. The examples come from real product work — Kody's role-based access control and event subscriptions, PayPal's three combobox implementations becoming downshift, and Instagram winning by deleting most of Burbn.
The payoff is a smaller action space with less guessing, fewer brittle workarounds, and behavior you can actually audit. The episode closes with homework you can run in your own codebase today: ask your agent which primitives you should create, combine, delete, or expand.
Podden och tillhörande omslagsbild på den här sidan tillhör
Kent C. Dodds. Innehållet i podden är skapat av Kent C. Dodds och inte av,
eller tillsammans med, Poddtoppen.
