Show Notes
James Ward (Developer Advocate at AWS, Agentic AI Foundation Technical Committee Member) joins Marco to map out the fast-moving landscape of AI agents on the JVM. From MCP and ACP to Spring AI, Embabel, and Ktor — James explains how the JVM ecosystem has not only caught up with Python for building agents, but may have surpassed it. He also introduces SkillsJars (putting agent skills on Maven Central), explains effect-oriented programming and why it supercharges AI coding, and shares how he's been shipping five projects in two months entirely from his phone.
💡 In This Episode • Why the JVM is no longer second-class for AI agents • MCP vs ACP vs A2A — when to use which • Spring AI, Embabel (Rod Johnson), Ktor, LangChain4J compared • GOAP planning and domain-integrated context engineering • Agent skills vs MCP servers — and why skills are winning • SkillsJars: versioned, composable skills on Maven Central • Testing non-deterministic agents with evals • Effect-oriented programming and why types matter more than ever
Timestamps: (00:00:00) Intro (00:00:49) Guest intro: James Ward, AWS, and the Agentic AI Foundation (00:01:37) Are developers now orchestrating AI agents? (00:02:51) Agent setup, context switching, and review fatigue (00:05:58) Why typed languages matter more in the AI era (00:07:14) Scala vs Kotlin vs Java (00:10:02) What agentic frameworks are and why they matter (00:14:08) MCP explained (00:19:42) ACP explained (00:21:56) How to get started with agent protocols and frameworks (00:23:43) JVM agent frameworks: Spring AI, Embabel, Koog, and LangChain4j (00:27:50) AIforJVM.com and building projects with AI (00:29:55) AI from your phone, dopamine, and productivity (00:33:14) Testing, evals, orchestration, and reliability in agent systems (00:41:03) What skills are and where they fit (00:43:46) SkillsJars and packaging skills for the JVM (00:49:34) Which AI standards will actually last? (00:55:35) Effect-oriented programming explained (01:06:37) Giveaway question (01:08:24) Rapid-fire round (01:10:58) Outro
New episodes every other Wednesday. Subscribe for more developer-focused conversations. 🎥 Watch the full episode on YouTube: https://youtu.be/ACP0Nx-sW10
More from The Marco Show
Michael Simons, a longtime Java developer and Neo4j engineer, joins Marco to talk about the engineering principles that have stayed relevant across decades of changing technologies. The conversation covers database-first thinking, Spring and the Java ecosystem, graph databases, developer tooling, and why pragmatic decisions often matter more than chasing the “best” framework. They also discuss how AI is changing software development, where AI tools genuinely help, and why human judgment and responsibility still matter. 💡 In this episode: Why Michael still starts with the data model when building applications
Venkat Subramaniam joins Marco to talk about what AI is really changing for developers. They discuss why AI often impresses novices more than experts, why “AI first” is the wrong mindset, and why critical thinking, fundamentals, and judgment matter more than ever. 💡 In this episode: Why AI is better at finding problems than writing code
Sébastien Deleuze, a longtime Spring Framework committer and member of the Spring AI team, joins Marco to talk about how 13 years on the Spring team shaped his pragmatic approach to software development. The conversation covers how Spring AI fits into the Spring ecosystem, why enterprise AI still needs deterministic workflows and human accountability, and why long-term software quality matters even as GenAI changes how code gets written. 💡 In this episode: How Sébastien joined the Spring team through open source contributions
Josh Long, Spring Developer Advocate at Broadcom, joins Marco to cover 25 years of Spring history and what the JVM's real shot at the AI era actually looks like. Josh has published a weekly blog since 2011 and a weekly podcast since 2018 without missing an episode. This conversation gets into why vibe coding concerns him as an engineer, what accountability for AI-generated code actually means, and why Python's dominance in AI is more a marketing gap than a technical one. 💡 In this episode: Spring's origin story: why the documentation came before the code
Martin Lippert, longtime maintainer of Spring Tools and one of the people who has witnessed developer tooling evolve from Eclipse to VS Code, joins Marco to discuss how AI is transforming Java development, and what that means for the future of software engineering. ⏱️ Timestamps: (00:00) Teaser(00:38) Meet Martin Lippert, Spring Tools & the evolution of Java IDEs(03:28) What happened to Eclipse? Lessons from the rise and fall of a Java giant(12:20) Why Spring Tools moved to VS Code and embraced the Language Server Protocol(20:03) How AI is changing Java development and everyday coding workflows(21:59) Martin's AI workflow: Cursor, IDEs, code review & testing(26:16) Building developer tools for AI agents instead of humans(31:10) Why AI is changing release cycles and developer tooling(36:03) AI review fatigue, cognitive depth & trusting generated code(39:06) Will AI replace senior developers? What happens to junior engineers?(42:16) The future of Java, Spring & software architecture in an AI-first world(48:42) AI's hidden energy problem and the sustainability challenge(54:39) Practical tips for greener software engineering and AI usage(1:00:06) Giveaway & rapid-fire questions