Podcasts about Rui

No episódio de hoje: descobrimos o segredo para o Rui fazer tudo o que lhe dizem (dica: envolve uma ressaca). Analisamos a obsessão dele com portas fechadas, a resposta da Red Bull à nossa dm marota e o drama do rapaz que oferece YSL a colega de trabalho trabalho. O que é que Rui faria, essa é a grande questão. Conseguimos ver esta situação sem pensar em ciúmes? Mais algumas coisas desta semana: temos um ninho de vespas que gostávamos bastante de dizimar e uma caixa de pão que dá para por três carcaças. Melhor, dá para por a quantidade de biagamas que o Rui compraAPOIOSPonto verde

Antes de mais pedimos desculpa por todas as vezes que dissemos canoa ou ganso. Quem dominar a linguagem de Rui vai entender. Esta semana vamos encarar o Bate Pé como uma conversa de amigos, tá? Ta! Deitamos tudo cá para fora no que toca a opiniões sobre os outros e admitimos algumas coisas que fazemos. Tipo o Rui que deu o resto da água do padel ao seu filho ou a Mafalda que estou obcecada com o Haaaland!! Esperemos que gostem do episódio e aproveitamos para agradecer a todos os que vieram ter conosco no Alive dizer para fazer podcast até aos 90 anos. Estamos a trabalhar para issoAPOIOSActivobank

Finding hope in season of loss  Att finna hopp genom sorgens årstid  Rui de Sousa Psalm 46:1 /Psaltaren 46:2  Ps 23:4  Jes 43:2  Lamentations 3:21-23  Klagovisorna 3:21-23   Joh 11:35  1 Thes 4:13 

Kawhi is still a Clipper! Wagler didn't get sped up in his debut! Rui got signed on a good contract! A lot has happened in Clippers-world, Clips n Dip talk the newest additions SL debuts, Rui's fit, and the never ending Kawhi saga…plus DIPS.

Anthony and Harrison react to Rui heading to the Clippers and how that means they have to pray the Lakers sign Jonathan Kuminga. They discuss some details from ESPN's reporting on the LeBron-Lakers split, then dive into the chat for a Q&A.

Yesterday was Shohei Ohtani's birthday. Former Lakers Rui Hachimura signed a 2 year with the LA Clippers. How come the Lakers couldnt make a deal with Rui? Rui showed signs that he wanted to stay in LA. Beto Duran comes in to hangout with the guys ahead of Destination for LA Sports. SHOP Talk Learn more about your ad choices. Visit podcastchoices.com/adchoices

Anthony has a couple more thoughts on Rui and Kuminga as that debate continues. He also noted a fun rumor over the weekend about Bronny that he thinks will help the Lakers fill their pantry. Then, he dives into a Q&A with the live audience.

Mais um episódio e desta vez Rui regressa à base. Ambos com muitas dúvidas. Falam sobre sobre a palavra “mor”, a regularidade com que se rega algumas plantas e o calor. Rui descobre que Mafalda anda a oferecer roupas que não goste que Rui use sem ele saber. Pelo meio falam sobre a série do momento - difícil de ver até ao fim, as crianças à venda na Vinted e perguntas incómodas no Mundial. Por fim, abordam o facto de o Rui estar em negação da idade e dos insultos que a Madalena Abecasis recebeu só por ter feito uma operação. XoXoApoiosActivoBank

As we await the Lakers' efforts to land a starting power forward, Anthony runs through this roster against last year's. He then debates Rui vs. Kuminga and explains why the debate is going on internally for the Lakers. He then dives into an incredibly active live chat after spending some time laughing at the Celtics.

Send us Fan MailA brand-new Japanese boy group is getting more than hype, they're getting receipts. STARGLOW has fans flooding our request form, and once we sat down with their tracks, we understood why: powerful vocals, clean production, and a real sense of range for a group that's still under a year into their journey.We talk through where STARGLOW comes from: the audition show The Last Piece and the BMSG world built by Sky-Hi. Then we introduce the five members (Adam, Kanon, Goichi, Rui, and Taiki) and dig into the songs that define their early era. “Moonchaser” pulls you in with a smooth hook and a vocal blend that feels instantly credible. “Love Myself '26” brings bright, playful self-confidence, while “Green Light” turns the same empowerment into something heavier and more driven. And when “Star Wish” hits with guitar-led pop, we both catch that unmistakable 90s boy band nostalgia without it feeling like a throwback gimmick.The big debate is “USOTSUKI” (possibly read as “liar): why does a song that sounds so upbeat carry a title that dark? We also get into “Good Boys Anthem,” including the surprising writing credits for Taiki and Goichi, plus what the translated lyrics suggest about standing your ground without losing your heart. We wrap with what's next, including their July 22 release, live DVD and Blu-ray, and the upcoming single “Driving My Life.”If you're curious about STARGLOW, hit play, subscribe, share this with a friend, and leave us a five-star review, then tell us your take: what do you think “USOTSUKI” is really saying?STARGLOW Instagram X YouTube officialMoonchaser  USOTSUKI  Love Myself'26  Green Light  Star Wish Good Boys AnthemSupport the showPlease help Music Elixir by rating, reviewing, and sharing the episode. We appreciate your support!Follow us on:TwitterInstagramBlueskyIf have questions, comments, or requests click on our form:Music Elixir FormDJ Panic Blog:OK ASIA

Shannon Sharpe, Chad “Ochocinco” Johnson and Iso Joe Johnson react to the Grizzlies struggling to find trade partner for Ja, Nets and Spurs eyeing Rui and Big3 Weekend 2 recap Subscribe to Nightcap presented by PrizePicks so you don’t miss out on any new drops! Download the PrizePicks app today and use code SHANNON to get $50 in lineups after you play your first $5 lineup! Visit https://prizepicks.onelink.me/LME0/NI... 1:11:35 - Memphis Grizzlies struggling to find a trade parter for Ja Morant1:28:25 - Nets and Spurs showing interest in Rui1:33:20 - Week 2 of the Big3 1:49:05 - Viral video of Angel Reese giving (Timestamps may vary based on advertisements.) #ClubSee omnystudio.com/listener for privacy information.

Note: this post is about PauseAI, not PauseAI US, which is a distinct entity with a different leadership team and approach. This post was written by Matilda da Rui and Maxime Fournes, with significant contributions from Benjamin Schmidt (PauseAI Germany co-lead). Executive Summary The existential AI safety community needs to take building a civic and social movement seriously as a core intervention. We believe this is a high-value, badly neglected approach to reducing catastrophic/x-risks from AI because it may significantly enhance the likelihood of governance efforts succeeding at keeping humanity safe. As far as we can tell, only one organisation is building this infrastructure across continents: PauseAI. This post lays out our reasoning and our track record, and makes the case that funding this work is one of the highest value-for-money contributions available to anyone looking to reduce AI risk. Why don't we already have a pause or strong controls on frontier AI? Multiple advocacy groups are communicating clear and convincing arguments for AI existential risk, and policy experts are putting forward comprehensive proposals. We need more of this work, but this work alone will not be enough, because one link is missing: what policymakers hear doesn't align with [...] ---Outline:(00:32) Executive Summary(06:16) Introduction(08:54) I. Our theory of change(08:58) Prologue(11:07) 1. The shape of the problem as we see it(14:27) 2. Necessary conditions for reaching a pause(17:24) II. Our role towards a global treaty and in the AI safety ecosystem(17:31) 1. Our niche within the ecosystem(21:35) 2. Policymakers need strong enough incentives to act(25:43) 3. The path to a treaty(31:36) 4. How we can grow fast without breaking(39:08) 5. Failure modes(40:10) III. Our path so far and where we're headed(40:40) 1. Bootstrap phase (2023-2025)(45:01) 2. New leadership, professionalisation and federation[... 6 more sections]--- First published: June 26th, 2026 Source: https://www.lesswrong.com/posts/aoqhszdEWqcFWbnda/existential-ai-safety-needs-an-effective-social-movement --- Narrated by TYPE III AUDIO. ---Images from the article:Apple Podcasts and Spotify do not show images in the episode description. Try Pocket Casts, or another podcast app.

Neste programa, Renato Cardoso deu continuidade, com mais detalhes, ao testemunho de Cássia e Rui, um casal de 60 e 64 anos, que depois de experiências frustradas decidiram não se relacionar mais até conhecerem a Terapia do Amor e o aplicativo Quero Te Conhecer. Segundo eles, ambos passaram por um processo de cura emocional, perdão e mudança de postura, deixando de lado mágoas e aprendendo a confiar nos princípios cristãos para avida amorosa.O casal conta que começou a se conhecer pelo aplicativo com acompanhamento de pastores, mantendo conversas por mensagens durante cerca de três meses. Depois, passaram a se comunicar pelo WhatsApp, ainda de forma cuidadosa, sem videochamadas, trocando apenas fotos, áudios e mensagens. Para eles, essa forma mais lenta de aproximação ajudou a construir um relacionamento baseado na razão e não apenas na emoção.O primeiro encontroO primeiro encontro presencial aconteceu em agosto de 2024, em São Paulo, após dificuldades de viagem causadas por enchentes no sul do país. O momento foi marcado por identificação imediata, e dali em diante o relacionamento avançou com acompanhamento espiritual e seguindo orientações da Terapia do Amor. O casal relata que manteve princípios como respeito e limites durante o namoro, entendendo o relacionamento como um propósito religioso.Depois de cerca de um ano e quatro meses de namoro, eles ficaram noivos em novembro de 2024 e se casaram em maio do ano passado. Hoje, Cássia e Rui afirmam viver um casamento feliz, baseado na fé, na superação pessoal e no aprendizado contínuo.Bem-vindos à Escola do Amor Responde, confrontando os mitos e a desinformação nos relacionamentos. Onde casais e solteiros aprendem o Amor Inteligente. Renato e Cristiane Cardoso, apresentadores da Escola do Amor, na Record TV, e autores de Casamento Blindado e Namoro Blindado, tiram dúvidas e respondem perguntas dos alunos. Participe pelo site EscoladoAmorResponde.com. Ouça todos os podcasts no iTunes: rna.to/EdARiTunes

O 'Doa a Quem Doer' desta semana conta a realidade de dois irmãos em que um está doente e o outro suicidou-se, mas deixou uma carta a pedir para cuidarem do irmão Rui.

Durante a Escola do Amor Responde de hoje, Cássia e Rui contaram que chegaram ao relacionamento após experiências amorosas difíceis e casamentos fracassados. Cássia foi casada duas vezes. No primeiro casamento, aos 20 anos, se uniu a um homem 28 anos mais velho por admiração profissional, mas a grande diferença de idade e de momento de vida gerou incompatibilidades. Depois, teve um segundo casamento, também marcado por expectativas frustradas e diferenças de maturidade e atitude.Rui também teve três relacionamentos sérios que não deram certo. Ele cresceu sem uma referência positiva de casamento e buscou aprender sobre relacionamentos por meio da fé e dos ensinamentos da Terapia do Amor. Com o tempo, percebeu que tentava mudar as pessoas em vez de escolher alguém que compartilhasse os mesmos valores.Quero Te ConhecerApós anos solteiros, ambos se aproximaram mais de Deus, amadureceram emocionalmente e passaram a agir de forma diferente em relação à vida amorosa. Foi então que se conheceram pelo aplicativo Quero Te Conhecer, exclusivo aos participantes da Terapia do Amor. Mesmo com certa resistência inicial ao aplicativo, decidiram dar uma oportunidade. A partir desse encontro, construíram um relacionamento baseado em propósitos, valores e maturidade, até chegarem ao casamento, que já dura pouco mais de um ano.Bem-vindos à Escola do Amor Responde, confrontando os mitos e a desinformação nos relacionamentos. Onde casais e solteiros aprendem o Amor Inteligente. Renato e Cristiane Cardoso, apresentadores da Escola do Amor, na Record TV, e autores de Casamento Blindado e Namoro Blindado, tiram dúvidas e respondem perguntas dos alunos. Participe pelo site EscoladoAmorResponde.com. Ouça todos os podcasts no iTunes: rna.to/EdARiTunes

Temos um bocado de girls talk, mas não temos Off Campus. Prometo que me controlei. Como prometido, episódio dividido entre Houston e Lisboa. O Rui passou a semana com a seleção e a Mafalda em casa a tentar fazer tudo o que costuma fazer + aquilo que o Rui costuma fazer. Chama-se dar valor? Creio que sim! Demos opinião sobre as polémicas da semana, o Rui fala do espirito de apoiar a seleção e Cristiano Ronaldo.APOIOS:Activobank

We look at our first pure point guard prospect in this with Kingston Flemings out of Houston. How does he compare to current NBA floor generals? Then, the Lakers' offseason takes center stage. They're faced with a choice of retaining their current free agents, using cap space, or trading for higher-end players than the ones they have? Who are some realistic names for them to go after? Should they prioritize LeBron and Rui or door number 2? 31:30 Golden State has nearly their full complement of draft picks, but desperately needs help on the wing and more creation with Jimmy Butler still sidelined.  Could they get Giannis?  If not, what are some lower level moves they can make to tread water until Butler returns? 55:30 Get 35% off a new membership to Dunc'd On Prime! Join Dunc'd On Prime for 35% off using the code mockoffseason2026! It's the only place to get every episode with Nate & Danny, plus every pod with John Hollinger & Nate as well!Subscribe on YouTube to get Dunc'd On Clutch Calls, Real Video Scouts, and more.Or, sign up for our FREE mailing list to get Dan Feldman's Daily Duncs with all the major topics around the league twice a week. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Neste episódio, o Fragoso e o Rui viajam até à Argentina para uma conversa sem guião sobre protagonistas e histórias de futebol que o país da albiceleste nos tem dado nas últimas décadas.

Hola! Estan bienne? Esta semana Mafalda e Rui quase que apenas se encontram para gravar podcast. Rui foi numa viagem de bagaçada a Espanha e Mafalda numa viagem de influencers. Portanto, sumo não falta. Rui compete com crianças num quizz numa quinta, falam sobre os Santos e de chorar num espectáculo de golfinhos. Agora, assuntos mais sérios, Mafalda teve paralisia do sono e foi uma coisa assustadora. Ainda houve tempo para falar sobre o doc das Patrocínio do do Rui ter sempre cara de banana nos stories. Enjoy! Ahh Mafalda está a ver off Campus, mas ninguém vê issoAPOIOS:sporttvhttps://www.sporttv.pt/aderir

Nesta segunda parte da conversa, os escritores Luísa Costa Gomes e Rui Cardoso Martins começam por comentar o que os perturba e ilumina atualmente no país, no dia em que se celebra o Dia de Portugal, de Camões e das Comunidades Portuguesas. Depois abrem os seus mais recentes livros, leem um excerto, e revelam um pouco do que lá vai dentro. Luísa conta como fez a seleção dos contos "O Triunfo do Triunfo" e Rui Cardoso Martins revela como usa o humor para aprofundar, e não para aligeirar, e recorda como o texto que dá arranque ao seu romance "As Melhoras da Morte", foi escrito sem o autor saber que ia resultar num romance. E ainda partilham os autores que andam a ler. Luísa lê Camões e Rui lê o romancista russo Andrei Platonov. No final, há ainda espaço para se ouvir uma pergunta do público que confronta algumas afirmações de Luísa e Rui. Boas escutas!See omnystudio.com/listener for privacy information.

What does real partnership between Europe and Africa actually look like in 2026? In this episode of the Liberal Europe Podcast, Ricardo Silvestre is joined by Rui Santos, CEO of CESO Development Consultants, a Portuguese firm celebrating its 50th anniversary this year and one of the most experienced implementers of European Commission projects across Africa, Latin America, and Asia. The conversation unpacks how EU cooperation has shifted away from the old donor-beneficiary model towards genuine, shoulder-to-shoulder collaboration. They discuss the EU's strategic partnership programmes with countries like Angola, the Global Gateway initiative, and PROCULTURA PALOP-TL/UE, a cultural ecosystem-building project across Portuguese-speaking African countries and East Timor. Along the way, Rui reflects on what 35 years in international development have taught him about reputation, patience, and the long-distance run that meaningful cross-border work demands. This podcast is produced by the European Liberal Forum in collaboration with Movimento Liberal Social and Fundacja Liberté!, with the financial support of the European Parliament. Neither the European Parliament nor the European Liberal Forum are responsible for the content or for any use that be made of.

Começamos no tiroliroliro este episódio mas com o Rui no tiroliroló devido a um treino de padel. Quem diria que um treino de padel ia proporcionar uma conversa sobre falha, não tentar e destituir de coisas. Ninguém. Outra coisa que ninguém iria adivinhar: o jardineiro veio cá a casa, não percebeu nada do que tinha que fazer MAS a culpa não é do Rui. Não!!!!! É de Camões. Falamos também do assunto da semana: Catarina Miranda foi a televisão terminar com o namorado em directo. Ainda sobre as aventuras de Rui na Champions e com a seleção de Portugal e o seu momento de super fama. (No final do episódio tivemos um problema com as câmaras e tivemos de terminar de forma rápida).APOIOS:SportTV

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

Fluent Fiction - Mandarin Chinese: Love Blossoms: Bridging Hearts from Shanghai to Paris Find the full episode transcript, vocabulary words, and more:fluentfiction.com/zh/episode/2026-06-01-22-34-01-zh Story Transcript:Zh: 阳光透过窗帘洒在莲的书桌上，他的公寓位于上海一个繁华的街区。En: Sunlight filtered through the curtains and onto Lian's desk.Zh: 窗外是一片生意盎然的景象，樱花在凉爽的春风中摇曳。En: His apartment was located in a bustling neighborhood in Shanghai.Zh: 莲慢慢放下手机，长长地叹了口气，心中思绪万千。En: Outside the window was a lively scene with cherry blossoms swaying in the cool spring breeze.Zh: 他的心被两座城市分割，一部分留在这里，和明一起。En: Lian slowly put down his phone, let out a long sigh, and his mind was filled with countless thoughts.Zh: 明是他的儿时玩伴，如今正在与慢性病抗争。En: His heart was divided between two cities, with one part staying here, with Ming.Zh: 莲经常去看望他，为他带去食物和希望。En: Ming was his childhood friend and was currently battling a chronic illness.Zh: 另一部分心则飞向遥远的巴黎，那里有他的爱人蕊。En: Lian would often visit him, bringing food and hope.Zh: 距离让他们的爱情如同长江与塞纳河般遥远，但蕊的存在总是在心中给予莲勇气。En: The other part of his heart flew to distant Paris, where his lover Rui was.Zh: 莲望着桌上那封刚收到的邮件，是蕊发来的新画。En: The distance made their love as far apart as the Yangtze River and the Seine River, but Rui's presence always gave Lian courage.Zh: 画上是一个身形模糊的人，站在樱花树下，满天的粉红色花瓣在风中飞舞。En: Lian looked at the email he had just received on the table; it was a new painting sent by Rui.Zh: 画中人低头凝视着地面，嘴角带着微笑，身旁是一个虚幻的影子，象征着未到的爱。En: The painting depicted a blurred figure standing under a cherry blossom tree, with pink petals flying in the wind.Zh: 莲感受到一种深深的理解和支持，从巴黎传来绵长的温暖。En: The figure in the painting was looking down at the ground, a faint smile on their lips, and beside them was an illusory shadow, symbolizing love yet to arrive.Zh: 心中某个角落轻轻一动，莲明白了。En: Lian felt a deep sense of understanding and support, a long-lasting warmth coming from Paris.Zh: 他决不能失去这段感情，也决不能对明掉以轻心。En: A gentle stir in a corner of his heart made Lian realize he could not lose this relationship, nor could he neglect Ming.Zh: 于是他想到了一个办法——将他们的生活连结在一起。En: So he thought of a way—to connect their lives together.Zh: 他与蕊商量，决定邀请明在网上与蕊合作艺术创作。En: He discussed with Rui and decided to invite Ming to collaborate on art projects online.Zh: 这样，蕊就仿佛来到了上海，能为明带来些许快乐。En: In this way, it would be as if Rui had come to Shanghai, bringing some joy to Ming.Zh: 明非常高兴，他在病痛间隙，砚边涂抹，笑意越来越多。En: Ming was very happy and would paint during the moments when he felt less pain, with more and more smiles appearing on his face.Zh: 每一次莲到医院探望明，都会带去他们的新创作。En: Every time Lian visited Ming in the hospital, he would bring their new creations.Zh: 看见明脸上逐渐恢复的神采，莲心中充满了温暖。En: Seeing Ming's gradually recovering spirit filled Lian's heart with warmth.Zh: 尽管他不能在物理上同时分身，但心灵却能跨越万里。En: Although he could not physically be in two places at once, his soul could traverse thousands of miles.Zh: 这个春天，樱花开得特别美。En: This spring, the cherry blossoms bloomed beautifully.Zh: 莲在落地窗前坐下，手中捧着从巴黎寄来的画，感受到这座城市的生命力以及自己内心的宁静。En: Lian sat in front of the floor-to-ceiling windows, holding a painting sent from Paris, and felt the vitality of the city and the peace within himself.Zh: 他知道，只要心在，距离就不会是阻碍。En: He knew that as long as the heart is present, distance would not be an obstacle.Zh: 从那以后，莲不再感到夹在两者之间的无奈。En: From then on, Lian no longer felt helpless being caught between the two.Zh: 他学会了如何去寻找和谐，明白到有爱就能创造出无数可能，而人的生命也因此更加完整。En: He learned how to find harmony and understood that love could create countless possibilities, making one's life more complete because of it. Vocabulary Words:filtered: 透过curtains: 窗帘bustling: 繁华swaying: 摇曳countless: 思绪万千battling: 抗争chronic: 慢性visit: 看望distant: 遥远depicted: 描绘blurred: 模糊illusory: 虚幻harmony: 和谐collaborate: 合作creations: 创作recovery: 恢复vitality: 生命力obstacle: 阻碍helpless: 无奈possibilities: 可能complete: 完整apartment: 公寓neighborhood: 街区presence: 存在courage: 勇气scene: 景象support: 支持neglect: 掉以轻心intervals: 间隙traverse: 跨越

Nesta emissão, recebemos Rui Passos Rocha, autor de Promessas do Futebol (Fundação Francisco Manuel dos Santos, 2026). O livro traça um raio-x ao "funil" do futebol, revelando como a sorte, o "efeito da idade relativa" e as barreiras socioeconómicas travam milhares de jovens talentos. Ao longo da conversa, Rui partilha connosco os bastidores da investigação, as descobertas que mais o surpreenderam, e histórias inéditas.Na segunda parte, mergulhamos na atualidade: analisamos a final da Liga dos Campeões entre PSG e Arsenal e celebramos o feito inédito dos quatro portugueses bicampeões europeus. Com o Mundial de 2026 à porta, debatemos as expectativas para a Seleção Nacional. Até onde pode chegar Portugal?Tudo isto e muito mais n'Os Meninos de Ouro.Nota: A apresentação pública de Promessas do Futebol acontece no dia 7 de junho, às 17h, na Feira do Livro de Lisboa.

Desta vez um verdadeiro batanete a fazer parte de mais um episódio. Para além dessa grande virtude, é também um dos maiores talentos nacionais (e internacionais), José Condessa! Falou-se sobre a intensidade de viver a representação desde novo, de dizer que não a projectos, de gerir ego e ter sempre aqueles amigos que dizem “tens que te acalmar”. Os bastidores dos grandes projetos, dos beijos técnicos e cenas nu. Ainda um quizz sobre qual o melhor namorado: Zé ou Rui.REDES SOCIAISMafalda Castro: https://www.instagram.com/mafaldacastroRui Simões: https://www.instagram.com/ruisimoes10Bate Pé instagram: https://www.instagram.com/batepeclipsBate Pé Tiktok: https://www.tiktok.com/@bate.peSPOTIFY: https://open.spotify.com/show/7bnvbtG4aHEKp90XbN0xm3?si=rsZeIGW1Q4ShAQaRRegnbA#josécondessa#mafaldacastro #ruisimões

Oiiii! Tudo jóia? Já viram algum GRWM para um divórcio? Nós já e por isso vimos e talvez tenhamos julgado. Se na semana passada tivemos a história de João Betão, esta semana temos a reacção de João Betão. Quem sabe não parece um dia destes num episódio para da um "oi". Durante a semana a mãe da Mafalda disse que devia sugerir alguns temas para o podcast e portanto esta semana cá estão: temos anjos, pioneira de expressões entre outros. Ainda houve espaço para a Mafalda arrancar um dente, vencer uma batalha contra Rui e ficar com um quentinho no coração por Rui ter riscado o próprio carro. Ainda falamos de outras coisas mas vamos deixar que vocês descubram. Fomos!!!!!APOIOSActivoBank

Rui Morais, CEO of Dis-Chem Pharmacies and prior to that, the youngest CFO of a listed company in South Africa, sits down with Debbie Goodman to discuss the real story behind Dis-Chem's much-misreported restructure, and why it's actually a signal of bold ambition, not downsizing. With 200 new roles being created alongside the reorganisation, Rui explains how Dis-Chem is evolving from a retail pharmacy into South Africa's healthcare authority, backed by an innovation hub, strategic partnerships, and a board deeply aligned on purpose.  The conversation goes behind the scenes of one of the most publicly scrutinized CEO successions in South African corporate history, exploring the unexpected tension, identity shifts, and emotional complexity that no governance framework fully prepares you for. Throughout, Rui emerges as a leader who is deeply purposeful, refreshingly candid, and unafraid to swing for the fences. Follow Debbie on LinkedIn here Follow Rui on LinkedIn here On Work and Revolution podcast exposes the real forces reshaping leadership, talent, and the future of work. Hosted by Debbie Goodman - CEO of Jack Hammer Global, a top executive search firm, author, advisor, and speaker - this podcast dives into bold ideas and honest conversations with CEO's reshaping today's workplaces and redefining what great leadership looks like. If you're a CEO, founder, or changemaker hungry for real insight into workplace trends, hiring strategy, and organizational transformation, this is your space to listen, learn, and lead differently. ✦ Explore more insights, guest details, and episode transcripts at: jhammerglobal.com✦ Follow Debbie on LinkedIn | YouTube ✦ Subscribe, share, and spark your own work revolution.

Sedano starts the show off welcoming Chris ‘Geeter' McGee, who is filling in for Kap today. Sedano is in Detroit after calling last night's Cavs-Pistons Game 7 - which Lindsey's Cavs won! Does this quiet the LeBron chatter for now? Producer Lindsey argues that the Cavs advancing in the playoffs may make Cleveland more attractive to LeBron - but how would that even work?! And Geeter says the Lakers should pay Rui because he's a “playoff player.” Dodgers talk! Berg's 3 things: Sasaki was GREAT, 31-3 weekend but NO SLUG!.. Plus Blake Snell's loose bodies. Learn more about your ad choices. Visit podcastchoices.com/adchoices

Mais uma jornada de Bate Pé. Conhecem a partida do João Botão? A vingança é um prato que se serve frio? Não sei, depende do gosto de cada um mas a verdade é que o Rui retribuiu o deboche que a Mafalda lhe deu há um ano atrás. Neste episódio falamos sobre a nossa condução, fazer uma sandes no restaurante e de coisas caras. Qual foi a pergunta mais inesperada que vos fizeram? O Rui consegue ganhar, acreditem. Falamos também dos Aliens files e temos finalmente a revelação da Mota. Por fim tábua de queijos é criminoso ou inocente? Digam-nos vocêsREDES SOCIAISMafalda Castro: https://www.instagram.com/mafaldacastro/Rui Simões: https://www.instagram.com/ruisimoes10/Bate Pé instagram: https://www.instagram.com/batepeclips/Bate Pé Tiktok: https://www.tiktok.com/@bate.pe

Mason and Ireland tip off the show today with Morales and ‘Live Imaging Tuesday!' The Lakers have been swept by the OKC Thunder. Take a listen to Rob Pelinka talking about the ‘Lakers Way' today at the end of year press conference. Why wasn't Rui on the court for the final 3 point attempt? What is next for the Lakers and Lebron James? Ice Breakers! Learn more about your ad choices. Visit podcastchoices.com/adchoices

Este episódio tem o apoio do Activobank. Os carecas precisam ou não de usar touca na natação? É a grande questão que queremos ver respondida neste episódio. Falamos do aniversário do Rui e da forma como recebe pessoas em casa e corta bolo. Estará tudo errado como sempre? Claro! No episódio anterior falamos da Julinha e Melinha, neste episódio damos um update. Ainda tudo sobre a avaliação do Manel na natação e de como é possível chumbar a tudo graças ao Pai, de introvertidos e extrovertidos e da TVI que devia pagar multa por abuso de IA nos anúncios e programas.REDES SOCIAISMafalda Castro: https://www.instagram.com/mafaldacastro/Rui Simões: https://www.instagram.com/ruisimoes10/Bate Pé instagram: https://www.instagram.com/batepeclips/Bate Pé Tiktok: https://www.tiktok.com/@bate.pe

Get Up resumes with a Laker stomping. Despite a great LeBron game, Reaves and Rui came up short leading to a Thunder beatdown! (0:00) Meanwhile - Finch's Rant - Wemby broke the playoff block record. Were any of them goaltends? (14:00) Then - Donovan Mitchell is the latest to complain about officials. Does the NBA have a reffing problem, or a complaining problem? (23:00) Learn more about your ad choices. Visit podcastchoices.com/adchoices

LeBron tried to set a tone, but no one outside of Rui was ready to match that energy. It reminded Anthony of another game where James was a heavy underdog and did all he could to steal a win. To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices

In case anyone needed any reminding, OKC is quite good. LeBron showed up ready to compete. So did Rui. Hell, even Ayton was mostly fine in the minutes he could play because of his foul trouble. Austin, much less so. Anthony and Raj discuss the game and what they want the Lakers to get from a series they're almost certainly going to lose. To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices

Este episódio tem o apoio da ABOUT YOU. Vamos começar por parabenizar o Rui. Foram precisos 255 episódios para admitir que estava errado. Grande homem! Temos um update de gatas, a carteira perdida e depois encontrada e ainda uma pequena ressaca depois de sair à noite. Claro que o Rui levou o pequeno almoço à cama mas não era bem o que a Mafalda estava à espera. Por falar nesta menina… perdeu a mesma moeda de 1 Euro duas vezes no espaço de um minuto. Parece-me que temos mais um momento taralhoca. Ainda falamos sobre os primeiros momentos do filho na natação e por fim um momento no shopping muito simpático - contém ironia entre outras coisas. Ah, não se esqueçam de consumir electrólitosEncontra as tuas marcas favoritas na ABOUT YOU! Usa o código BATEPE20 para poupar 20% na tua encomenda, válido até 16/05/2026.. Aplicam-se os termos e condições(https://www.aboutyou.pt/cp/condicoes-gerais-de-vouchers-e-descontos-106082).REDES SOCIAISMafalda Castro: https://www.instagram.com/mafaldacastro/Rui Simões: https://www.instagram.com/ruisimoes10/Bate Pé instagram: https://www.instagram.com/batepeclips/Bate Pé Tiktok: https://www.tiktok.com/@bate.pe

Rui Hachimura has launched plenty of takes during his time as a Laker but once again, he's risen to the moment in the playoffs. So Anthony asks Harrison and Raj about whether this run has changed their minds on a potential Rui return. The wrap with some final thoughts about the series. To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices

We start the show off with some super cross talk with Mason, Pepe, & Mychal Thompson. The crew is both in studio along with Greg Bergman who joins us every Wednesday! Travis went to go watch UCSB beat the UCLA Bruins in baseball last night. Greg and Travis are going to watch Shohei Ohtani Pitch tonight. Who needs to step up for the Lakers with Luka and Austin Reaves out of the lineup? Is it Rui? Ayton? Kennard? Dodgers pitcher Shohei Ohtani will not be a DH today against the Mets. Learn more about your ad choices. Visit podcastchoices.com/adchoices

Get Up resumes with a sad ending to a monumental return. Jayson Tatum went back to MSG looking to resurrect the old ways of the Celtics when the Garden was Js. Josh Hart had something else in mind... (0:00) Meanwhile - Jerry with two first round draft picks? Sounds Dangerous! Kevin Clark and Ben Solak on how Jerry can avoid being dragged through the wringer this offseason! (14:40) Then - We are family, I got Bronny, Bron and Rui! Which Western Conference team could the Lakers new big 3 take down in round 1? (24:40) Learn more about your ad choices. Visit podcastchoices.com/adchoices

Mason and Ireland are both out today, Andy Kamenetzky and Ramona Shelburne are in! The Lakers got blown out again by the Thunder. Are there any silver linings the Lakers can take away from the loss to the Thunder? The guys dive into JJ Redick's interactions and comments about Rui, Ayton, and Vanderbilt. How is Adam Silver going to manage the 65 game rule? Ice Breakers! Learn more about your ad choices. Visit podcastchoices.com/adchoices

Assistant head coach Rui Pedro Silva sits down for an exclusive Wolves Express interview; his very first since returning to Wolves in December. Having previously worked alongside Nuno Espírito Santo during a memorable four‑year spell at Molineux, Rui reflects on his favourite moments from that era, the culture that shaped the team, and the achievements that still mean so much to him today. Rui also reveals what inspired him to return to Wolves, the warm welcome he's received from supporters, and how it feels to be back in familiar surroundings. Plus, he discusses his relationship with head coach Rob Edwards, how their partnership works behind the scenes, and the shared vision driving the club forward. Make sure you are following Wolves Express for the latest, exclusive Wolves news or head to Wolves.co.uk Learn more about your ad choices. Visit podcastchoices.com/adchoices

This week, hosts Solarina Ho and Rui Zhong speak with Yangyang Cheng, a Research Scholar at Yale's School of Law focusing on science and technology development in China and US-China relations. In this episode, Solarina, Rui, and Yangyang speak on the struggles of scientists in the current political climate, the place of women in the intersection of politics and science, and China's history and future in the geopolitical landscape. They also discuss Yangyang's career as a researcher, writer, and academic, and delve into her tips for aspiring writers. 

Welcome to 听故事说中文, the podcast where stories come alive to help you improve your Chinese language proficiency and cultural competency. Have you ever felt like someone was watching you? For Pipi, a 32-year-old working in Beijing, that feeling became a literal reality overnight. Her company, struggling with declining profits, decided to install high-tech AI surveillance—cameras that don't just record video, but analyze exactly how long you're at your desk and even if you look like you're daydreaming. Management hoped this "digital boss" would spark a new wave of productivity. Instead, the office went silent. Genuine collaboration was replaced by anxiety and a quiet, collective resistance known as "lying flat." In today's episode, we follow Pipi as she navigates an environment where trust has been replaced by algorithms. It's a fascinating look at the modern workplace, the limits of technology, and the universal human need for dignity. Let's dive into the story and see why Pipi believes that true efficiency can't be forced by a camera. —Rui and Simeng ************************************************************ Support Our Podcast If our podcast brings value to your life and you'd like to help us continue creating great content, consider becoming a patron for as little as $7 a month. As a patron, you will enjoy: ✨ Ad-free episodes for an uninterrupted listening experience.

MAKEEN Energy is a global engineering and technology company serving the energy sector in more than 100 countries. In this special two-host episode of Assets UNSCRIPTED, Berend Booms and Sarah Nicastro sit down with Rui Melo Ferrera, Corporate Maintenance & Asset Manager at MAKEEN Energy, to explore how digitalization is transforming asset management, field service, and service-led business growth.In this conversation, Rui shares how MAKEEN Energy moved from fragmented tools to a more unified digital approach, why data and transparency are essential for performance-based service models, and how digital transformation helps service organizations move from reacting to problems to predicting and preventing them.He explains:▪️How digitalization helps shift from selling equipment to delivering service outcomes▪️Why data is the foundation for asset performance management and servitization▪️How MAKEEN Energy builds a complete “picture of the moment” for customer assets▪️Why transparency strengthens customer trust and long-term service relationships▪️How one service visit can demonstrate measurable impact and drive contract growth▪️How digital tools remove friction from frontline work and improve technician experience▪️Why modernizing field roles is essential for attracting the next generation of talent▪️Why listening to frontline teams is critical for successful change management00:00 Intro00:55 Meet Rui Melo Ferrera at MAKEEN Energy02:15 From Fragmented Tools to One Unified Platform05:25 Why Portugal Became a Benchmark for Digital Transformation06:44 Building a Complete Picture of Customer Assets10:47 When Data Becomes Non-Negotiable12:14 The Future of Predictive Asset Intelligence14:40 How Digitalization Enables Servitization17:53 The Shift Toward Performance-Based Contracts19:25 Using Transparency as a Competitive Advantage21:49 Demonstrating Impact and Building Long-Term Partnerships25:55 Removing Friction From Frontline Work30:04 Modernizing Field Roles to Attract Talent32:05 Change Management Lessons: Listen, Personalize, Support36:40 Key Takeaways and Final ThoughtsFollow Berend Booms on LinkedIn: https://www.linkedin.com/in/berendbooms/Follow Future of Assets on LinkedIn: https://www.linkedin.com/company/future-of-assetsLearn more about Assets UNSCRIPTED: https://www.futureofassets.com/Learn more about the UNSCRIPTED podcasts: https://www.futureoffieldservice.com/podcast/

Today, We talk about why Morgan should or should not read on the treadmill! We also discuss the unusual weather trends and how Sam and Morgan need to travel immediately to somewhere warmer.  Side Note: We received this novel as an audiobook ARC from NetGalley and HarperCollins. Thank you so much for allowing us to dive deep into this novel early! About The Novel: The world has moved on. With the missing death god restored to the underworld, it appears that equilibrium has been regained. But the Nothing continues to threaten the underworld - and the mortal realm. Trapped in Hell, Zizi fights the takeover of his soul by Four's. As he begins to access Four's memories, he discovers a tragic love story that could be the key to keeping the mortal realm safe. Now, Zizi must defy his fate and escape Hell once more. On the surface, Rui's life has changed as she is hailed a hero by the Exorcist Guild. But she soon discovers the spell Zizi was forced to create is transforming innocent humans into vicious Hybrid Revenants. With the help of the other cadets, she vows to stop them. Now magicless, Yiran watches, hungrier than ever, until he begins a dangerous dalliance with Yuki, hoping the Hybrid will recover Yiran's magic. And when he discovers a dark family secret, he must decide what he stands for - before it's too late.   Wanna Check Us Out? Then Click Here!

This conversation explores the tax policies in Italy and Portugal, focusing on the basic tax structures, ways to minimize tax burdens for foreigners, available deductions, filing requirements, common mistakes made by expats, and final thoughts on navigating the tax systems in both countries. Experts Nick and Rui provide insights into the complexities of taxation for new residents and the importance of professional guidance.Rui's website: https://goalseek.pt/Nick's website: https://www.italiantaxes.com/

What would you do if your income tripled in just 60 days? In this powerful episode of the CEO Glow Show, Sheila Bella sits down with beauty boss Rui Zamarripa, owner of Heaven's Touch Spa in Atwater, California, to break down exactly how she went from inconsistent $10K months to nearly $30K in her biggest month — in just three months after joining Pretty Rich Bosses. But this episode isn't just about numbers. It's about visibility. Belief. Sales conversations. Paid ads. Coaching. And becoming the kind of woman who trusts herself enough to invest before she sees the proof. Rui shares how shifting from transactional selling to relationship building changed everything, how running ads created consistent inquiries, and why mentorship helped her finally stop feeling lost in her business. If you are stuck at the same income ceiling and wondering what it actually takes to double or triple your revenue, this episode is your blueprint.

Welcome to 听故事说中文, the podcast where stories come alive to help you improve your Chinese language proficiency and cultural competency. Have you ever felt like someone was watching you? For Pipi, a 32-year-old working in Beijing, that feeling became a literal reality overnight. Her company, struggling with declining profits, decided to install high-tech AI surveillance—cameras that don't just record video, but analyze exactly how long you're at your desk and even if you look like you're daydreaming. Management hoped this "digital boss" would spark a new wave of productivity. Instead, the office went silent. Genuine collaboration was replaced by anxiety and a quiet, collective resistance known as "lying flat." In today's episode, we follow Pipi as she navigates an environment where trust has been replaced by algorithms. It's a fascinating look at the modern workplace, the limits of technology, and the universal human need for dignity. Let's dive into the story and see why Pipi believes that true efficiency can't be forced by a camera. —Rui and Simeng ************************************************************ Support Our Podcast If our podcast brings value to your life and you'd like to help us continue creating great content, consider becoming a patron for as little as $7 a month. As a patron, you will enjoy: ✨ Ad-free episodes for an uninterrupted listening experience.

If the plan is indeed to kick this can down the road and hope for Giannis, then it's time to actually commit to that plan and acquire something for Rui rather than let him walk for nothing. To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices

Anthony breaks down the situation as he sees it regarding these De'Andre Hunter-Rui Hachimura rumors. This would be a pretty underwhelming return for Rui, so Anthony explains why this isn't what the final deal will look like. He discusses the entirety of the trade market and then answers questions from the live audience. To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices