Rhys has an unusually current perspective on product engineering because he is working right at the edge of the agent tooling shift. The conversation starts with his recent work on Vercel Domains and then moves into Executor, where the challenge is no longer just implementing integrations, but choosing the abstractions that make a system composable, safe, and pleasant to use over time.

What makes the episode strong is how often it comes back to product judgment instead of novelty. Rhys and Kent talk about finding the right primitives, observing how other products solve hard UX problems, resisting the urge to ship every request immediately, and building systems that help agents without letting them become dangerously "helpful."

• Create a dedicated notes channel or system where you save examples of products doing something well.
• Use those notes as reusable product input: when you need to build a flow later, pull the examples back up instead of starting from scratch.

• Executor
• Rhys Sullivan — site
• Executor — GitHub
• OpenCode

• Company: Executor
• GitHub: @RhysSullivan
• 𝕏: @RhysSullivan

• Website: kentcdodds.com
• 𝕏: @kentcdodds
• GitHub: @kentcdodds
• YouTube: Kent C. Dodds

Watch this episode on YouTube

Alex brings a product and marketing lens that fits this season perfectly: great products do not just solve technical problems, they help the right people recognize that you understand their world. The conversation starts with finding an audience and quickly turns into a practical way to build product sense inside a company: learn how customers describe themselves, observe where they gather, listen for the language they use, and speak from their priorities instead of your own taste.

The second half gets into Sales Safari, Stacking the Bricks' observational research practice. Alex explains why surveys and interviews can miss important signal, what to look for in real conversations, and how notes on jargon, pain, worldview, and recommendations can turn scattered internet conversations into useful product understanding. The through-line is simple and demanding: reduce the distance between you and the people you serve so your software, messaging, and decisions feel anticipated rather than manipulative.

• The next time coworkers or product teammates disagree about direction, step back and observe the conversation.
• Ask: who is this disagreement in service of? Is it serving the customer, the decision maker, the loudest person, or someone else?
• Practice this once a day or once a week, then use the patterns you notice to decide what you should contribute.

• Stacking the Bricks
• 30x500
• The Tiny MBA
• The Mom Test
• Alex Hillman on X

• Company: Stacking the Bricks
• GitHub: @alexknowshtml
• 𝕏: @alexhillman

• Website: kentcdodds.com
• 𝕏: @kentcdodds
• GitHub: @kentcdodds
• YouTube: Kent C. Dodds

Watch this episode on YouTube

Julius is building right in the middle of one of the fastest-moving product categories in software, and that gives this episode a useful tension: everything feels possible, but that does not mean everything belongs in the product. The conversation covers the shift from one-agent-at-a-time coding to orchestration, why T3 Code focuses so much on a fast app layer, and how Julius thinks about what should live in the core product versus forks, plugins, or future work.

The deeper lesson is about judgment under speed. Julius and Kent keep returning to the same idea from different angles: when agents can generate a lot of implementation quickly, the real work is deciding what is worth building, what will age well, and what future decisions you might accidentally box yourself out of.

• Take a step back and look at your product from the whole picture, not just the slice you currently touch.
• Before prioritizing a feature, ask whether it keeps the product maintainable long-term and whether it fits the job to be done for your users.

• T3 Code
• T3 Chat
• Julius Marminge — GitHub
• OpenCode

• GitHub: @juliusmarminge
• 𝕏: @jullerino

• Website: kentcdodds.com
• 𝕏: @kentcdodds
• GitHub: @kentcdodds
• YouTube: Kent C. Dodds

Watch this episode on YouTube