Podcasts about orchestrating

Rizo Velovic Postseason Interview Survivor 50 comes to a close with a deep-dive post-season interview as host Rob Cesternino sits down with the unforgettable Rizgod for an exclusive look behind the scenes. Rob and Rizgod revisit the wild journey of Survivor 50, exploring the strategy, alliances, and personal moments that shaped one of the most talked-about seasons in franchise history. From playing back-to-back seasons to navigating tricky social waters and iconic twists, this episode is your ticket to understanding what really happened on and off camera. Rizgod opens up about his experience entering Survivor 50 just nine days after finishing Survivor 49, sharing the pressures of living up to his own legacy. He walks through the chaos of Vatu's tribal dynamics, the scramble to form new alliances after the tribe swap, and his evolving bond with players like Cirie and Ozzy. Rob and Rizgod also break down key moves—like surviving by social awareness after the Kyle medevac, the infamous Mr. Beast coin flip that turned Tribal Council on its head, and the strategic calculus behind blindsides and idol plays. The interview takes a personal turn as Rizgod explains how he processed his jury vote, his take on endgame strategies, and what it's like to be seen as both a superfine strategist and a target. – Rizgod's approach to back-to-back seasons and mentally resetting between games – Social slip-ups and adaptation after falling out of favor with early allies – The formation of the Cirie-Ozzy-Rizgod alliance—a modern echo of old-school strategy – Wildcard moments like the Mr. Beast advantage and the shifting post-merge landscape – Candid discussion about final tribal council, jury perceptions, and Rizgod's vision for his Survivor future As Rob and Rizgod analyze the highs and lows of Survivor 50, they ask: What does it really take to play—and win—against a cast of legends? How do you recover after a massive target gets painted on your back? Don't miss this honest, behind-the-scenes breakdown and personal reflection on the strategies, betrayals, and bonds that define Survivor 50. Chapters: 0:00 Rizgod Joins Rob to Recap 1:20 Preparing for Survivor 50 Return 3:45 Early Vaatu Chaos and Alliances 7:59 Building Trust with Aubry Bracco 11:17 Surviving the Tribe Swap Shakeup 16:36 Dee's Distrust and Idol Fallout 21:05 Ozzy Picks Rizo for Exile 24:21 After Exile: Strategic Losses Mount 29:44 Rick Devens' Idol at Tribal Shocks 37:40 MrBeast Coin Flip Changes Game 40:19 Power Broker Twist and Aubry’s Survival 46:42 Orchestrating the Endgame Boot Order 59:23 The RIZGOD and ROBGOD Sign-Off To order Rob’s book, The Tribe and I Have Spoken, visit www.robhasabook.com Never miss a minute of RHAP's extensive Survivor coverage! LISTEN: Subscribe to the Survivor podcast feed WATCH:  Watch and subscribe to the podcast on YouTube SUPPORT:  Become a RHAP Patron for bonus content, access to Facebook and Discord groups plus more great perks!

Rizo Velovic Postseason Interview Survivor 50 comes to a close with a deep-dive post-season interview as host Rob Cesternino sits down with the unforgettable Rizgod for an exclusive look behind the scenes. Rob and Rizgod revisit the wild journey of Survivor 50, exploring the strategy, alliances, and personal moments that shaped one of the most talked-about seasons in franchise history. From playing back-to-back seasons to navigating tricky social waters and iconic twists, this episode is your ticket to understanding what really happened on and off camera. Rizgod opens up about his experience entering Survivor 50 just nine days after finishing Survivor 49, sharing the pressures of living up to his own legacy. He walks through the chaos of Vatu's tribal dynamics, the scramble to form new alliances after the tribe swap, and his evolving bond with players like Cirie and Ozzy. Rob and Rizgod also break down key moves—like surviving by social awareness after the Kyle medevac, the infamous Mr. Beast coin flip that turned Tribal Council on its head, and the strategic calculus behind blindsides and idol plays. The interview takes a personal turn as Rizgod explains how he processed his jury vote, his take on endgame strategies, and what it's like to be seen as both a superfine strategist and a target. – Rizgod's approach to back-to-back seasons and mentally resetting between games – Social slip-ups and adaptation after falling out of favor with early allies – The formation of the Cirie-Ozzy-Rizgod alliance—a modern echo of old-school strategy – Wildcard moments like the Mr. Beast advantage and the shifting post-merge landscape – Candid discussion about final tribal council, jury perceptions, and Rizgod's vision for his Survivor future As Rob and Rizgod analyze the highs and lows of Survivor 50, they ask: What does it really take to play—and win—against a cast of legends? How do you recover after a massive target gets painted on your back? Don't miss this honest, behind-the-scenes breakdown and personal reflection on the strategies, betrayals, and bonds that define Survivor 50. Chapters: 0:00 Rizgod Joins Rob to Recap 1:20 Preparing for Survivor 50 Return 3:45 Early Vaatu Chaos and Alliances 7:59 Building Trust with Aubry Bracco 11:17 Surviving the Tribe Swap Shakeup 16:36 Dee's Distrust and Idol Fallout 21:05 Ozzy Picks Rizo for Exile 24:21 After Exile: Strategic Losses Mount 29:44 Rick Devens' Idol at Tribal Shocks 37:40 MrBeast Coin Flip Changes Game 40:19 Power Broker Twist and Aubry’s Survival 46:42 Orchestrating the Endgame Boot Order 59:23 The RIZGOD and ROBGOD Sign-Off To order Rob’s book, The Tribe and I Have Spoken, visit www.robhasabook.com Never miss a minute of RHAP's extensive Survivor coverage! LISTEN: Subscribe to the Survivor podcast feed WATCH:  Watch and subscribe to the podcast on YouTube SUPPORT:  Become a RHAP Patron for bonus content, access to Facebook and Discord groups plus more great perks!

The Slow-Motion Coup in Bolivia. Guest: Ernesto Araújo and Alejandro Peña Esclusa. The segment addresses the crisis in Bolivia, where Evo Morales is accused of orchestrating a "slow motion coup" via blockades. Ernesto Araújo criticizes Brazilian President Lula's silence on the matter, while Alejandro Peña Esclusa suggests that regional support for the elected government may finally lead to Morales facing legal consequences. 6

In Episode 308 of the FNO InsureTech Podcast, hosts Rob Beller and Lee Boyd welcome Tim Welsh, President of CCC Intelligent Solutions, for a powerful conversation on one of the most important and emotional moments in insurance: the accident experience and how it can be improved through better connectivity, data, and orchestration across the ecosystem. Tim shares his unique journey from consulting at McKinsey to banking and now leading a cornerstone InsureTech platform that connects insurers, repair facilities, OEMs, and service providers. He explains how CCC has been building toward this moment for decades and how the company is now bringing together AI, data, and partnerships to create a more seamless and supportive claims experience. The conversation explores the reality that car accidents are not just operational events, but deeply personal ones that people remember for years. Tim highlights how CCC is focused on redesigning that experience from the consumer's perspective, using a combination of technology and human expertise to guide individuals through a stressful moment and help them move forward quickly. Rob and Lee also dig into the growing complexity of vehicles, rising repair costs, and the pressure on affordability across the system. Tim shares how CCC is addressing these challenges through orchestration, real time decision making, and a "together on purpose" approach that aligns everyone in the ecosystem. This episode goes beyond technology, offering a human centered view of innovation and a clear vision for how the claims experience can evolve to better serve both consumers and the industry. Key Highlights [04:00] Meet Tim Welsh and CCC Intelligent Solutions An introduction to CCC and its role as a long standing platform connecting insurers, repair shops, OEMs, and service providers across the claims ecosystem. [07:00] A Career Built on Helping People Tim shares his unconventional journey from preparing for the priesthood to consulting, banking, and ultimately leading at CCC. [10:00] Why Accidents Are So Memorable A discussion on how car accidents rank among life's most vivid experiences and why improving that moment matters so deeply. [13:00] The Complexity Behind a Simple Repair How modern vehicles, with thousands of parts and software driven systems, have dramatically increased repair costs and claims complexity. [16:00] The Consumer at the Center Introducing "Ava," the model consumer, and how CCC is designing the claims experience around her needs from first notice through repair. [19:00] Orchestrating the Claims Journey How technology is connecting each step of the process, from photos and estimates to scheduling and parts ordering, into a seamless flow. [22:00] Preventing Total Loss Through Real Time Decisions A look at how dynamic decision making across the ecosystem can reduce unnecessary total losses and improve outcomes for everyone involved. [25:00] Affordability and the Small Claims Problem Why rising premiums and deductibles are changing consumer behavior and leading to fewer small claims being reported. [28:00] AI as Orchestration, Not Replacement How CCC is using AI to guide workflows and enhance human decision making rather than replace adjusters and claims professionals. [31:00] AI Guidance in Action Examples of how AI can prioritize tasks for adjusters, helping them focus on the most impactful actions each day. [34:00] The Power of Ecosystem Connectivity Why bringing insurers, repair shops, OEMs, and partners together on one platform is critical to unlocking better outcomes. [37:00] Together on Purpose The philosophy behind CCC's approach, aligning all players around a shared goal of improving the consumer experience. [40:00] Feeding Insights Back to Manufacturers How data from claims can influence vehicle design and repairability over time. [42:00] What "Easy" Looks Like A real world example of a smooth repair experience and why that is the ultimate goal. [44:00] Final Thoughts on the Future of Claims Tim shares his vision for a more connected, efficient, and human centered claims experience that benefits both consumers and the entire industry.

David Homan David Homan is the founder and CEO of Orchestrated Connecting, a global community of connectors; Orchestrated Opportunities, an impact-focused advisory firm; and SOAR CONNECT, a start-up focused on the strength of authentic relationships. He hosts a podcast called Orchestrated, focused on developing relationship value, is an active classical composer, and is a proud father of two. From middle-class beginnings as the son of a college professor father and nonprofit-focused mother, he has built a network reaching into the most private and incredible circles globally while maintaining a code of purposeful community building called Orchestrated Connecting. Noah Askin Noah Askin is an Associate Professor of Organisation and Management at UC-Irvine's Paul Merage School of Business, where he also serves as Faculty Director of their Leadership Development Institute. An award-winning teacher and researcher, Noah is an expert in organisational dynamics, leadership, and culture, focusing on the informal networks of communication and connection that drive organisational life. Noah's work has garnered him recognition on the Thinkers 50 Radar list and has been covered by various publications, including the BBC, The Economist, Rolling Stone, NPR, Vox, and Forbes. He lives with his family in Southern California. Orchestrating Connections In this episode, David Homan and Noah Askin talk about their book, Orchestrating Connections. The authors believe that meaningful relationships emerge when people are connected through shared values rather than credentials, status, or transactional goals. They propose five principles, namely curiosity, diversity, vulnerability, generosity, and gratitude, that lead to transformative communities. Noah Askin approaches relationships through sociology and network science. While many people study the structure of networks, his interest was in what actually creates meaningful connections. As David was already running a community, Noah started interviewing members to get a sense of the on-the-ground reality of connections. He realised that many of the most connected individuals identified as introverts rather than extroverts, and traced their empathy to formative challenges earlier in life. These findings challenged conventional assumptions about networking, leading the authors to distinguish between “networking for personal success” and “community building to help others”. Networking is focused on personal success and exchange, while community is oriented toward support, learning, development, and collective growth. Strong communities emerge when people are guided by a clear sense of purpose and create environments where relationships become a long-term source of mutual growth rather than short-term transactions. Trust and reciprocity, rather than transactions, become the foundation.   Run time – 01:17:38 mins. Links for Subhanjan  subhanjan@pitch.link  https://www.linkedin.com/in/subhanjansarkar For Authors: https://orchestrating connection.com https://noahaskin.com LinkedIn – https://linkedin.com/in/noahaskin LinkedIn – https://linkedin.com/in/davidhoman

This episode features Dmitry Shevelenko, Chief Business Officer, Perplexity, in conversation with Stuart Riley, Group Chief Information Officer, HSBC. They explore the speed of change in AI models and what it takes to turn that pace into real commercial value in large enterprises. The conversation covers multi-model orchestration, why data hygiene is an evergreen investment, and how to think about security and adoption as AI moves from tools to agentic workflows.Watch or listen to find out more.This episode was recorded on the sidelines of the HSBC Global Investment Summit in Hong Kong in April 2026. Find out more here https://www.business.hsbc.com/en-gb/campaigns/global-investment-summitDisclaimer: Views of external guest speakers do not represent those of HSBC.

AI isn't just changing how enterprises do business, it involves a new kind of leadership and fundamentally reshaping the C-suite. In the season 1 finale of Techfluential, we connect the dots across our conversations with C-suite and board executives, revisiting the most powerful insights on why technology leadership is a shared enterprise agenda, and how leaders can drive real, recognizable value and measurable impact for their organization.  Listen to recent episodes here. 

Join Roytman Piccoli, Founder and CEO of SoftQuantus, for a deep dive into the next generation of deep-tech computing architecture. Moving beyond the theoretical hype of quantum physics, Roytman's work focuses on the immediate, multi-vendor realities of hybrid workflows—combining Quantum Processing Units (QPUs), High-Performance Computing (HPC), and Artificial Intelligence to solve massive industrial optimization and scientific simulation problems. In this episode, we explore how SoftQuantus is building provider-agnostic execution layers that turn volatile quantum technologies into reliable, audit-ready tools for global enterprises.

Orchestrating Power: The American Associational State in the First World War⁠ (Cornell University Press, 2025) explores how the expansion of the American state for the First World War reshaped the nature of governance. This wartime state expansion is examined through the creation, structure, activities, and impact of the Council of Defense system on the ability of the United States to mobilize for a significant conflict in a foreign land.  Dr. Nathan K. Finney focuses on North Carolina's Council of Defense to describe how the council was mediated by specific people at various levels of society and the results of their decisions. The result is a compelling story about how individuals drove dynamic and compelling regional and national events that propelled a massive national wartime mobilization.  Positioned between the national government and the people of North Carolina, the Council of Defense mediated the activities of public, private, and individual efforts in support of mobilization activities. Because of this intermediary positioning, the council was instrumental in expanding state capacity and capability for military and resource mobilization and supporting an increase in the nation's ability to mobilize for the war.  The council's intermediary role, however, also allowed those managing the state mobilization to prevent any significant challenge to the state's social and political structures, despite the dynamic changes wrought by the need to mobilize the nation for war. As a result, Orchestrating Power helps us understand the crucial decisions and developments of early twentieth-century America, showing why the country mobilized for war in the specific ways that it did.  This interview was conducted by Dr. Miranda Melcher, whose⁠ book⁠ focuses on post-conflict military integration, understanding treaty negotiation and implementation in civil war contexts, with qualitative analysis of the Angolan and Mozambican civil wars. You can find Miranda's interviews on ⁠New Books with Miranda Melcher⁠, wherever you get your podcasts.  Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/new-books-network

Orchestrating Power: The American Associational State in the First World War⁠ (Cornell University Press, 2025) explores how the expansion of the American state for the First World War reshaped the nature of governance. This wartime state expansion is examined through the creation, structure, activities, and impact of the Council of Defense system on the ability of the United States to mobilize for a significant conflict in a foreign land.  Dr. Nathan K. Finney focuses on North Carolina's Council of Defense to describe how the council was mediated by specific people at various levels of society and the results of their decisions. The result is a compelling story about how individuals drove dynamic and compelling regional and national events that propelled a massive national wartime mobilization.  Positioned between the national government and the people of North Carolina, the Council of Defense mediated the activities of public, private, and individual efforts in support of mobilization activities. Because of this intermediary positioning, the council was instrumental in expanding state capacity and capability for military and resource mobilization and supporting an increase in the nation's ability to mobilize for the war.  The council's intermediary role, however, also allowed those managing the state mobilization to prevent any significant challenge to the state's social and political structures, despite the dynamic changes wrought by the need to mobilize the nation for war. As a result, Orchestrating Power helps us understand the crucial decisions and developments of early twentieth-century America, showing why the country mobilized for war in the specific ways that it did.  This interview was conducted by Dr. Miranda Melcher, whose⁠ book⁠ focuses on post-conflict military integration, understanding treaty negotiation and implementation in civil war contexts, with qualitative analysis of the Angolan and Mozambican civil wars. You can find Miranda's interviews on ⁠New Books with Miranda Melcher⁠, wherever you get your podcasts.  Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/military-history

Orchestrating Power: The American Associational State in the First World War⁠ (Cornell University Press, 2025) explores how the expansion of the American state for the First World War reshaped the nature of governance. This wartime state expansion is examined through the creation, structure, activities, and impact of the Council of Defense system on the ability of the United States to mobilize for a significant conflict in a foreign land.  Dr. Nathan K. Finney focuses on North Carolina's Council of Defense to describe how the council was mediated by specific people at various levels of society and the results of their decisions. The result is a compelling story about how individuals drove dynamic and compelling regional and national events that propelled a massive national wartime mobilization.  Positioned between the national government and the people of North Carolina, the Council of Defense mediated the activities of public, private, and individual efforts in support of mobilization activities. Because of this intermediary positioning, the council was instrumental in expanding state capacity and capability for military and resource mobilization and supporting an increase in the nation's ability to mobilize for the war.  The council's intermediary role, however, also allowed those managing the state mobilization to prevent any significant challenge to the state's social and political structures, despite the dynamic changes wrought by the need to mobilize the nation for war. As a result, Orchestrating Power helps us understand the crucial decisions and developments of early twentieth-century America, showing why the country mobilized for war in the specific ways that it did.  This interview was conducted by Dr. Miranda Melcher, whose⁠ book⁠ focuses on post-conflict military integration, understanding treaty negotiation and implementation in civil war contexts, with qualitative analysis of the Angolan and Mozambican civil wars. You can find Miranda's interviews on ⁠New Books with Miranda Melcher⁠, wherever you get your podcasts.  Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/political-science

Orchestrating Power: The American Associational State in the First World War⁠ (Cornell University Press, 2025) explores how the expansion of the American state for the First World War reshaped the nature of governance. This wartime state expansion is examined through the creation, structure, activities, and impact of the Council of Defense system on the ability of the United States to mobilize for a significant conflict in a foreign land.  Dr. Nathan K. Finney focuses on North Carolina's Council of Defense to describe how the council was mediated by specific people at various levels of society and the results of their decisions. The result is a compelling story about how individuals drove dynamic and compelling regional and national events that propelled a massive national wartime mobilization.  Positioned between the national government and the people of North Carolina, the Council of Defense mediated the activities of public, private, and individual efforts in support of mobilization activities. Because of this intermediary positioning, the council was instrumental in expanding state capacity and capability for military and resource mobilization and supporting an increase in the nation's ability to mobilize for the war.  The council's intermediary role, however, also allowed those managing the state mobilization to prevent any significant challenge to the state's social and political structures, despite the dynamic changes wrought by the need to mobilize the nation for war. As a result, Orchestrating Power helps us understand the crucial decisions and developments of early twentieth-century America, showing why the country mobilized for war in the specific ways that it did.  This interview was conducted by Dr. Miranda Melcher, whose⁠ book⁠ focuses on post-conflict military integration, understanding treaty negotiation and implementation in civil war contexts, with qualitative analysis of the Angolan and Mozambican civil wars. You can find Miranda's interviews on ⁠New Books with Miranda Melcher⁠, wherever you get your podcasts.  Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/world-affairs

Orchestrating Power: The American Associational State in the First World War⁠ (Cornell University Press, 2025) explores how the expansion of the American state for the First World War reshaped the nature of governance. This wartime state expansion is examined through the creation, structure, activities, and impact of the Council of Defense system on the ability of the United States to mobilize for a significant conflict in a foreign land.  Dr. Nathan K. Finney focuses on North Carolina's Council of Defense to describe how the council was mediated by specific people at various levels of society and the results of their decisions. The result is a compelling story about how individuals drove dynamic and compelling regional and national events that propelled a massive national wartime mobilization.  Positioned between the national government and the people of North Carolina, the Council of Defense mediated the activities of public, private, and individual efforts in support of mobilization activities. Because of this intermediary positioning, the council was instrumental in expanding state capacity and capability for military and resource mobilization and supporting an increase in the nation's ability to mobilize for the war.  The council's intermediary role, however, also allowed those managing the state mobilization to prevent any significant challenge to the state's social and political structures, despite the dynamic changes wrought by the need to mobilize the nation for war. As a result, Orchestrating Power helps us understand the crucial decisions and developments of early twentieth-century America, showing why the country mobilized for war in the specific ways that it did.  This interview was conducted by Dr. Miranda Melcher, whose⁠ book⁠ focuses on post-conflict military integration, understanding treaty negotiation and implementation in civil war contexts, with qualitative analysis of the Angolan and Mozambican civil wars. You can find Miranda's interviews on ⁠New Books with Miranda Melcher⁠, wherever you get your podcasts.  Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/american-studies

Author and activist Dan Kovalik discusses his books, Syria the Anatomy of a Regime Change and The Plot to Overthrow Venezuela: How the US is Orchestrating a Coup for Oil.   An award winning front-line investigative news magazine, that focuses on human, civil and workers right, issues of war and peace, Global Warming, racism and poverty, and other issues. Hosted by Dennis J. Bernstein. The post An Interview with Author and Activist Dan Kovalik appeared first on KPFA.

Send us Fan MailWhat does it truly mean to build relationships that matter?In this episode, I sit down with David Homan, founder and CEO of Orchestrated Connecting, Orchestrated Opportunities, and SOAR CONNECT. David has spent over a decade developing a powerful methodology around what he calls Orchestrated Connecting—a system designed to create meaningful, trust-based relationships that extend far beyond traditional networking.From his early roots in music and composition to becoming a global “connector of connectors,” David shares how his unique path shaped his perspective on community, trust, and contribution. We explore why most people misunderstand connection, how transactional relationships erode trust, and what it really takes to build something enduring in both life and business.This conversation goes deep into the human side of performance—where generosity, curiosity, and patience become the real drivers of opportunity.We also touch on: Why trust takes years to build—and how to accelerate it the right way  How to identify one-sided relationships before they cost you  The difference between networking and genuine connection  Why success without contribution ultimately falls short  How small acts of generosity can open unexpected doors If you care about building a meaningful career, a strong network, and a life grounded in purpose, this one will resonate.If you liked this EP, please take the time to rate and comment, share with a friend, and connect with us on social channels IG @Kingopain, TW @BuiltbyScott, LI+FB Scott Livingston. You can find all things LYM at www.LYMLab.com, download your free Life Lab Starter Kit today and get busy living https://lymlab.com/free-lym-lab-starter/Please take the time to visit and connect with our sponsors, they are an essential part of our success:www.ReconditioningHQ.comwww.FreePainGuide.com 

MacVoices Live! returned after a brief hiatus to discuss the leadership transition from Tim Cook to John Ternus, exploring timing, succession planning, and potential impact. Chuck Joiner, David Ginsburg, Web Bixby, Guy Serle, Jim Rea, Jeff Gamet, Marty Jencius, Brian Flanigan-Arthurs and Eric Bolden debate whether the move is surprising, how it aligns with product cycles, and Apple's strategic stability. They highlight strong internal leadership, ongoing success across hardware and services, and why it points to a well-managed transition plan. MacVoices is supported by Macstock Connference, along with Ecamm Creator Camp, taking place in Crystal Lake IL on July 9 - 12. Sign up at macstockconference.com and use the code “macvoices” to save $50 off your ticket. Show Notes: Chapters: 0:00 Introduction and return of the live panel 0:36 Panel introductions and show reset after hiatus 5:53 Breaking news: leadership transition discussion begins 7:11 Timing of announcement and WWDC implications 8:28 Business strategy and product momentum considerations 9:39 Role changes and executive structure explained 11:05 Succession planning and internal leadership strength 12:19 Reactions to timing and public perception 14:20 Evaluating past leadership decisions and milestones 18:40 Market response and stock stability discussion 19:59 Orchestrating a smooth CEO transition 21:32 Leadership roles and internal promotions 23:20 Importance of internal succession vs external hires 26:52 Optimism for future leadership and innovation Links: This detail about Apple's CEO transition shows the company can still keep important secrets https://9to5mac.com/2026/04/21/this-detail-about-apples-ceo-transition-shows-the-company-can-still-keep-important-secrets/     Apple stock is having a surprisingly muted reaction to CEO Tim Cook's exit. Here are 3 reasons why https://www.fastcompany.com/91529987/apple-stock-reacts-surprisingly-ceo-tim-cook-exit-3-reasons-why   Guests: Web Bixby has been in the insurance business for 40 years and has been an Apple user for longer than that.You can catch up with him on Facebook, Twitter, and LinkedIn, but prefers Bluesky. Eric Bolden is into macOS, plants, sci-fi, food, and is a rural internet supporter. You can connect with him on Twitter, by email at embolden@mac.com, on Mastodon at @eabolden@techhub.social, on his blog, Trending At Work, and as co-host on The Vision ProFiles podcast. Brian Flanigan-Arthurs is an educator with a passion for providing results-driven, innovative learning strategies for all students, but particularly those who are at-risk. He is also a tech enthusiast who has a particular affinity for Apple since he first used the Apple IIGS as a student. You can contact Brian on twitter as @brian8944. He also recently opened a Mastodon account at @brian8944@mastodon.cloud. Jeff Gamet is a technology blogger, podcaster, author, and public speaker. Previously, he was The Mac Observer's Managing Editor, and the TextExpander Evangelist for Smile. He has presented at Macworld Expo, RSA Conference, several WordCamp events, along with many other conferences. You can find him on several podcasts such as The Mac Show, The Big Show, MacVoices, Mac OS Ken, This Week in iOS, and more. Jeff is easy to find on social media as @jgamet on Twitter and Instagram, jeffgamet on LinkedIn., @jgamet@mastodon.social on Mastodon, and on his YouTube Channel at YouTube.com/jgamet. David Ginsburg is the host of the weekly podcast In Touch With iOS where he discusses all things iOS, iPhone, iPad, Apple TV, Apple Watch, and related technologies. He is an IT professional supporting Mac, iOS and Windows users. Visit his YouTube channel at https://youtube.com/daveg65 and find and follow him on Twitter @daveg65 and on Mastodon at @daveg65@mastodon.cloud.   Marty Jencius, Ph.D.,is a counselor educator and technology pioneer who has spent 30 years bringing emerging tech into his field — from founding one of the first professional listservs (CESNET-L) to podcasting, virtual reality, and now AI and AR. He is the founder of ThePodTalk.net, where he produces Vision ProFiles, The Old Mac Gang, A.I. Productivity Workflow, The Tech Savvy Professor, 15 Minute Bytes, The Neo Notebook, and Fade to Chat: Golden Age Cinema. He is also a regular panelist on MacVoices Live!, In Touch with iOS, and The Mac Show. Find him on Bluesky and Mastodon. Jim Rea built his own computer from scratch in 1975, started programming in 1977, and has been an independent Mac developer continuously since 1984. He is the founder of ProVUE Development, and the author of Panorama X, ProVUE's ultra fast RAM based database software for the macOS platform. He's been a speaker at MacTech, MacWorld Expo and other industry conferences. Follow Jim at provue.com and via @provuejim@techhub.social on Mastodon. Guy Serle, best known for being one of the co-hosts of the MyMac Podcast, sincerely apologizes for anything he has done or caused to have happened while in possession of dangerous podcasting equipment. He should know better but being a blonde from Florida means he's probably incapable of understanding the damage he has wrought. Guy is also the author of the novel, The Maltese Cube. You can follow his exploits on Twitter, catch him on Mac to the Future on Facebook, at @Macparrot@mastodon.social, and find everything at VertShark.com. Support: Become a MacVoices Patron on Patreon      http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect: Web:      http://macvoices.com Twitter: http://www.twitter.com/chuckjoiner      http://www.twitter.com/macvoices Mastodon:      https://mastodon.cloud/@chuckjoiner Facebook:      http://www.facebook.com/chuck.joiner MacVoices Page on Facebook:      http://www.facebook.com/macvoices/ MacVoices Group on Facebook:      http://www.facebook.com/groups/macvoice LinkedIn:      https://www.linkedin.com/in/chuckjoiner/ Instagram:      https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes      Video in iTunes      Subscribe manually via iTunes or any podcatcher: Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

MacVoices Live! returned after a brief hiatus to discuss the leadership transition from Tim Cook to John Ternus, exploring timing, succession planning, and potential impact. Chuck Joiner, David Ginsburg, Web Bixby, Guy Serle, Jim Rea, Jeff Gamet, Marty Jencius, Brian Flanigan-Arthurs and Eric Bolden debate whether the move is surprising, how it aligns with product cycles, and Apple's strategic stability. They highlight strong internal leadership, ongoing success across hardware and services, and why it points to a well-managed transition plan. MacVoices is supported by Macstock Connference, along with Ecamm Creator Camp, taking place in Crystal Lake IL on July 9 - 12. Sign up at macstockconference.com and use the code "macvoices" to save $50 off your ticket. Show Notes: Chapters: 0:00 Introduction and return of the live panel 0:36 Panel introductions and show reset after hiatus 5:53 Breaking news: leadership transition discussion begins 7:11 Timing of announcement and WWDC implications 8:28 Business strategy and product momentum considerations 9:39 Role changes and executive structure explained 11:05 Succession planning and internal leadership strength 12:19 Reactions to timing and public perception 14:20 Evaluating past leadership decisions and milestones 18:40 Market response and stock stability discussion 19:59 Orchestrating a smooth CEO transition 21:32 Leadership roles and internal promotions 23:20 Importance of internal succession vs external hires 26:52 Optimism for future leadership and innovation Links: This detail about Apple's CEO transition shows the company can still keep important secrets https://9to5mac.com/2026/04/21/this-detail-about-apples-ceo-transition-shows-the-company-can-still-keep-important-secrets/     Apple stock is having a surprisingly muted reaction to CEO Tim Cook's exit. Here are 3 reasons why https://www.fastcompany.com/91529987/apple-stock-reacts-surprisingly-ceo-tim-cook-exit-3-reasons-why   Guests: Web Bixby has been in the insurance business for 40 years and has been an Apple user for longer than that.You can catch up with him on Facebook, Twitter, and LinkedIn, but prefers Bluesky. Eric Bolden is into macOS, plants, sci-fi, food, and is a rural internet supporter. You can connect with him on Twitter, by email at embolden@mac.com, on Mastodon at @eabolden@techhub.social, on his blog, Trending At Work, and as co-host on The Vision ProFiles podcast. Brian Flanigan-Arthurs is an educator with a passion for providing results-driven, innovative learning strategies for all students, but particularly those who are at-risk. He is also a tech enthusiast who has a particular affinity for Apple since he first used the Apple IIGS as a student. You can contact Brian on twitter as @brian8944. He also recently opened a Mastodon account at @brian8944@mastodon.cloud. Jeff Gamet is a technology blogger, podcaster, author, and public speaker. Previously, he was The Mac Observer's Managing Editor, and the TextExpander Evangelist for Smile. He has presented at Macworld Expo, RSA Conference, several WordCamp events, along with many other conferences. You can find him on several podcasts such as The Mac Show, The Big Show, MacVoices, Mac OS Ken, This Week in iOS, and more. Jeff is easy to find on social media as @jgamet on Twitter and Instagram, jeffgamet on LinkedIn., @jgamet@mastodon.social on Mastodon, and on his YouTube Channel at YouTube.com/jgamet. David Ginsburg is the host of the weekly podcast In Touch With iOS where he discusses all things iOS, iPhone, iPad, Apple TV, Apple Watch, and related technologies. He is an IT professional supporting Mac, iOS and Windows users. Visit his YouTube channel at https://youtube.com/daveg65 and find and follow him on Twitter @daveg65 and on Mastodon at @daveg65@mastodon.cloud.   Marty Jencius, Ph.D.,is a counselor educator and technology pioneer who has spent 30 years bringing emerging tech into his field — from founding one of the first professional listservs (CESNET-L) to podcasting, virtual reality, and now AI and AR. He is the founder of ThePodTalk.net, where he produces Vision ProFiles, The Old Mac Gang, A.I. Productivity Workflow, The Tech Savvy Professor, 15 Minute Bytes, The Neo Notebook, and Fade to Chat: Golden Age Cinema. He is also a regular panelist on MacVoices Live!, In Touch with iOS, and The Mac Show. Find him on Bluesky and Mastodon. Jim Rea built his own computer from scratch in 1975, started programming in 1977, and has been an independent Mac developer continuously since 1984. He is the founder of ProVUE Development, and the author of Panorama X, ProVUE's ultra fast RAM based database software for the macOS platform. He's been a speaker at MacTech, MacWorld Expo and other industry conferences. Follow Jim at provue.com and via @provuejim@techhub.social on Mastodon. Guy Serle, best known for being one of the co-hosts of the MyMac Podcast, sincerely apologizes for anything he has done or caused to have happened while in possession of dangerous podcasting equipment. He should know better but being a blonde from Florida means he's probably incapable of understanding the damage he has wrought. Guy is also the author of the novel, The Maltese Cube. You can follow his exploits on Twitter, catch him on Mac to the Future on Facebook, at @Macparrot@mastodon.social, and find everything at VertShark.com. Support:      Become a MacVoices Patron on Patreon      http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:      http://macvoices.com      Twitter:      http://www.twitter.com/chuckjoiner      http://www.twitter.com/macvoices      Mastodon:      https://mastodon.cloud/@chuckjoiner      Facebook:      http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:      http://www.facebook.com/macvoices/      MacVoices Group on Facebook:      http://www.facebook.com/groups/macvoice      LinkedIn:      https://www.linkedin.com/in/chuckjoiner/      Instagram:      https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes      Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

In this episode, Legal Speak co-host Patrick Smith speaks with Miguel Zaldivar, the CEO of the soon-to-be Hogan Lovells Cadwalader, about the genesis of the merger with Cadwalader, the process he and the firm went through to secure the partnership vote, and what comes next.   Hosts: Patrick Smith & Cedra Mayfield Guest: Miguel Zaldivar, Producer: Charles Garnar

For complete Medicare guidance, dial 580-308-0975 to speak with my trusted partner, Chapter, or go to https://askchapter.org/oconnor Nancy Pelosi told America "it was his decision" about Eric Swalwell's resignation — the exact same words she used about Joe Biden stepping aside. Then CNN confirmed she personally called Swalwell Friday night and told him to resign. The playbook is exposed. Larry O'Connor breaks down Pelosi's pattern of forcing allies out while denying involvement, reacts live to an accuser's harrowing Beverly Hills press conference, and dismantles Pelosi's defense of congressional stock trading. SHOP OUR MERCH: https://store.townhallmedia.com/ BUY A LARRY MUG: https://store.townhallmedia.com/products/larry-mug Watch LARRY with Larry O'Connor LIVE — Monday-Thursday at 12PM Eastern on YouTube, Facebook, & Rumble! Find LARRY with Larry O'Connor wherever you get your podcasts! SPOTIFY: https://open.spotify.com/show/7i8F7K4fqIDmqZSIHJNhMh?si=814ce2f8478944c0&nd=1&dlsi=e799ca22e81b456f APPLE: https://podcasts.apple.com/us/podcast/larry/id1730596733 Become a Townhall VIP Member today and use promo code LARRY for 50% off: https://townhall.com/subscribe?tpcc=poddescription https://townhall.com/ https://rumble.com/c/c-5769468 https://www.facebook.com/townhallcom/ https://www.instagram.com/townhallmedia/ https://twitter.com/townhallcomBecome a Townhall VIP member with promo code "LARRY": https://townhall.com/subscribeSee omnystudio.com/listener for privacy information.

-The feud between Elon Musk and OpenAI is getting even more contentious as the two sides get ready for trial later this month. -The Federal Aviation Administration is targeting gamers in its most recent job advertisement for air traffic controllers. The administration's annual hiring window opens at 12AM ET on April 17, and considering the ongoing shortage of air traffic controllers. -Immigration and Customs Enforcement has a certain Redditor in its crosshairs and it's now strong-arming the social media platform to reveal who they are with a grand jury subpoena, according to a report from The Intercept. Learn more about your ad choices. Visit podcastchoices.com/adchoices

We're proud to release this ahead of Ryan's keynote at AIE Europe. Hit the bell, get notified when it is live! Attendees: come prepped for Ryan's AMA with Vibhu after.Move over, context engineering. Now it's time for Harness engineering and the age of the token billionaires.Ryan Lopopolo of OpenAI is leading that charge, recently publishing a lengthy essay on Harness Eng that has become the talk of the town:In it, Ryan peeled back the curtains on how the recently announced OpenAI Frontier team have become OpenAI's top Codex users, running a >1m LOC codebase with 0 human written code and, crucially for the Dark Factory fans, no human REVIEWED code before merge. Ryan is admirably evangelical about this, calling it borderline “negligent” if you aren't using >1B tokens a day (roughly $2-3k/day in token spend based on market rates and caching assumptions):Over the past five months, they ran an extreme experiment: building and shipping an internal beta product with zero manually written code. Through the experiment, they adopted a different model of engineering work: when the agent failed, instead of prompting it better or to “try harder,” the team would look at “what capability, context, or structure is missing?”The result was Symphony, “a ghost library” and reference Elixir implementation (by Alex Kotliarskyi) that sets up a massive system of Codex agents all extensively prompted with the specificity of a proper PRD spec, but without full implementation:The future starts taking shape as one where coding agents stop being copilots and start becoming real teammates anyone can use and Codex is doubling down on that mission with their Superbowl messaging of “you can just build things”.Across Codex, internal observability stacks, and the multi-agent orchestration system his team calls Symphony, Ryan has been pushing what happens when you optimize an entire codebase, workflow, and organization around agent legibility instead of human habit.We sat down with Ryan to dig into how OpenAI's internal teams actually use Codex, why the real bottleneck in AI-native software development is now human attention rather than tokens, how fast build loops, observability, specs, and skills let agents operate autonomously, why software increasingly needs to be written for the model as much as for the engineer, and how Frontier points toward a future where agents can safely do economically valuable work across the enterprise.We discuss:* Ryan's background from Snowflake, Brex, Stripe, and Citadel to OpenAI Frontier Product Exploration, where he works on new product development for deploying agents safely at enterprise scale* The origin of “harness engineering” and the constraint that kicked off the whole experiment: Ryan deliberately refused to write code himself so the agent had to do the job end to end* Building an internal product over five months with zero lines of human-written code, more than a million lines in the repo, and thousands of PRs across multiple Codex model generations* Why early Codex was painfully slow at first, and how the team learned to decompose tasks, build better primitives, and gradually turn the agent into a much faster engineer than any individual human* The obsession with fast build times: why one minute became the upper bound for the inner loop, and how the team repeatedly retooled the build system to keep agents productive* Why humans became the bottleneck, and how Ryan's team shifted from reviewing code directly to building systems, observability, and context that let agents review, fix, and merge work autonomously* Skills, docs, tests, markdown trackers, and quality scores as ways of encoding engineering taste and non-functional requirements directly into context the agent can use* The shift from predefined scaffolds to reasoning-model-led workflows, where the harness becomes the box and the model chooses how to proceed* Symphony, OpenAI's internal Elixir-based orchestration layer for spinning up, supervising, reworking, and coordinating large numbers of coding agents across tickets and repos* Why code is increasingly disposable, why worktrees and merge conflicts matter less when agents can resolve them, and what it really means to fully delegate the PR lifecycle* “Ghost libraries”, spec-driven software, and the idea that a coding agent can reproduce complex systems from a high-fidelity specification rather than shared source code* The broader future of Frontier: safely deploying observable, governable agents into enterprises, and building the collaboration, security, and control layers needed for real-world agentic workRyan Lopopolo* X: https://x.com/_lopopolo* Linkedin: https://www.linkedin.com/in/ryanlopopolo/* Website: https://hyperbo.la/contact/Timestamps00:00:00 Introduction: Harness Engineering and OpenAI Frontier00:02:20 Ryan's background and the “no human-written code” experiment00:08:48 Humans as the bottleneck: systems thinking, observability, and agent workflows00:12:24 Skills, scaffolds, and encoding engineering taste into context00:17:17 What humans still do, what agents already own, and why software must be agent-legible00:24:27 Delegating the PR lifecycle: worktrees, merge conflicts, and non-functional requirements00:31:57 Spec-driven software, “ghost libraries,” and the path to Symphony00:35:20 Symphony: orchestrating large numbers of coding agents00:43:42 Skill distillation, self-improving workflows, and team-wide learning00:50:04 CLI design, policy layers, and building token-efficient tools for agents00:59:43 What current models still struggle with: zero-to-one products and gnarly refactors01:02:05 Frontier's vision for enterprise AI deployment01:08:15 Culture, humor, and teaching agents how the company works01:12:29 Harness vs. training, Codex model progress, and “you can just do things”01:15:09 Bellevue, hiring, and OpenAI's expansion beyond San FranciscoTranscriptRyan Lopopolo: I do think that there is an interesting space to explore here with Codex, the harness, as part of building AI products, right? There's a ton of momentum around getting the models to be good at coding. We've seen big leaps in like the task complexity with each incremental model release where if you can figure out how to collapse a product that you're trying to.Build a user journey that you're trying to solve into code. It's pretty natural to use the Codex Harness to solve that problem for you. It's done all the wiring and lets you just communicate in prompts. To let the model cook, you have to step back, right? Like you need to take a systems thinking mindset to things and constantly be asking, where is the Asian making mistakes?Where am I spending my time? How can I not spend that time going forward? And then build confidence in the automation that I'm putting in place. So I have solved this part of the SDLC.swyx: [00:01:00] All right.[00:01:03] Meet Ryan swyx: We're in the studio with Ryan from OpenAI. Welcome.Ryan Lopopolo: Hi,swyx: Thanks for visiting San Francisco and thanks for spending some time with us.Ryan Lopopolo: Yeah, thank you. I'm super excited to be here.swyx: You wrote a blockbuster article on harness engineering. It's probably going to be the defining piece of this emerging discipline, huh?Ryan Lopopolo: Thank you. It is it's been fun to feel like we've defined the discourse in some sense.swyx: Let's contextualize a little bit, this first podcast you've ever done. Yes. And thank you for spending with us. What is, where is this coming from? What team are you in all that jazz?Ryan Lopopolo: Sure, sure.Ryan Lopopolo: I work on Frontier Product Exploration, new product development in the space of OpenAI Frontier, which is our enterprise platform for deploying agents safely at scale, with good governance in any business. And. The role of VMI team has been to figure out novel ways to deploy our models into package and products that we can sell as solutions to enterprises.swyx: And you have a background, I'll just squeeze it in there. Snowflake, brick, [00:02:00] stripe, citadel.Ryan Lopopolo: Yes. Yes. Same. Any kind of customerswyx: entire life. Yes. The exact kind of customer that you want to,Vibhu: so I'll say, I was actually, I didn't expect the background when I looked at your Twitter, I'm seeing the opposite.Stuff like this. So you've got the mindset of like full send AI, coding stuff about slop, like buckling in your laptop on your Waymo's. Yes. And then I look at your profile, I'm like, oh, you're just like, you're in the other end too. Oh, perfect. Makes perfect.Ryan Lopopolo: I it's quite fun to be AI maximalist if you're gonna live that persona.Open eye is the place to do it. And it'sswyx: token is what you say.Ryan Lopopolo: Yeah. Certainly helps that we have no rate limits internally. And I can go, like you said, full send at this stay.swyx: Yeah. Yeah. So the Frontier, and you're a special team within O Frontier.Ryan Lopopolo: We had been given some space to cook, which has been super, super exciting.[00:02:47] Zero Code ExperimentRyan Lopopolo: And this is why I started with kind of a out there constraint to not write any of the code myself. I was figuring if we're trying to make agents that can be deployed into end to enterprises, they should be [00:03:00] able to do all the things that I do. And having worked with these coding models, these coding harnesses over 6, 7, 8 months, I do feel like the models are there enough, the harnesses are there enough where they're isomorphic to me in capability and the ability to do the job.So starting with this constraint of I can't write the code meant that the only way I could do my job was to get the agent to do my job.Vibhu: And like a, just a bit of background before that. This is basically the article. So what you guys did is five months of working on an internal tool, zero lines of code over a mi, a million lines of code in the total code base.You say it was cenex, more like it was cenex faster than you would've. If you had done it by end. SoRyan Lopopolo: yeah, thatVibhu: was the mindset going into this, right?Ryan Lopopolo: That's right.[00:03:46] Model Upgrades LessonsRyan Lopopolo: Started with some of the very first versions of Codex CLI, with the Codex Mini model, which was obviously much less capable than the ones we have today.Which was also a very good constraint, right? Quite a visceral feeling to ask the [00:04:00] model to build you a product feature. And it just not being able to assemble the pieces together.Which kind of defined one of the mindsets we had for going into this, which is whenever the model just cannot, you always pop open at the task, double click into it, and build smaller building blocks that then you can reassemble into the broader objective.And it was quite painful to do this. Honestly, the first month and a half was. 10 times slower than I would be. But because we paid that cost, we ended up getting to something much more productive than any one engineer could be because we built the tools, the assembly station for the agent to do the whole thing.[00:04:43] Model Generations, Build Systems & Background ShellsRyan Lopopolo: But yeah, so onward to G BT 5, 5, 1, 5, 2, 5, 3, 5 4. To go through all these model generations and see their kind of corks and different working styles also meant we had to adapt the code base to change things up when the model was revved. [00:05:00] One interesting thing here is five two, the Codex harness at the time did not have background shells in it, which means we were able to rely on blocking scripts to perform long horizon work.But with five, three and background shells, it became less patient, less willing to block. So we had to retool the entire build system to complete in under a minute and. This is not a thing I would expect to be able to do in a code base where people have opinions. But because the only goal was to make the Asian productive over the course of a week, we went from a bespoke make file build to Basil, to turbo to nx and just left it there because builds were fast at that point.swyx: Interesting. Talk more about Turbo TenX. That's interesting ‘cause that's the other direction that other people have been doing.Ryan Lopopolo: Ultimately I have. Not a lot of experience with actual frontend repo architecture.swyx: You're talking that Jessica built the sky. So I'm like, I know the NX team. I know Turbo from Jared [00:06:00] Palmer.And I'm like, yeah, that's an interesting comparison.[00:06:02] One Minute Build LoopRyan Lopopolo: The hill we were climbing right, was make it fast.swyx: Is there a micro front end involved? Is it how how complex reactRyan Lopopolo: electron base single app sort of thingswyx: And must be under a minute. That's an interesting limitation. I'm actually not super familiar with the background shelf stuff.Probably was talked about in the fight three release.Ryan Lopopolo: BA basically means that codex is able to spawn commands in the background and then go continue to work while it waits for them to finish. So it can spawn an expensive build and then continue reviewing the code, for example.swyx: Yeah.Ryan Lopopolo: And this helps it be more time efficient for the user invoking the harness.swyx: And I guess and just to really nail this, like what does one minute matter? Like why not five, okay, good. We want no. WeRyan Lopopolo: want the inner loop to be as fast as possible. Okay. One minute was just a nice round number and we were able to hit it.swyx: And if it doesn't complete, it kills it or some something,Ryan Lopopolo: No.We just take that as a signal that we need to stop what we're doing, double click, decompose a build graph a bit to get us to high back under so that we [00:07:00] can able the agent continue to operate.swyx: It's almost like you're, it's like a ratchet. It's like you're forcing build time discipline, because if you don't, it'll just grow and grow.That's right. And you mentioned that my current, like the software I work on currently is at 12 minutes. It sucks.Ryan Lopopolo: This has been my experience with platform teams in the past, where you have an envelope of acceptable build times and you let it go up to breach and then you spend two, three weeks to bring it back down to the lower end of the average low bed stop.But because tokens are so cheap Yeah. And we're so insanely parallel with the model, we can just constantly be gardening this thing to make sure that we maintain these in variants, which means. There's way less dispersion in the code and the SDLC, which means we can simplify in a way and rely on a lot more in variance as we write the software.[00:07:45] Observability, Traces & Local Dev StackVibhu: Lovely.[00:07:46] Humans Are BottleneckVibhu: You mentioned in your article, like humans became the bottleneck, right? You kicked off as a team of three people. You're putting out a million line of code, like 1500 prs, basically. What's the mindset there? So as much as code is disposable, you're doing a lot of review. A lot [00:08:00] of the article talks about how you wanna rephrase everything is prompting everything, is what the agent can't see.It's kind of garbage, right? You shouldn't have it in there. So what's like the high level of how you went about building it, and then how you address okay, humans are just PR review. Like how is human in the loop for this?Ryan Lopopolo: We've moved beyond even the humans reviewing the code as well.[00:08:19] Human Review, PR Automation & Agent Code ReviewRyan Lopopolo: Most of the human review is post merge at this point.But post, post merge, that's not even reviewed. That's justswyx: Oh, let's just make ourselves happy by YouRyan Lopopolo: haven't used fundamentally. The model is trivially paralyzable, right? As many GPUs and tokens as I am willing to spend, I can have capacity to work with my hood base.The only fundamentally scarce thing is the synchronous human attention of my team. There's only so many hours in the day we have to eat lunch. I would like to sleep, although it's quite difficult to, stop poking the machine because it makes me want to feed it. You have to step back, right?Like you need to take a systems thinking mindset to things and [00:09:00] constantly be asking where is the agent making mistakes? Where am I spending my time? How can I not spend that time going forward? And then build confidence in the automation that I'm putting in place. So I have solved this part of the SDLC, and usually what that has looked like is like we started needing to pay very close attention to the code because the agent did not have the right building blocks to produce.Modular software that decomposed appropriately that was reliable and observable and actually accrued a working front end in these things, right?[00:09:35] Observability First SetupRyan Lopopolo: So in order to not spend all of our time sitting in front of a terminal at most, doing one or two things at a time, invested in giving the model that observability, which is that that graph in the post here.swyx: Yeah. Let's walk through this traces and which existed firstRyan Lopopolo: we started with just the app and the whole rest of it. From vector through to all these login metrics, APIs was, I dunno, half an [00:10:00] afternoon of my time. We have intentionally chosen very high level fast developer tools. There's a ton of great stuff out there now.We use me a bunch, which makes it trivial to pull down all these go written Victoria Stack binaries in our local development. Tiny little bit of python glue to spin all these up. And off you go. One neat thing here is we have tried to invert things as much as possible, which is instead of setting up an environment to spawn the coding agent into, instead we spawn the coding agent, like that's the entry point.It's just Codex. And then we give Codex via skills and scripts the ability to boot the stack if it chooses to, and then tell it how to set some end variables. So the app and local Devrel points at this stack that it has chosen to spin up. And this I think is like the fundamental difference between reasoning models and the four ones and four ohs of the past, where these models could not think so you had to put them in [00:11:00] boxes with a predefined set of state transitions.Whereas here we have the model, the harness be the whole box. And give it a bunch of options for how to proceed with enough context for it to make intelligent choices. SoVibhu: sales, so like a lot of that is around scaffolding, right? Yes. Previous agents, you would define a scaffold. It would operate in that.Lube, try again. That's pivoted off from when we've had reasoning models. They're seeming to perform better when you don't have a scaffold, right? That's right.[00:11:28] Docs Skills GuardrailsVibhu: And you go into like niches here too, like your SPEC MD and like having a very short agent MG Agent md.swyx: Yes. Yes.Vibhu: Yeah. So you even lay out what it is here, but I likeswyx: the table contents.Vibhu: Yeah.swyx: Like stuff like this, it really helps guide people because everyone's trying to do this.Ryan Lopopolo: This structure also makes it super cheap to put new content into the repository to steer both the humans and the agents.swyx: You, you reinvented skills, right?Vibhu: One big agents andswyx: skills from first princip holdsRyan Lopopolo: all skills did not exist when we started doing this.Vibhu: You have a short [00:12:00] one 100 line overall table of contents and then you have little skills, right? Core beliefs, MD tech tracker. Yeah. Yeah. The scale is overRyan Lopopolo: The tech jet tracker and the quality score are pretty interesting because this is basically a tiny little scaffold, like a markdown table, which is a hook for Codex to review all the business logic that we have defined in the app, assess how it matches all these documented guardrails and propose follow up work for itself.Before beads and all these ticketing systems, we were just tracking follow up work as notes in a markdown file, which, we could spa an agent on Aron to burn down. There's this really neat thing that like the models fundamentally crave text. So a lot of what we have done here is figure out ways to inject textswyx: intoRyan Lopopolo: the system right when we get a page, because we're missing a timeout, for example.I can just add Codex in Slack on that page and say, I'm gonna fix this by adding a timeout. Please update our reliability documentation. To require that all network calls have [00:13:00] timeouts. So I have not only made a point in time fix, but also like durably encoded this process knowledge around what good looks like.swyx: Yeah.Ryan Lopopolo: And we give that to the root coding agent as it goes and does the thing. But you can also use that to distill tests out of, or a code review agent, which is pointed at the same things to narrow the acceptable universe of the code that's produced.swyx: I think one of the concerns I have with that kind of stuff is you think you're making the right call by making, it's persisted for all time across everything.Yes. But then you didn't think about the exceptions that you need to make, right? And that you have to roll it back.Vibhu: Part of it isswyx: also sometimes it can follow your s instructions too.Vibhu: It's somewhat a skill, right? So it determines when it uses the tools, right? Like it's not like it'll run outta every call.It'll determine when it wants to check quality score, right?Ryan Lopopolo: Yeah. And we do in the prompts we give these agents, allow them to push back,[00:13:51] Agent Code Review RulesRyan Lopopolo: When we first started adding code review agents to the pr, it would be Codex, CLI. Locally writes the change, pushes up a PR on [00:14:00] those PR synchronizations of review agent fires.It posts a comment. We instruct Codex that it has to at least acknowledge and respond to that feedback. And initially the Codex driving the code author was willing to be bullied by the PR reviewer, which meant you could end up in a situation where things were not converging. So yeah, we had to,swyx: he's just a thrash.Ryan Lopopolo: We had to add more optionality to the prompts on both of these things, right? The reviewer agents were instructed to bias toward merging the thing to not surface anything greater than a P two in priority. We didn't really define P two, but we gave it, youswyx: did define P two.Ryan Lopopolo: We gave it a framework within which to score its outputswyx: and then greater than P zero is worse, right?Yes. P two is very good.Ryan Lopopolo: P zero is you will mute the code place ifswyx: you merch thisRyan Lopopolo: thing, right?swyx: Yeah.Ryan Lopopolo: But also on the code authoring agent side, we also gave it the flexibility to either defer or push back against review feedback, right? This happens all the time, right? Like I happen to notice something and leave a code review, [00:15:00] which.Could blow up the scope by a factor of two. I usually don't mean for that to be addressed Exactly. In the moment. It's more of an FYI file it to the backlog, pick it up in the next fix it week sort of thing. And without the context that this is permissible, the coding agents are gonna bias toward what they do, which is following instructions.swyx: Yeah.[00:15:19] Autonomous Merging Flowswyx: I do wanted to check in on a couple things, right? Sure. All the coding review agent, it can merge autonomously. I think that's something that a lot of people aren't comfortable with. And you have a list here of how much agents do they do Product code and tests, CI configuration and release tooling, internal Devrel tools, documentation eval, harness review, comments, scripts that manage the repository itself, production dashboard definition files, like everything.Yes. And so they're just all churning at the same time, is there like a record that, that any human on the team pulls to stop everythingRyan Lopopolo: Because we are building a native application here. We're not doing continuous deploy. So there's still a human in the loop for cutting the release branch.I see. We require a blessed [00:16:00] human approved smoke test of the app before we promote it to distribution, these sort of things.swyx: So you're working on the app, you're not building like infrastructure where you have like nines of reliability, that kinda stuff?Ryan Lopopolo: That's correct. That's correct. Okay. And also like full recognition here that all of this activity took in a completely greenfield repository.There's. Should be no script that this applies generally toswyx: this is a production thing, you're gonna shipRyan Lopopolo: toswyx: customers. Of course. Yeah, of course. So this is realVibhu: And like one of the things there is, you mentioned you started this as a repo from scratch. The onboarding first month or so was pretty, it was like working backwards, right?Yeah. And then you had to work with the system and now you're at that point where you know, you're very autonomous. I'm curious like, okay, so what, how human in the loop is it? So what are the bottlenecks that you wish you could still automate? And part of that is also like, where do you see the model trajectory improving and offloading more human in the loop?We just got 5.4. It's a really good,Ryan Lopopolo: fantastic model, by the way.Vibhu: Yeah. Yeah. It's the first one that's merged. Top tier coding. So it's codex level coding and reasoning. So general reasoning both in one model. SoRyan Lopopolo: andVibhu: computer [00:17:00] use vision.Ryan Lopopolo: Now we now with five four, I can just have Codex write the blog post, whereas for this one I had to balance between chat.swyx: Oh, I need to, I might be out of a job. Oh my God.Ryan Lopopolo: Oh,swyx: I know. You just gave me an idea for a completely AI newsletter that five four could do. Yeah, I get it Now.Ryan Lopopolo: This sort of thing is just one example of closing the loop, right? Like the dashboard thing you mentioned. We have Codex authoring the Js ON, for the Grafana dashboards and publishing them and also responding to the pages, which means when it gets the page, it knows exactly which dashboards are defined and what alerts.What alert was triggered by which exact log in the code base. ‘cause all of this stuff is collated together.swyx: It has to own everything.Yes. Yeah. Yeah.Ryan Lopopolo: And it means that if we have an outage that did not result in a page. It has the existing set of dashboards available to it. It has the existing set of metrics and logs and can figure out where the gaps in the dashboard are or [00:18:00] in the underlying metrics and fix them in one go.In the same way, you would have a full stack engineer be able to drive a feature from the backend all the way to the front end.Vibhu: So it, it seems like a lot of the work you guys had to do was you as a small team are fully working for a way that the model wants the software to be written. It's like less human legible for better. Code legibility, agent legibility. How do you think that affects broader teams? So one at OpenAI, do liaison, like this is how software should be written. Like I can imagine, say you join a new team with this methodology, this mindset there's ways that, teams do code review, teams write code, like teams are structured and a lot of it is for human legibility.So should we all swap? Like how does this play back one broader into OpenAI and then like broader into the software engineering, right? Is it like teams that pick this up will it's pretty drastic, right? You have to make a pretty big switch. Should they just full send Yeah.Ryan Lopopolo: The mindset is very much that I'm removed from the process, right? I can't really have deep code level opinions about [00:19:00] things. It's as if I'm. Group tech leading a 500 person organization.Vibhu: Yeah.Ryan Lopopolo: Like it's not appropriate for me to be in the weeds on every pr. This is why that post merge code review thing is like a good analog here, right?Like I have some representative sample of the code as it is written, and I have to use that to infer what the teams are struggling with, where they could use help, where they're already moving quickly and I can pivot my focus elsewhere.Vibhu: Yeah.Ryan Lopopolo: So I don't really have too many opinions around the code as it is written.I do, however, have a command based class, which is used to have repeatable chunks of business logic that comes with tracing and metrics and observability for free. And the thing to focus on is not how that business logic is structured, but that it uses this primitive ‘cause I know that's gonna give leverage by default.Vibhu: Yeah.Ryan Lopopolo: Yeah, back to that sort of systems stinking,Vibhu: and you have part of that in your blog post, enforcing architecture and ta taste how you set boundaries for what's used. There's also a section on redefining [00:20:00] engineering and stuff, but yeah, it's just, it's interesting to hear,Ryan Lopopolo: and as the models have gotten better, they have gotten better at proposing these abstractions to unblock themselves, which again, lets me move higher and higher up the stack to look deeper into the future on what ultimately blocked the team from shipping.swyx: Yeah. You mentioned so you, this is primarily a, it is like a 1 million line of code base electron app. But it manages its own services as well, so it's like a backend for front end type thing.Ryan Lopopolo: We do have a backend in there, but that's hosted in the cloud.Yeah. This sort of structure is actually within the separate main and render processesWithin theswyx: electric.That's just how electronic works.Ryan Lopopolo: Yeah, of course. So have also treated like. MVC style decomposition with the same level of rigor, which has been very fun.swyx: I have a fun pun. This is a tangent, NVC is model view controller. Any sort of full stack web Devrel knows that.But my AI native version of this is Model view Claw, the clause the harness.Ryan Lopopolo: That's right. That's right. I do think that there is an interesting space to [00:21:00] explore here with Codex, the harness as part of building AI products, right? There's a ton of momentum around getting the models to be good at coding.We've seen big leaps in like the task complexity with each incremental model release where if you can figure out how to collapse a product that you're trying to build, a user journey that you're trying to solve into code, it's pretty natural to use the Codex Harness to solve that problem for you. It's done all the wiring and lets you just communicate and prompts to let the model cook.Yeah. It's been very fun. And there's also a very engineering legible way of increasing capabil. It's fantastic, right? Yeah. Just give you, just give the model scripts, the same scripts you would already build for yourself.swyx: Yeah.Yeah. So for listeners, this is Ryan saying that software engineering or coding against will eat knowledge work like the non-coding parts that you would normally think.Oh, you have to build a separate agent for it. No, start a coding agent and go out from there. Which open Claw has like it's pie Underhood.Ryan Lopopolo: [00:22:00] Yes.Vibhu: Basically define your task in code. Everything is a codingswyx: agent by the way. Since I brought it up, it's probably the only place we bring it up. Is any open claw usage from you?Any?Ryan Lopopolo: No. No. Not for me. I don't have any spare Mac Minis rattling around my house.swyx: You can afford it? No. I just, I'm curious if it's changed anything in opening eye yet, but it's probably early days. And then the other, the other thing I, I wanna pull on here is like you mentioned ticketing systems and you mentioned prs and I'm wondering if both those things have to go away or be reinvented for this kind of coding.So the git itself and is like very hostile to multi-agent.Ryan Lopopolo: Yeah. We make very heavy use of work trees.swyx: But like even then, like I just did a, dropped a podcast yesterday with Cursors saying, and they said they're getting rid of work trees ‘cause it still has too many merge conflicts.It's still un too un unintuitive. But go ahead.Ryan Lopopolo: The models are really great at resolving merge conflicts. Yeah. And to get to a state where I'm not synchronously in the loop in my terminal, I almost don't care that there are mergeswyx: with disposable.[00:23:00] Yeah.Ryan Lopopolo: We invoke a dollar land skill and that coaches codex to push the PR Wait for human and agent reviewers Wait for CI to be green.Fix the flakes if there are any merged upstream. If the PR comes into conflict, wait for everything to pass. Put it in the merge queue. Deal with flakes until it's in Maine. End. This is what it means to delegate fully, right? This is in a, very large model re probably a significant tax on humans to get PRS merged, but the agent is more than capable of doing this and I really don't have to think about it other than keep my laptop open.swyx: Yeah. I used to be much more of a control freak, but now I'm like, yeah, actually you could do a better job of this than me. Yeah. With the right context. Yes.[00:23:47] Encoding Requirementsswyx: Anything else in harness in general? Just this piece, I just wanna make sure we,Ryan Lopopolo: I think one thing that I maybe didn't make super clear in the article that I heard on Twitter as an interesting, that's respond [00:24:00]swyx: to them.What's the chatter and then what's your response?Ryan Lopopolo: Ultimately, all the things that we have encoded in docs and tests and review agents and all these things are ways to put all the non-functional requirements of building high scale, high quality, reliable software into a space that prompt injects the agent.We either write it down as docs, we add links where the error messages tell how to do the right thing. So the whole meta of the thing is to basically tease out of the heads of all the engineers on my team, what they think good looks like, what they would do by default, or what they would coach a new hire on the team to do to get things to merch.And that's why we pay attention to all the mistakes, mistakes that the agent makes, right? This is code being written that is misaligned with some as yet not written down, non-functional requirement.swyx: Sorry, what? Did the online people misunderstand orRyan Lopopolo: No,swyx: whatyouRyan Lopopolo: responded to? Somebody just literally said that.I was like, oh yeah,swyx: okay,Ryan Lopopolo: This is the [00:25:00] thing. This is what I've been doing. Oh, youswyx: agree? Yeah. I see. Interesting.Ryan Lopopolo: One other neat thing, which I did totally did not expect is folks were just. Taking the link to the article and giving it to pi or Codex and say, make my repo this,Vibhu: you achi a whole recursion.Ryan Lopopolo: And it was wildly effective. Really? It was wildly effective. NoVibhu: way. It just actually is something I tried with five, four yesterday. I didn't have time. Last time I was like out speaking of something, and this is one of my things, I was like, okay, I have this article. Can we just scaffold out what it would be like to run this?And I, I did it first as that and then I was like, okay, let me take another little side repo and say okay, if I was to fully automate this like this because I haven't written a line of code, it'sRyan Lopopolo: like over full, setVibhu: it right. The side thing I'm doing of voice. TTS I'm just like, slobbing out, whatever.It's nothing production. I'm like, how would I make this like this? And it's actually like a really good way. It's like a good way to learn what could be changed, what could be like, it's just a good analyzing, right? You give it all the codes, you give it all the context, you give it the article and it walks you through it very well.That's right. That's right.[00:25:57] Inlining Dependencies[00:25:57] Dependencies Going Away & Brett Taylor's Responseswyx: I guess one more thing before we go to Symphony is I wanted to cover [00:26:00] Brett Taylor's response. We had him on the show. He is your chairman, which is wild. Yeah. That he's reading your articles as well and like getting engaged in it. He says software dependencies are going away.Basically they can just be like vendored. Yes. Response.Ryan Lopopolo: Aswyx: hundred percent. A hundred percent agree. You still pro qr, you still pay Datadog. You still pay Temporal. Thank you.Ryan Lopopolo: Yep. The level of complexity of the dependencies that we can internalize is, I would say low, medium right now. Just based on model capability.What does the,swyx: what is medium?Ryan Lopopolo: I would say like a. A couple thousand line dependency is a thing that we could in-house No problem. Call in an afternoon of time. One neat thing about it is like probably most of that code you don't even need. Like by in-house and abstraction, you can strip away all the generic parts of it and only focus on what you need to enable the specific thing.Yes. You're building,swyx: I've been calling this the end of b******t plugins.Ryan Lopopolo: Yeah.swyx: Because there's so much when I published an open source thing, I want to accept everything, be liberal. I want to accept, this is post's law, but that means there's so much bloat. Yes. There's so much overhead.Ryan Lopopolo: One other neat thing about [00:27:00] this too is when we deploy Codex Security on the repo, it is able to deeply review and change. The internalized dependencies in a much lower friction way than it would be to like, push patches upstream, wait for them to be released, pull them down, make sure that's compatible with all the transitive I have in my repo and things like that.So it's also much lower friction to internalize some of these things if code is free. ‘cause the tokens are cheap sort of thing.swyx: Yeah. Yeah. I think like the only argument I have against this is basically scale testing, which obviously the larger pieces of software like Linux, MySQL, he calls up even the Datadog and Temporals and then maybe security testing where Yes.Classically, I think, is it linis tos, it said security open source is the best disinfectant.Ryan Lopopolo: Many eyes.swyx: Many eyes. And if inline your dependencies and code them up, you're gonna have to relearn mistakes from other people that Yep.Ryan Lopopolo: Yep. And to internalize that dependency, you're back to zero and you have to start.Reassembling all those bits and pieces to Yeah. Have [00:28:00] high confidence in the code as it is written. Yeah.Vibhu: Even part of the first intro of this, you basically mentioned like everything was written by codex, including internal tooling, right? So internal tooling, like when you're visualizing what's going on it's writing it for itself.swyx: Yeah. I'm built internal tools way I now, and like I just show them off and they're like, how long did you spend? And I didn't spend any time. I just prompted it,Ryan Lopopolo: very funny story here.swyx: Yeah, go ahead.Ryan Lopopolo: We had deployed our app to the first dozen users internally had some performance issues, so we asked them to export a trace for us get a tar ball, gave it to our on-call engineer, and he did a fantastic job of working with Codex to build this beautiful local Devrel tool, next JS app, the drag and drop the tar ball in, and it visualizes the entire trace.It's fantastic. Took an afternoon, but none of this was necessary. Because you could just spin up codex and give it the tar ball and ask the same thing and get the response immediately. So in a way, optimizing for human [00:29:00] legibility of that debugging process was wrong. It kept him in the loop unnecessarily when instead he could have just like Codex cooked for five minutes and gotten this same.swyx: Yeah, you verify your instincts here of this is how we used to do it. Or this is how I would have used to solve it.Ryan Lopopolo: Yeah. In this local observability stack. Like sure, you can de deploy Yeager to visualize the traces, but I wouldn't expect to be looking at the traces in the first place because I'm not gonna write the code to fix them.swyx: Yeah. So basically there needs to be like this kind of house stack and owning the whole loop. I think that is very well established. And it sounds like you might be like sharing more about that in the future, right?Ryan Lopopolo: Yeah. I think we're excited to do[00:29:36] Ghost Libraries Specs[00:29:36] Ghost Libraries & Distributing Software as SpecsRyan Lopopolo: We're gonna talk about Symphony in a little bit, but like the way we distribute it as a spec, which I think folks are calling Ghost Libraries on Twitter.This is like a such a cool name. It does mean it becomes much cheaper to share software with the world, right? You define a spec, how you could build your own specifying as much as is required for a coding agent to reassemble it [00:30:00] locally. The flow here is very cool. Like we have taken. All the scaffolding that has existed in our proprietary repo spun up a new one.Ask Codex with our repo as a reference. Write the spec. We tell it. Spin up a team ox spawn a disconnected codex to implement the spec. Wait for it to be done. Spawn another codex and another team ox to review the spec com or review the implementation compared to upstream and update the spec so it diverges less.And then you just loop over and over Ralph style until you get a spec that is with high fidelity able to reproduce the system as it is. It's fantastic.Vibhu: And you're basically, you're not really adding any of your human bias in there, right? That's correct. A lot of times people write a spec and be like, okay, I think it should be done this way, and you'll riff on something.And it's no, the agent could have just handled it like you're still scaffolding in a sense, right? I want it done this way. It can determine its spec better.swyx: That's right. That's right. Part of me it, I'm, I've been working a lot on evals recently, and part of me is wondering if [00:31:00] an agent can produce a spec that it cannot solve.Is it always capable of things that he can imagine or can you imagine things that it is impossible to do?Ryan Lopopolo: I think with Symphony, we, there's like this there's this axis where you have things that are easier, hard, or established or new, right? And I think things that are hard and new is still something that the models need humans.Yeah. Drive.swyx: Yeah. Yeah.Ryan Lopopolo: But I think those other quadrants are largely salt. Given the right scaffold and the right thing that's gonna drive the agent to completion,swyx: it's crazy that it solved,Ryan Lopopolo: but it means that the humans, the ones with limited time and attention get to work on the hardest stuff, like the problems where it's pure white space out in front. Or like the deepest refactorings where you don't know what the proper shape of the interfaces are. And this is where I wanna spend my time. ‘cause it lets me set up for the next level of scale.swyx: Yeah. Yeah. Amazing. Let's introduce Symphony.I think we've been mentioning it every now and then. Elixir. Interesting option.Ryan Lopopolo: Yeah.swyx: Yeah. I'm not,Ryan Lopopolo: again, like the [00:32:00] elixir manifestation here is just a derivative. Is it a modelswyx: chosen? Yeah.Ryan Lopopolo: Yeah. Yeah. And it chose that because the process supervision and the gen servers are super amenable to the type of process orchestration that we're doing here.You are essentially spinning up little Damons for every task that is in execution and driving it to completion, which. Means the mall gets a ton of stuff for free by using Elixir and the Beam.swyx: I had to go do a crash course in Beam and Elixir, and I think most people are not operating at that scale of concurrency where you need that.But it is a good mental model for Resum ability and all those things. And these are things I care about. But tell me the story, the origin story of Symphony. What do you use it for? Is this, how did it form maybe any abandoned paths that you didn't take?[00:32:46] Terminal Free Orchestration[00:32:46] Symphony: Removing Humans from the LoopRyan Lopopolo: At the end of December we were at about three and a half PRS per engineer per day.This was before five two came out in the beginning of January. Everyone gets back from holiday with five two and no other work [00:33:00] on the repository. We were up in the five to 10 PRS per day per engineer. And I don't know about y'all, but like it's very taxing to constantly be switching like that. Like I was pretty tapped out at the end of the day, again, where are the humans spending their time? They're spending their time context switching between all these active tmox pains to drive the agent forward.swyx: Yeah. No way. Yeah.Ryan Lopopolo: So let's again, build something to remove ourselves from the loop. And this is what frantic sprinted adapt here to find a way to remove the need for the human to sit in front of their terminal.So a lot of experimentation with Devrel boxes and, automatically spinning up agents, like it seems like a fantastic end state here, where my life is beach. I open live twice a day and say yes no to these things. Yeah. And this is again, a super, super interesting framing for how the work is done.Because I become more latency and sensitive. I have [00:34:00] way less attachment to the code as it is written. Like I've had close to zero investment in the actual authorship experience. So if it's garbage. I can just throw it away and not care too much about it. In Symphony, there's this like rework state where once the PR is proposed and it's escalated to the human for review, it should be a cheap review.It is either mergeable or it is not. And if it's not, you move it to rework. The elixir service will completely trash the entire work tree NPR and start it again from scratch. Okay. And this is that opportunity again to say, why was it trash right? What did the agent do that wasswyx: bad. Yeah.Ryan Lopopolo: Fix that before moving the ticket toswyx: endRyan Lopopolo: of progress again.swyx: Yeah. Why is this not in codex app? I guess this, you guys are ahead of Codex app,Ryan Lopopolo: yeah, so the way the team has been working is basically to be as AI pilled as possible and spread ahead. And a lot of the things we have worked on have fallen out [00:35:00] into a lot of the products that we have.Like we were in deep consultation with the Codex team to. Have the Codex app be a thing that exists, right? To have skills be a thing that Codex is able to use. So we didn't have to roll our own to put automations into the product. So all of our automatic refactoring agents didn't have to be these hand rolled control loops.It has been really fantastic to be, in a way, un anchored to the product development of Frontier and Codex and just very quickly try to figure out what works and then later find the scalable thing that can be deployed widely. It's been a very fun way to operate. It's certainly chaotic. I have lost track very often of what the actual state of the code looks like.‘cause I'm not in the loop. There was. One point where we had wired playwright directly up to the Electron app. With MCPM CCPs, I'm pretty bearish on because the harness forcibly injects all those tokens in the [00:36:00] context, and I don't really get a say over it. They mess with auto compaction. The agent can forget how to use the tool.There's probably only what three calls in playwright that I actually ever want to use. So I pay the cost for a ton of things. Somebody vibed a local Damon that boots playwright and exposes a tiny little shim CLI to drive it. And I had zero idea that this had occurred because to me, I run Codex and it's able to, it's oh, it's better.Yeah. Like no knowledge of this at all. Uhhuh.[00:36:30] Multi Human ChaosRyan Lopopolo: So we have had like in human space to spend a lot of time doing synchronous knowledge sharing. We have a daily standup that's 45 minutes long because we almost have to. Fan out the understanding of the current state.swyx: Yeah, I was gonna say this is good for a single human multi-agent, but multi human, multi-agent is a whole like po like explosion of stuff.Ryan Lopopolo: Yeah. And that this is fundamentally why we have such a rigid, like 10,000 [00:37:00] engineer level architecture in the app because we have to find ways to carve up the space so people are not trampling on each other.swyx: Sorry, I don't get the 10,000 thing. Did I miss that?Ryan Lopopolo: The structure of the repository is like 500 NPM packages.It's like architecture to the excess for what you would consider, I think normal for a seven person team. But if every person is actually like 10 to 50. Then the like numbers on being super, super deep into decomposition and sharding and like proper interface boundaries make a lot more sense.swyx: Yeah. To me, that's why I talked about Microfund ends and I, an anex is from that world, but Cool. It is just coming back to, to, to this I dunno if you have other, thoughts on. Orchestrating so much work coin going through this. Is this enough? Is this like any aha moments?Vibhu: It'll be interesting to see like where, okay, so right now you pick linear as your issue tracker, right?swyx: Or it's like a is it actually linear? This is actually linear.[00:37:55] Linear vs Slack WorkflowVibhu: Oh, that's linear. It's linear.swyx: Oh I never looked atVibhu: video. The demo video I had to download to [00:38:00] run.swyx: So I, because I'm a Slack maxie, but Yeah, linear. Linear is also really good. Yes,Ryan Lopopolo: we do make a good use of Slack. We we fire off codex to do all these lotion, elasticity, fix ups, the things that like sync that knowledge into the repository.It's super cheap. Yeah.swyx: Yeah.Ryan Lopopolo: Just do it in Codex.swyx: My biggest plug is OpenAI needs to build Slack. You need to own Slack. Build yours. Turn this into Slack.Ryan Lopopolo: I did read about it. Youswyx: did?Ryan Lopopolo: Yeah.[00:38:25] Collaboration Tools for AgentsRyan Lopopolo: I would say that if we think that we want these agents to do economically valuable work, which is like this is the mission, right?We want AI to be deployed widely, to do economically valuable work, then we need to find ways for them to naturally collaborate with humans, which means collaboration tooling, I think, is an interesting space to explore.swyx: Yeah, totally. Yeah. GitHub, slack, linear.Vibhu: Yeah, that was my thing. Okay, where do we see right now Codex has started Codex Model, then CLI, now there's an app, app can let me shoot off multiple Codex is in parallel, but there's no great team collaboration for Codex.And it [00:39:00] seems like your team had some say into what comes out, right? So you talked to ‘em, codex kind of was a thing. From there, if you guys are on the bound, what stuff that like, you might not focus on, but what do you expect other people to be building, right? So people that are like five x 50 Xing.Should you build stuff that's like very niche for your workflow, for your team? Should it be more general so other people can adopt? Is there a niche there? ‘Cause part of it is just okay, is everything just internal tooling? Do we have everything our own way? Like the way our team operates has our own ways that we like to communicate or is there a broader way to do it?Is it something like a issue tracker? Just thoughts if you wanna riff on that.[00:39:35] Standardizing Skills and CodeRyan Lopopolo: I think TBD we have not figured this out in a general way. I do think that there is leverage to be had in making the code and the processes as much the same as possible. If you think that code is context, code is prompts, it's better from the agent behavior perspective to be able to look in a package in directory X, Y, Z, and it not to have to page so [00:40:00] deeply into directory if you C, because they have the same structure, use the same language, they have the same patterns internally.And that same like leverage comes from aligning on a single set of skills that you're pouring every engineer's taste into to make sure that the agent is effective. So like in our code base, we have, I think, six skills. That's it. And if some part of the software development loop is not being covered, our first attempt is to encode it in one of the existing setup skills, which means that we can change the agent behavior.Yeah. More cheaply than changing the human driver behavior.swyx: Yeah.[00:40:39] Self Improvement via Logsswyx: Have you ever, have you experimented with agents changing their own behavior?Ryan Lopopolo: We do.swyx: Yeah. Or parent agent changing a subagents, behavior or something like that.Ryan Lopopolo: We have some bits for skill distillation. So for example, there's one neat thing you can do with Codex, which is just point it at its own session logs to ask it to tell you how you can use [00:41:00] the tool pedal better.swyx: It's like introspectionRyan Lopopolo: or ask it to do things. I useVibhu: this session better. What skills should Iswyx: high? I like the modification of, you can do, just do things to you can just ask agent to do things.Ryan Lopopolo: Yeah. You can just codex things. This is like a, this is like a silly emoji that we have, right? You can just codex things, you can just prompt things.It's really glorious future we live in, but okay, you can do that one-on-one. But we're actually slurping these up for the entire team into blob storage and. Running agent loops over them every day to figure out where as a team can we do better and how do we reflect that back into the repositories?Yes, though everybody benefits from everybody else's behavior for free. Same for like PR comments, right? These are all feedback. That means the code as written, deviated from what was good, a PR comment, a failed build. These are all signals that mean at some point the agent was missing context. We gotta figure out how toswyx: Yeah.Ryan Lopopolo: Slurp it up and put it back in the reboot.swyx: By the way, I do this exactly right. I used to, when I use cloud code for [00:42:00] knowledge work, cloud cowork is like a nice product, right? Yes. In I think you would agree. I always have it tell me what do I do better next time? And that's the meta programming reflection thing.So I almost think like you have six reflection extraction levels in symphony and almost like the zero of layer. So the six levels are PO policy, configuration, coordination, execution, integration, observability. We've talked about a couple of these, but the zero layer is like the, okay, are we working well?Can we improve how we work? Yes. Can I modify my own workflow without MD or something? I don't know.Ryan Lopopolo: Yeah, of course. Yeah, of course you can. Like this thing is also able to cut its own tickets ‘cause we give it full access.Yeah. Make it a ticket to have it cut. Tickets you can.Put in the ticket that you expect it to file as on follow up work,swyx: like Yeah. Self-modifying. Yeah.Ryan Lopopolo: Yeah.[00:42:44] Tool Access and CLI FirstRyan Lopopolo: Put, don't put the agent in a box. Give the agent full accessibility over it. Domain.swyx: I had a mental reaction when you said don't put the agent in a box. So I think you should put it in a box. Like it's just that you're giving the box everything it needs.Ryan Lopopolo: Yeah. Context and tools.swyx: But we're like, as developers, we're used to calling [00:43:00] out to different systems, but here you use the open source things like the Prometheus, whatever, and you run it locally so that you can have the full loop. I assume.Ryan Lopopolo: Yep.Vibhu: I think likeRyan Lopopolo: another, you wanna minimize cloud, cloud dependencies.Vibhu: You also want to make sure that you think about what the agent has access to. What does it see? Does it go back into the loop, like from the most basic sense of you let it see its own like calls, traces it can determine where it went wrong. But are you feeding that back in? So you know, just the most basic level of you wanna see exactly what's input output, like does the agent have access to.What is being outputted, right? It can self-improve a lot of these things. It's allRyan Lopopolo: text, right? My job is to figure out ways to funnel text from one agent to the other.swyx: It's so strange like way back at the start of this whole AI wave Andre was like, English is the hottest day programming language.It's here, it's just Yeah. The feature as well.Vibhu: A lot of, okay. Like a lot of software, a lot of stuff. There's a gui, it's made for the human. We're seeing the evolution of CLI for everything, right? All tools have CLIs. Your agents can use [00:44:00] them well, do we get good vision? Do we get good little sandboxes?Like right now? It's a really effective way, right? Models love to use tools. They love the best. They love to read through text. So slap a CLI let it go loose. That works for everything.Ryan Lopopolo: It does. Yeah. Yeah.[00:44:14] UI Perception and RasterizingRyan Lopopolo: We've also been adapting nont, textual things to that shape in order to improve model behavior in some ways, right?We want the agent to be able to see the UI agents do not perceive visually in the same way that we do. They don't see a red box, they see red box button, right? They see these things in latent space. So if we want, Hey, yeah, I do. We haveswyx: a ding if that goes off every time. Alien spaceRyan Lopopolo: ding.Anyway if we wanna actually make it see the layout, it's almost easier to rasterize that image to ask EOR and feed it in to the agent. Ha. And there's no reason you can't do both, right? To like further refine how the model perceives the object it's [00:45:00] manipulating.swyx: Cool. Could we, you wanna talk about a couple more of these layers that might bear more introspection or that you have personal passion for?[00:45:07] Coordination Layer with ElixirRyan Lopopolo: I will say that the coordination layer here was a really tricky piece to get right.swyx: Let's do it. Yep. I'm all about that. And this is Temporal core.Ryan Lopopolo: This is where when we turn the spec into Elixir, where like the model takes a shortcut, right? Like it's oh, I have all these primitives that I can make use of in this lovely runtime that has native process supervision.Which is I think, a neat way to have taken the spec and made it more choices achievable by making choices that naturally mapswyx: Yeah.Ryan Lopopolo: To the domain, right? In the same way that like you would prefer to have a TypeScript model repo if you are doing full stack web development, right? Because the ability to share types across the front end and backend reduces a lot of complexity.And becauseswyx: that's what graph kill used to be.Ryan Lopopolo: That's right. Andswyx: I don't know if it's still alive, butRyan Lopopolo: [00:46:00] no humans in the loop here. So like my own personal ability to write or not write elixir. Doesn't really have to bias us away from using the right tool for the job. It is just wild.swyx: Love it. I love it.Yeah. I wonder if any languages struggle more than others because of this? I feel like everyone has their own abstractions. That would make sense. But maybe it might be slower, it might be more faulty where like you'd have to just kick the server every now and then. I, I don't know. I think observability layer is really well understood.Integration layer, CP is dead. I think all these just like a really interesting hierarchy to travel up and down. It's common language for people working on the system to understandRyan Lopopolo: The policy stuff is really cool, right? Yeah. You don't really have to build a bunch of code to make sure the system wait for the, to passswyx: it's institutional knowledge.Ryan Lopopolo: Yeah. You just give it the G-H-C-L-I with some text that say CI has to pass. It makes the maintenance of these systems a lot easier.[00:46:57] Agent Friendly CLI Outputswyx: Do you think that CLI maintainers need to be [00:47:00] do anything special for agents or just as is? It's good because like I don't think when people made the G GitHub, CLI, they anticipated this happening.Ryan Lopopolo: That's correct. The GH CLI is fantastic. It's great super industry.swyx: Everyone go try GH repo create GH pull and then pull request number, right? GH HPR, like 1 53, whatever. And then it like pullsRyan Lopopolo: basically my only interaction with the GitHub web UI at this point is GH PR view dash web.Exactly. Glanceswyx: at the diffRyan Lopopolo: and be like Sure thing. Send it. Yeah. But the CLI are nice ‘cause they're super token efficient and they can be made more token efficient really easily. Like I'm sure you all have seen like I go to build Kite or Jenkins and I could just get this massive wall of build output.And in order to unblock the humans, your developer productivity team is almost certainly gonna write some code that parses the actual exception out of the build logs and sticks it in a sticky note at the top of the page. And you basically [00:48:00] want CLI to be structured in a similar way, right? You're gonna want to patch dash silent to prettier because the agent doesn't care that every file was already formatted.Just wants to know it's either formatted or not. So it can then go run a right command. Similarly, like in our PNPM distributed script runner, when we had one, when you do dash recursive, like it produces a absolute mountain of text. But all of that is for passing. Test suites. So we ended up wrapping all of this in another scriptswyx: to suppress the,Ryan Lopopolo: which you can vibe the channel only output the failing parts of the tests.swyx: You make a pipe errors versus the standard, standard out. I don't know. Okay. Whatever. Too much thinking have to do that. The CII used to maintain SCLI for my company and yeah, this is like core, very core to my heart. But you're vibing my job.Ryan Lopopolo: That's right.swyx: Cool. Any other things?This is a long spec. [00:49:00] I appreciate that. It's got a lot of strong opinions in here. Any other things that we should highlight? I think obviously you can spend the whole day going through some of these, but I do think that some of these have a lot of care or some of this you might wanna tell people, Hey, take this, but, make it your own.[00:49:15] Blueprint Spec and GuardrailsRyan Lopopolo: Fundamentally, software is made more flexible when it's able to adapt to the environment in which it is deployed, which means that things like linear or GitHub even are specified within the spec, but not required pieces of it. There's like a more platonic ideal of the thing that you could swap in like Jira or Bitbucket, for example.But being able to tightly specify things like the ID formats or how the Ralph Loop works for the individual agents. Basically means you can get up and running with a fully specified system quickly that you then evolve later on. I think we never intended for this to be a static spec that you can [00:50:00] never change.It's more like a blueprint to get something worth a starting point up and running.swyx: Yeah.Ryan Lopopolo: For you then to vibe later to your heart's content,swyx: you have like code and scripts in here where it's oh, I think this is a really good prompt. It's just a very long prompt.Ryan Lopopolo: Fundamentally, the agents are good at following instructions, so give them instructions.And it will, improve the reliability of the result. We, much like the way we use Symphony, we don't want folks to have to monitor the agent as it is vibing the system into existence. So being very opinionatedVery strict around what these success criteria are means that our deployment success rate goes up. Yeah. It means we don't have to get tickets on this thing.Vibhu: Think it all goes back to that like code to disposable, right? Like early on when you had CLI or you'd kick off a Codex run, it would take two hours. You would wanna monitor okay, I'm in the workflow of just using one.I don't want it to go down the wrong path. I'll cut it off and, just shoot off four, like that was my favorite thing of the Codex app, right? Yeah. Just Forex it like, [00:51:00] it's okay. One of them will probably be right, one of them might be better. Stop overthinking it. Like my first example was probably like deep research.When you put out deep research and I'd ask it something like, I asked it something about LLM, it thought it was legal something and spent an hour, came back with a report completely off the rails. And I was like, okay, I gotta monitor this thing a bit. No don't monitor it. Just you want to build it so it's that it, it goes the right way.And you don't wanna, you don't wanna sit there and babysit, right? You don't want to babysit your agentsRyan Lopopolo: with that deep research query that you made. Looking at the bad result, you probably figured out you needed to tweak your prompt Yeah. A bit, right? That's that guardrail that you fed back into the code base for the task, your prompt to further align the agent's execution.Same sort of concept supply there too.swyx: When you talk, how are the customers feelingRyan Lopopolo: for Symphony? I think we have none, right? This is a thing we have put out into theswyx: world. Symphony's internal, right? As long as you are happy, you are the customer. That'

If you're from Wisconsin, chances are good that you've enjoyed a June Dairy celebration somewhere in the course of your life. Organizing the volunteers and all the educational opportunities is one mission supported by Dairy Farmers of Wisconsin. Mitch Kappelman is a fifth generation dairy operator that sits on DFW's board of directors. He represents dairy operators in Manitowoc and Calumet counties. Kappelman reminds us that there's more to June Dairy month then just the food and friendship. These face-to-face events allow Wisconsin dairy to tell its story. Kappelman says the care of our dairy animals and the dedication to preserving land and water resources is something he does everyday. However, sharing that story with consumers isn't something that happens everyday. Kappleman notes that 99% of all Wisconsin dairy operations are family owned and operated. That's not a story that consumers pick up just driving by. The work farms do with conservation practices to keep soil in place and maintain water quality are also stories not seen from a distance. That's why Kappelman believes these June Dairy experiences are one way to have meaningful exchanges with visitors. See omnystudio.com/listener for privacy information.

With Ryan Guth, Founder, Goldfin Group Overview Jason Diamond speaks with Ryan Guth, Founder of Goldfin Group, on moving beyond Edward Jones to build a business defined by control, differentiation, and entrepreneurial alignment. It's a thoughtful conversation about independence, and what it really means to build a business that fits your clients, your strengths, and your long-term vision. Listen in… > Download a transcript of this episode… NOTE: The views and opinions expressed by the guests on this podcast are their own and do not necessarily reflect the views and opinions of Diamond Consultants. Neither Diamond Consultants nor the guests on this podcast are compensated in any way for their participation. Watch… https://youtu.be/SRQSjRbtRzY About this episode… Advisors usually don't set out seeking change. In fact, the opposite is usually true. They build within a system, take advantage of the opportunities in front of them, and grow something meaningful over time. And for a while, that alignment works. But over time, priorities evolve. What once felt like the right environment can start to feel limiting: whether it's how you serve clients, how you present yourself in the market, or how much control you really have over the direction of your business. And that's where things begin to shift. In this episode, Ryan Guth, Founder of Goldfin Group, talks through that evolution in a very real and practical way. Ryan started his career at Edward Jones – an experience he still speaks very highly of – but ultimately decided to go independent to build a business that better reflected how he wanted to serve his entrepreneurial clients and express his entrepreneurial instincts. What makes Ryan's perspective especially interesting is his background. Before wealth management, he was a musical conductor. And that lens carries through into how he thinks about the advisor's role today—not as someone focused on products or portfolios, but as the person coordinating all the moving parts of a client's financial life. Ryan unpacks it all with Jason Diamond, including: The decision to leave Edward Jones—and what he was looking to gain in independence. The importance of marketing—and how “differentiation” plays a major role in Goldfin's success. The inside view of a transition—and what other advisors can learn both operationally and strategically. The alignment of his values and mindset with those of his clients—and how being an entrepreneur became more important over time. The impact of acquisitions—and Ryan's firsthand perspective on the acquisition of his broker dealer, Atria. It's a thoughtful conversation about independence, but more importantly, it's about what it really means to build a business that fits your clients, your strengths, and your long-term vision. Want to learn more about where, why, and how advisors like you are moving? Click to contact us or call 908-879-1002. Related Resources Player or Coach? Why Every Advisor Eventually Has to Choose As advisory firms grow, founders often face a critical inflection point: double down on being a top producer or evolve into a leader who builds lasting enterprise value. The Annual Report on Recruiting, Deals, and Transitions A companion to our annual Advisor Transition Report, Jason Diamond and Louis Diamond unpack what's driving advisor movement in 2025, and what the data reveals about control, growth, and where the industry is heading. IBD vs. RIA – Which Model Fits Your Future This guide offers a clear, side-by-side view of the two models—including distinctions between the DIY route of building an RIA from scratch and opting for a supportive independence platform to help align your business goals with greater options and opportunities. Diamond Consultants Edward Jones Advisor Transition Report 2025 This “firm-focused report” seeks to look under the hood at movement to and from Edward Jones from January to June of 2025. Have You Outgrown Your IBD or the Model Itself? Spending years inside the independent broker dealer framework can eventually spark a deeper reckoning. Advisors begin to look beyond the logo on the statement and ask a more fundamental question: does this structure still align with the future they're building, or has their business outgrown its foundation? Ryan Guth Founder​ I lead Goldfin Group from Franklin, TN and Albuquerque, NM, where I combine strategic financial guidance with a deep understanding of entrepreneurs' pivotal transitions. My leadership reflects a blend of professional insight and personal commitment, guiding clients toward aligning their financial strategies with their God-given purpose and gifts. I am a CERTIFIED FINANCIAL PLANNER™ professional. ​I am married to my wife, Amanda, and am the father to three boys. I enjoy all things entrepreneurial and am always on the lookout for new and innovative ways to solve bigger problems for more people, so they can be a greater force for good in the world. I recently became an author in 2024 with my first book Permission to Exit: Prepare to Sell Your Business Without Regret. In my spare time, I enjoy CrossFit, reading/listening to books and podcasts, and finding ways to serve through ministry.

This week on Commerce Code, we speak with Rikard Bandebo from VantageScore and Arvind Ronta from Pentadata. A little about the companies - VantageScore is a leading credit scoring company whose model is especially predictive because it uses new data sources that make it possible to provide credit scores to people even if they have limited credit history.Pentadata is a big reason VantageScore is able to do this. Pentadata is a financial data orchestration platform – which means its customers can access many different kinds of financial data through a single point of contact, or, in software terms, a single API.Rikard and Arvind have joined us to talk about:What's making credit scores more accurate - things like rent and utility payments that are big predictors of consumer payment behavior, but which have been omitted from credit scoring until recently.What it takes to get new kinds of data like that into the credit scoring system - it's not as easy as it looks!And what all of this means for the marketplace, from consumers to businesses.

Bryan Stewart is the Chief of Marketing and External Relations at Goodwill of Southern Nevada (GoodwillVegas.org), a nonprofit organization dedicated to workforce development, job training, and community support through retail operations and programs that help individuals overcome barriers to employment (often summarized as "saving the waste in people and things").He joined the organization in late 2021 (initially as Vice President of Marketing and Communications) and has since led major initiatives including:Launching the “Goodwill Works” brand platform and guidelines.Building in-house creative/publication services, standard signage, and multi-channel campaigns.Orchestrating the organization's 50th anniversary celebration.Creating internal programs like awards/recognition, customer compliments portal, leadership development fellowship, and an in-store fundraising initiative supporting local nonprofits.

In this episode, Ashutosh Garg sits down with David Homan, author of Orchestrating Connection, classical composer, and founder.David shares his journey—from overcoming childhood illness to navigating professional challenges like the Bernie Madoff Ponzi scheme—and explains how these experiences shaped his philosophy of connection.Discover why David draws a clear distinction between networking and genuine connection, how vulnerability and generosity build lasting relationships, and why diversity and empathy are essential for thriving communities.Whether you are a leader, connector, or simply curious about human relationships, this episode will transform how you think about community and connection.

In this episode, Carlos Gonzalez de Villaumbrosia interviews Chris Geoghegan, VP of Product at Zapier. As the company's first-ever Product Manager, Chris has spent nearly a decade scaling Zapier into a $5 billion automation giant that serves over 3.4 million businesses and 69% of the Fortune 1000.Zapier is not just building AI tools; they are powering their entire company with them. Chris reveals that his team currently runs over 800 active AI agents internally to manage everything from calendar prep to engineering triage. He breaks down the Code Red moment that shifted their strategy and how they are defining the future of Agentic Workflows.What you'll learn:Agentic vs. Deterministic: Why standard workflows follow a set path, while agents can reason, access knowledge, and change course to solve problems.The Orchestration Layer: How to hire and onboard AI agents using Context Engineering and Model Context Protocols (MCPs).Adoption vs. Transformation: Why adoption is just doing old tasks faster, while transformation unlocks business models that were previously impossible.Building a Moat: How Zapier uses its vast data on user intent to stay ahead of commodity LLM features.Key takeaways:Treat Agents Like Employees: You can't just deploy an agent; you must onboard it with specific context and tools to be effective.Lead by Building: Transformation fails if leaders don't use the tools. Zapier's execs do show-and-tell sessions to prove they are hands-on.AI Governance is Key: To move up-market to the enterprise, you must solve for Observability (who sent what data) and Access Control.Credits:Host: Carlos Gonzalez de VillaumbrosiaGuest: Chris Geoghegan Social Links: Follow our Podcast on Tik Tok here Follow Product School on LinkedIn here Join Product School's free events here Find out more about Product School here

Gamma is everywhere right now. With viral videos starring Rainn Wilson, massive drone shows over San Francisco, and a valuation of $2.1 billion, this AI startup has mastered the art of capturing attention in a crowded market. But behind these huge stunts is a surprisingly small, scrappy team using a very specific playbook to punch way above their weight class.My guest today is Kristin Fracchia, the Head of Marketing at Gamma. She's the architect behind the company's explosive growth to 70 million users and its transition from a quiet product-led company to a brand that dominates the conversation. Kristin reveals how she orchestrates “audacious” marketing moments that break the internet without breaking the bank.In this episode, we deconstruct the exact strategies Gamma uses to go viral repeatedly. You'll learn how to manufacture “luck” in PR, why unscalable influencer marketing is your biggest advantage, and how to execute massive brand stunts like The Sphere and celebrity cameos—even if you're just a team of ten.Here's what you'll learn in this episode:(00:00) Intro(01:29) The “Audacious” Launch Playbook for breaking through AI noise(05:28) Why constant shipping kills marketing momentum (and what to do instead)(10:38) The “Twist” Framework: How changing one element makes you viral(12:30) Landing a New York Times exclusive without a big agency(16:31) How to find the unique angle journalists actually care about(20:34) Scaling influencer marketing from manual outreach to 70M users(23:36) Why you can't track ROI on influencers (and the proxy metric to use instead)(28:54) The “How did you hear about us?” attribution model(35:51) The strategy behind Gamma's viral video parodies (Severance, Mission Impossible)(41:00) How Kristin used ChatGPT to negotiate a contract with Rainn Wilson(46:11) The real cost of celebrity cameos for B2B startups(48:01) Why distribution matters more than the creative asset itself(52:52) Production costs: When to go in-house vs. hiring an agency(56:44) Exploiting the “Gap”: How Gamma hacked The Sphere in Las Vegas(01:03:28) Orchestrating a 4,000-person drone show using existing events(01:08:55) “Peacocking”: Why your brand is your marketing budget(01:12:21) Using AI Tarot cards to win at Dreamforce(01:13:42) Rapid Fire: Favorite books and marketing inspirationsLINKS:Connect with Kristin:LinkedIn: https://www.linkedin.com/in/kristinfracchia/Twitter: @KristinFracchiaWebsite: https://gamma.app/Connect with Tim:Where to find Tim:LinkedIn: https://www.linkedin.com/in/timsoulo/X: @timsouloWebsite: https://www.timsoulo.com/References:“Audacious” by Mark Schaefer : https://businessesgrow.com/audacious/Lenny's Podcast:  ⁨@LennysPodcast⁩Claire Vo (Product/AI thought leader): https://www.linkedin.com/in/clairevo/

Tim Berglund talks to Colt McNealy (LittleHorse Enterprises) about his career in distributed systems. Colt's first job: software engineer at a real estate company. His challenge: working in a complex microservices environment and turning that pain into Little Horse.Colt's Current 2024 talk: https://current.confluent.io/2024-sessions/kafka-streams-as-a-data-store-for-a-workflow-engineGunnar Morling's blog: https://www.morling.dev/blog/Jack Vanlightly's blog: https://jack-vanlightly.com/SEASON 2 Hosted by Tim Berglund, Adi Polak and Viktor Gamov Produced and Edited by Noelle Gallagher, Peter Furia and Nurie Mohamed Music by Coastal Kites Artwork by Phil Vo

In this episode of The Wisdom Of ... Show, host Simon Bowen speaks with Lindsay Davis, Founder & CEO of FemTech Association Asia, the region's first and largest femtech network representing 80+ companies across 10 countries. From her global expansion leadership at Quintessentially to building an ecosystem that didn't exist, Lindsay shares profound insights on courage, ecosystem orchestration, and what it takes to drive systemic change in women's health across vastly different cultures and markets.Ready to systematically capture your leadership wisdom and turn it into scalable frameworks? Join Simon's exclusive Masterclass on The Models Method: https://thesimonbowen.com/masterclassEpisode Breakdown00:00 Introduction and the mission to advance women's health in Asia04:32 The career pivot from luxury brand expansion to femtech ecosystem building12:18 Why women's health receives only 4% of global R&D funding19:45 Building something that doesn't exist: October 2021 to 80+ companies across 10 countries28:36 The courage question - where resilience comes from35:52 Having a high threshold for shame and being happy failing42:28 The leadership lesson from someone who put aside their book49:15 Orchestrating founders, investors, corporates, governments around a single mission56:47 The UN ESCAP commission and defining transformational change01:03:22 FemTech Connect Asia: Creating the region's first femtech conference01:11:08 The suffragette movement insight and being part of the continuumAbout Lindsay DavisLindsay Davis started her career in multicultural advertising in the USA, then was recruited by the world's leading luxury lifestyle management brand, Quintessentially in the UK, to lead global expansion into 25 countries and oversee 60 offices worldwide, with secondments in NYC, China and Qatar. Davis was honoured on the Luxury Daily list of “Luxury Women in Watch” because of her global impact in the luxury sector. As the Founder & CEO of Singapore-based One Bee Consulting, Davis works with brands to develop and elevate loyalty solutions, customer experience and brand affinity through product development, content and programming, PR, community engagement and strategic partnerships.With a vision of available, accessible and affordable healthcare for all women in Asia, Davis founded FemTech Association Asia in October 2021 as the region's first and largest industry network for founders, professionals, and investors with the core focus on improving women's health through technology solutions. The organisation represents 80+ companies across 10 countries in Asia. FemTech Asia was a Finalist in the GIOF – 2022 Business Inclusivity Awards and is a member of the UNFPA Equity 2030 Alliance and a Founding Member of the Milken Institute Women's Health Network.In 2023-24, Davis was commissioned by the United Nations Economic and Social Commission for Asia and the Pacific (UN ESCAP) as a thought leader and researcher to define what is required to drive transformational and catalytic change in femtech in Southeast Asia. Davis is a contributor for the Milken Institute and sits on the Advisory Board for Women in Global Health – Singapore and Ovy Health in Indonesia.Connect with Lindsay DavisLinkedIn: https://www.linkedin.com/in/lindsay-davis-2584812/Instagram: https://www.instagram.com/femtechasia/Website: www.femtechassociation.comAbout Simon...

Taka Ariga hits all the right notes for AI at scale: clarity of purpose, strong foundations, sustainable innovation, engaged ownership, and a confident workforce.    Taka and Kimberly discuss going beyond novel AI prototypes; the limits of automation; context building; data sovereignty and integrity; the unstructured data deluge; the unique sensitivities and needs of public agencies; valuing ownership and viable ways to scale; plagiarizing for good; foundations for AI success; wanting innovation without change; rethinking governance; enabling confident AI use; making space for reinvention; and being a skeptical AI advocate.Taka Ariga is a heretical technologist and the founder of Sol Imagination. He focuses on AI strategy design, implementation, and value capture. Taka served the US Office of Personnel Management (OPM) as CDO and CAIO and the US Government Accountability Office (GAO) as Chief Data Scientist and Director of the Innovation Lab. Related Resources:Sol Imagination (company)                  https://sol-imagination.ai/  A transcript of this episode is here.   

In this episode, I sit down with David Homan, master connector, podcaster, start-up founder, co-author of Orchestrating Connection and founder of Orchestrated Connecting. We explore how connection, generosity, and purpose can transform our businesses and our lives.David shares how he's built a system to track and honor referrals — so that connectors get recognized for the value they create. We also talk about his insight that while most people are great at helping others, they often struggle to ask for what they need.We dive into why being intentional about who you surround yourself with matters, and how success often comes down to the right people in the right conditions. Key Takeaways:The best connectors give freely — but they also need to learn to ask for themselves.Every introduction has value; honoring the chain of connection strengthens trust.Purposeful communities grow when people align around shared values and generosity.The equation for meaningful success: the right people + the right conditions.True connection isn't networking — it's orchestrating relationships with intention.David can be found at: orchestratedconnecting.com In appreciation for being here, I have some gifts for you:A LinkedIn Checklist for setting up your fully optimized Profile:An opportunity to test drive the Follow Up system I recommend by checking this presentation page - you won't regret it. AND … Don't forget to connect with me on LinkedIn and be eligible for my complimentary LinkedIn profile audit – I do one each month for a lucky listener!Connect with me:http://JanicePorter.comhttps://www.linkedin.com/in/janiceporter/https://www.facebook.com/janiceporter1https://www.instagram.com/socjanice/Thanks for listening!Thanks so much for listening to our podcast! If you enjoyed this episode andthink that others could benefit from listening, please share it using the socialmedia buttons on this page.Do you have some feedback or questions about this episode? Leave a note inthe comment section below!Subscribe to the podcastIf you would like to get automatic updates of new podcast episodes, you cansubscribe to the podcast on Apple Podcasts or your favorite podcast app.Leave us an Apple Podcast reviewRatings and reviews from our listeners are extremely valuable to us andgreatly appreciated. They help our podcast rank higher on Apple, whichexposes our show to more awesome listeners like you. If you have a...

David Homan is the founder and CEO of Orchestrated Connecting, a global community built on the power of authentic relationships. He also leads Orchestrated Opportunities, hosts the Orchestrated podcast, composes classical music, and somehow still finds time to be a dad from middle-class roots to some of the most private circles in the world.About the book: Orchestrating Connection explores why we feel more isolated despite being more connected than ever and offers a practical blueprint for building intentional, purpose-driven communities. The book blends mindset and method—showing how clarity of personal purpose, shared values, and principles like generosity, curiosity, and vulnerability create belonging and collective impact. It's a guide for anyone—from leaders to individuals—who wants to replace fragmentation with meaningful connection. https://orchestratingconnection.com/Activate trust in your network, check out Soar Connect by clicking on this link: https://soarconnect.ai/ Connect with David Homan: Website: http://orchestratedconnecting.com LinkedIn: https://www.linkedin.com/in/davidrhoman/ Instagram: https://www.instagram.com/the_connection_orchestrator/ TurnKey Podcast Productions Important Links:Guest to Gold Video Series: www.TurnkeyPodcast.com/gold The Ultimate Podcast Launch Formula- www.TurnkeyPodcast.com/UPLFplusFREE workshop on how to "Be A Great Guest."Free E-Book 5 Ways to Make Money Podcasting at www.Turnkeypodcast.com/gift Ready to earn 6-figures with your podcast? See if you've got what it takes at TurnkeyPodcast.com/quizSales Training for Podcasters: https://podcasts.apple.com/us/podcast/sales-training-for-podcasters/id1540644376Nice Guys on Business: http://www.niceguysonbusiness.com/subscribe/The Turnkey Podcast: https://podcasts.apple.com/us/podcast/turnkey-podcast/id1485077152

In this inspiring conversation on Refocused Network, Shemaiah Reed sits down with David Homan — founder and CEO of Orchestrated Connecting, co-author of the bestselling book Orchestrating Connection: How to Build Purposeful Community in a Tribal World, and creator of SOAR CONNECT, a startup revolutionizing how we build and manage meaningful relationships.Starting from a middle-class background, David built an insanely connected global network of nearly 2,000 "superconnectors" — spanning entrepreneurs, investors, artists, activists, philanthropists, and more. He shares his personal journey, the pivotal decisions that redefined his path, and the repeatable methodology he's refined over a decade to move beyond transactional networking into deep, values-driven, trust-based connections.https://orchestratedconnecting.com/Key highlights from the interview:How one choice can transform your leadership and life trajectoryThe principles of curiosity, vulnerability, and "honoring the chain of connections"Building purposeful communities that drive real-world impact (mental health, climate, social justice, philanthropy, and beyond)Launching a startup (SOAR CONNECT) to scale authentic relationship-buildingWhy relationships are the true currency for creating positive changeDavid's story is a powerful reminder: with intention, integrity, and the right system, anyone can orchestrate connections that ripple out to make the world better. If you're ready to refocus on deeper relationships and purposeful momentum, this episode will light the way.

On today's show we feature an interview and discussion of US foreign policy with Dan Kovalik, author of the book, “The Plot to Overthrow Venezuela: How the US Is Orchestrating a Coup for Oil.” Then we turn our attention to Cuba and the situation facing that  island nation's people which has worsened since the US kidnapping of president Nicolas Maduro of Venezuela. Finally, we talk with a tech expert from the Electronic Frontier Foundation about the new electronic surveillance tools used by the Israeli Defense Force, in Gaza that are now being used by ICE here in the United States. The post Dan Kovalik on The US Orchestrating a Coup in Venezuela For Oil appeared first on KPFA.

Karl and Erum kick off 2026 with deep reflections on prosperity, consciousness, and the idea that we might be living in a simulation. But the real focus is on a concept that could make or break biotech companies: orchestration. They dive into why most biotech innovations outside of pharma struggle to commercialize and introduce the idea of value chain syndication—bringing together innovators, manufacturers, investors, and big incumbents to create entire ecosystems rather than just individual deals. Using examples like K18 Hair's marketing orchestration and the urgent need to replace Red Dye 40, they break down how founders can architect strategic "seed deals" that build toward transformative industry shifts. This isn't about traditional sales or business development—it's about becoming the center of an ecosystem that includes everyone from ingredient suppliers to end customers. With tailwinds from geopolitical changes, supply chain concerns, and increasing demand for bio-based solutions, the time for orchestration is now. Whether you're a founder trying to scale or a big company looking to innovate, this episode shows you how to think bigger than your own company and build the infrastructure for a bio-based future.Grow Everything brings the bioeconomy to life. Hosts Karl Schmieder and Erum Azeez Khan share stories and interview the leaders and influencers changing the world by growing everything. Biology is the oldest technology. And it can be engineered. What are we growing?Learn more at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠www.messaginglab.com/groweverything⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Chapters:(00:00:00) - Welcome and New Year reflections from California and Cape Town(00:01:00) - Prosperity, money circulation, and building a better society(00:04:23) - Consciousness, simulation theory, and the philosophy of everything(00:09:00) - Why we're replaying the orchestration episode(00:10:00) - What is orchestration and why it's not just sales or business development(00:15:00) - Why biotech companies struggle to commercialize outside pharma(00:18:00) - Value chain syndication and manufacturing orchestration explained(00:20:00) - Seed deals: How to start small and build toward the big picture(00:22:00) - The Red Dye 40 case study: Architecting an ecosystem for change(00:27:00) - Why founders need to think differently and become deal architects(00:31:00) - Why now? Geopolitical and economic tailwinds for biomanufacturing(00:34:00) - Risks, rewards, and the 5-10 year arc of ecosystem building(00:37:00) - Final reflections and how to get started with orchestrationLinks and Resources:MessaginglabNational Security Commission on Emerging Biotechnology's Report: Charting the Future of BiotechnologyRed Dye ban153. Ghosts of Biotech Past: Veronica Breckenridge's Playbook for Smarter Scaling149. Beyond Capital: Phil Morle of Main Sequence Ventures on Collaboration as the New Competitive Edge120. Busting Biotech's Bottlenecks: Veronica Breckenridge on the Path to Industrial Scale26. Breaking Bad Hair Habits with Biology: Suveen Sahib's K18 Rescues Your StrandsStar Talk Neil deGrasse TysonTopics Covered: biotech, CPG, business models, industry, bacterial cellulose, fermentationHave a question or comment? Message us here:Text or Call (804) 505-5553 ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠  / ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Twitter⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ / ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ / ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Youtube⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ / ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Grow Everything⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Email: groweverything@messaginglab.comMusic by: NihiloreProduction by: Amplafy Media

What happens when a class clown from Monaghan builds one of the most quietly impactful healthtech companies in Europe - and then takes on the U.S. healthcare system? In this year-end episode of The Shot of Digital Health Therapy, we sat down with Neill Dunwoody

In this episode of Inside Personal Growth, Greg sits down with David Homan — classical composer, nonprofit leader, global “connector of connectors,” and author of the bestselling book Orchestrating Connection. David shares the remarkable life events that shaped his philosophy on building authentic relationships at scale, from childhood adversity to leading an arts organization through crisis, to eventually forming a global community of over 2,300 super connectors. He breaks down the five principles of meaningful connection, explains why vulnerability and accountability matter more than ever, and reveals how to design relationships intentionally instead of leaving them to chance. David also shares powerful real-life stories that show how generosity and trust can create life-changing ripple effects. This episode is an inspiring guide to the art and science of human connection — and how it can transform your career, relationships, and purpose. ⭐ What Listeners Will Learn 1. The difference between networking and intentionally designing relationships 2. The Five Principles of Connection 3. Why reputation is the strongest currency you have 4. How to shift from “What can I get?” to “How can I serve?” 5. The emotional story that shows the true power of connection 6. How David built a global community of trusted connectors 7. The truth about finding your tribe 8. Practical steps listeners can use immediately Our Guest, David Homan: ➥ Book: Orchestrating Connection: How to Build Purposeful Community in a Tribal World ➥ Buy Now: https://a.co/d/1Iq1hGh ➥ https://orchestratedconnecting.com/ Beta sign-up for SOAR Connect: available on the website ➥soarconnect.ai ➡️LinkedIn: https://www.linkedin.com/in/davidrhoman Learn more about your Inside Personal Growth host, Greg Voisen: ➥ https://gregvoisen.com ➡️Instagram: https://www.instagram.com/insidepersonalgrowth/ ➡️Facebook: https://www.facebook.com/InsidePersonalGrowth/ ➡️LinkedIn: https://www.linkedin.com/in/gregvoisen/ ➡️Twitter/ X: https://twitter.com/lvoisen/

Agentic AI Revolution: How Smart Parents Are Building Business Automation Empires Episode Summary Tracy Brinkmann reveals the $50 billion agentic AI revolution that's creating a new class of parent entrepreneurs who build "ghost businesses" - income streams that run themselves, make decisions without human input, and generate real money while the owner is completely offline. This isn't basic automation; it's AI agents that think, decide, and execute entire business workflows. Tracy breaks down his Weekend Warrior Blueprint showing exactly how to build your first profitable AI agent in 48 hours, even with zero coding experience. Key Timestamps & Insights 00:00 - Opening 00:45 - Episode Overview 01:55 - The Age of Doing vs Orchestrating 04:25 - Weekend Warrior Blueprint - Complete System Phase 1 Foundation Agent setup Phase 2 Intelligence Layer Phase 3 Profit Engine implementation 05:05 - Five Best Business Verticals for Parents 06:10 - No-Code Platforms 06:25 - Decision Trees Explained 07:26 - Intelligence Layer Strategy 09:00 - Profit Engine Implementation 10:30 - Monitoring and Optimization 12:45 - The Bigger Picture: Democratization of Business 14:00 - The Psychological Barrier 14:45 - Whiskered Wisdom: Tonight's Action Step Strategies Shared The Weekend Warrior Blueprint (Complete 3-Phase System) Phase 1: Foundation Agent (Saturday Morning - 2 hours) Choose business vertical from the five best opportunities Set up infrastructure using Make.com or Zapier Create decision trees for automated choices Phase 2: Intelligence Layer (Saturday Afternoon - 3 hours) Connect to multiple AI models (Claude, GPT-4, specialized tools) Build memory systems using Notion or Airtable Create feedback loops for continuous learning Phase 3: Profit Engine (Sunday - 4 hours) Implement revenue-generating workflows Set up automated upselling and dynamic pricing Create monitoring and optimization systems Plan horizontal scaling strategy The Three-Tier Automation Empire Tier 1: Simple task agents Tier 2: Decision-making agents Tier 3: Full business orchestration systems Key Success Principles Focus on orchestrating, not doing Start with one automated task, master it, then scale Use AI agents that get smarter over time Build systems that work 90% without human intervention Resources Mentioned Platforms & Tools Make.com - No-code AI agent platform Zapier - Automation platform with AI capabilities Notion - AI memory system and database Airtable - Alternative database for AI memory Claude - AI for complex reasoning and analysis GPT-4 - AI for creative content generation Business Verticals for Parents Content creation and social media management Customer service and support E-commerce order processing and inventory management Lead generation and email marketing Data analysis and reporting Action Steps to Take Immediate Actions (Tonight) Write down three repetitive tasks you do in your business or side hustle Research automation for ONE task using Make.com or Zapier's AI features Don't overthink - pick the task that resonated most when you heard the list This Weekend Actions Saturday Morning (2 hours): Set up your Foundation Agent Choose your business vertical Create Make.com or Zapier account Build your first decision tree Saturday Afternoon (3 hours): Build Intelligence Layer Connect multiple AI models Set up memory system Create feedback loops Sunday (4 hours): Launch Profit Engine Implement revenue workflows Set up monitoring systems Plan scaling strategy Long-term Strategy Master one agent before adding another Focus on 90% automation, 10% human intervention Scale horizontally once profitable Consider teaching others as additional revenue stream Call to Action Primary CTA: AI Escape Plan Newsletter https://DarkHorseInsider.com - Join the AI Escape Plan newsletter - your twice-weekly roadmap for parents ready to break free from the 9-to-5 grind. Each issue delivers practical, AI-powered strategies to start, grow, and streamline side hustles, all designed to protect your family time while boosting your income. Your roadmap to more money, more freedom, and more of what truly matters. Secondary CTA: Take Action Tonight Don't wait for the "perfect time." The 18-month window for maximum advantage is open now. Start with one task automation tonight and begin building your escape from trading hours for dollars.

From early 2022 through late 2024, a group of threat actors publicly known as APT28 exploited known vulnerabilities, such as CVE-2022-38028, to remotely and wirelessly access sensitive information from a targeted company network. This attack did not require any hardware to be placed in the vicinity of the targeted company's network as the attackers were able to execute remotely from thousands of miles away. With the ubiquity of Wi-Fi, cellular networks, and Internet of Things (IoT) devices, the attack surface of communications-related vulnerabilities that can compromise data is extremely large and constantly expanding.   In the latest podcast from the Carnegie Mellon University Software Engineering Institute (SEI) Joseph McIlvenny, a senior research scientist, and Michael Winter, vulnerability analysis technical manager, both with the SEI's CERT Division, discuss common radio frequency (RF) attacks and investigate how software and cybersecurity play key roles in preventing and mitigating these exploitations.

This 'Media Buzz Meter' first aired on September 29th, 2025 … Howie Kurtz on Trump seeking more retribution against political enemies, Trump planning on sending troops to various Democrat run cities and Eric Adams dropping out of the NYC mayoral race. Follow Howie on Twitter: ⁠⁠⁠⁠⁠⁠⁠⁠@HowardKurtz⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠For more #MediaBuzz click here Learn more about your ad choices. Visit podcastchoices.com/adchoices

For Janet Cheung, every space begins with a feeling. Born in Sydney, raised in Hong Kong, and now based in Singapore, she brings a global rhythm to design. As Studio Principal at Peter Silling and Associates, Janet has spent over fifteen years shaping hospitality experiences that move people, from grand hotels and casinos to quiet cocktail bars that hum with intimacy. To her, design is emotional choreography, a song written in light, texture, and rhythm. A place, she says, should guide you like music does: through arrival and build-up, pause and reveal — each note drawing you closer, not just to the space, but to the people within it. In this conversation, Janet shares how thoughtful design can help us linger a little longer, build connection, and even heal. From the memories that spaces hold to the universal truths that transcend culture, she reminds us that behind every great interior is a story that stays with you long after you've left. [Her Story] 1. How living across Sydney, Hong Kong, and Singapore shaped her global eye for design 2. She describes every project as a song, layered, intimate, and unforgettable 3. A glimpse into some of the signature spaces she's crafted 4. Why the future of design and luxury is rooted in emotional sustainability, in how a space can comfort and heal 加入會員，支持節目： https://careher.firstory.io/join 留言告訴我你對這一集的想法： https://open.firstory.me/user/cky6u8bgpwpn00858w0xrike6/comments Powered by Firstory Hosting

In "Orchestrating Chaos: Lully's Take on the Top Warehousing Challenges", Joe Lynch and Mike Myers, the Founder and CEO of Lully.ai discuss how to supercharge existing Warehouse Management Systems with bolt-on algorithms for labor and cost savings. About Mike Myers Mike Myers is the Founder and CEO of Lully.ai, a bolt on technology that allows warehouses to ship more orders on time, with fewer resources, using the equipment, capabilities, and systems you already have. Mike's career has included roles at a large apparel brand, multiple national 3PL leaders, and finally a automation firm focused on autonomous vehicles. Mike describes himself as "obsessed with warehouses," and it shows! About Lully.ai Lully.ai helps customers drive both cost and labor savings, by leveraging a combination of simple operating rules and world-class algorithms, all available via API. Their approach enables you to supercharge your WMS without the typical pains of technology integration. Lully's focus is on making the work easier for the team on the floor; less travel, fewer location visits, better utilized equipment. The end result is happier employees and bolstered bottom lines. Key Takeaways: Orchestrating Chaos: Lully's Take on the Top Warehousing Challenges The "Orchestrating Chaos" Philosophy: Warehousing challenges are framed not as insurmountable problems, but as "chaos" that can be "orchestrated" using smart, targeted technology. The core message is that efficiency is found in harmonizing existing equipment and processes, rather than in complete overhauls. Supercharge, Don't Replace (The "Bolt-On" Approach): Lully.ai's solution is a "bolt on technology... available via API." This takeaway emphasizes that warehouses can achieve massive optimization by supercharging their existing WMS without the typical high-cost and painful technology integration, making advanced algorithms accessible and fast to deploy. The Dual Bottom Line Focus: The solution directly addresses the two critical pressures in logistics: driving both cost and labor savings. The algorithms are designed to improve the financial bottom line while simultaneously tackling the labor crisis by making floor work more efficient. Human-Centric Optimization: Lully.ai translates optimization directly into benefits for the floor team, leading to happier employees. Key improvements include significantly less travel, fewer location visits, and better utilized equipment, which reduces fatigue, increases accuracy, and improves retention. Experience-Driven Solution: Mike Myers' diverse background—which spans a large apparel brand, 3PL leaders, and autonomous vehicle automation—provides a unique, holistic, and deeply practical understanding of warehouse operations. This real-world expertise informs a solution that is grounded in operational necessity. The Algorithm/Rules Combination: The technology's effectiveness stems from blending "simple operating rules and world-class algorithms." This suggests that complex optimization is delivered via practical, easily adoptable rules, ensuring the technology is not only intelligent but also simple for floor managers and workers to implement. Maximizing Existing Assets (Capital-Light Efficiency): A major takeaway for warehouse leaders is that the solution helps ship more orders on time, with fewer resources, using the equipment, capabilities, and systems you already have. This focus on maximizing current assets offers a capital-light path to high-performance warehousing. Learn More About Orchestrating Chaos: Lully's Take on the Top Warehousing Challenges Mike Myers | Linkedin Lully.ai | Linkedin Lully.ai Lully.ai | YouTube Logistics of Logistics Listeners special offer The Logistics of Logistics Podcast If you enjoy the podcast, please leave a positive review, subscribe, and share it with your friends and colleagues. The Logistics of Logistics Podcast: Google, Apple, Castbox, Spotify, Stitcher, PlayerFM, Tunein, Podbean, Owltail, Libsyn, Overcast Check out The Logistics of Logistics on Youtube

Orchestrating the Nomad Century: Quotas, New Cities, and the Food Production Revolution. Gaia Vince encourages a proactive vision for managing massive climate-driven migration, involving facing expected heat, enlarging northern cities, and building entirely new ones. Vince provides an optimistic example of a managed migration where a farmer in Gujarat, India, applies for migration and is assigned to Aberdeen, Scotland. She suggests establishing a new United Nations agency with "real teeth" to organize migration among host and origin nations, allocating people via a quota system to specific jobs and areas. To mitigate hostility, migrants would commit to taking jobs in high-need industries for their first few years. A major challenge is food supply, requiring a complete overhaul of global food production, necessitating a shift toward a plant-based diet, as mass meat production is extremely inefficient. Alternative food sources like plant-based meats, insects, and vertical farming in cities are essential. Vince emphasizes the enormous potential for biodiversity restoration if damaged natural landscapes are left alone.

© Richard Buskin, 2025

© Richard Buskin, 2025

© Richard Buskin, 2025

© Richard Buskin, 2025

Dems Launch ‘Civil War' Narrative By Orchestrating Antifa Chaos In Blue Cities, Forcing Trump To Respond With Federal Forces

Howie Kurtz on Trump seeking more retribution against political enemies, Trump planning on sending troops to various Democrat run cities and Eric Adams dropping out of the NYC mayoral race. Follow Howie on Twitter: ⁠⁠⁠⁠⁠⁠⁠@HowardKurtz⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠For more #MediaBuzz click here Learn more about your ad choices. Visit podcastchoices.com/adchoices