Podcasts about Filling

1. Filled with prayer and fellowship 2. Filling the apostolic vacancy

AFC North OTA's are officially in the books—well, except for Cincy, who is still clocking in overtime next week. Tap-in with Tate, Pay & Dirt as they call out who's really cooking (stock UP) and who's currently fumbling the bag (stock DOWN). We're talking final roster moves before training camp and keeping the content up through the NFL's summer drought. Don't sleep on this episode. Hit play on the Steel Curtain Network or wherever you get your audio podcasts! Check out Meinelschmidt Distillery at meineldistillery.com and use the code SCNJUN to save 10% at checkout! Learn more about your ad choices. Visit megaphone.fm/adchoices

Recorded 2026-06-13 11:36:58

In this episode of the Celebrate Kids podcast, Dr. Kathy delves into the complexities of technology, particularly cell phones, and their impact on children. Reflecting on a poignant conversation about hopes for the next generation, she explores how kids recognize the negative aspects of technology but feel compelled to keep using it due to societal pressures. Dr. Kathy emphasizes the importance of not just banning technology, but also providing meaningful alternatives to fill the void. Additionally, she highlights the support from their ministry partner, Summit Ministries, which offers a two-week worldview camp that helps kids engage with cultural dynamics and personal development. Tune in for valuable insights on navigating technology in today's world.

Five-time Grammy Award-winning artist CeeLo Green joins Rickey Smiley On The Spot for one of the most entertaining and insightful conversations yet. This conversation originally took place on the Rickey Smiley On The Spot podcast, CeeLo dives into Atlanta's influence on music, the rise of Dungeon Family, and the lessons he's learned throughout his incredible journey of working with Kanye, Outkast, and more. Listen to the full interview on Apple Podcasts: Listen On Apple Podcasts Spotify: Listen On Spotify CHAPTERS (00:25) - Intro (02:23) - The truth about joining Outkast (03:34) - Filling in for Big Boi & joining Goodie Mob (04:33) - The origins of Gnarls Barkley (05:31) - Connecting with Danger Mouse in Athens (06:59) - Collaborating with Kanye West on "Bully" (10:10) - Performing "Bully" at SoFi Stadium ABOUT THE PODCAST Rickey Smiley On The Spot is Rickey in his truest form — Authentic. Funny. Heartfelt. Honest. Each episode brings audiences up close with one of comedy’s most trusted voices as he dives into real conversations that mix humor with humanity.See omnystudio.com/listener for privacy information.

Recorded 2026-06-12 16:09:52

Tune in here to this Friday's edition of the Brett Winterble Show! Jason Lewis is filling in for Brett Winterble. Jason kicks off the program by talking about the growing debate over property taxes in Mecklenburg County and across the country, highlighting concerns that homeowners are paying increasing tax bills without a clear understanding of the value of services they receive in return. He argues that rising housing costs and inflation have intensified frustrations, contributing to what he describes as a broader property tax revolt. Lewis also brings in broader themes about government taxation, public spending, and whether current tax systems reflect individual choice or forced redistribution. The discussion then expands into economic theory, touching on libertarian ideas about public goods, the role of government services, and whether taxpayers should directly pay for what they use. Listen here for all of this and more on The Brett Winterble Show! For more from Brett Winterble check out his YouTube channel. See omnystudio.com/listener for privacy information.

If you're posting every day and your retreat still isn't filling…You're not alone. But you are likely focusing on the wrong thing. In this episode of The Retreat Leaders Podcast, Shannon Jamail breaks down the real reasons your retreat isn't filling-even when you feel like you're "doing all the things" on social media. Posting is not a strategy Visibility takes time to build And most retreat leaders don't give it enough time Shannon walks through the biggest mistakes retreat leaders make when it comes to marketing and visibility-and what to do instead if you actually want bookings. You'll learn: Why posting daily isn't enough to fill your retreat The difference between posting and real marketing Why visibility is built over time (not overnight) What's actually missing from your strategy How to start getting in front of NEW people She also shares a simple path forward using AI + SEO strategies to help you get found beyond social media. What You'll Learn in This Episode • Why posting ≠ marketing • The real reason your retreat isn't filling • Why visibility takes longer than you think • How to start getting in front of new audiences • The foundational pieces most retreat leaders are missing Key Takeaways Posting Is Not the Problem You don't need more content-you need better strategy. You're Likely Not Reaching New People If your audience isn't growing, your bookings won't either. Visibility Takes Time Most retreat leaders quit or pivot before their visibility efforts actually start working. You Need More Than Social Media SEO, blogs, Pinterest, and AI visibility are where long-term growth happens. You Must Give Your Marketing Time to Work You cannot expect: consistent bookings growing awareness strong demand …if you're constantly starting over. Mentioned in This Episode If you're ready to actually build visibility (without guessing what to do next):  Grab Shannon's AI + SEO Mini Course for Retreat Leaders Only $17  https://pages.lpcontent.net/mindbodyacademy/mini-ai-course-sales-page This course walks you through exactly how to start getting found online using AI and SEO-so your retreats don't rely only on social media. The Retreat Leaders Podcast Resources and Links: Learn to Host Retreats Join our private Facebook Group Top 5 Marketing Tools Free Guide Get your legal docs for retreats Join Shannon in Denver at the Retreat Industry Forum  Join our LinkedIn Group Apply to be a guest on our show Grab the AI + SEO Mini Course Thanks for tuning into the Retreat Leaders Podcast. Remember to subscribe for more insightful episodes, and visit our website for additional resources. Let's create a vibrant retreat community together! Subscribe:  Apple Podcast | Google Podcast | Spotify -------- TIMESTAMPS Why Your Retreat Isn't Filling (00:01:06) Shannon addresses the common struggle of retreat leaders whose retreats don't fill despite posting on social media every day. Visibility is the Real Strategy (00:02:46) The speaker explains that filling retreats requires a comprehensive visibility strategy, not just social media marketing, including ads, SEO, and AI. Effective Calls to Action (CTAs) (00:04:02) Shannon discusses the importance of using clear CTAs in social media posts, like asking for engagement or offering lead magnets. Using Lead Magnets (00:05:20) An explanation of how to use lead magnets, like a free video or PDF, to capture email addresses and nurture leads. The Power of Blogging (00:07:20) Shannon emphasizes that blogging with a keyword strategy and FAQs is crucial for improving SEO and AI search rankings. Leveraging Pinterest for Visibility (00:10:25) Pinterest is highlighted as a visual search platform, not just social media, perfect for reaching people planning travel and self-improvement. Strategic Collaborations (00:12:33) Advice on collaborating with partners who have a warm, engaged audience that matches your ideal guest demographic for increased visibility. The Importance of Email Growth (00:13:53) The speaker stresses that growing an email list is essential, as it's a more effective sales tool than social media. Creating a Long Warm-Up Period (00:14:28) Shannon explains the necessity of a long warm-up period, sometimes up to two years, to build trust and excitement. A Successful Warm-Up Example (00:15:43) Shannon shares her personal success story of selling out a 2027 France retreat by using a long, strategic warm-up. Common Mistakes in Retreat Timing (00:17:35) The host points out the mistake of launching a retreat only a few months in advance, which is often unrealistic. The Investment of Hosting Retreats (00:20:00) Hosting profitable retreats requires an investment of time and money, and a comprehensive visibility strategy beyond just posting and praying. AI and SEO Mini-Course Offer (00:20:56) Shannon offers a special $17 mini-course on AI and SEO strategy, with prompts and videos, for podcast listeners.

Wednesday June 10, 2026 Intro: False teaching is not new: for full notes: https://www.cgtruth.org/index.php?proc=msg&sf=vw&tid=3305

Tune in here to this Wednesday’s edition of the Brett Winterble Show! Curtis Sliwa is filling in for Brett Winterble. Curtis kicks off the program by talking about President Donald Trump and the Republican Party's political strategy heading into the upcoming midterm elections. Sliwa questions Trump's recent comments regarding inflation, arguing that rising prices are hurting Americans and could damage Republican prospects at the ballot box. He expresses frustration with what he sees as blind loyalty among some Trump supporters and challenges listeners to explain why the president would praise inflation numbers that he believes are harmful to working families. Listen here for all of this and more on The Brett Winterble Show! For more from Brett Winterble check out his YouTube channel. See omnystudio.com/listener for privacy information.

If you have ever wondered what is really the difference between going to a doctor, a holistic doctor, a dietitian, or a certified holistic nutritionist — this episode is for you. If you have heard things online and thought, this person has a degree, this person doesn't, what does that even mean for me — today we are getting into all of it. I believe in conventional medicine. I also believe there are gaps that need to be filled. And I am passionate about sharing different ways to steward your health and wellness so that you can steward everything else. IN THIS EPISODE • What a doctor is actually trained to do — and why your labs can come back “normal” while you still don't feel well • How the conventional model approaches disease, diagnosis, and prescription • Where a registered dietitian fits in — and how their recommendations are connected to the same system • What a certified holistic nutritionist does and does not do, and why that distinction matters for you • Why the body shows signs of imbalance long before a diagnosis is possible • How functional lab work is used as data points alongside lifestyle — not as diagnosis • Why referring clients back to their doctor is always part of the process • The family health legacy that brought Cher into this work — and why she believes you can build a different one “For we are his workmanship, created in Christ Jesus for good works, which God prepared beforehand, that we should walk in them.” — Ephesians 2:10 Ready to take the next step? Apply to work with Cher at styleandstewardship.com/apply — no cost, just a short application so we can figure out if we are a good fit before we ever get on a call. Questions? Send them to hello@styleandstewardship.com Content shared on this podcast is for educational purposes only and does not constitute medical advice, diagnosis, or treatment

Champ Talk thanks listeners as the show nears 200 episodes, asks viewers to share, subscribe, and comment, and explains he's fasting while recording. He says this isn't a religious podcast but shares how a difficult year—sparked by Charlie Kirk's killing, multiple violent news events, a hard partying trip, and getting sick afterward—pushed him to strengthen his relationship with God. After trying churches, he and his family began consistently attending Canvas Church and he describes how Sundays now “fill his cup,” improve his mindset, and provide moral grounding, even as he remains imperfect and still argues with his wife. He discusses valuing Jesus' teachings, questioning some biblical issues, rejecting guilt- and fear-based faith, and believing many personal development ideas echo scripture. He connects faith to purpose, service, and breaking generational patterns for his family, and closes by encouraging listeners to share the episode.00:00 Welcome and Support00:46 Not a Sermon02:04 Why Faith Returned05:39 Finding a Church Home08:02 Blissfully Dissatisfied10:57 Faith and Moral Compass14:22 Gray Areas and Boundaries19:42 Family and Church Roots23:20 Teachings Over Fear26:03 Imperfect Progress27:28 Jail Turning Point31:21 Purpose and Legacy33:32 Closing Gratitude

(60) Magic Island - Chamber Filling With WaterBecome a supporter of this podcast: https://www.spreaker.com/podcast/harold-s-old-time-radio--4206392/support.

I am so excited today to be able to tell you about a wonderful new book that is coming into the world today. My lovely daughter in law, Keelia Clarkson, is sending out her first book, Chapter One Again.

Mentioned in the episode:Smidge- All Supplements and Products | Smidge® Code- GOLDIVY10 for a 10% discount at checkoutDr. Stephanie's- Shop Dr. Stephanie's Here Code- GOLDIVY30 for 30% off at checkoutGuest: Molly DeweyDownload Romy on iOS: https://apps.apple.com/us/app/romy/id6760265825Download Romy on Android: https://play.google.com/store/apps/details?id=health.leena.app&hl=en_USWebsite: www.romyhealth.coHave you ever left a doctor's appointment feeling dismissed, confused, or completely alone in your symptoms? The gaps in women's healthcare are real, but our guest today is delivering the answer women everywhere have been waiting for.In this episode, we sit down with entrepreneur and community advocate Molly Dewey, the co-founder of Romy—an AI-powered women's health companion built for the conditions medicine has historically gotten wrong. From endometriosis and PCOS to PMDD, perimenopause, and over 20 other conditions, Romy is rewriting the female health narrative. Molly shares how this groundbreaking platform combines clinically grounded health guidance, longitudinal symptom tracking, and actionable tools—like visit prep, provider summaries, advocacy letters, and pattern analysis—into a single, private, always-available companion. Whether you are in between appointments, in the middle of a painful symptom flare, or sitting in a waiting room trying to figure out what to say, this episode will show you how tech is becoming the ultimate advocate to ensure you never have to navigate your body alone.*Additionally, we want to remind you that this podcast is presented solely for educational and entertainment purposes. We are not licensed therapists, and this podcast is not intended as a substitute for the advice of a physician, professional coach, psychotherapist, or other qualified professional.*Find Andrea & Brooke as @goldivyhealthco on Instagram: Brooke Herbert | Andrea Herbert (@goldivyhealthco) • Instagram photos and videos#womenshealth #pcos #gapsinhealthcare #romy #mentalhealth #chronichealthconditionsSupport the show

send us a text via Fan Mail!It's actually chapter five.  Filling tanks and restraining reaction.  ContactOn Instagram at @make.joy.normal By email at makejoynormal@gmail.comSearch podcast episodes by topic www.bonnielandry.caShop my recommended resourcesThanks for listening to Make Joy Normal Podcast! 

send us a text via Fan Mail!We must find ways to fill our own tanks if we are going to be able to fill our children's tanks...ContactOn Instagram at @make.joy.normal By email at makejoynormal@gmail.comSearch podcast episodes by topic www.bonnielandry.caShop my recommended resourcesThanks for listening to Make Joy Normal Podcast! 

GET IN THE CAR BITCHES WE'VE GOT A SUMMER VACATION SERIES!!!!! Welcome to Filling In with Dr. Connie Wang - a show about getting into everyones business, literally and figuratively! I "fill in" for a shift in the most random industries, to take you behind the scenes of different careers and see if you have what it takes to fill in! Think the shows Dirty Jobs meets The Simple Life. Along the way we meet new faces, learn new skills, and walk away with a deeper appreciation for everyone around us that makes some place a home. Episode 1: https://www.youtube.com/watch?v=-0LDAqHMWmY&feature=youtu.beToday, I fill in for Woodgy aka the mascot of the New England Major League Rugby team, The Free Jacks! We meet Enzo, the man within Woodgy (or the Woodgy within the man?) to learn the ins and outs of helping a character come to life, influence a crowd, and have fun all at the same time. IG and Tik Tok: @drconniewang

Tune in here to this Tuesday's edition of the Brett Winterble Show! Chad Adams is filling in for Brett Winterble. Chad kicks off the program by talking about artificial intelligence, data centers, and the public debate surrounding their rapid expansion. He pushes back against concerns that AI data centers are uniquely harmful, arguing that large-scale data centers have existed for decades and are simply becoming more powerful as technology advances. Adams compares criticism of data centers to opposition faced by other industries and suggests many fears about AI are exaggerated. Listen here for all of this and more on The Brett Winterble Show! For more from Brett Winterble check out his YouTube channel. See omnystudio.com/listener for privacy information.

Discover how Torah wisdom can guide us through life's challenges with resilience, purpose, and emotional awareness. In this episode, Katia Bolotin, pianist, composer, song-writer, lecturer, and most recently, author of Making It Relevant shares her inspiring journey from a traditional upbringing to embracing Torah Judaism, and how she leverages her background as a musician to connect deeply with spiritual and personal growth. Her insights offer practical tools to live intentionally in today's fast-paced world.Main Topics:The transformative power of Jewish inspiration and sustaining momentumIntegrating Torah principles with personal and professional life as an artistBalancing the paradox of being a singer with the Torah concept of Kol IshaThe concept of "becoming" versus "being" and ongoing growth through TorahOvercoming challenges with anti-Semitism and strengthening Jewish identityApplying emotional resonance and relevance to Torah studyThe significance of purpose over fleeting pleasure in lifeInsights into Jewish life and growth from her new book, Making It RelevantMaking It Relevant: Timeless Torah Wisdom for an Ever-Changing WorldBuy on Amazon HereMosaica PressChabad.orgAish.comTimestamps:00:00 - Introduction to Katia Bolotin and her multifaceted background02:04 - The weekly Parsha and the importance of sustaining inspiration03:34 - The story of her early Jewish education and pivotal moments04:48 - Impact of Torah learning during her conservatory years06:26 - The process of embracing Torah and overcoming difficulty07:23 - Trusting oneself and the role of intuition in spiritual growth08:41 - The analogy between piano practice limitations and Torah observance09:15 - The significance of Naase Venishma and experiential learning10:32 - Balancing a career in music with Shabbat and Torah observance11:20 - Using her voice to empower Jewish women and her transition to Kolisha13:00 - The shock of Kolisha and her commitment to Torah halacha14:09 - Founding One Voice and the vibrant Jewish women's music scene in Israel15:52 - Teaching the beauty and intimacy of singing in Torah context17:03 - How she accepted her initial spiritual restrictions as a divine plan18:21 - The metaphor of the Kohen with a disability serving others19:02 - Recognizing oneself as created according to God's will20:31 - The importance of transforming impulses through Torah and self-awareness22:07 - The diversity of musical interpretation and internal spiritual uniqueness23:44 - The meaning behind the detailed offerings of the 12 princes24:33 - Her book Making It Relevant—timeless lessons for modern life26:23 - The relevance of Torah character traits in today's tech-driven society27:42 - The concept of human becomings and continuous growth28:50 - How Torah promotes emotional resonance and life relevance30:34 - From dreams to reality: writing her book through divine support32:34 - The role of her husband in her journey and his encouragement33:36 - The simplicity and authenticity of her writing process35:02 - A deep dive into Yosef's story—transforming victimhood into purpose36:36 - Changing life's story by shifting perspective and mindset38:27 - Advice for young Jews facing anti-Semitism and strengthening identity39:54 - The importance of connecting to Israel and spiritual reawakening43:55 - Filling the gap in her Jewish education through consistent self-study45:56 - The power of regular Torah learning and self-education47:20 - Acknowledging life's struggles while pursuing purpose and happiness48:15 - The message of moving forward, unstuck, and living with purpose49:19 - How and where to purchase her book Making It Relevant Resources & Links :Connect with Katia Bolotin:

What is freeboard? How much media should really go into a tank? Mike Urbans explains freeboard, minimum bed depth, backwash expansion, upper screens, and common dealer mistakes that can damage control valves and reduce treatment performance. Trust the Frog™ 

Why do some Pilates studios consistently fill classes while others seem stuck in a cycle of promotions, discounts, and unpredictable revenue?In this episode of The Pilates Business Podcast, host Seran Glanfield explores one of the biggest mistakes boutique fitness studio owners make when it comes to marketing: treating it as a reactive activity rather than a strategic system. Seran shares why random marketing creates random results, how inconsistent messaging impacts client trust, and what successful Pilates, barre, and yoga studio owners do differently to create sustainable growth. If you're tired of posting on social media, sending emails, and running promotions without seeing the bookings you want, this episode will help you build a more intentional marketing strategy that attracts ideal clients, fills classes, and creates predictable revenue for your boutique fitness business.In This Episode You'll Learn:Why reactive marketing creates inconsistent revenueThe hidden delay between marketing efforts and client bookingsHow random marketing leads to random resultsWhy consistency always beats intensityThe importance of brand clarity and messagingHow to become the obvious choice in your communityWhy broad marketing messages often fail to attract ideal clientsThe difference between generating leads and building demandHow to create predictable growth through intentional marketing systemsThe marketing shifts successful studio owners make to fill classes consistentlyGot a question for Seran? Add it here

Tune in here to this Monday's edition of the Brett Winterble Show! Chad Adams is filling in for Brett Winterble. Chad kicks off the program by talking about media bias and political polarization. Responding to feedback from previous shows, he argues that criticizing Democrats is not the same as “bashing” them and says Americans should be able to disagree politically without hostility. He points to what he views as bias in mainstream media, particularly citing the handling of political figures by news organizations, and contends that many journalists fail to recognize their own political leanings. Adams also discusses differences between conservatives and progressives in how they view America, suggesting that conservatives tend to focus on the nation’s history, achievements, entrepreneurship, and innovation, while progressives are more focused on political power and control. Listen here for all of this and more on The Brett Winterble Show! For more from Brett Winterble check out his YouTube channel. See omnystudio.com/listener for privacy information.

Recorded 2026-06-07 14:42:37

1. God Wants to Speak to You Key Point: God actively communicates with His people, but we must be willing and able to perceive His voice. Supporting: God may speak in one way or another, yet people often do not perceive it (Job 33:14). Throughout Scripture, God spoke in many ways—dreams, visions, a still small voice, and even unexpected means. The issue is not whether God speaks, but whether we are listening and recognizing His voice. 2. The Condition of Your Heart Matters Key Point: Your heart determines how you receive and respond to God's Word. Supporting: The Word of God is the seed, and the heart is the soil. Different heart conditions produce different results, but the goal is a fruitful heart—one that receives, believes, and obeys God's Word. Fruitfulness comes when the Word is not just heard but acted upon. 3. Be a Doer, Not Just a Hearer Key Point: Hearing God's Word without obeying it leads to self-deception. Supporting: James 1 teaches that hearing the Word without doing it is like looking in a mirror and forgetting what you saw. The Word reveals our true spiritual condition, but transformation only happens when we respond in obedience. Blessing follows those who both hear and act. 4. God's Word Is the Primary Way He Speaks Key Point: Every message, impression, or experience must be tested against Scripture. Supporting: The Bible is inspired, authoritative, and without error. While God speaks in many ways—through people, circumstances, or impressions—everything must be filtered through His Word. A strong foundation in Scripture helps us discern truth from error. 5. God Also Speaks Through Impressions and the Holy Spirit Key Point: God often speaks through internal impressions, inspiration, and guidance from the Holy Spirit. Supporting: God's voice is not always audible. He often speaks through thoughts, ideas, and impressions that align with His truth. The Holy Spirit guides believers into truth, bringing clarity, creativity, and direction. These impressions should always align with Scripture and be confirmed wisely. 6. Guard Against Misusing “God Told Me” Key Point: Claiming God's voice can be misunderstood or misused, so discernment is essential. Supporting: People can confuse emotions or desires with God's voice, or even use “God told me” to manipulate situations. While God truly speaks, believers must remain grounded, humble, and anchored in Scripture to avoid deception. 7. Cultivate God's Presence Daily Key Point: Consistent time with God positions you to hear Him clearly. Supporting: Prayer, worship, and reading Scripture are not routines to check off—they cultivate God's presence in your life. Filling your mind with God's truth allows the Holy Spirit to bring guidance at the right time. What you “store” spiritually will be available when you need it. 8. Spiritual Perception Must Be Developed Key Point: Hearing God requires intentional spiritual awareness. Supporting: Just as natural perception helps us interpret the world, spiritual perception helps us understand what God is saying. Distractions, lack of focus, or a hardened heart can block clarity. A receptive, attentive heart is essential. 9. Balance Is Necessary in Hearing God Key Point: Avoid extremes—God speaks, but not every thought is from Him. Supporting: One extreme denies that God speaks at all; the other assumes every idea is from God. Truth lies in balance. We test impressions through Scripture, seek wise counsel, and remain grounded in truth. 10. Example: God Confirms His Voice Key Point: God can confirm His guidance in meaningful and personal ways. Supporting: An example shared was receiving the phrase “practice the presence of God” during prayer, then immediately encountering the same message in a devotional. This kind of confirmation reflects how God can affirm what He is speaking, bringing peace and clarity.

Tracey and Sally are joined by a silent guest, Nic in this super fun episode of The Golden Crown Podcast! They complete a mystery series that stems all the way from season one- we hope that you enjoy:)

Take your personal data back with Incogni! Use code MARKDAVIS at the link below and get 60% off an annual plan: https://incogni.com/markdavisSee omnystudio.com/listener for privacy information.

See omnystudio.com/listener for privacy information.

Take your personal data back with Incogni! Use code MARKDAVIS at the link below and get 60% off an annual plan: https://incogni.com/markdavisSee omnystudio.com/listener for privacy information.

Take your personal data back with Incogni! Use code MARKDAVIS at the link below and get 60% off an annual plan: https://incogni.com/markdavisSee omnystudio.com/listener for privacy information.

Tune in here to this Thursday’s edition of the Brett Winterble Show! Curtis Sliwa is filling in for Brett Winterble. Curtis kicks off the program by talking about his return to Charlotte’s WBT airwaves and his long friendship with Brett Winterble, dating back to Winterble’s days as a phone screener for Rush Limbaugh. Sliwa introduces himself to listeners by reflecting on his career in talk radio, his leadership of the Guardian Angels, and his past runs for mayor of New York City. He shares stories about helping combat crime in New York during the turbulent late 1970s and credits the Guardian Angels with helping restore public safety when police resources were stretched thin. Listen here for all of this and more on The Brett Winterble Show! For more from Brett Winterble check out his YouTube channel. See omnystudio.com/listener for privacy information.

If we move past the confusing labels of "biblical manhood," what are we actually left with?

Ryan McQuade of AwardsWatch.com joins Christina to discuss the mega-hits Obsession (directed by 26-year-old Curry Barker) and Backrooms (by 20-year-old Kane Parsons), the rise of YouTube content creators in cinema and more! Plus they talk basketball! :) Don't miss it

Take your personal data back with Incogni! Use code MARKDAVIS at the link below and get 60% off an annual plan: https://incogni.com/markdavisSee omnystudio.com/listener for privacy information.

Summary When a rollout lands badly on the frontline, the cost isn't just lost productivity. It's the people who quietly start looking elsewhere. And it's rarely the people you'd guess. In this episode, Justin talks with Kapil Dua, Associate Director of Change Management and Issues Management at a Fortune 100 company, who has spent over a decade leading large-scale SaaS implementations, including current rollouts impacting more than 20,000 stakeholders. Kapil makes the case that the real downside of a poor change isn't the immediate friction, it's the slow erosion of trust that follows: your strongest performers have options, and when they decide a workplace has a "taxed relationship" with change, they leave. From there, the conversation moves into what actually works at scale. Kapil walks through why he chases down cynics instead of avoiding them, why most change communications fail at the language layer (not the strategy layer), and why the best implementations he's been part of were the ones nobody talked about afterward. He also shares the "two wolves" story, his "right things, for the right reasons, in the right ways" rule, and a memorable line about why ignoring how something feels for the user is like designing toilet paper out of sandpaper, it gets the job done, but it hurts. If you're rolling out anything that touches the frontline this year, this one is worth your time. Key Topics Why the biggest cost of a failed rollout is the best people you didn't realize you were losing The case for being honest when a change will mean more work, not less How to convert cynics into your strongest change champions The "two wolves" story, and why change always feeds the dark wolf first Communication design: writing every message to be misread, not just understood Working through layers of stakeholders when one-on-one isn't possible at 20,000 people Why a great change isn't celebrated, it's seamless The 10:1 ratio: it takes ten good experiences to erase one bad one "How will it feel?" as the question most rollouts skip Chapters 00:00 Introduction to Change Management and Adoption 01:56 The Consequences of Poor Adoption 04:33 Measuring the Impact of Employee Satisfaction 07:32 Generational Perspectives on Work and Change 10:09 Balancing Macro and Microeconomic Perspectives 12:13 The Pressure of Public Companies 15:50 The Importance of Employee Experience 18:19 Aligning Associate Experience with Profitability 20:46 The Emotional Impact of Change 24:44 Filling the Gaps in Communication 25:32 Engaging Skeptics in Change Initiatives 29:40 The Reality of Change and Data Collection 31:32 The Importance of Honesty in Change Management 38:07 Navigating Change at Scale 46:58 Building a Change Network 57:50 The Human Element in Change Implementation Guest Bio Kapil Dua is Associate Director, Change Management and Issues Management at a Fortune 100 company, where he leads enterprise transformation focused on process alignment, operational excellence, and user adoption. With over a decade of experience driving large-scale SaaS implementations, including rollouts impacting more than 20,000 stakeholders, he brings a practical, people-first, data-driven perspective on leading change across complex organizations. Resources Frontline Innovators Podcast Kapil Dua on LinkedIn Skyllful - Frontline Enablement Platform

Tune in here to this Wednesday's edition of the Brett Winterble Show! Curtis Sliwa is filling in for Brett Winterble. Curtis kicks off the program by talking about his long career in talk radio and public service, as well as his recent run for mayor of New York City. He shares stories about his decades leading the Guardian Angels, a volunteer organization focused on public safety, and reflects on the challenges facing major cities across America, including crime, homelessness, and quality-of-life issues. Sliwa also discusses his friendship with Brett Winterble and their shared history in radio, including Winterble’s early days working alongside Rush Limbaugh. Throughout the opening segment, Curtis highlights his independent political approach, his commitment to community activism, and his passion for animal rescue, noting that he and his wife have spent years saving and adopting out cats from shelters. He invites listeners to join the conversation and previews a discussion about the growing migration of Northeastern residents to North Carolina and South Carolina. Listen here for all of this and more on The Brett Winterble Show! For more from Brett Winterble check out his YouTube channel. See omnystudio.com/listener for privacy information.

Tune in here to this Tuesday’s edition of the Brett Winterble Show! Chris Kroc is filling in for Brett Winterble as he kicks off the program by talking about the controversial Shelby police assault case that has sparked national attention. Kroc questions the public reaction surrounding the viral Ring doorbell video showing former officer Carson Hider repeatedly punching 33-year-old Shari Moore during an arrest. He argues that the public is only seeing a limited portion of the encounter and suggests there may have been critical moments before the video began that are being ignored. While making clear that he does not defend the repeated punches shown in the footage, Kroc criticizes what he sees as a rush to judgment driven by media narratives and racial politics. He also takes aim at civil rights attorney Benjamin Crump, accusing him of attempting to frame the incident as racially motivated before all the facts are known, while comparing the situation to other nationally debated cases involving police and race. Listen here for all of this and more on The Brett Winterble Show! For more from Brett Winterble check out his YouTube channel See omnystudio.com/listener for privacy information.

If you've ever stared at a shrinking salmon season and wondered who decides this stuff—and why—this episode is for you. Jamie sits down with Gabe Miller, longtime fishing buyer and 14-year member of the Puget Sound Sport Fishing Advisory Group, to pull back the curtain on North of Falcon, the models behind your seasons, and the one 30-second habit that could actually help. You'll walk away understanding the system better than 99% of anglers out there.Episode Overview:How North of Falcon, the feds, the tribes, and Canada all have to line up before your inside seasons get setWhy the $3 billion economic value of WA sport fishing keeps getting ignoredWhat VTRs are and how filling them out honestly protects future seasonsWhy "don't tell the fish checker anything" is quietly hurting all of usHow the advisory group really works—and why those hallway relationships matterThe real bottleneck in the whole season-setting process (it's not what you'd think)Timestamps: 00:00 – Meet Gabe Miller & his PNW fishing background 00:02 – The serendipitous path to becoming a fishing buyer 00:05 – The $3 billion sport fishing economy nobody credits 00:11 – How losing steelhead opportunity pulled him into advocacy 00:12 – ESA, Hood Canal & how salmon stocks get managed 00:18 – Getting involved: joining the advisory group 00:24 – What VTRs are and why they matter 00:29 – The 30-second habit that protects your season 00:31 – Inside the Puget Sound Sport Fishing Advisory Group 00:38 – How the North of Falcon process actually works 00:41 – The real bottleneck: timing 00:44 – Gabe's epic fishing story with his sonKey Takeaways:WA sport fishing drives $3 billion, 17,000 jobs, and $275M in tax revenue—and rarely gets credit for it.Telling the fish checker "I caught nothing" feels clever but sabotages next year's season.Filling out a VTR honestly takes 30 seconds and genuinely helps the department manage seasons.The advisory group carries no formal weight, but the relationships built there move the needle.The biggest problem with season-setting isn't the science—it's the compressed last-minute timing.Getting involved beats complaining online every single time.Resources & Links:WDFW Fishing Regulations: https://wdfw.wa.gov/fishing/regulationsNorth of Falcon process info: https://wdfw.wa.gov/fishing/management/north-falconPacific Fishery Management Council: https://www.pcouncil.orgVTR Form https://str.wdfw-fish.us/home FREE Salmon Training: https://anglersunlimited.co/3-essential-luresJoin the Gold waitlist: https://anglersunlimited.co/goldWant the full structured learning experience? Join the waitlist for Anglers Unlimited Gold membership at https://anglersunlimited.co/goldAbout the Podcast: Fishing for a Reason is the Pacific Northwest saltwater fishing education podcast for new anglers and families who want to catch more salmon, halibut, lingcod, shrimp and crab in Washington waters. Hosted by Jamie & Scott Propst from Anglers Unlimited, each episode delivers practical techniques, local knowledge, and expert insights to help you get off the couch and into the fish. Perfect for relocated professionals, military families, and boaters who are just getting into fishing.

Take your personal data back with Incogni! Use code MARKDAVIS at the link below and get 60% off an annual plan: https://incogni.com/markdavisSee omnystudio.com/listener for privacy information.

I'm excited to work with Microsoft once again as the presenting sponsors of the AI Engineer World's Fair! We'll streaming live from MS Build today for a special crossover pod with our friends at No Priors and the one and only Satya Nadella. However we did not hold back with this interview - we asked all the burning questions about uptime and Copilot that we know you have in your minds. Lets go!For almost two decades, GitHub has been the home of software, where both open source and closed flow, through commits, pull requests, reviews, actions, etc.This ecosystem flourished as open-source maintainers and contributors would continue shipping code for the benefit of the community. However as coding agents began to ship mass quantities of code - growing 1400% in 2026, it marked a new era that was both extremely exciting and challenging for GitHub.While these agents help more people ship more projects, they also significantly increase the floor of how much code is shipped, how often it is shipped, how many people commit code, and basically orders of magnitude multiples in every dimension of GitHub infrastructure:Now GitHub inevitably experiences more pressure on their infrastructure which was originally designed around human developers moving at human speed. This has resulted in a very publicly notable uptime story:So it begs the question of whether current systems around code can absorb what AI produces. Can CI/CD keep up when every idea becomes a build? Can open source maintainers survive floods of AI-generated slop contributions? Can GitHub preserve the human social contract of software while becoming the operating layer for agents?Which brings us to the perfect person to answer these questions: GitHub COO Kyle Daigle. In this episode, he joins swyx to unpack what happens when AI doesn't just autocomplete code, but starts changing how companies operate, how open source works, how pull requests get reviewed, and how GitHub itself has to scale. We go deep on GitHub's internal AI workflows: micro-skills, WorkIQ, MCP, Slack, Teams, email, Copilot workflows, the new Copilot desktop app, CLI, cloud agents, and how Kyle uses agents to look backwards across company context before deciding what to do next. Kyle also reflects on GitHub's history building webhooks, APIs, Actions, npm, Dependabot, and Semmle, why the AI era is breaking GitHub in new ways, how Actions became a general-purpose compute layer, and what Copilot becomes after code completion.Full Video PodWe discuss:* Kyle's expanded role across GitHub* How AI got Kyle coding again after years in leadership* Why GitHub rolls out AI through existing workflows instead of forcing new tools* WorkIQ, MCP, Slack, Teams, email, and GitHub as company context* Why massive “mega-skills” are giving way to small, atomic micro-skills* How AI changes summarization, communications, marketing, and analyst work* Why former developers in leadership may have a unique advantage in the AI era* Kyle's “15 agents on Saturday” workflow* How Kyle built an AI-generated executive presentation for CRO/CFO teams* Why AI changes the chief of staff role without removing the human work* GitHub Actions, webhooks, arbitrary code execution, and secure agent compute* The npm acquisition, supply-chain security, 2FA, and token invalidation* Slop forks, vendoring, and whether AI agents change dependency management* What pull requests become when most PRs come from agents* Prompt requests, vouching, AI review, and trust in open source* What counts as a “developer” when AI lowers the barrier to building* GitHub Spark, low-code, and why GitHub refuses to hide the code* 14x commit growth, Actions load, databases, monorepos, and availability* Copilot's evolution from completion to CLI, desktop app, cloud agents, and SDK* Context, memory, rules, and making GitHub “act like Kyle wants it to act”* Ambient AI, OpenClaw, enterprise security, and the new operating system for agents* What swyx should ask Satya Nadella about Microsoft's AI futureKyle Daigle* LinkedIn: https://www.linkedin.com/in/kyledaigle* X: https://x.com/kdaigleTimestamps00:00:00 Introduction00:03:36 Why AI Got Kyle Coding Again00:07:04 Running GitHub with AI: WorkIQ, MCP, Slack, Teams, and Skills00:15:39 The Golden Age for Former Developers in Leadership00:17:31 15 Agents on Saturday and AI-Generated Executive Work00:20:20 How AI Changes the Chief of Staff Role00:21:45 GitHub's History: Actions, npm, Webhooks, and Open Source00:28:45 Slop Forks, Vendoring, and AI Dependency Management00:33:57 Pull Requests, Prompt Requests, and Trust in Agent-Generated Code00:41:21 GitHub Stars, 200M+ Developers, and the New AI Builder Wave00:45:15 GitHub Spark, Low-Code, and Why GitHub Still Shows the Code00:47:38 GitHub's Hardest Era: 14x Growth, Reliability, and Scale00:59:21 Actions as the Compute Layer for CI/CD and Automation01:02:04 The State and Future of GitHub Copilot01:08:24 Ambient AI, Background Agents, and the Future of the SDLC01:13:09 OpenClaw, Enterprise Security, and the New OS for Agents01:18:03 Build Announcements, WorkIQ, FoundryIQ, and Microsoft Context01:21:41 What Should swyx Ask Satya?TranscriptIntroduction: Kyle Daigle's Expanded Role at GitHub and MicrosoftSwyx [00:00:00]: We're here with Kyle Daigle, COO of GitHub. Welcome.Kyle [00:00:07]: Hey, thanks for having me.Swyx [00:00:08]: You're not just CEO of GitHub. People know you as that. You have a new role.Kyle [00:00:11]: So I have an expanded role now. I've been working at GitHub for thirteen years and doing all things developer. Joined as a developer myself. And now, I'm also responsible as the CMO of Developer for Microsoft. And so all the kind of learnings and passion for developers and how we work with them and how we communicate and how we bring our products to market, we're also bringing that expertise to the broader Microsoft ecosystem and helping every developer that uses a Microsoft product or would like to have a sort of similar experience that they've had with GitHub over the years. So it's a different role in some ways, but it's also just building on the experience that I've had at GitHub of just sort of tell the truth, be authentic, show people how to use it and then let the products speak for themselves. Now just doing that with, all of Microsoft.Swyx [00:01:09]: We'll be releasing this in conjunction with Build. You got lots of stuff planned, and we can sort of touch on that whenever it's appropriate. I think one of the interesting things is I rarely meet a COO who's also a CMO. I think you're a very outward facing and you're very confident publicly. That's rare. Do you actually view yourself as COO? What's What is your thing?From GitHub Developer to COO/CMO: Building the Platform and Operating GitHubKyle [00:01:33]: I think for me, it's been funny. The titles have always been, a— have always felt a little strange to me. I joined GitHub as a developer? I wrote so much of theSwyx [00:01:46]: Let's bring that up. You wrote the back ends?Kyle [00:01:48]: I was going through, I was going through, some old photos, when folks were talking about how things were being built or how there was a build GitHub. I built, webhooks and worked with teams building the API, built the platform layer. Anything that integrated with GitHub, up until really twenty eighteen, I built or ran the engineering teams. And that's kind of where my the beginning of my passion always was helping people build things, deliver them to, their customers. And so being a developer, building for developers was always super unique. In a— I think as my role expanded, it became my ability to talk to not just developers, but also enterprise customers or business leaders and have this translation layer. And then through all those years, GitHub has always operated pretty uniquely. Post-pandemic, working remotely was not as novel as it was when GitHub started in two thousand and eight. But all that expertise of running remote teams, doing it well, became this sort of bigger role, ultimately turning into the COO role of how do we operate GitHub in the way that GitHub's always operated after the Microsoft acquisition. And kind of so on from there. So like for me, I think the— I've, I still code. I love coding but the problem has always been, people. It's a much harder problem to both support our own employees, a harder problem to communicate to developers and enterprise buyers what we're building why it matters, ‘cause those are two very different messages. And so getting to work in the mix of COO, CMO, also just being a dev, I think is what's kept me at GitHub for so long.AI Workflows for Leadership: Commits, Retrospectives, and ContextSwyx [00:03:40]: Apparently, you have— your commits have gone up. What's this? What's going on?Kyle [00:03:45]: Rui's called me out pretty aggressively. So I think— as you can imagine, right, you can see my normal era of being a dev In the twenty thirteen, twenty fourteen era, and then moving into management, and then ultimately the COO role. I think what you see there is me, really getting back to coding thanks to AI. I— similar to, attaching problems between how to market and how to operate a business and how to code, I find, building agents and workflows that are connecting very disparate problems to be what's driving this. So that's, some of it's writing software. A lot of it is, connecting a ton of a different data sources to, help me out. But that is completely me really diving in on the AI side in trying out our tools, trying out everyone's tools, But building for me, building for the non-technical leader, though I'm technical and how we're, able to use these tools more than just the simple, call and response that I think a lot of the non-technical, your employers, you have to get— you have to use AI, and so everyone uses, ChatGPT or Copilot or Claude or whatever. To really get into, how is this going to help me out, it— I find that it's not the I need to write a blog post, I need to those simple examples. Helping people find the workflows of, “Okay, I need you to go through all the PRs today. I need you to go through everything that we've posted online. I need you to go through what we did the last three months. Go through all of my Obsidian notes for any mentions of this then go through my transcripts at work.” We use, Teams, so, using WorkIQ, go call that MCP server, grab all the transcripts, go through all the Slack, and then build me out the plan of, what this week's messaging actually was. That's something that was, impossible because for me, I find AI in a what most of this launch here is actually, less building forward. It's actually, a recursive loop backwards. I'm always looking at what had happened first. Go back through the week and tell me what we did, what worked, what didn't work? And then tell me in the next three or four days-What would you tweak based on this sort of like looking backwards and then looking ahead a little bit? I find that to be so much more valuable, especially for like non-technical, because that retrospection is actually LLMs are very good at that. Like finding all the patterns, pulling them out, and then applying that retrospection to just a couple of days or just like a short period of time. Is all a bunch of apps that I've built and launched a bunch of, internal tools. I use the new, GitHub Copilot app, the desktop app with workflows. Every time I crack open my laptop, it's running workflows for me. It's just a ton of different stuff and of course, it all ends up on, it all ends up on GitHub.Swyx [00:06:47]: Of course. That's where, that's where, stuff is hosted. Man, there's so much to ask you. I was going to leave the how do you run a company with AI thing at the end. I have to ask one— double click one thing. You said, you are looking back at the week. You're, you're understanding what happens. When you say we That's three thousand people. How?Rolling Out AI Internally: Skills, CLIs, and Company ContextKyle [00:07:09]: I think when we started rolling out AI internally beyond engineering, right? One of the things that I was really, passionate about is like we have to do this in a way where no one has to change how they work. I don't want to have to teach you a tool. I don't want to have to teach you something new. And so for us, we tried out a few tools. Most of them don't work because I got to get you on board? I got to teach you how to use it. What we've actually ended up doing is we've built like a set of skills internally. We have we each have our set of skills, and we've just been distributing even to the non-technical folks, the CLI. And then effectively, we're just giving it access to like read about everything that we're writing. So that's for us, that's usually GitHub, Teams, Email, and Slack. So Teams for, video chat, generally speaking.Swyx [00:08:03]: Teams and Slack?Kyle [00:08:04]: so we use Teams for video communication, but we don't use it for chat. W-we— GitHub for a long history, right? We're alwaysSwyx [00:08:13]: Also SlackKyle [00:08:14]: Talking about ChatOps and like everything is built into Slack. Like every command, every flow.Swyx [00:08:18]: So even though you have been acquired for I don't know, eight years nowKyle [00:08:22]: we stillSwyx [00:08:23]: You still use Slack?Kyle [00:08:23]: it's a purpose-built tool for us, and I think the reality is that moving off of it would be so bluntly expensive? Simply because all the tooling is, baked in with that paradigm. And they both have their pros and cons but they don't work the same way at all. We still use a bunch of different tools Because it's the purpose-built tools that We need. And thenSwyx [00:08:47]: Well, the same doesn't go for the rest of Microsoft, presumably.Kyle [00:08:50]: like the like various teams like operateSwyx [00:08:53]: They make their own decisionsKyle [00:08:54]: Various ways. I think it just matters what you're trying to what you're trying to do. But we do we do work across kind of every tool that we use, and then by giving everyone access to all of that context and the new WorkIQ MCP server, which is quite cool if you do live in the M365 like world. I can ask it all these backwards-facing questions, and it's incredibly important for our teams that are working remotely. There's a lot of stuff you miss when you're not in an office, and we are spread out all over the world. So most of that is looking back. And then we post, we post either auto-automatically into GitHub issues or discussions, these sorts of like findings or like our industry reports. Like what's happening this morning, today, yesterday. A little automation gets run. We'll use the app. We might use GitHub Actions like with, our agentic workflows just to go do that run, and then we push it into GitHub, and w-we keep having a conversation. So usually for us, it's about that sort of like looking back, looking forward on the non-technical side. And then of course for a lot of those folks, it's also building an app, pushing it to GitHub pages or pushing it somewhere to host it et cetera. But it's just like enabling everyone with that power of it's going to take me a week to figure this out. Instead, we're going “Okay I built a skill. Let's put it into a repo. We'll all share that skill together, and then we'll use the CLI or now the app-” “just to run it.”Micro Skills vs. Mega Skills: How GitHub Uses AI at WorkSwyx [00:10:26]: All right. I think, I think we're going straight into like the team management and productivity thing. I think a lot of people are getting various levels of LLM psychosis. How do you manage the bloat of skills? Like everyone Has their thing, and they're Like trying to promote it to the rest of their peers in their org, right? And obviously, whoever becomes a skill influencer internally becomes like an AI leader, right? Of sorts. I assume you have those.Kyle [00:10:50]: like I think we haveSwyx [00:10:52]: And I assume it's a mess a Yeah.Kyle [00:10:54]: there's like I— like I think the reality is there's two pieces. Like first is I think that we're ending the era of these like massive, beautiful, perfect skills that are just like not any of those things. ‘cause for a while, right every tweet every day is like go download the skills, the perfectly managed thing to do this entire workflow. And I think that like what we've found and what— I was just with my team, this week, and we were talking about the skill side, and we're really talking about these like incredibly micro skills that are just doing one thing for us very well Versus a skill that's going to do I said, that full report. That doesn't really exist on our side anymore. It's usually how do— like a single skill that's going to identify the most important marketing information given any MCP server. Like this is the most important thing. Less about stitch a bunch of tools together and have it produce this mega output because then weeks go by, months go by, things change, and you want to tweakSwyx [00:11:58]: It's brittleKyle [00:11:58]: Your mega skill and you're screwed? You can't do that. And so now we're really just talking about the Legos we're using and just letting the instruction book be something we're all putting together. Whereas I think a lot of AI skills for a while have been that mega instruction book style.Swyx [00:12:15]: I've, thought a lot about Postel's law. I don't know if that's a term that is, means things to folks. It's the idea that you should be liberal in what you accept and strict in what you output, right? And I think that's like a good framing principle for skills. This is my skills, obviously on GitHub. I feel like everyone should have like how like some repos In GitHub are special repos? I feel like we should sort of reify the slash skills and everyone like give it some kind of special presentation. Anyway, so, yeah, this is one of those like download Download anything, transcribe anything, and then you can string together the atomic skills that do one thing well Into like some kind of orchestration skill that calls other skills. I assume, does that match?Kyle [00:12:56]: I like I think so. I think that theSwyx [00:13:00]: Summarize anything.Kyle [00:13:01]: Like I think the- For me, summarizing something for I do communications and PR and analyst relations and marketing and customer activities, and so my summarize everything is very different for each one of those like Contexts. What ‘Cause if I'm summarizing something for an analyst, that's a very different thing than, probably how I'm going to summarize something for like a customer meeting or an engagement. So that's I think like the difference when we're talking about the like the tools I might use on Saturday or the skills I might use on a Saturday when it's just for Kyle. Yeah, those are kind of like they have an atomic actual tool underneath or maybe skill, and then Kyle cares about X. But I think when we're talking about work and enabling the the marketers, communicators there, it's the atomic, this is what good summarization is, and then this is what I care about as for marketing for communications For whatever. And that I think is like the interesting matrix problem when we go from like a developer set of concerns to all kinds of different professions, is that what that word means to me is different than it means to you is different than it means to the analyst or the salesperson, and that's where I think the matrix mess is that we're starting to like still starting to find. It's about these mega skills but they're all just slight permutations, but those permutations are really important. It's the difference between someone reading this and going “Did AI make this?” what Or “This makes total sense, and I would expect this when I'm giving a briefing to Gartner,” or like whatever else.Swyx [00:14:37]: I think the beauty of it maybe is that you don't have to be that careful about what goes in there. It doesn't have to exactly fit as long as it like roughly is contained in there. I used to complain about plugin hell, basically. Like when you have a framework and then you have a hundred things that you need to integrate, everyone does like the GitHub used to be bloated full of these things. And now we don't need them anymore ‘cause now you just use skills.Former Developers in Leadership: AI as a Creation MultiplierKyle [00:15:00]: And like I think the most magical thing is the just that like I can just also crack it open. Like Like yes, I could go like change the how the plugin is coded, or like I could go do that now with AI, but I think there's just something more magical about getting a response back and being “That's not right,” and then you just crack the skill open, you just type English words and it's different. That building block is just, I think very unique. Once I get everyone to kind of understand how to best how to best make those changes to get the most power out of them.Swyx [00:15:36]: Is there a— you have a your peer group that Of people like you. Is there a common framing for Something I'm feeling is, which is true, is that is this a golden age for former developers who are now in leadership? Because you can wield the tools, you would know the right words, you're maybe not too close to the details. Doesn't matter. But like you're more effective than someone who doesn't come from that background.Kyle [00:15:59]: I think that like the secret has always been your ability to identify patterns and solve problems, and I think that for folks that like myself that don't code day to day anymore, that has made me successful as a developer, made me successful as a COO and now CMO. And so now that I have access to get and write code, I'm now applying that sort of like pattern finding and problem solving, and I know enough still about how to then go and say, “Oh, I want to make an app, but I don't want to break into jail or create something that's not going to be able to work or to be deployed scale or whatever.” that ability to apply all that additional business knowledge and still code I think is what makes that so interesting to me. Slightly different than I think some of the other like technical leaders that became business leaders and now are going back to their apps and updating them. Good for them? But I think the more, much more interesting thing is, well, now I have this whole new set of expertise over ten plus years. Why not take that and use that as a developer with these AI tools? So I definitely think that makes me more powerful, but I think that's true for like every dev as well. Most of the dev friends I still have also have some other underlying skill and passion. There's really talented, very kind of linear computer science software devs, absolutely. I just find that the folks that came from a different career, went to school for something else, went off and did this random thing, and then became a software dev, or were a dev, did a random thing, came back. Learning that extra set of information, learning those extra skills, and now having the power of an AI where I can crank up fifteen agents on Saturday while my kids are doing lacrosse, That's like really powerful. And I think it gets me back to that feeling of like creation, and it's very hard to replicate that in most other senses? That first time you build an app and you click it and you show someone that's magical. And so being able to do that not just in code, but across all kinds of different assets that's, that's huge. We were doing we're doing our every year we do our revenue planning. We talk about okay, what is it going to look like for next year? And of course as you imagine, there's, slideshows everywhere talking about what are we going to talk about, what's the narrative, et cetera. And so as you said I'm “Okay, well, I could probably just like build something to build this and then that way I don't have to go build the whole spreadsheet or I have to pass it to my team.” So we went through this process, and I got all the information and used the skills I mentioned. I built like a little app just to make it so I could look at some of the information in a SQLite database, more easily. And I ultimately built this entire presentation without touching any of it and I was “Okay, I'm just going to present this to our CRO, the CFO, their teams,” without mentioning I'd built it with AI. I like built a skill to make it look very much not AI driven. Just not pretty.AI-Generated Presentations, Human Taste, and the Changing Chief of Staff RoleSwyx [00:19:03]: Like a design. Yeah.Kyle [00:19:03]: Not pretty. But just like very clearly not AI. Kind of like don't do anything interesting.Swyx [00:19:08]: That's, yeah, that is valuable.Kyle [00:19:08]: Just go Exactly. We did the whole thing through. It used my notes from Obsidian, it used all the context I mentioned before, the plans, and Never came up once that it was AI generated.Swyx [00:19:20]: It didn't matter.Kyle [00:19:20]: Never once. D It didn't matter. And so now I takeSwyx [00:19:23]: This is a toolKyle [00:19:23]: I can take that tool and go, “Look, I don't want you to go build slideshows.” They're just helping us share information with each other. If this thing can do it With a little bit of crafting from you and then we can look at it together, awesome. There's no value in all that extra work. I think that the ability to, make it look humanly bad and and build a little app to, manipulate the data I think is part of, that upside for devs that are now in leadership roles. Because, the thing that I feel like I said before, this that's all a people, that's all a people problem. I know if you've used a coworker or not to build a slide deck, unless you spent a bunch of time to not do it.Swyx [00:20:07]: I know, but like it was so, I think there's a certain charm to just being blatantly AI. ‘Cause I think that you're well, you're just honest about There may be mistakes here that I cannot vouch for. So how much value is there? But anyway I think, actually the real question I want to ask is, there's a— You were a chief of staff To Thomas. And in the pre-AI world, the that job would've been a chief of staff job of like Can you prep me these slides and all that? And now you do it yourself.Kyle [00:20:35]: I still, I still have a chief of staff. Because, the difference is it's sort of the discussion every time we have some sort of technology evolution is it's not that the jobs the roles don't all go away, they just change? And so yeah, I don't have someone spending all their time building out slides for me and presentations ‘cause I don't need that anymore. But now I need that person that is able to go and find all the different connections between humans in those discussions to help me find out, okay, I should be meeting with this group and this team, and they have an opportunity, and I'm going to be in San Francisco today, I'm going to be in Seattle tomorrow. Those sorts of human connection aspects are still incredibly valuable and has always been a big part of that chief of staff role. But now just like chiefs of staff are not opening up, letters to process, they're doing emails. What It's the same thing. And now they're, they're not building out as many of these presentations because they have the the ability to have a AI take it on for, and share that with me and great. Let's keep moving ‘cause it's allowing us to go faster and make better decisions more quickly.Swyx [00:21:45]: Awesome. Well, so we can dive into more sort of, Productivity insights as you go. I did want to do a little bit of a brief history of colleague and hub. Because, we started here. And then you also involved the NPM acquisition. I did, I do want to touch upon that. And then more recently, I just want to bring up to present day where we're having uptime issues Which transparently we've already Addressed publicly, but we'll, we'll discuss in the pod. Did I miss anything? Like what, any other major highlights? Obviously, it's, it's a lot of years to cover.A Brief History of GitHub: Webhooks, Actions, Acquisitions, and Platform EvolutionKyle [00:22:15]: No the I think one of one highlight was right before the acquisition closed in twenty eighteen, I got to launch the first version of ActionsSwyx [00:22:27]: OhKyle [00:22:27]: At GitHub Universe. So it was OSwyx [00:22:29]: They're that young?Kyle [00:22:30]: It was October of twenty eighteen, I think. Yeah. Yeah.Swyx [00:22:33]: Gee, Jesus.Kyle [00:22:34]: I got to I was the engineering leader on that project and got to launch that. And then, yeah, we did acquisitions of NPM you said, Semmle, Dependabot Pul Panda a whole bunch of things. That was a bigSwyx [00:22:47]: Pul Panda.Kyle [00:22:48]: Abi is doing well.Swyx [00:22:51]: DX. Holy crap.Kyle [00:22:52]: Did well on DX. I and like that was a that was the big shift, after the acquisition. I had to join the sort of business side.Swyx [00:23:00]: So I need to hit you on some of these things ‘cause you were there. Right? And how often do I get to talk to someone who was there? But yeah, Actions. Is that the number one source of security issues on GitHub?Kyle [00:23:11]: Oh, sh I think that the number one source of, security issues is probably like all, the literal code in everyone's like underlying repositories. I would say back further than that is, if you remember I had to show in this graph was this is, I'm, didn't say this before, this is ultimately webhooks.Swyx [00:23:30]: You yeah.Kyle [00:23:31]: Like circa whatever it was.Swyx [00:23:32]: It says Hookshot in there.Kyle [00:23:32]: I forget. Yeah. Yeah, Hookshot's in there. And so like back then, it says GitHub Services. Do you see, it says Hookshot FE for front end, and then it says GitHub Services. GitHub Services back in the old days, right? You we had a repository that was Ruby code, and you could write any Ruby code in there, and then we would execute that On your behalf As a service, and then that way if an if you were trying to integrate with something, it didn't we would run it for you.Swyx [00:23:57]: And of course no containers ‘causeKyle [00:23:58]: No, ‘cause it wasSwyx [00:23:59]: Well, no containersKyle [00:24:00]: Twenty fourteen. And so there was some isolation obviously, but it was mostly the separations on the server level. That's like an example as long as the very old version of Pages, which ran on its own containerization infrastructure, not on Actions.Swyx [00:24:15]: Which like all-time great product.Kyle [00:24:16]: Pages powers the internet at this point to some degree. Those were places where like clearly there were no like issues like to my knowledge. But it was those things where I'm looking at and going “Okay, well we can't be running arbitrary Ruby code,” like on everyone's behalf. Then containerizing all of that up intoUh into actions now where yeah the containerization, is r-really good. The pinning most folks aren't pinning it the like to a particularSwyx [00:24:48]: ImagesKyle [00:24:48]: Sha, et cetera like their workflows, and so that's a big that's a big place Of pain for folks if they're just doing similar to any dependency management, just V1 or newest or latest, I think. But, that journey from that day to “Okay, we're just going to run all this arbitrary code, and, it'll basically be okay,” to now, no, we have, really good containerization. We have a new, underlying, ag-agent, containerization, service. It's like we're using it under the hood. It's through Azure. They recently announced it. The Azure, Dev Compute, but it's, very fast, very fast compute to be able to, spin up your own cloud agents, or whatnot. We're using it under the hood for some parts of the new,Swyx [00:25:36]: Microsoft Dev Box?Kyle [00:25:37]: No. Dev Compute, yeah.Swyx [00:25:41]: Hmm. Not finding it just yet.Kyle [00:25:44]: Oh, it's, it's in there somewhere.Swyx [00:25:46]: All right. Well, we'll cut that out.Kyle [00:25:47]: Sorry. But with, Dev Compute, you can, run, really fast, spin up really, small VMs really quickly, so you're doing a tool callSwyx [00:25:58]: Same conceptKyle [00:25:58]: Just do it containerize exact-exactly. So we're using that so definitely moving that direction to protect us from every every piece of code that we're ultimately running.Swyx [00:26:07]: look, that grows into the full SDLC? Code hosting was just the start and and then it's grown beyond that. Let's talk about NPM may-maybe ‘cause I think that's also, a very major point in the industry. I do think, it was looking for a home. It was, kind of struggling as a business, right? I don't know, I don't know how you would characterize that whole acquisition and how itNPM, Package Security, and Keeping the Internet RunningKyle [00:26:33]: like when we were talking to the team, I think the big thing for the both of us was to find a way to keep NPM, which was basically powering the internet then and way more so now to some degree running. Keep it going keep continuing to scale. It was having scaling problems, if I recall, back at that time. They were doing some rewrites. ItSwyx [00:27:00]: that's cute compared to now.Kyle [00:27:01]: Well, that's the thing is like when I'm talking to folks now, there's there's so many more underlying uses of NPM than there were back when we had them join in with GitHub. But that was ultimately the goal. It was really okay, we used to have pages. We have, the world's code. Let's make sure that we can keep NPM running well for the world. And we put a bunch of time and investment into fixing some of the underlying backend, changes, some of which we talked about some of the manifest work, et cetera. And then now, really trying to bring the the security posture of NPM up to speed. But, it is a unique challenge in that every move that we make to make it more secure will break a lot of people. And security is paramount. And also, we take it very seriously. We're, the any time that we have a problem with GitHub or we make a change that makes us more secure but hurts, there's, a snow day for developers or a really bad fire that they have to go put out. And so we've, have changed the 2FA policies. We've changed the way the tokens work. When we find tokens that have been exposed or potentially, exposed, we invalidate them, andSwyx [00:28:22]: I love that feature in GitHub. Yeah, it's greatKyle [00:28:23]: That creates issues, but, the but that's the thing is we're trying to push the community, forward without necessarily, doing something that is going to break the contract that's been for 15 years or close to it or some amount of years on NPM.Slop Forks, Vendoring, and the Future of Open Source Supply ChainsSwyx [00:28:43]: I think the— So now we're talking about, open source and publishing. And I think there's something here with what people are calling slop forks, which, I think Malta from Vercel is doing. And, part of me thinks, well, the way to get past any vulnerabilities, we just, let's just get rid of the concept of NPM. And we only publish source code. And anytime you want to import it you have your coding agent look at it and then adapt whatever subset you're going to use into your vendor it. But, the AI vendor it. Is that realistic? I don't know. Is it— Will that solve all our security issues? I don't know.Kyle [00:29:24]: I don't think it'll solve I so Mitchell was just talking Mitchell Hashimoto Was just talking about this today, and I think that I-in some ways, it's all all things, old or new again? Yeah, absolutely vendoring everything. Like I do I do remember twenty thirteen, twenty fourteen.Swyx [00:29:42]: This is Yeah. Let's, we must return toKyle [00:29:43]: That's what is We were vendoring everything. We were having actual discussions around, or at least I remember we were “Should we take this full thing?” “Why is this so big? We only need this one file.” And so I do think there's something true there where having either taking only what you need or the dependencies just getting incredibly small over time, I think will help to some degree, but it's not going to solve the fundamental problem, I don't think, because the vulnerabilities in an agent looking at them, there's time and time again, there's a million different ways in which we can convince an agent that this thing is, secure or not and pull it in. Or we can do static code analysis or runtime testing to say whether the code works or not. That is, I think, the step that needs to continue to be, invested in. The question is just on, how much scope. Should it be this enormous project that I'm pulling down, or should it be this piece? Either most companies are running some amount of security checking on the on the packages that they're bringing in or vendoring. That I think won't change. That's like what advanced security does to some degree, Socket does some degree. Like everyone is doing a piece of that. How we each do that like especially when we're talking to enterprise customers, is just like very different. No there's no one wants one single way to do it. And I think that's always been GitHub's, unique position in the world. I talk a lot to maintainers, I talk a lot to folks about this. It's we're— we rarely start like a process and a practice and like push it onto the community. We usually wait for the sort of like RFC process socially or literally, everyone agreeing, and then we'll cement something in. Because otherwise we'reMaintainers, RFCs, Vouching, and the Social Layer of TrustSwyx [00:31:35]: That fits your role in the ecosystem, yeahKyle [00:31:36]: We're GitHub. Yeah, we don't want to shape the whole thing. We want it to be figured out. But like how do you balance that like sort of Role in the industry to keep everything as secure as is possible and make sure that you're you're not going to be compromised as a human, ‘cause that's usually how it all happens. And Not not create a process or lock us into a flow that you're not going to or like Mitchell's not going to or other open source projects aren't going to like. That's always been a tricky balance for us, and I think that's something that we haven't talked about enough is we're not going to be able to fix everything for everyone in a way that everyone is going to like. So tell, help us, tell us what is working. When Mitchell was talking about, the Upvote, the upSwyx [00:32:22]: I was going to bring up his thing. Yeah.Kyle [00:32:23]: I forget what it Yeah. When he's talking to us, I was chatting with him and talking to him about this and I put it on Twitter and we talked to, also over DM, was “We're going to keep working.” but I think the important thing is I do actually want to hear what isn't working for you. And as, be as specific and clear for your project as is possible. And to every piece of credit over the many years that we've known each other through the industry, he's always done that and I appreciate that ‘cause there are places that we need to fix up, and we hear from him, and we'll fix up just like we do all other kinds of maintainers. But that that process between making those types of improvements and being more secure and like creating, I forget what he calls it's not the proof process, not the claims process. Do what I'm talking about? He has that he his projects have a way for you to kind of like,Swyx [00:33:13]: VouchKyle [00:33:13]: Vouch. Thank you. Yeah. He has like the vouch system for saying, “Hey, you should accept my PRs.” That's beenSwyx [00:33:20]: I just built this into GitHub. I don't know.Kyle [00:33:22]: Well, see, but that's the thing is that you say that and like he and his community really likes this and then I'll go talk to other maintainers and other maintainers, globally, and they're “No, this doesn't work for me.” And that is the tension, but also the kind of beauty of GitHub, depending on which way you look at it is we want to help maintainers, so we create all these tools to let you have more control over how much you take in from AI and PRs. But you can also use this. What You can go use this project, and if it takes off and becomes the kind of mostly standard, then yeah, we probably wouldn't enforce it but we would add it in because that's the flow that we tend to do?Swyx [00:34:02]: I hear a lot of people don't know the history of the pull request. And like like that's how, that's something that GitHub standardized basically.Kyle [00:34:08]: Yeah. It was a very messy process Like beforehand, and now the we have the benefit of it being the process? And now we have to go and Figure out the next best process or what adaptations change, or what does a pull request look like when eighty percent of your PRs are just coming from your agents and not From other devs?Swyx [00:34:31]: Do you like the prompt request idea from Peter?Kyle [00:34:34]: like I think that for each like each idea I think has its merits. I'm not, I'm not avoiding saying anything good or bad, but I feel like I've seen a version of we have that we have entire Thomas' store. Take all the assets of what you've built and put that in. I think that's got great ideas. There's all these various permutations of the PR flow, but I think the reason why there's not a single answer is ultimately we're trying to codify trust. We're trying to say “Okay, if Sean reviews this I'm going to trust it because you're Sean or you're the senior dev or you're the whatever.” And right now, when we are working in a flow where an agent writes code and another agent reviews code and then Kyle goes and looks at it the trust is kind of diffuse. And most of the tools that we're talking about are talking more about verification flows. We have more assets to look at, so I can probably say whether this is a good PR or not. But that still doesn't solve, I think, the human problem of I'm looking at a PR and I want to know if I can trust it. And we're still, we still tend to use human signals for that? Mitchell approving it or Kyle approving it or whatever. And so I think that's, I think that's why most of these options haven't really solved it is because, it's a social problem ultimately. It's a it's a human problem to review it and agree. Or you fully trust the tool and you're imbuing that tool with full trust Which I think in some cases that absolutely exists.AI-Generated PRs, Trust, and the Waymo AnalogySwyx [00:36:08]: And so like in the same way that there will be a tipping point in society when we don't allow humans to drive anymore Because machines are measurably better than Than humans. I'm looking for that tipping point, right? Like Mythos is ridiculously expensive. Someday we'll have Mythos on a desktop. I don't know. Will, does that change the equation?Kyle [00:36:30]: I think it's more I took a Waymo here, and I was on my phone and not looking around at all. There are other, self-driving, vehicles that I would not trust while, staring at the road. And I think that trust is something that isSwyx [00:36:48]: Is this a Zoox thing? What is itKyle [00:36:50]: I think that is both. I think that is both. LikeSwyx [00:36:53]: There's Zoox in this robo taxi. That's it. It'sKyle [00:36:56]: Well, depending on what level Of self-driving. But, my point is sort of that I think part of that is I strongly believe that's, a mixture of verifiable proof. Like how many accidents, how much data, and so on, and the human aspect of how I feel when I'm in this car, what it tells me, et cetera. And so that's why I think some of the like Some of these some of our AI tools tend to, imbue me with more of that feeling of trust, even if the data says this is 100% accurate. I feel like it takes more time for us to go, “Should I trust this or not?” And that's in the soft sense of, startups with high agency, weekend projects, and open source. And then there's enterprises and regulated industries and everything else, and that is an even harder problem to go solve because even when it is fully verified, not only do you have to have trust from the humans on the team, you probably have to have trust from multinational,Swyx [00:37:55]: Oh my GodKyle [00:37:55]: Multi governments around the world and regulating agencies. And so that's where I feel like until we tip over to your point on the sort of like human EQ side of it. I feel okay this feels okay I've been proven enough. Then the ball will start to roll a lot faster, where we'll end up getting to the “Okay, we can trust this,” and feel good about it in the Most difficult of cases.Reputation, Sponsors, Stars, and Bot Activity on GitHubSwyx [00:38:18]: If human trust is the thing that matters, I feel like GitHub as the developer social network could maybe do more there. Like vouchers are one system But, we have star counts, and then we have Contributor rights, and that's it. And I feel like there should be more in that space. I don't know if there's any other design decisions there.Kyle [00:38:37]: I think that one of the places that we don't really expose right now in this sort of way is, some degree of like hard trust and support, which would like for me is like sponsors is a good example of that.Swyx [00:38:49]: Ah.Kyle [00:38:49]: It like costs you something. To prove that I believe in your project and I trust you To some degree or I want to support you at the very least.Swyx [00:38:56]: Solve payments for open source. Why not?Kyle [00:38:58]: I think that I think that like as we keep moving forward, right, there's more and more projects where I'm, adding more and more dollars into sponsors personally because I want to like support them, but I also like know of I've probably never met them in person, but, I know of enough of their work that I want to support them. I think the thing that I don't love about stars or commit counts or anything else is ultimately, even with all of the various, abuse and de-spamming and deduplication work that we do or anti-abuse work that we do, these are all, not active social signals. They're passive ones that are ultimately gamifiable. And you may trust me, but another open source maintainer may not. And on what heuristic should you be, trusting me? That I think, is kind of where some of our thinking is right now. What signal from me is most important to you? You— If you can define that potentially, honestly in an agentic workflow that's what we see some of these open source projects do, where you have GitHub actions, and then you have like an agentic workflow that's calling AI, and you're setting these rules. Like if Kyle has submitted and gotten accepted PRs across any given project and has a social handle tied to his account in GitHub, and that social account's older than a certain amount. Really complex measures that matter to you ‘cause most open source projects have that heuristic built into their heads, if not written down in the contributing guidelines. You could take that and then go apply that and then just say, “Oh, we're not going to accept this PR.” Building something that is, I think, malleable to everyone's needs, is a little bit better, rather than going “Hmm, this account's too young.” Because what happens? The attackers just go and go and create a multitude of accounts, and they wait Until it ages up. Needs to have a certain amount of stars. That's how star inflation happens. Need to have a certain amount of reposSwyx [00:40:46]: Oh my God. YeahKyle [00:40:47]: With PRs. They all just create repos and submit PRs to each other, and then they come in and do something nefarious. And so, it's hard. It's hard to find the measure. So I think we're, we're looking more at how can we provide you tools so you can kind of choose what's best for you. And of course, we'll give you some standards. But the trust vector, gets down to I don't know, some version of like human digital ID like everyone's been talking about. Like how do I prove that it's meSwyx [00:41:13]: Give me your eyeballsKyle [00:41:14]: On the internet. Give me your eyeballs. Exactly.Swyx [00:41:18]: The I got to keep moving on Topics, but obviously I can go all day on this stuff because, I've been involved in GitHub and open source My entire professional career. Stars. Very superficial. Everyone knows it. But I think time to one hundred thousand stars is the fastest I've ever seen. Like people just reached that in I don't know, months. And then like at the same time I don't trust it right? Like how many of these are real or bot or like whatever. I don't know how to ask this but like what can we do about it? LikeKyle [00:41:49]: JustSwyx [00:41:49]: Is stars broken? Is stars fine?Kyle [00:41:51]: I think that there's kind of two, there's like two pieces. Obviously we're constantly like trying to find ways in which like your users are producing spam, which would, I would include like be like only doing star gamification. When we find them, we pluck ‘em out and we,Swyx [00:42:08]: But it's like a Whac-A-MoleKyle [00:42:10]: It's a hundred percent like a Whac-A-MoleSwyx [00:42:11]: There's no wayKyle [00:42:11]: Now, powered by AI to be helpful. But I think more so what I'm seeing is, a lot of the like fastest time to X tends to be because we're now inviting so many more people into like software development on GitHub That like the zeitgeist is just swarming? And it'sSwyx [00:42:32]: It's not just developers anymoreKyle [00:42:33]: And it's not you and I. Like like however you want to say like what a developer is it's not just folks who have been coding for a very long time. It's folks that have maybe started coding or only joined in since the AI era. And nowSwyx [00:42:44]: what's the latest Octoverse number? I know eighty million was my lastRem- member that a number of developers on GitHubKyle [00:42:50]: Oh, we're over 200 million now.Swyx [00:42:53]: Okay. Well, so you see?Kyle [00:42:55]: Like over 200 million developers now.Swyx [00:42:56]: But it's not developers, right? It's, it's people with a GitHub account.What Counts as a Developer in the AI Era?Kyle [00:43:00]: So, so this is, this is the biggest debate that I would say, everyone loves to have at GitHub at this point. From my perspective, right, I think that there's, there's clearly a difference between, professional enterprise developer and then developers. But I think that I think that the idea that we should be I don't know, splitting hairs or segmenting developers in the early era of software development is, not worth our not worth the time. SoSwyx [00:43:29]: When you get into gatekeepingKyle [00:43:31]: 100%Swyx [00:43:31]: What is a developer?Kyle [00:43:31]: 100%. ‘Cause I wasn't a developer when I started writing code? I was going toSwyx [00:43:36]: Oh, no. I made— I cloned a thing, seven years before I learned to code. And then I and then I wrote about my learning to code journey, and people Just called me a fraud ‘cause I had a GitHub account. And I'm “Well, no, I just use GitHub, but I don't know-” “I didn't know what I was doing.”Kyle [00:43:49]: I I remember that. I remember those sets of posts, and like that's, that's b******t. So I fight very clearly on the line of, if you create code, if you have an idea and you create it into some way of, I'm, I'm going to run it and use the app right now, you may still use AI in that moment, but that's okay. At some point you're going to do the next thing. You're going to create a big— You're going to have to learn about this database. You're going to fix a bug, whatever. We're all on some same journey, and those people are also hearing about the great new agent skill package or a new CLI tool or a new whatever. And those projects are going up because you want to be a part of this moment, just like I wanted to be a part of the Ruby community when Ruby was popping off when I started becoming a developer, and now I can just click the star button. And so I think that yes, there's clearly some amount of like spamming and game gamification that we're working against, but I really think we're just seeing this whole new cohort of folks that are moving from technology to technology because they're not working on a 20-year-old software application. They're working on a side app that they built on the weekend for their friends or for their new idea or whatever. And that's how you see these enormous charts going up and to the right with With stars.Swyx [00:44:59]: I think something that's remarkable is the persistence or, that GitHub extends to those folks. Usually when I see platforms go into a new audience, they usually have to, have like a second platform with a different name that wraps the main platform. But somehow GitHub has been able to sort of persist and extend, and it's friendly and whatever? So it's, it's nice.Spark, Low-Code, and Always Showing the CodeKyle [00:45:19]: I that's partially why I think as we've tried to move into I don't know, more like low-code-y things. We so we started working on Spark as like a way to, build an app and run it. I think that the reality is that we anytime we try to, kind of put even a veneer on top of it without when we put a veneer on top of something, we still always show you the code. That's kind of like a tenant. We're never going to, hide the code from you ever, because whatSwyx [00:45:52]: Why would you?Kyle [00:45:52]: That's, yeah, that's the whole point? However, I think that what we learned with things like Spark is that really the value of Spark for most devs is, easy runtime. And you may have a runtime or a host that you're going to use for that or you just build something and run it but, the package of making that even more simple isn't really needed for folks that are trying to build software and not just trying to build, an app, which is, slightly different, a slightly different goal. So I want to get you in, I want to get you comfortable. I think the best thing for me as, someone that did not traditionally come into software dev way back, I want anyone to be able to breach that chasm and not be in the I don't know, I feel like we're, we're still in an era of, STEM. I've got a 12-year-old and an eight-year-old, and it's “We got to get ‘em into STEM,”? Over and over. And I like I do, I do the things that good parents do. I was “Oh, you want to do coding?” “Yes, I want to do coding.” Do coding classes. But now they're just not afraid of doing software. And that's, I think, the thing that's honestly kept me at GitHub for so long. Anyone should be able to go and build a thing, just like I can go change a light switch in my house. I'm not going to go into the breaker box ‘cause I'll probably kill myself? But, I can go change that light switch. Everyone should be able to go and say, “This fricking app doesn't do what I want. I want it to work like this.” And that I think, is what's kind of kept us all connected with GitHub through the years and some and during the easiest of times or in the hard times because of that opportunity of, we're the home for all developers, and we want everyone to be able to have that feeling that we've had of, had an idea, I created it and holy s**t here it is.Swyx [00:47:37]: Here it is. All right, I'm going to try to do more spicy questions.GitHub's Hardest Scaling Moment: Growth, Agents, and UptimeKyle [00:47:42]: Great.Swyx [00:47:42]: Is it an easy time now or a hard time?Kyle [00:47:45]: Oh at GitHub? It's a hard time. Like, it's a hard time and also, I was just with my team and I said, “This is also, the best and most exciting time that I think I can remember at GitHub.” BecauseSwyx [00:47:57]: Best of times, worst of times. It's never oneKyle [00:47:59]: ‘cause we've we were talking about Octoverse reports and, usually we do an Octoverse report once a year, and we look at the numbers, and we say, “Oh my goodness.” I was at Universe in October saying, “This was the fastest year of growth that we've ever had,” right? And now we're doing more in a month than we did in a year last year.Swyx [00:48:20]: You're talking about PRs.Kyle [00:48:21]: Commits.Swyx [00:48:21]: Commits, yeah.Kyle [00:48:22]: PRs. Kind of like you name it by roughly every measure that we're looking at, there's some amount of sort of growth that is much bigger, and that is breaking our system in new ways, not old ways. Like webhooks were always notoriously, unreliable over the years?Swyx [00:48:38]: Whose fault is that?Kyle [00:48:39]: not anymore mine, but for a period of time, I'm sure you could pull up a tweet that was “It was me. I'm sorry.” but, now, that got rewritten at a scale level that is still working and is not having problems today. Now what we're finding isn't just the isn't the-The simple stuff that folks are on the sometimes on Twitter or on the internet are “Hey, why is this like this?” Sure. There's absolutely silly problems that we shouldn't exist. But now we're talking about, unique, novel permission problems that happen only at a scale across all different objects or whatever, that now we have to go rewrite this underlying system. And so it's, there are problems that yeah, caught us off guard, which I think I said. Like the growth is astronomical, but also we're making such material progress in that I'm excited once we're once we've kind of like reimagined the underlying foundation layer, or pieces of it at least, what's going to be possible when it's not just all of us and all the new people that are being developers and all of their agents and all the tools like working together. Because that'll still happen in that in that GitHub tool, that GitHub community. But it's a it's a hard day anytime we can't give you what you're looking for. We have the same problem internally. We operate through github. Com. Of course, we have backups when things go down and whatnot for our own operations but we feel it too. If it's not working it's not working for us, and that's kind of like the promise of dogfooding for GitHub. It's always been true. We're using the same tool you're using. We're not using a super secret version. We and so we also need it to be great for us for our customers of course for open source. And now an exponential growth of agents, Doing it too.Swyx [00:50:32]: I wanted to load for audio listeners who maybe haven't seen your tweets, whatever. So one billion commits in twenty-five. Now it's two hundred and seventy-five million per week on pace for fourteen billion this year, if growth remains linear. Is that still the pace? I don't know. It's been aKyle [00:50:48]: it's, it's speedingSwyx [00:50:50]: Roughly.Kyle [00:50:50]: It's still speeding up.Swyx [00:50:51]: It's, it's April, so yeah.Kyle [00:50:51]: Exactly. This was in April.Swyx [00:50:53]: All right. So basically you have fourteen x growth, right? Year on year on year. And I think that's a scaling issue. I think, I'm going to like try to really steel man this thing. People have experienced fourteen x growth. They haven't had your downtime. And that's like— C-can we go dig into that? Why? Like what's the— what broke? What are we doing to fix it? Like just anything for the community to reassure them.Why GitHub Reliability Is Breaking in New WaysKyle [00:51:18]: so there's a Like I was saying, there's a couple different places that we've seen the growth issues. Some of the growth issues, which is why we're t— I was talking about pushing hard on more CPUs is in actions in particular. More tools, more agents, more PRs mean more builds, more builds mean more CPUs. And so we are expanding through not just our data center, but obviously we were talking about moving to Azure and moving to, adding an additional cloud compute because we simply need more CPUs. Not as much GPUs. We definitely need GPUs too, but now CPUs are becoming a factor.Swyx [00:51:53]: It's very CPU heavy.Kyle [00:51:54]: Underneath the hood when it comes to some of the underlying services, we've been breaking up over the years our database infrastructure, so that way we have, more cognitive separation between our the various services. The place that we continue to have pain is in, permissioning. And so right now m-many of our permissioning layers sit into a database that we like internally call MySQL One, and old Hubbers will know what I'm talking about. And so we've been pulling things out of MySQL One for many years, because like and we use we use Vitess and we use other technologies to shard and we do it as one bigSwyx [00:52:31]: Famous thing, PlanetScale was born from this andKyle [00:52:32]: A hundred percent. Sam Old Hubber and friend. And so finding these opportunities to like break this out and then do that globally. The other thing that I think is interesting and both a unique opportunity and tricky is we also run everything I just talked about in a black box container with GitHub Enterprise Server for people that work on-prem. So we take everything I just said, and we also do it on-prem, and we also do all of that and we do it in a data residence setup for customers that need to have their data in a single location. Each of these has the unique characteristic around how we're sort of storing that data in MySQL or in a permissioning setup. That's where some of these outages have oc-occurred, where you're seeing it more like across the board rather than just like the one pieceSwyx [00:53:17]: Filling the databaseKyle [00:53:17]: Isn't quite working. Exactly. And so part of it is that. I think there's been some other places where agents are much more or more projects appear to be moving towards monorepo versus we were going the other direction for many years in the industry. Repos were smaller, but there were more of them, and now we're seeing the opposite. Repos are bigger, and there's, not fewer of them per se ‘cause there's new growth, but, we're just seeing many more big repos. Big repos, big monorepos have always had, a unique performance problem. Because each one, is slightly different if, particularly if the underlying blobs are incredibly big Inside the repos. And so we've done a ton of work that you pro— like most people haven't probably experienced, unless you're in this case of the monorepo. But that Git, infrastructure layer improvement does help the overall, system because, many of the improvements that make monorepos work better make all repo infrastructure work better. And so, I could kind of keep going down the line where it's another thing where we're moving out of, We're changing how we do j I'll just say job queuing for lack of a better, explanation changing the underlying technologies there.Swyx [00:54:32]: I spent two years being a job queuing guy, so.Kyle [00:54:34]: And so it's kind of a little bit of a little bit of piece by piece, and it's mostly because as we were— as it was built, we built everything in a way that assumed, I guess in some ways that the size of the pipe of work was going to remain the same. There's just going to be more people coming through each of those pipes. But instead now in places whereA git push was, generally a certain size for example, is now, no longer true.Swyx [00:55:03]: Oh, yeah.Kyle [00:55:03]: OrSwyx [00:55:05]: I push a thousandKyle [00:55:06]: On the average. 100%Swyx [00:55:06]: A thousand line commits like dailyKyle [00:55:07]: Same thing with PRs. Like PRs same thing. And like we've talked about optimizing that and making changes where, and there were technology choices that did not work there? And it got slow, and it didn't It was not fast. It did not do what the users wanted. And so we've been reeling that all out and going “Okay, that's just not right. Let's stop putting good money after bad and do it the do it the right way or the right way now.” So there's It's a it's a lot of things, not quite when I've experienced scale at GitHub historically, it's almost always two options that we've used. We go vertical scaling, particularly with databases, right? And we go horizontal scaling. Oh, we just have more people using this service. Great. We're going to add more servers, and we rack them in our data center, or we use it in a cloud. And now we're sort of in a like diagonal, where like vertical doesn't really work anymore. Horizontal isn't work either because we're all We all have some CPU or GPU constraints in the world now, and now we have to go in and like crack open services that have been running for 10 or 15 years and go, “Okay, the rules of this service have legitimately changed, and now we have to rewrite them.” None of this is an excuse. This is like we're We have to do the work. We have to make it better.Swyx [00:56:22]: actually as an infra guy, I'm “This is like one of the most fascinating scaling challenges I've ever seen.”Kyle [00:56:26]: That's that's, that's the thing that's the thing that it's hard for Like when we weren't talking about it publicly, and I was like I came out, and I was “Hey, I just want to explain what's going on.” Part of it comes from a very old GitHub ethos, which is it's our it's our uptime. It's down. W What I know you're a developer, so you're, you're inclined to want to understand more what's going on. But at the same time us going “Hey, this service didn't, perform the way we expected, and now we have to go change it,” we weren't We're not trying to hide anything from you i

This week, I'm joined by Clancy Denton, co-host of the podcast The Loud Quiet, for a conversation about motherhood, transitional stages, and leaning into the "loud quiet" of life after grown children leave home.Clancy shares her own experience and how she and her husband started mentoring an entire community of empty nesters, both in-person and over the airwaves.Clancy talks about their book, as well, which would make an excellent gift for Father's Day, college move-in day, Mother's Day, or graduation!Connect with Clancy:The Loud Quiet WebsiteFind the BookListen to The Loud Quiet Podcast____________________Want to be a guest on The Motherhood Experience? Send Val Kleppen a message on PodMatch, here: https://www.podmatch.com/hostdetailpreview/1758742098661627c9cc46f40

Take your personal data back with Incogni! Use code MARKDAVIS at the link below and get 60% off an annual plan: https://incogni.com/markdavisSee omnystudio.com/listener for privacy information.

The Enlightened Family Business Podcast Ep. 161: AI Is Coming Fast — What Family Businesses Should Do Now with Jack Potvin   In this episode of the Enlightened Family Business Podcast, host Chris Yonker is joined by AI product builder Jack Potvin for a fast-moving, practical conversation about artificial intelligence and what privately held and family businesses need to do — right now — to stay competitive. Jack built his AI foundation working on one of the world's first computer vision models for sports before the rise of large language models, and now dedicates his work to helping independent businesses harness this technology before the window closes. Chris and Jack make the case for why family businesses — historically outperformers — are at a critical inflection point: large corporations are pouring tens of billions into AI adoption, and the playing field will not stay level for those who wait. Together they explore what AI actually is, the two core value drivers of efficiency and capability expansion, where to start when your team is at zero, why governance policies matter more than most owners realize, which specific tools deliver immediate value, and what AI genuinely cannot replace — deep domain expertise, broken process diagnosis, and nuanced human judgment. They also dive into real-world case studies from a beverage manufacturer and an insurance agency that have completely transformed their operations through AI, and close with a grounded, practical framework for family business leaders ready to take their first meaningful steps. Episode Chapters ·       0:00   Welcome and Framing the Opportunity ·       1:00   Meet Jack Potvin — From Sports AI to Family Business Adoption ·       4:06   Why Family Businesses Are at a Competitive Inflection Point ·       7:28   What Is AI? Defining LLMs, Efficiency, and Capability Expansion ·       13:18  Should Your Company Have an AI Policy? ·       16:04  Addressing the Fear: Job Loss, Data Privacy, and the Real Risks ·       22:10  Where to Start: Daily Drivers, Existing Tools, and Filling the Gap ·       26:54  Best AI Tools Right Now: Read AI, Whisper Flow, Notion, Gamma ·       30:29  Operational Efficiency, Analytics, and Business Development ·       31:11  Two Real-World Case Studies: Beverage Manufacturer and Insurance Agency ·       35:23  What AI Is Great At — and Where Humans Must Lead ·       40:40  AI for Business Development, Outbound, and CRM Automation ·       45:59  Strategic Planning, Knowledge Bases, and Building Your Company's AI Brain ·       50:20  Q&A and Closing Resources   Websites ·       businessautomation.com ·       chrisyonker.com   About Jack Potvin Jack Ryan Potvin is an entrepreneur and AI strategist focused on helping businesses adopt practical artificial intelligence solutions that improve efficiency, decision-making, and competitive positioning. As the founder of Business Automation, Jack works with companies to integrate AI into everyday business operations — from automating workflows and improving internal knowledge systems to enhancing marketing, sales, and strategic insight. Jack specializes in translating rapidly evolving AI capabilities into practical tools that business leaders can implement today, without requiring large technical teams or massive technology investments. He is particularly passionate about helping family-owned and employee-owned companies adopt AI in ways that strengthen their long-term competitiveness while preserving the leadership values and culture that make these businesses successful.

Do you feel mentally exhausted, overwhelmed, or constantly behind no matter how hard you try?In this Mindset Coaching episode of Coaching In Session, Michael Rearden breaks down the growing problem of mental overload and how stress, distractions, and lack of structure can slowly pull your life out of alignment.Many people try temporary fixes to escape stress, but those quick solutions often create bigger long-term problems. Michael explains how awareness, focus, prioritization, and intentional structure can help you regain control, reduce overwhelm, and create lasting mental clarity.This episode explores how to reverse engineer stress, manage priorities effectively, and focus your energy on what truly matters so you can stop surviving chaos and start living with purpose.If you've been feeling mentally drained, emotionally overloaded, or stuck in constant pressure, this episode will help you reset your mindset and reclaim your focus.Mental clarity begins when you take back control of your attention, energy, and priorities.WHAT YOU'LL LEARN FROM THIS EPISODE• Why mental overload happens• How stress builds without awareness• The dangers of temporary fixes• Why focus and energy matter• How to reverse engineer your stress• The importance of structure and organization• How prioritization reduces overwhelm• How to regain mental clarity and controlKEY TAKEAWAYS✅ Mental overload often happens gradually✅ Temporary fixes create long-term problems✅ Awareness is the first step toward change✅ Structure helps reduce stress and chaos✅ Prioritizing correctly improves mental clarity✅ Focused energy creates better outcomes✅ Intentional action helps regain control✅ Filling your life with meaningful priorities creates fulfillment

Tune in here to this Monday's edition of the Brett Winterble Show! Chris Kroc is filling in for Brett Winterble as he kicks off the program by talking about the controversial arrest video involving a Shelby, North Carolina police officer now charged with assault after footage surfaced showing him punching a woman during an altercation. Kroc argues that the public and media are rushing to judgment based on only 42 seconds of video, without knowing what happened before or after the confrontation. He emphasizes that the woman had previously pleaded guilty to resisting an officer in a separate case involving the same officer and points to what he sees as a broader pattern of hostility toward law enforcement. Kroc also discusses police use-of-force standards, defending officers’ authority to escalate force when physically confronted. While acknowledging the video looks troubling, he questions whether the officer deserves immediate condemnation, firing, or prosecution before all the facts and context surrounding the incident are fully known. Listen here for all of this and more on The Brett Winterble Show! For more from Brett Winterble check out his YouTube channel See omnystudio.com/listener for privacy information.

Send us Fan MailYou can grind from 7 a.m. to 9 p.m., stack your calendar with meetings, and still end the day with zero dollars to show for it. That's why I'm drawing a sharp line between being busy and actually building, because this difference quietly destroys businesses that look “productive” on the surface. Busyness is motion. Building is momentum.I talk through the mindset trap that makes busyness feel safe and rewarding, even when it doesn't move the needle. Then I give you a practical filter you can use immediately: ask better questions about every commitment. Is this activity creating leverage, freeing time, or producing an asset that compounds? Or is it just keeping you occupied? This is also where your zone of genius matters. When you spend your best hours on low-value tasks and unnecessary meetings, you give away the very work only you can do.To make it stick, I share a visual I love from my trip to the Amazon rainforest in Peru. When you're under the trees, you can't see far, so you keep pushing forward and hope you're headed somewhere good. The real advantage is lifting your head up, looking around, and evaluating direction so you can make a small adjustment before you waste weeks. Your takeaway is simple: identify one building task you'll implement this week, then track the change it creates.If this hits home, subscribe for more short, practical business advice, share this with a friend who's drowning in meetings, and leave a review so more builders can find the show. What's the one building task you're choosing this week? To Reach Jordan:Email: Jordan@Edwards.Consulting Youtube:https://www.youtube.com/channel/UC9ejFXH1_BjdnxG4J8u93ZwFacebook: https://www.facebook.com/jordan.edwards.7503Instagram: https://www.instagram.com/jordanfedwards/Linkedin: https://www.linkedin.com/in/jordanedwards5/Hope you find value in this. If so please provide a 5-star and drop a review.Complimentary Edwards Consulting Session: https://calendly.com/jordan-edwardsconsulting/30min 

Bud Elliott sits down with Eric Henry of 247Sports to preview Texas' 2026 season. - Texas Team Site: https://247sports.com/college/texas/ - (00:00) Intro  (1:01) Defense under Will Muschamp (3:46) Offense in year 2 with Arch Manning (6:05) Arch Manning recovering from foot injury (7:11) WR Cam Coleman (9:28) Running Backs (10:51) Offensive Line (12:31) Under-the-radar player on offense (14:32) Filling loss of Anthony Hill Jr (15:48) EDGE Colin Simmons (17:40) Biggest question marks on defense (18:44) Cornerbacks (20:02) Schedule breakdown Cover 3 is available on Apple Podcasts, Spotify and wherever else you listen to podcasts.  Visit ⁠the betting arena on CBSSports.com⁠ for all the latest in ⁠sportsbook reviews⁠ and ⁠sportsbook promos⁠ for ⁠betting on college football⁠. Watch Cover 3 on YouTube: ⁠https://www.youtube.com/cover3⁠ Follow our hosts on Twitter: ⁠@Chip_Patterson⁠, ⁠@TomFornelli⁠, ⁠@DannyKanell⁠, ⁠@BudElliott3⁠ For more college football coverage from CBS Sports, visit ⁠https://www.cbssports.com/college-football/⁠ To hear more from the CBS Sports Podcast Network, visit ⁠https://www.cbssports.com/podcasts/

What's going on with the Strait of Hormuz? Filling in for Glenn, Pat Gray and Jeff Fisher discuss the latest updates over in Iran and what's happening with ship access to the Strait of Hormuz. Jeffy gives his Fat Five headlines, including exploding oven doors, Elon Musk potentially becoming the world's first trillionaire, and the fastest-growing cities in the country. The guys react to a recent CNN clip featuring Rep. Byron Donalds (R-Fla.) standing strong in defense of President Trump's dealings with Iran. The guys also react to the ladies of "The View" losing their minds over Trump making prescription drugs cheaper for Americans. "The Late Show with Stephen Colbert" ended this week, and Colbert continues to blame Trump for its cancellation. Another illegal immigrant driving a truck has now been accused of killing two Americans in a crash. The guys react to the latest clip from Texas Senate candidate James Talarico (D), who continues to confuse people by claiming he's a Christian but saying un-Christian things. Pat Gray goes through recent archaeological findings that prove the Bible's accuracy.  Learn more about your ad choices. Visit megaphone.fm/adchoices

As tensions with Iran continue to worsen, President Trump needs to make a decision soon. Filling in for Glenn, Pat Gray and Jeff Fisher discuss how Iran appears to be doing whatever it wants to do, regardless of the ceasefire agreement. Jeffy gives his Fat Five headlines, including layoffs at Facebook as Meta pivots toward AI and baby chickens hatching from a 3D-printed artificial egg. Pat and Jeffy react to the latest political ad by Los Angeles mayoral candidate Spencer Pratt, which parodies "The Lego Movie's" “Everything Is Awesome” song. The guys also react to CNBC's interview with Amazon founder Jeff Bezos on wealth in America and the current tax system. Sen. Ted Cruz (R-Texas) bodied Sen. Mazie Hirono (D-Hawaii) during a voting rights and redistricting hearing. Jeffy gives the top ten reputable companies, according to consumers. The guys fact-check a claim from a recent Frisco town hall meeting, where a man claimed he is the descendant of both Sam Houston and Davy Crockett.  Learn more about your ad choices. Visit megaphone.fm/adchoices

Rep. Thomas Massie (R-Ky.) officially lost his primary and will be leaving Congress after over a decade. Was President Trump's criticism of him part of the reason he's getting ousted? Filling in for Glenn, Pat and Jeffy discuss Massie's loss and debate what may have been the reason. The guys also discuss Trump's endorsement of Texas Senate candidate Attorney General Ken Paxton (R) over sitting Sen. John Cornyn. Jeffy gives his Fat Five headlines of the day, including a food hack to save you money, the viewership of Netflix's Ronda Rousey-Gina Carano fight, and the headliners for the halftime show at the World Cup. Pat analyzes Trump's latest efforts to make medication more affordable for more Americans. Pat and Jeffy critique the Left's habit of freaking out over every little thing Trump does, including being against the construction of a new White House ballroom. The guys react to a video released by Secretary of State Marco Rubio that focuses on the important role that faith has played in America's success. The second batch of UFO files is set to be released. What should we expect to find? The guys take calls from listeners about their views on the potential for alien life and whether it conflicts with their faith. Learn more about your ad choices. Visit megaphone.fm/adchoices