Speed, prioritization, and maintainability — product engineering with Julius Marminge

What this episode covers

Kent talks with Julius Marminge about building T3 Code in the agent-orchestrator wave: why speed still matters, why fast shipping does not mean shipping every possible feature, and how product judgment becomes more important as parallel AI workflows make implementation cheap. They dig into dogfooding, core-product trade-offs, monetization pressure, customization vs defaults, and how to keep agent-built software maintainable over time. 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. Homework 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. Resources T3 CodeT3 ChatJulius Marminge — GitHubOpenCode Guest: Julius Marminge GitHub: @juliusmarminge𝕏: @jullerino Host: Kent C. Dodds Website: kentcdodds.com𝕏: @kentcdoddsGitHub: @kentcdoddsYouTube: kentcdodds-plusPodcast: epicproduct.engineer See on Epic Product Engineer

PodParley-generated summary based on available episode metadata and transcript content.