Merge Conflict is a developer show built around the messy middle of modern software work. James and Frank talk through tools as people who use them, break them, argue with them, and then try them again the next week. Recent episodes lean hard into AI-assisted development. Agents, Copilot, MCP servers, skills, GitHub Actions, GitHub Spark, source maps, and native UI validation all show up as practical problems rather than abstract trends. The show has a casual surface. Under it is a steady concern with whether new tools actually help developers ship better software. That distinction matters. AI is not treated as a magic layer that makes engineering disappear, and it is not dismissed as a toy. The conversations return to friction: authentication, debugging, interface inspection, brownfield code, multitasking agents, and the work of checking what an agent produced. Mobile development gives the show much of its texture. .NET MAUI, iCircuit, iPad behavior, iPhone layouts, popovers, toolbars, and old UI decisions become material for larger questions about software taste and maintainability. The hosts can be goofy. They can also be exacting. A discussion might start with an aside, a camera setup, or a ride in an autonomous vehicle, then land on why graphical interfaces still matter when command-line agent tools are everywhere. That movement gives Merge Conflict its shape: loose entry, technical pressure, practical judgment. It suits a listener who wants current developer-tool talk without a scripted product-demo feel. The show is especially useful when the subject is the gap between what a tool promises and what a working developer has to do to make it useful. It is not pristine. It is not trying to be. The value is in hearing builders think out loud, disagree, revise, and keep shipping.