Podcasts about contributors

On the Monday episode of the North Shore Drive podcast, presented by FanDuel and Edgar Snyder & Associates, the Post-Gazette's Adam Bittner and Christopher Carter wrap up Steelers OTAs with a focus on the 2026 NFL draft class. How should this group be viewed with Germie Bernard still the only player expected to contribute quickly? Can Max Iheanachor, Drew Allar, Gennings Dunker and/or Daylen Everette accelerate their respective timelines and make impacts the way names like Joey Porter Jr., Broderick Jones, Zach Frazier, Keeanu Benton, Mason McCormick and Derrick Harmon have in recent years under GM Omar Khan? And are we sleeping on the potential of specialist players like Kaden Wetjen, Eli Heidenreich and Riley Nowakowski to stand out within their roles? Our duo tackles those questions and more as new coach Mike McCarthy's first team starts to take shape around established stars like DK Metcalf, Aaron Rodgers, T.J. Watt and Cam Heyward. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

In this episode, Dr. Farina King and guest co-host Dr. Kiara Vigil talk with the editors and contributors of the new book Lyda Conley and the Fight to Preserve Huron Indian Cemetery, which tells the story of a trailblazing Wyandot lawyer and activist who defended the burial grounds of her family and ancestors in Kansas City. This work focuses on the life and legacy of Eliza ("Lyda") Burton Conley, a Wyandot woman whose fight to protect her people's burial ground continues to shape how we think about federal Indian law, sovereignty, and memory in the United States. Lyda is widely recognized as the first Indigenous woman to argue a case before the U.S. Supreme Court, but as our guests remind us, she never stood alone. Her sisters Ida and Helena, and generations of Wyandot women, shared in the labor of defending their cemetery and their community, both in the courts and on the ground.Our guests—historian and educator Dr. Tai Edwards, Wyandot Nation of Kansas member and editor Stephanie Bennett, researcher and writer Samantha (Sam) Gill, and Wyandotte playwright Madeline (Maddie) Easley—discuss how their collaborative book brings together biography, archival documents, oral histories, and theater. They talk about reading newspapers and treaties against the grain, navigating access to scattered archives, and recording oral histories with living relatives and tribal leaders. The book offers not just a narrative of Lyda's life but a source reader and teaching tool that invites more research and classroom conversation.Together, the editors and contributors frame Lyda's story as a refusal to accept erasure—what they call “fighting for memory, fighting for honor.” Their work reminds us why this story matters now, in a moment when Indigenous lands, ancestors, and rights are still contested, and when community-based scholarship and art can help chart more just futures.The University Press of Kansas launched the Lyda Conley Series on Trailblazing Indigenous Futures several years ago named in honor of Lyda Conley. Kiara Vigil, Tai Edwards, and Farina King serve as co-editors of the series, and they have hoped for a book to acknowledge and highlight the life and work of Lyda Conley. Finally, that hope is realized with this new book.Resources:Order the book Lyda Conley and the Fight to Preserve Huron Indian Cemetery Samantha Gill, blog piece titled, “Lyda Conley: Women's History Everyone Should Know” (March 2026) “As a thank you for reading the UPK blog, enjoy 20% off this new book when you order directly from the University Press of Kansas website. Use code: 24BLOG2026 at checkout. Because protecting scholarship and empowering informed citizens starts with readers like you. Good through the end of 2026.”Madeline Easley websiteNative Circles Episode 20: The Lyda Conley Series on Trailblazing Indigenous Futures

2 - Why are New York fans the absolute worst? 210 - Man of the People Graham Platner graduated from the most prestigious school in America. But he's not rich! 215 - Dom's Money Melody! 225 - The Washington Post is price gouging? Is surveillance pricing real? Your calls. 235 - Joe Concha, Author and Fox News contributor, is here today. Are Knicks fans attacking him too? What does Joe think of the scene after Knicks games? Is there a late addition to Joe's “worst people” book? Who's worse, Yoko Ono or Meghan Markle? Will Trump go back and forth with Stephen A. Smith? What is Joe's take on Graham Platner? 250 - The Lightning Round!

(Jun 11, 2026) Assemblyman Robert Smullen is running as a Republican to represent the North Country in Congress; a husband and wife in Keeseville are serving up free dinners at a local church; and we hear from some of our most frequent contributors to NCPR's Photo of the Day.

In this episode, a conversation with two contributors to Griffith Review 92. Griffith Review is a quarterly literary journal, with every edition exploring a different theme, bringing together long-form critical and analytical non-fiction and creative writing from the finest emerging and established writers from Australia and overseas. In his piece ‘Encircling the flames,' Raeden Richardson reflects upon his time at Yale-NUS College, Singapore, and in her own work, ‘The limits of authenticity,' Mindy Gill asks the reader to contemplate, just as she does, on literary culture, inclusion and the commodification of identity. The two writers were joined in conversation by Darby Jones, a writer and editorial assistant at Griffith Review, to discuss the themes of these essays more broadly. Enjoyed what you heard? Click here to purchase the book: https://www.readings.com.au/product/9781923213197/griffith-review-92--2026--9781923213197

The following article of the AI Cloud & Data industry is: 'Patient Centricity: Who Should Own Your Medical Data?' by Alejandro Ruiz Bernal, Health Consultant, Independent Contributor. 

We cover a lot of ground this week, with an avalanche of T20 Blast games to get through, the return of the County Championship; Essex's winning streak, Somerset's woes, clouds hanging over Lancashire and Surrey rubbing Middlesex's noses in it! PLUS we ask if the in-form Dan Lawrence should have been given the nod over Jordan Cox for the Second Test at The Oval. Contributors this week:Dan HaggarOliver HawkeHarry EverettAlex GatesCraig TranterBarrie FunnellDavid Wright.

Liz shares her perspective on Graham Plattner's victory in the Maine primary and examines the field of other potential challengers. She and Mark discuss the changing public opinion in the United States toward Israel, especially as tensions with Iran escalate. They also consider whether the anticipated SpaceX IPO, expected on Friday, could significantly impact the stock market.See omnystudio.com/listener for privacy information.

In this Dialogue episode of The Synopsis we discuss whether we are in an AI bubble and various factors investor should consider.  YouTube Video Links: Why This Isn't an AI Bubble (Yet)  Five Minute Money Newsletter Free Sign Up   ~*~ You can also get a free trial to AlphaSense to read 200k+ expert calls through this link.  ~*~ For full access to all of our updates and in-depth research reports become a Speedwell Member here. Please reach out to info@speedwellresearch.com if you need help getting us to become an approved research vendor in order to expense it. -*-*-*-*-*-*-*-*-*-*-*-*-*-*- Show Notes (0:00)  — Financial vs Technology Bubbles (5:45)  — Are AI Model Companies in a Bubble? (11:04)  — Arguments For Why We Are in an AI Bubble (25:51)  — How Reflexivity Affects Outcomes (35:33)  — Software Bull Case (38:12)  — AI Bubble Argument Summary (41:29)  — AI Bubble Counterarguments (46:36)  — What You Can Do as an Investor -*-*-*-*-*-*-*-*-*-*-*-*-*-*- For full access to all of our updates and in-depth research reports, become a Speedwell Member here. Please reach out to info@speedwellresearch.com if you need help getting us to become an approved research vendor in order to expense it. *-*-*- Follow Us: Twitter: @Speedwell_LLC Threads: @speedwell_research Email us at info@speedwellresearch.com for any questions, comments, or feedback. -*-*-*-*-*-*-*-*-*-*- Disclaimer Nothing in this podcast is investment advice nor should be construed as such. Contributors to the podcast may own securities discussed. Furthermore, accounts contributors advise on may also have positions in companies discussed. This may change without notice. Please see Speedwell's and Drew Cohen Money's full disclaimers here:  https://speedwellresearch.com/disclaimer/ https://www.drewcohenmoney.com/disclaimers 

Brian Geltzeiler, Host on Sirius XM NBA Radio & Contributor at NBA TV, joins Sid to recap last night's Game 3 of the NBA Finals between the Knicks & San Antonio Spurs, and if Game 4 tomorrow night is a "must win" for New York after losing Game 3. Learn more about your ad choices. Visit megaphone.fm/adchoices

The following article of the Health industry is: 'The Wellness Paradox: When Good Intentions Create Unfair Outcomes' by Erick Diaz, Independent Contributor, Independent Contributor.

The following article of the Sustainability industry is: 'Mexico's Next Logistics Crisis: Energy and Water' by Paola Nuñez, Supply Chain Director, Independent Contributor. 

Buster compares the Braves & Dodgers, gives us an update on Drake Baldwin and says Walt Weiss will have to eventually decide if Ha-Seong Kim is his shortstop. See omnystudio.com/listener for privacy information.

Buster compares the Braves & Dodgers, gives us an update on Drake Baldwin and says Walt Weiss will have to eventually decide if Ha-Seong Kim is his shortstop. See omnystudio.com/listener for privacy information.

She weighs in on whether Steve Hilton stands a real chance in the governor's race. Meanwhile, Karen Bass is ahead of Steven Pratt for Mayor of Los Angeles. Liz questions what Karen Bass has actually done for California and is skeptical about the Democratic Party shifting back to the center.See omnystudio.com/listener for privacy information.

Brian Geltzeiler, Host on Sirius XM NBA Radio & Contributor at NBA TV, joins Sid to talk about how the Knicks have transformed their game to become so dominant ahead of the start of the NBA Finals tonight in San Antonio against the Spurs. Learn more about your ad choices. Visit megaphone.fm/adchoices

Show Notes: Mathooshan Manoharan talks about his time at Umbrex role and upcoming business school plans. Mathooshan shares his initial lack of business background and management skills when he joined Umbrex. Mathooshan explains his coffee chat strategy, including reaching out to professionals on LinkedIn and refining his message approach through A/B testing. The Coffee Chats Initiative Mathooshan details his experience with coffee chats, starting with over 150 and now over 400. He describes the types of coffee chats he had, including both virtual and in-person meetings. Mathooshan explains how he initially reached out to people on LinkedIn and refined his message to increase response rates. He talks about the importance of initiative and how anyone can replicate Mathooshan's approach. Learning from Coffee Chats Mathooshan shares that he didn't initially document his coffee chats but started after a conversation with Will. He created a spreadsheet to track response rates, positions, and sources of contacts. Mathooshan mentions the importance of follow-up calls and how he leveraged initial contacts to make more introductions. He discusses the value of documenting and learning from these interactions. The First Lesson Mathooshan outlines his first lesson: the importance of creating a project tracker to avoid forgetting tasks. He describes how he developed a system using checklists, notifications, and alerts in their CRM.  Will shares his own experience of learning the same lesson in the Navy. Mathooshan emphasizes the need for a structured approach to manage tasks effectively. Prioritization and Focus Mathooshan discusses the second lesson: the importance of prioritization and focus blocking. He explains how he initially struggled with shiny object syndrome and the need to prioritize tasks. Mathooshan describes how he started blocking time in his calendar for specific tasks and aligning priorities. They discuss the importance of setting clear expectations and managing workload effectively. Managing Upwards Mathooshan shares the third lesson: the importance of managing upwards and being pleasantly persistent. He explains how he learned to follow up effectively and make it easy for Will to respond. Mathooshan discusses the concept of "unless otherwise directed" (UOD) and how it helped him take initiative. Will and Mathooshan emphasize the importance of making it easy for managers to approve or correct tasks. Learning from Mistakes Mathooshan introduces the fourth lesson: the importance of learning from mistakes. He explains how he started a lessons learned sheet to document mistakes and their context. Mathooshan describes the root cause analysis he implemented to address the root causes of mistakes. Will and Mathooshan discuss the importance of systemic changes to prevent recurring mistakes. Team Management Mathooshan transitions to lessons learned in team management. He shares his initial overconfidence in managing a team and the challenges he faced. Mathooshan explains the importance of providing clarity, checkpoints, and systems for his team. Will and Mathooshan discuss the need for effective communication and support in team management. Trusting the Team Mathooshan introduces the fifth lesson: the importance of trust but verify in team management. He shares an example of a project where he trusted his team too much and the consequences. Mathooshan emphasizes the need for regular check-ins and spot checks to ensure tasks are on track. The conversation turns to the balance between trusting the team and maintaining oversight. Empowering the Team Mathooshan shares the sixth lesson: the importance of empowering the team. He explains how he initially had an individual contributor mindset and the need to change it. Mathooshan discusses the importance of explaining the "why" behind tasks and providing guidance. Will and Mathooshan emphasize the long-term benefits of empowering the team through training and support. Timestamps:  02:54: Effective Coffee Chat Techniques  05:24: Documenting and Learning from Coffee Chats  07:53: Lessons in Self-Management  10:32: Prioritization and Focus Blocking  13:11: Managing Upwards and Being Pleasantly Persistent  15:46: Never Waste a Good Mistake  18:38: Transitioning to Team Management  21:27: Trust but Verify  23:49: Empowering the Team  Links: Linkedin: https://www.linkedin.com/in/mathooshan-manoharan/ Substack: https://mathooshan.substack.com/ This episode on Umbrex: https://umbrex.com/unleashed/episode-648-mathooshan-manoharan-from-individual-contributor-to-manager-lessons-learned-at-umbrex/ Unleashed is produced by Umbrex, which has a mission of connecting independent management consultants with one another, creating opportunities for members to meet, build relationships, and share lessons learned. Learn more at www.umbrex.com. *AI generated timestamps and show notes.  

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

RF-69 INARA GEORGE AUDREY DAGGETT LEONARD NIMOY STEVE MEHALLO MICHAEL MURPHY VICKIE BRAUN KEVIN HODGE BUDDY MORROW AND HIS ORCHESTRA SHARK JAY ALLEGRETTI REMMY AND JULIA KAREN CHANCE OF STARDUST VINTAGE EMPORIUM MARTIN DENNY MILK SURFACE OTTO VON STROHEIM GEORGE CATES COMBUSTIBLE EDISON MILT RASKIN KOOP NELSON RIDDLE PAUL ROU HOYT CURTIN JOHN BARRY TERRY CALLIER THE KELPS NEAL HEFTI LES BAXTER KID OK from SACRAMENTO • the heart of california and around the world GENUINE MODERN RADIO - – — RADíO FLoMM related derTung post: flomm.us/googie (coming soon!) dial the FL0MM AN5WERing MACHINE +1 (916) 741 2394 RADíO FLoMM is produced by STEVE MEHALLO and MILK SURFACE RADíO FLoMM is licensed under a CREATIVE COMMONS ATTRIBUTION 4.0 international license • however • recordings of CONTRIBUTORS or GUESTS of RADíO FLoMM are still protected under international copyright law All episodes can be downloaded for your convenience RADíO FLoMM contains works featured for REVIEW • OPINION/CRITIQUE and/or ARTISTIC TRANSFORMATION and will contain ADULT CONTENT •• NUDITY WAT IST FLOMM?? FLOMM is an educatiónal art movement + créative collectiv ••• www.flomm.org + we are @flommus on most social media we are all FLOMMISTS you can be too

Topics covered in this episode: CVE-2026-48710: A Maintainer's Perspective daily-stars-explorer Markdown to pdf with pandoc and typst postman2pytest Extras Joke Watch on YouTube About the show Brian #1: CVE-2026-48710: A Maintainer's Perspective Marcelo Trylesinski suggested by Lee Luocks Short version: users of Starlette: upgrade to Starlette 1.0.1 security professionals: we can't treat open source projects like corporations This top link is a Starlette security advisory with the title Missing Host header validation poisons request.url.path, bypassing path-based security checks The CVE apparently caused some negative press targeting starlette. However, “the vulnerability came from the application pattern and the deployment, never from something Starlette intended.” A quote from an OSTIF article: “This bug is a classic “responsibility gap” where if this maintainer didn't patch, thousands of exposed projects would have to individually secure their projects. In doing this work, they've voluntarily taken on the responsibility to protect the ecosystem from long-term systemic harm. As with all open source projects, they owed us nothing and could have left this to be everyone else's problem and took the extraordinary steps of helping the ecosystem.” Both X40 D-Sec and Ars Technica expected immediate fixes and responses from Starlette. That's not good. We can do better. Michael #2: daily-stars-explorer Explore the full history of any GitHub repository.

This weekend Buster said the NL East & NL West divisions are over! Does he stand on that? Acuna's getting hot The Braves bullpen Skubal's trade value - future Brave? Labor issues? See omnystudio.com/listener for privacy information.

This weekend Buster said the NL East & NL West divisions are over! Does he stand on that? Acuna's getting hot The Braves bullpen Skubal's trade value - future Brave? Labor issues? See omnystudio.com/listener for privacy information.

Recorded live on April 30, 2026AMA & Hangout with Contributors (May 2026) | Yaron Brook Show#TrumpIRS #FreeMarkets #Capitalism #Objectivism #PoliticalPhilosophy #HealthcarePolicy #EconomicFreedom #CulturalDecline #FreeSpeech #RationalThinkingThe Yaron Brook Show is Sponsored by -- The Ayn Rand Institute (https://www.aynrand.org/starthere)-- Energy Talking Points, featuring AlexAI, by Alex Epstein (https://alexepstein.substack.com/)-- Express VPN (https://www.expressvpn.com/yaron)-- Hendershott Wealth Management (https://www.youtube.com/watch?v=X4lfC...) https://hendershottwealth.com/ybs/-- Michael Williams & The Defenders of Capitalism Project (https://www.DefendersOfCapitalism.com)Join this channel to get access to perks: / @yaronbrook Like what you hear? Like, share, and subscribe to stay updated on new videos and help promote the Yaron Brook Show: https://bit.ly/3ztPxTxSupport the Show and become a sponsor: / yaronbrookshow or https://yaronbrookshow.com/ or / yaronbrookshow Or make a one-time donation: https://bit.ly/2RZOyJJContinue the discussion by following Yaron on Twitter (https://bit.ly/3iMGl6z) and Facebook (https://bit.ly/3vvWDDC )Want to learn more about Ayn Rand and Objectivism? Visit the Ayn Rand Institute: https://bit.ly/35qoEC3Become a supporter of this podcast: https://www.spreaker.com/podcast/yaron-brook-show--3276901/support.Yaron is the executive chairman of the Ayn Rand Institute and a world class speaker. He is the coauthor of the national best-seller Free Market Revolution: How Ayn Rand's Ideas Can End Big Government, Equal is Unfair: America's Misguided Fight Against Income Inequality and In Pursuit of Wealth: The Moral Case for Finance. He speaks around the world on a variety of topics including the morality of capitalism, Ayn Rand and her philosophy, finance and economics, and the value of inequality.

In hour 3, Mark is joined by Mack Bradley, a local space writer and the author of “The Space to Lead”. They discuss the Blue Origin rocket explosion in Cape Canaveral, NASA's timeline to get back to the moon and more. He's later joined by Tim Sommer, a Music Journalist, Former Record Executive and a Contributor to The Rock and Roll Globe. They discuss Paul McCartney, The Rolling Stones and more. They wrap up the show with the Audio Cut of the Day.

In this segment, Mark is joined by Tim Sommer, a Music Journalist, Former Record Executive and a Contributor to The Rock and Roll Globe. They discuss Paul McCartney, The Rolling Stones and more.

In hour 1 of The Mark Reardon Show, Mark is joined by the Reardon Roundtable which is made up by Missouri State Representative Steve Butz and Political Consultant Jean Evans. They discuss and debate multiple topics including the Iran conflict, if the potential end of the Missouri Income Tax would be beneficial for citizens, James Talarico and more. In hour 2, Sue hosts, "Sue's News" where she discusses the latest trending entertainment news, this day in history, the random fact of the day and more. Mark is then joined by Paul Hall, with Common Guy's Film Reviews. They discuss the latest trending movies and shows to watch including "Pressure", "The Breadwinner" and more. He's later joined by KSDK Sports Director Frank Cusumano. He previews the upcoming Cardinals vs Cubs series, the latest roster moves for the Cards and more. In hour 3, Mark is joined by Mack Bradley, a local space writer and the author of “The Space to Lead”. They discuss the Blue Origin rocket explosion in Cape Canaveral, NASA's timeline to get back to the moon and more. He's later joined by Tim Sommer, a Music Journalist, Former Record Executive and a Contributor to The Rock and Roll Globe. They discuss Paul McCartney, The Rolling Stones and more. They wrap up the show with the Audio Cut of the Day.

In this hour of VSiN By The Books, Dave Ross and Jensen Lewis break down Thunder at Spurs game 6 and preview their Western Conference Finals MVP picks, also they give out the rest of their best bets for the day. Quentin Mills, with The Insiders of College Baseball Central and Contributor of The Diamond Report joins the show to talk some MLB with the guys. Later, Chris Meaney, Writer/Editor at NHL.com joins to talk some NHL playoffs with the guys. Get instant access to expert picks, public betting splits data, and pro betting tools when you join VSiN pro. You can take 17% off an annual subscription when you use promo code: POD26. Click Here to get started Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

The Rod and Greg Show Daily Rundown – Wednesday, May 27, 20264:20 pm: Jake Dreyfous, Managing Director of Grow the Flow, joins the program for a conversation about the group's concerns about data centers and the public meetings they are holding to discuss those concerns.4:38 pm: M.D. Kittle, Senior Elections Correspondent for The Federalist, joins the show to discuss his piece about how conservatives are driving RINOs out of the Senate.6:05 pm: Ward Clark, Contributor to RedState, joins the program to discuss his story about how the province of Alberta is considering becoming an independent nation and seceding from Canada.6:20 pm: Kevin McCullough, a nationally syndicated host and podcaster, joins the show to discuss his piece for Townhall in which he states President Trump has until the 4th of July to convince Americans of victory in Iran or he will face the consequences during the November midterms.6:38 pm: Todd Akins, Executive Director of the Oregon Hunters Association, joins Rod and Greg to discuss a radical voter initiative that would ban hunting, fishing and trapping in Oregon.  The signature verification process is the last hurdle before the initiative goes on the ballot.

Jay Town , Former US Attorney and Newsmax Contributor join to talk about the DOJ going after UCLA for creating 'antisemitic atmosphere.' See omnystudio.com/listener for privacy information.

From the Ha-Seong Kim struggles to Matt Olson's success in Fenway, Buster is in Boston and we talk about our first place Braves, Tarik Skubal, Paul Skenes, the streaky Cubs, and much more. See omnystudio.com/listener for privacy information.

From the Ha-Seong Kim struggles to Matt Olson's success in Fenway, Buster is in Boston and we talk about our first place Braves, Tarik Skubal, Paul Skenes, the streaky Cubs, and much more. See omnystudio.com/listener for privacy information.

What does it take for a single idea to travel from a research lab in New Haven to war zones in Uganda, refugee camps in Malaysia, and clinics across 30 countries and six continents? In this episode, we sit down with Dr. Myrna Weissman, one of the most consequential figures in modern psychiatry, to find out.Dr. Weissman co-developed Interpersonal Psychotherapy (IPT) alongside her late husband, Dr. Gerald Klerman, on a simple premise: that human suffering is deeply tied to human connection. Grief. Conflict. Loneliness. Life upended. These are not niche clinical categories, but rather a universal language of distress. And IPT was built to respond to it.In this conversation, Dr. Weissman reflects on five decades of research, the pandemic-era project that became a sweeping global volume (now available free via open access), and what it means to build something that outlives its origins. *This episode briefly mentions suicide.(Re-post: This is one of our most beloved episodes, brought back by popular demand. If you've heard it before, we hope it moves you just as much the second time.)What Is Interpersonal Therapy (IPT) and Why Does It Work?IPT links the emergence of psychiatric symptoms to what is happening in a person's current life. It focuses on four core problem areas:1. Grief — the loss of a loved one2. Disputes — conflict with someone important to you3. Transitions — life changes, even positive ones, that disrupt relationships4. Loneliness/Isolation — chronic or newly developed lack of attachmentThese four areas have proven to resonate across vastly different cultures because they reflect fundamental aspects of the human condition. Dr. Weissman emphasizes that IPT is not the only evidence-based psychotherapy — it is “one tool in the toolbox, not a religion.”IPT for AdolescentsAdolescence is a prime time for IPT's problem areas, especially disputes, transitions, and loneliness. Key takeaways for parents:• Try to understand the specific stressors behind an adolescent's symptoms rather than reacting to global, dramatic statements.• Always be alert to the possibility of suicidal ideation.• Communication barriers between teens and parents are common; a trusted third party (grandparent, therapist, family friend) can sometimes serve as a valuable bridge.The New Book: IPT Around the WorldThis book is now available open access for readers everywhere!The COVID-19 pandemic gave Dr. Weissman the unexpected opportunity to connect with IPT practitioners worldwide. What began as a routine update to the standard IPT manual grew into a sweeping collaborative volume covering more than 30 countries across Africa, Asia, Europe, and the Americas. Contributors were asked: What are you doing? What works? What doesn't? What adaptations did you need to make?Notable chapters include:• Uganda — IPT was introduced around 2003 amid civil war and a mental health crisis. A landmark clinical trial published in JAMA confirmed its effectiveness. Sean Mabry, a former WHO worker, went on to treat hundreds of thousands of people using IPT, even by telephone during the pandemic, and has now established a low-cost program in New Jersey.• China — After government engagement and training by Columbia experts, IPT became what practitioners called a “rapidly growing practice,” with books, training programs, and internet-based delivery.• Malaysia — IPT has been applied with refugees, using the “transitions” framework to help people process displacement and profound loss.• Africa (Ethiopia, Kenya, Mozambique, Senegal, Zambia, Uganda) — Adaptations have been made for cultural context, including how disputes are communicated and resolved within different family and community structures.• Japan and Hong Kong — Initial resistance to psychotherapy has given way to growing acceptance and translated materials.• United States special populations — Chapters cover Alaska Natives, people who are incarcerated, sexual and gender minorities, pre-adolescents, adolescents, and older adults.Cultural AdaptationsDr. Weissman shares a vivid example from Uganda: women in marital disputes are often encouraged not to confront their husbands directly, but to work through an elder who mediates. The underlying IPT principle, that the dispute is driving the symptoms, remains intact; only the implementation changes.Resources Mentioned• International Society of Interpersonal Psychotherapy (ISIPT) — volunteer-run, affordable membership, biannual international conference (10th meeting held in the UK, March 2024)• Dr. Weissman's new book on IPT across international sites — published Open Access, freely available to practitioners and researchers worldwide• Oxford University Press — publisher of the standard IPT manualAbout the GuestDr. Myrna Weissman is the Diana Goldman Kemper Family Professor of Epidemiology and Psychiatry at Columbia University's Vagelos College of Physicians and Surgeons and Mailman School of Public Health, and Chief of the Division of Translational Epidemiology at the New York State Psychiatric Institute. Alongside her late husband, Dr. Gerald Klerman, she co-developed Interpersonal Psychotherapy (IPT), now backed by over 140 clinical trials, translated into numerous languages, and recommended by the World Health Organization.

In this Dialogue episode of The Synopsis, we discuss S&P 500 valuations and concentration, and provide short thoughts on Constellation Software, Intuit, Sea Limited, and Mercado Libre.  YouTube Video Links: S&P 500 Concentration  Five Minute Money Newsletter Free Sign Up   ~*~ You can also get a free trial to AlphaSense to read 200k+ expert calls through this link.  ~*~ For full access to all of our updates and in-depth research reports become a Speedwell Member here. Please reach out to info@speedwellresearch.com if you need help getting us to become an approved research vendor in order to expense it. -*-*-*-*-*-*-*-*-*-*-*-*-*-*- Show Notes (0:00)  — S&P 500 Concentration a Risk? (20:40)  — Adobe Report Tease (23:18)  — Intuit Earnings Review (36:12)  — CSU Earnings and AGM (44:34)  — Why AI is a Beneficiary for Axon (49:17)  — Mercado Libre Earnings Takeaways and Risks (56:38)  — Sea Limited Earnings Takeaways and Risks -*-*-*-*-*-*-*-*-*-*-*-*-*-*- For full access to all of our updates and in-depth research reports, become a Speedwell Member here. Please reach out to info@speedwellresearch.com if you need help getting us to become an approved research vendor in order to expense it. *-*-*- Follow Us: Twitter: @Speedwell_LLC Threads: @speedwell_research Email us at info@speedwellresearch.com for any questions, comments, or feedback. -*-*-*-*-*-*-*-*-*-*- Disclaimer Nothing in this podcast is investment advice nor should be construed as such. Contributors to the podcast may own securities discussed. Furthermore, accounts contributors advise on may also have positions in companies discussed. This may change without notice. Please see Speedwell's and Drew Cohen Money's full disclaimers here:  https://speedwellresearch.com/disclaimer/ https://www.drewcohenmoney.com/disclaimers 

“Australia Wide” brings you stories and perspectives from across the country. This week from Adelaide, new contributor Leo Kubota reports on growing concerns over a mouse plague affecting farming communities north of the city, along with the latest developments surrounding the algal bloom impacting South Australia. - 国内各地の話題や情報をお伝えするコーナー『オーストラリアワイド』。今週はアデレードから、新しいコントリビューターの久保田怜央さんが、アデレード北部の農業地帯で警戒が強まるネズミの大量発生や、州内で続く藻類ブルームの最新状況などについてリポートします。SBSの日本語放送は火木金の午後１時からSBS3で生放送！火木土の夜10時からはおやすみ前にSBS1で再放送が聞けます。SBS日本語放送ポッドキャストから過去のストーリーを聞くこともできます。無料でダウンロードできるSBS Audio Appもどうぞ。SBS 日本語放送のFacebookとInstagramもお忘れなく。

Subscribe to Boy Green's daily New York Jets-centric YouTube channel here! Follow Boy Green for daily New York Jets updates on X/Twitter! Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Dr. Jacob Teitelbaum, an Integrative Medicine physician, researcher, and best-selling author specializing in chronic fatigue syndrome, details “adrenal fatigue,” contrasting Endocrine Society guidelines focused on overt adrenal failure with his view that the adrenals can be functionally exhausted and may be missed by standard testing and “normal ranges.” They discuss adrenal roles in stress response, blood sugar regulation, blood pressure, immunity, and symptoms suggesting low adrenal function (irritability when hungry, sugar cravings, fatigue, recurrent infections, lightheadedness/brain fog, mood shifts). Contributors include high sugar intake, chronic stress, dehydration, and salt restriction, with modern media fear/divisiveness cited as a major stressor; hypothalamic dysfunction and circadian rhythm disruption may cause “tired but wired” insomnia. They cover options such as licorice (not DGL), dietary and lifestyle changes, Adrenaplex, adaptogens (ashwagandha standards, HRG80 red ginseng study), phosphatidylserine for high nighttime cortisol, cautious low-dose hydrocortisone thresholds, and DHEA/pregnenolone considerations, plus resources at endfatigue.com.

Special guest Gordo from the podcast Play Tessie joins Mark Corbett and Mat Germain for an in-depth look at the current state of the Boston Red Sox. The crew breaks down Boston's elite pitching, offensive struggles, leadership concerns, player development, trade deadline possibilities, and how the Red Sox compare to the Rays model of success. Red Sox Pitching is Carrying the Team Boston's starting rotation and bullpen have been among the best in the American League during May.  Sonny Gray's dominant outing sparks discussion about the strength of the staff.  Gordo explains how the pitching staff consistently gives the Red Sox opportunities to win games. Offensive Problems Continue The Red Sox remain one of the weakest offensive teams in baseball despite strong pitching and defense.  Trevor Story, Jarren Duran, and Caleb Durbin are discussed as major offensive disappointments.  Gordo notes that even league average run production would make Boston one of baseball's top teams. Life After Rafael Devers and Alex Bregman Discussion on the impact of losing star players and veteran leadership.  Pressure has shifted onto younger players who may not yet be ready to carry the offense.  Roman Anthony's development becomes a major focal point for the franchise moving forward. Christian Campbell and the Youth Movement Debate over Christian Campbell's future position and timeline to return to the majors.  The group discusses whether Campbell should move back to the infield.  Concerns are raised about rushing top prospects before they are fully ready. Comparing the Rays and Red Sox Development Systems Mat explains how the Rays build organizational identity from the Florida Complex League all the way to the majors.  Gordo discusses Boston's analytics-heavy developmental philosophy and recent coaching changes.  The conversation explores whether the Red Sox lack a unified organizational identity. Leadership and Clubhouse Identity Alex Cora's firing and Chad Tracy's promotion are discussed in detail.  The hosts examine whether Boston lacks veteran leadership and emotional anchors in the clubhouse.  Comparisons are made to successful Rays teams built around accountability and defense-first baseball. Ownership and Spending Questions The crew debates whether Red Sox ownership still has the same urgency to win.  Comparisons are made between Boston's current payroll strategy and previous championship seasons.  Fenway Sports Group's expanding business interests become part of the discussion. Brutal Upcoming Schedule The Red Sox face one of the toughest remaining schedules in baseball.  Matchups against the Braves, Yankees, Rays, Blue Jays, Mariners, Dodgers, and others could define the season. Trade Deadline Speculation Gordo breaks down possible trade chips including Sonny Gray, Aroldis Chapman, and Garrett Whitlock.  Mat discusses why the Rays could potentially pursue Chapman at the deadline.  The group debates whether Boston should buy, sell, or retool for next season. What Gordo is Watching the Rest of the Season Roman Anthony's health and development remain the biggest storyline for Boston.  Gordo explains why Anthony could still become the centerpiece of the franchise. Featured Guest Gordo from the Play Tessie podcast  Contributor to Baseball Isn't Boring Follow Gordo on X: @BOSSportsGordo Remember to like and subscribe to BaseballBiz On Deck. You may also find BaseballBiz on Deck, on YouTube at iHeart Apple, Spotify, Amazon Music, and at baseball biz on deck dot com. Also you can find Mat at M-A-T-G-E-R-M-A-I-N dot B Sky social. That's Mat at M-A-T-G-E-R-M-A-I-N dot B, Sky social or Mark at baseballbizondeck at gmail.com and BaseballBiz On Deck with Facebook social 

What does it take to move from individual contributor to C-Suite and from the public to the private sector? This conversation reveals the hidden mistakes that keep smart people stuck and the mindset leaps required to succeed. In this powerful episode, Dr. Mira Brancu sits down with forensic psychiatrist and CMO, Dr. Mehul Mankad, to explore the real journey from being a high-performing technical expert to becoming an effective executive leader. It dives deep into the mindset shifts required to move from simply doing the work to leading others, including how to handle responsibility, prioritize what truly matters, and influence decisions at a higher level. You'll also learn the stark differences between working in structured environments and stepping into fast-paced startup roles where there's no safety net and accountability is entirely on you. More importantly, this discussion highlights why continuous learning and adaptability matter far more than collecting degrees, and how understanding people, systems, and decision-making can redefine your career path. Whether you're aiming for leadership, considering a career shift, or feeling stuck despite working hard, this episode offers insights that can completely change how you approach growth and success.Ready to stop over-doing and start leading? Subscribe to The Hard Skills for weekly strategies on clinical and corporate high performance.Referenced Episodes and Links:The Science and Future of Great Coaching, with BetterUp's Chief Coaching Officer, Dr. Woodward: https://youtu.be/3X3xs_B6L4M?si=bhzJVgSF2sJx8Xt6How to Build a Career That Actually Serves Your Life, with Dr. Sharon Hull: http://youtube.com/watch?v=Wdfa3axn0TI https://www.linkedin.com/in/drmankad/ https://podcasts.apple.com/us/podcast/psychiatry-and-law-podcast/id1352806975https://www.novumhealth.com/ IF YOU ENJOYED THIS EPISODE, CAN I ASK A FAVOR?We do not receive any funding or sponsorship for this podcast. If you learned something and feel others could also benefit, please leave a positive review. Every review helps amplify our work and visibility. This is especially helpful for small women-owned boot-strapped businesses. Simply go to the bottom of the Apple Podcast page to enter a review. Thank you!Subscribe to my free newsletter at: mailchi.mp/2079c04f4d44/subscribeWork with me one-on-one: calendly.com/mira-brancu/30-minute-initial-consultationConnect with me on LinkedIn: www.linkedin.com/in/MiraBrancuLearn more about my services: www.gotowerscope.comGet practical workplace politics tips from my books: gotowerscope.com/booksAdd this podcast to your feed: www.listennotes.com/podcasts/the-hard-skills-dr-mira-brancu-m0QzwsFiBGE/

Plan for Ronald Acuna, Matt Olson possible injury, National League Cy Young front runners, Trade deadline buyers and sellers, and the Phillies turn aroundSee omnystudio.com/listener for privacy information.

Plan for Ronald Acuna, Matt Olson possible injury, National League Cy Young front runners, Trade deadline buyers and sellers, and the Phillies turn aroundSee omnystudio.com/listener for privacy information.

With so much happening in the world, we are very excited to be joined by “Queen of the War Room” Ashley Etienne!She previously served as an advisor to Presidents Barack Obama and Joe Biden, and later as Communications Director for Vice President Kamala Harris and Speaker Nancy Pelosi. Join us as we discuss the U.S./Iran conflict, nationwide redistricting battles, government transparency, and what may be next for the Democratic Party.

Liz thinks Trump may have convinced Xi to get Iran to open the Strait of Hormuz, since Iran is such a close ally of China. But she says there was no official agreement signed. She also pointed out that China didn't expect so many big-name CEOs (especially from tech) would show up with Trump, and she thinks Trump might have to get tough on Iran again to keep his word. On top of that, China is struggling with oil supply and new business.See omnystudio.com/listener for privacy information.

MAKING OF THE JBS, FEATURING GORDON CHANG, JIM HOLMES, PETER HUESSY, STEVE YATES, 5-12-26SEPTEMBER 1932.This collection of transcripts examines the shifting geopolitical landscape in Asia, specifically focusing on Indonesia's strategic pivot away from neutrality. Experts discuss how Jakarta is strengthening ties with the United States to counter China's aggressive maritime claims near the Strait of Malacca. The dialogue transitions to the complexities of nuclear proliferation, highlighting concerns regarding China's lack of transparency and its support for unstable regimes like Iran. Additional segments analyze the high-stakes diplomacy between Donald Trump and Xi Jinping, noting the absence of traditional formal documentation in their communications. Contributors evaluate how economic dependenciesand competition for technological dominance in AI and space exploration define the current adversarial relationship. Ultimately, the sources portray a region increasingly defined by military exercises and the delicate balancing of global trade interests.

Bobby Cox, Ha-Seong Kim's return, Spencer Strider's masterpiece in LA, the Mets last hurrah, Tarik Skubal's unique surgery, and a Framber Valdez story you won't believe. See omnystudio.com/listener for privacy information.

Stuart Newsome is joined by Lindsey Nelson, Gretchen Manica, Jeremie Gluckman, and Viveka Jagadeesan for a practical discussion about the subtle but important ways AI is changing everyday work, how that shift mirrors the same staffing and efficiency pressures healthcare organizations face, and what revenue cycle leaders should consider as they adopt AI without losing sight of governance, context, and outcomes. That framing is consistent with the brainstorm's emphasis on the “ordinary user” becoming more of a contributor, the need for human-in-the-loop oversight, and the importance of tying the conversation back to real RCM pressures rather than generic AI hype. Find all of our network podcasts on your favorite podcast platforms and be sure to subscribe and like us. Learn more at www.healthcarenowradio.com/listen

Activist/Influencer Samantha Ettus joins Sid to discuss the races for Mayor and Governor in her home state of California. Learn more about your ad choices. Visit megaphone.fm/adchoices

They talk about how Spirit Airlines might've been saved if the JetBlue merger had gone through, and Liz doesn't hold back on her frustration with Mayor Mamdani; she says he's not doing his homework, especially on the rent freeze affecting thousands of New Yorkers. Tensions are still sky-high in the Strait of Hormuz as the war between the US and Iran drags on. Word is Iran's missile stockpile has only grown since fighting started back in February.

They talk about how Spirit Airlines might've been saved if the JetBlue merger had gone through, and Liz doesn't hold back on her frustration with Mayor Mamdani; she says he's not doing his homework, especially on the rent freeze affecting thousands of New Yorkers. Tensions are still sky-high in the Strait of Hormuz as the war between the US and Iran drags on. Word is Iran's missile stockpile has only grown since fighting started back in February.See omnystudio.com/listener for privacy information.

The California primary is less than a month away. The top two candidates, regardless of party, move on to the general election in November. Right now, the race is still wide open, but republican Steve Hilton has been consistently at or near the top of the polls … in what is a crowded field of mostly democrats Hilton, who was a senior advisor to UK Prime Minister David Cameron and a former FOX News host and Contributor, spoke with us on the FOX News Rundown about his campaign and his chances of becoming the first Republican governor of California since Arnold Schwarzenegger won a special election in 2003. He also talks about the issues he's focused on, including the recovery effort following last year's fires in Southern California. We often have to cut interviews short during the week, but we thought you'd like to hear the entire interview. Today on the FOX News Rundown Extra, we share our full interview with Steve Hilton. Learn more about your ad choices. Visit podcastchoices.com/adchoices