Podcasts about ABI

Cloning may seem like a futuristic topic largely reserved for science fiction but plants are doing it all the time. Clonality is one of the many aspects that can make plant species successful across the landscape. It can also greatly impact the way we approach plant conservation efforts. Despite the importance of cloning in plants, we still know very little about how its influences plant population dynamics. Which plants are clonal? How long can clones live? How does cloning influence pollination? These questions and more are what drive people like Dr. Ashley Morris. Join us as we look at why she is so fascinated by cloning and conservation in plants. This episode was produced in part by Chris, Gerald, Elise, Maggie, Mamie, A.J., Dallas, Channele, KC, Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie. See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

What does an Andy Burnham government mean for UK agriculture? This week, Westminster watcher Jeremy Moody examines the new prime minister’s farming credentials – and whether a land value tax could hit agricultural businesses. We also examine the law on defending yourself and your property after prosecutors decide that a Derbyshire farmer who fatally shot an intruder will face no criminal charges. Agricultural solicitor Aled Owen explains when force may be considered necessary and reasonable—and why picking up a firearm should always be a last resort. Elsewhere, we bring you the latest harvest results, advice on handling exceptionally dry oilseed rape, this week’s livestock and arable prices, and an unusual field fire started by a buzzard. And finally, could chickpeas become a profitable, climate-resilient break crop for UK growers? Louise Impey visits field-scale trials in Cambridgeshire and Suffolk to find out. This episode is brought to you by plant breeder KWS. Special Guests Jeremy Moody – secretary and adviser, Central Association of Agricultural Valuers Matt Bull – product manager, KWS Aled Owen – agricultural solicitor and partner, HCR Law David White – Cambridgeshire arable farmer and chickpea trial grower Josiah Meldrum – Hodmedod’s Wholefoods Chapters 00:55 What does an Andy Burnham government mean for agriculture?04:51 Could farmers face a land value tax?08:45 Will rural Britain be heard?11:47 Farmers Weekly Harvest Update with KWS15:15 Farmer faces no charges over fatal shooting15:52 What does the law allow householders to do?19:44 Advice for farmers facing an intruder26:10 Harvest results: wheat, barley, beans and oilseed rape28:02 Adding moisture to very dry oilseed rape29:23 Buzzard blamed for standing-crop fire30:48 Church rejects blanket rewilding target31:41 Environment Agency farm inspection findings33:04 Should rural speed limits fall to 20mph?35:31 Market update38:11 Could chickpeas become a UK break crop?45:18 Closing remarks Useful links ⁠Farmers Weekly ⁠Central Association of Agricultural Valuers ⁠HCR Law agricultural regulatory team ⁠Crown Prosecution Service guidance on self-defence and crime prevention ⁠AHDB grain-storage moisture targets United Oilseeds ⁠NIAB: UK chickpea production research ⁠Hodmedod’s Farmers Weekly market prices This episode of the Farmers Weekly Podcast is hosted by Johann Tasker with Abi Kay, Louise Impey and Hugh Broom. Edited and produced by Johann Tasker. To get in touch with the Farmers Weekly Podcast: - Contact or follow Johann: linkedin.com/in/johanntasker/ Contact or follow Abi: https://uk.linkedin.com/in/abi-kay-38927130 Contact or follow Louise: linkedin.com/in/louise-impey-95470b20b/ Contact or follow Hugh: linkedin.com/in/hugh-broom-9b11906a/ For Farmers Weekly, visit fwi.co.uk or follow linkedin.com/company/farmers-weekly To contact, sponsor or advertise on the Farmers Weekly Podcast, email podcast@fwi.co.uk. In the UK, you can also text the word FARM followed by your message to 88 44 0. See omnystudio.com/listener for privacy information.

Three years ago Jamie Bedwell and his wife Abi were on this podcast as newly licensed professional triathletes with the world opening up before them. This week Jamie is back, riding solo, and the story has taken a turn nobody planned for. Three years of gradual deterioration. Chronic back pain, loss of power in the left leg, pins and needles that left him feeling, in his own words, more like a pirate with a wooden leg than a semi-decent triathlete. Every race ended the same way. Every solution fell short. Until earlier this year, when he finally got a diagnosis: flow limitation of the iliac artery, FLIA, a condition where the main artery feeding blood to the leg kinks under the repeated stress of cycling and running. There was a surgery. There was a one in five chance of it going wrong. There was a man in the waiting room who had been back eight times. And there was a surgeon who asked Jamie a simple question: why would you risk so much just to compete in triathlon? Jamie didn't need the six weeks he was given to decide. He said no to the surgery, yes to swimming, and started figuring out what comes next. This is one of the most honest and quietly moving conversations I have had on this podcast. 5 KEY POINTS FLIA affects competitive cyclists and triathletes specifically. Millions of pedalling repetitions thicken the iliac artery over time, restricting blood flow under race conditions. Day to day there is no pain at all. The surgery carries a one in five failure rate. If it goes wrong, the athlete doesn't just lose their sport. They lose the ability to walk uphill or ride a bike with their kids. Jamie said no to protect something bigger than his career. He wanted to remain in sport for the rest of his life. The surgery put that at risk. Once he understood that, the decision was straightforward. Swimming has always been his weakest discipline. He won his first open water race on the River Arun and qualified for the national championships in Sheffield. He is just getting started. Resilience isn't about pushing through. It is about knowing what you are actually fighting for and making decisions that protect it. 3 TAKEAWAYS Know what you are protecting. Jamie turned down surgery not because he gave up on sport but because he refused to risk losing it permanently. Discipline and love will take you further than a fixed goal. Jamie doesn't know where swimming will take him. He just knows those two things are enough. Identity is bigger than the sport. Jamie is applying for ordination, building a community of Christian athletes with Abi, and becoming, in his own words, a more gentle and humble person.   KILLER QUOTE "I'm so grateful there is such a thing called sport. Whether you're going to Park Run or competing at the highest level — sport gives every single person the opportunity to test themselves. And I'm grateful I still have that opportunity."   CONNECT with Jamie Jamie Bedwell is a former professional triathlete and competitive open water swimmer. He and Abi run an email list sharing their journey in sport and faith. Join Jamie and Abi's email list:   FuelledbyFaith@outlook.com for regular updates on their progress   Instagram -  Fuelledbyfaithajb Jamie and Abi are sponsored by Raceskin Wetsuits Jamie's favourite book: Unbroken by Laura Hillenbrand - A Powerful WWII Survival Story of Endurance in the Pacific War If you haven't listened to the previous Be Battle Ready podcast with James & Abi, you can find it here: Husband and wife racing duo   If this conversation has resonated and you want a training structure built around your whole life, not just your performance targets, that is exactly what SWAT is designed for. CLICK HERE TO START YOUR MISSION   FREE Download

Meta ve Google reklam panellerinde "Kampanya Oluştur" yeşil butonuna basmayı herkes biliyor. Hangi tuşun ne işe yaradığını, Advantage+ veya PMax kampanyalarının nasıl kurgulanacağını YouTube'daki on dakikalık ücretsiz bir videoyla bile öğrenebilirsiniz. Panel kullanmak kolaydır; çünkü panel günün sonunda kodlanmış basit bir arayüzdür. Peki, sektördeki e-ticaret markalarının %90'ı neden hala reklam bütçesini çöpe atıyor, neden ROAS ekranlarında sahte illüzyonlarla avunup ay sonunda banka hesabında gerçek bir kârlılık göremiyor?Bu sorunun cevabını, geçtiğimiz günlerde yayınları sıkı takip eden değerli dinleyicimiz Mustafa Altay'dan gelen çok samimi bir itirafla masaya yatırıyoruz. Mustafa'nın sorduğu, aslında bugün milyonlarca lira bütçe yöneten ajansların ve pazarlama direktörlerinin en büyük kanayan yarası: "Abi her şeyi anladım, psikolojiyi ve reklamı anladım ama şu müşteriyi araştırması kısmını, pazardaki müşteriyi anlayıp ona göre reklam çıkma matematiğini bir türlü oturtamıyorum."Filtresiz Dijital'in 97. bölümünde, reklam panelinden önceki o konuşulmayan "Karanlık Bölgeye" dalıyoruz. Altınızdaki araba bir Ferrari bile olsa, navigasyona yanlış adresi girerseniz sadece yanlış yere çok daha hızlı gidersiniz. Bu Bölümde Hangi Ödünsüz Gerçekleri Deşifre Ediyoruz?• Demografik Çöplük ve "Gece 3 Sancısı": Ajansların Excel tablolarına yazdığı "25-45 yaş arası, büyükşehirde yaşayan, yoga yapan kadınlar" gibi içi boş personaların neden birer çöplük olduğunu yüzleşerek konuşuyoruz. İnsanlar yaşlarına veya oturdukları semte göre değil, amigdalalarını tetikleyen acılara göre satın alır. Müşterinizin gece saat 3'te yatağında tavana bakarken hangi problemi yüzünden uyuyamadığını (Gece 3 Sancısı) bulmanın ve ona ürünün özelliğini değil, acısız bir akşamı satmanın formülünü veriyorum.• Dijital İstihbarat ve Rakip Yorumlarını Hacklemek (Review Mining): Masa başında kahve içerek "bence bizim müşteri şunu sever" deme devri bitti. Pazarın lideri olan en dişli 3 rakibinizin Amazon, Trendyol ve Hepsiburada'daki 1 ve 2 yıldızlı yorumlarını nasıl birer istihbarat madenine dönüştüreceğinizi anlatıyorum. Rakiplerinizin lojistik, kumaş veya müşteri hizmetleri zaaflarını alıp, kendi reklam kampanyalarınızda müşteriyi ensesinden yakalayan o yenilmez kancalara (Hook) nasıl çevireceğinizi adım adım gösteriyorum.• Sosyal Dinleme (Social Listening) ile "BS Detector"ü Kapatmak: Anket verilerinin neden her zaman yalan söylediğini, rasyonel ön lob ile duygusal satın alma beyni arasındaki farkı inceliyoruz. Ekşi Sözlük, Reddit ve Kadınlar Kulübü gibi insanların maskelerini çıkardığı platformlara sızarak kitlenin sokak jargonunu nasıl kopyalayacağınızı anlatıyorum. Sizin o plaza dilinizi değil, kendi kelimelerini reklam metninde gören müşterinin zihnindeki "yalan savar" (BS Detector) kalkanını nasıl indireceğinizi deşifre ediyoruz.• Yapay Zekayı Davranışsal Ekonomi Uzmanına Dönüştürmek: ChatGPT veya Claude'u sadece "Instagram metni yaz" diyerek hesap makinesi gibi kullanmayı bırakın. Yüzlerce filtresiz müşteri şikayetini yapay zekaya besleyerek; kitlenin en derin 3 korkusunu, duygusal satın alma tetikleyicilerini ve savunmaya geçtiği kelimeleri saniyeler içinde çıkaran o 2026 model özel "Nöropazarlama Analisti" komutumu (prompt) sizlerle paylaşıyorum.Siz de bu yayını dinledikten sonra e-ticaret sitenizi ve reklam kurgularınızı birer deneme yanılma tahtası olmaktan çıkarıp, salt bir insan psikolojisi ve veri madenciliği matematiğine dönüştürmek istiyorsanız, masadaki parayı rakiplerinize bırakmamak için şu an bu kanalı hemen takip edin ve bildirimleri açın.Bu işin sadece panel boyutunu değil, tüketici psikolojisini ve yapay zeka ile pazar araştırması mimarisini bir meslek olarak en ince detayına kadar öğrenmek istiyorsanız Joy Akademi eğitimlerimize katılın. "Faruk, benim operasyonum var, bu derin psikolojik kurguyu ve reklam matematiğini markam için doğrudan siz kurun ve ciromu büyütün" diyorsanız, joykek.com üzerinden ajansımızla iletişime geçin.

Unsere freien Stellen: https://join.com/companies/broes-media In dieser Folge des Onlineshop Geflüster Podcasts geht es um einen Satz, den ich ständig höre: Ich bin Produktmensch, kein Zahlenmensch. Genau das ist oft der Grund, warum ein Shop irgendwann nicht mehr weiterwächst. Viele Brands starten als kreative Idee oder als Hobby, von Quereinsteigern mit Leidenschaft fürs Produkt und ohne BWL-Hintergrund. Das Bauchgefühl und ein gutes Produkt tragen dich erstaunlich weit, meistens bis irgendwo zwischen 20.000 und 100.000 Euro Monatsumsatz. Ich kenne das gut, ich habe Mathe im Abi gehasst und in meinem eigenen Shop lange nicht verstanden, dass manche Bestellungen unterm Strich sogar Geld gekostet haben. Ab einem gewissen Punkt reicht der Riecher allein aber nicht mehr, um auf 200.000, 500.000 oder eine Million im Monat zu kommen, dafür läuft E-Commerce zu datenbasiert. Die gute Nachricht: Du musst dafür kein Controller werden. Im Kern geht es um drei Zahlen. Erstens, wie viel du für einen Neukunden ausgeben kannst und ab wann er profitabel ist. Zweitens, wie viel Umsatz deine Bestandskunden bringen müssen, um die Fixkosten zu decken. Und drittens, wie viel du pro Tag innerhalb dieser Kennzahlen ausgeben darfst, um deine Ziele zu erreichen. Diese drei Zahlen steuern schon einen Großteil deines Unternehmens. Dein Geschmack und dein Bauchgefühl bleiben deine Stärke, aber sie müssen mit den Zahlen Hand in Hand gehen. Wenn du gerade stagnierst und nicht planbar sagen kannst, woher der nächste Wachstumsschritt kommt, fehlt dir genau diese Struktur. Viel Spaß beim Anhören! Dein Berend. __________ Mache den ersten Schritt und buche dir eine kostenlose SHOPANALYSE: https://www.berend-heins.de/termin __________

Daisy trees, petrels, and pink iguanas... The Galápagos Islands are home to unique endemic species found nowhere else in the world. Sadly, the ecosystems that support them are under threat from invasive species and outright destruction. If something isn't done to turn the tide, species will be lost forever. Luckily, organizations such as Jocotoco Conservation Foundation are hard at work slowing and hopefully reversing this trend. Join me and Juan Alejo Chávez as we discuss the efforts to restore daisy trees (Scalesia pedunculata) and other native plants that comprise this unique forest ecosystem. This episode was produced in part by Chris, Gerald, Elise, Maggie, Mamie, A.J., Dallas, Channele, KC, Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

On this week's Conversation Street, we chat about the episodes of Corrie shown between the 6th and the 10th July (Episodes #11,893 - #11,897). Just a short episode of the podcast this week - by our standards at least - as we're up in Manchester for the Walk For Webster this weekend, we've had a bit of a busy day and we're absolutely knackered! Fortunately, there wasn't too much in the way of massive story twists or revelations to keep us talking in today's episode, although we do delve relatively deeply into Christina's admission that she has a spending addiction - to be honest, we're just pleased she hasn't been up to anything irredeemably sneaky! Also this week, Abi discovers she's got a bit of   a mould issue at her flat that nearly has fatal consequences for Alfie, Will tries to adjust to life after Megan, and Tyrone comes face to face with his long-lost father! 

This podcast covers episodes 11,893 to 11,897. Abi discovers the source of Alfie's illness and it's Idris to blame. Cassie and Tracy's feud is rekindled when Cassie makes plans to propose once more to Steve. Will is distressed when he learns that Megan has already fallen foul of her fellow felons. Christina's mystery calls continue and Glenda sees her suspiciously exiting a stranger's car. Maria is incredibly frustrated at Gary's refusal to tell her the truth. Todd wasn't taking minutes. Kit has a Sonny Crockett jacket. Hope harvests DNA.

Time to dip your foot in the pool of more Hip-Hop music with the QUANTUM LEAP crew! If the streets are betting on Dopeako this week, wiil they secure a win? The Artifacts have gotten complicated. An explanation for Jay-Z and "The Plugs" go on the road with "Abi & Al." New music from Grand Agent, Raz Fresco, El Gant and more... Click play and take the leap!!!Follow us NOW on YouTube, iHeartRadio, Apple Podcasts, Google Podcasts, Spreaker, and more...!!You like what hear..? PROVIDE a donation on @kpft.org (DONATE button)QUANTUM LEAP RADIO broadcasting and streaming live from #HUEston T.X.Every Saturday from 4-6p.m. CST (90.1FM KPFT Houston in HD2) & Thursday 1-3a.m. CST (on the F.M. dial)Worldwide@kpft.org/listen & KPFT APP

In this Meaningful Money Q&A episode, Pete Matthew and Roger Weeks answer listener questions on key UK personal finance topics, including long mortgage terms, pension contributions, ISAs, investing property sale proceeds and planning for retirement with confidence. They explore flexible ISAs, SIPPs, Junior SIPPs, Gift Aid, money market funds and the £100k tax trap, with practical guidance for UK savers and investors. The episode also looks at financial literacy, how to teach money skills, and how to balance pensions, ISAs and accessible savings when building long-term financial security.   Shownotes: https://meaningfulmoney.tv/QA54    01:23  Question 1 Hi Pete & Roger, I'm a chartered management accountant so maybe I should know this but clearly not. I'm wondering is there a financial disadvantage of just taking the longest mortgage deal you can (i.e. 40yrs for example) & then each time it's up for renewal don't worry too much about reducing the term. As long as the mortgage interest rate is lower than the average long term return you'd expect on the stock market (say min 6%), is it not just best to pay lower monthly mortgage payments each month and keep the spare money invested? On a pound vs pound basis aren't you better off? I understand the stock market can go up and down but over the long term I'm struggling to see what the disadvantage is of this strategy, apart from the apparent freedom of being mortgage free. Thanks Jamie   06:45  Question 2 Hi, Why are these things not widely known or discussed? Flexible ISA's. SIPP contributions when retired. £2880+ Rebate. Junior SIPP when worried about Junior ISA end date. I have heard that Parents/Family/Grand parents don't want to pay in to an ISA when you don't know how the child will react to suddenly having control of this ISA money at 18. A SIPP may be a better option. Also one to watch, if you are retired and contributing to charities and tick "Gift Aid" then HMRC may back charge you if you are not paying tax. Emergency fund in Money Market Fund. Regards, Gary   13:00  Question 3 Dear Butch and Sundance   Long time listener, first time caller. Thanks for all you do, filling in the gaps in our financial education that should (but doesn't) start in school.   I'm 56 and looking at my later career options, something that contributes back and can supplement my (early) retirement income. I enjoyed the episodes you did on becoming a financial planner and if I were younger I may well have gone down that route. Instead I would like to help educate people on basic financial good practice. I'm particularly thinking about schools and young people. What options exist in this space, and if they don't exist and I want to create them, what sort of financial qualification would give me a good grounding so that I am not just an enthusiastic amateur.   I'm writing this in February, so if it makes it on to the podcast Merry Christmas everyone! Keep doing what you're doing, it's working. Nick   18:40 Question 4 Hello guys I have been an avid listener for many years, really enjoy the content. I finally have a question of my own. I am about to sell a property which I own outright and would like some advice on where to invest the money going forward, ie bonds, etf's, pensions, ive even considered premium bonds... I would rather spread the money into different pots rather than one product. I understand a pension would be the most tax efficient and I plan to put a small portion into my sipp and max out my s&s Isa however I'd rather be invested in something more flexible I don't intend to utilise the money anytime soon so I want to maximise its potential. I already have been investing in index funds for many years and built up a nice portfolio through s&s isa's. Any advice would be great appreciated Thanks, Paul   22:09 Question 5 Hello Peter and Roger! Thank you for the excellent videos. I listen to them on my daily walks and while cooking, and I always come away having learned something new—so thank you for all the insight you share! I have a question about planning my finances using the Die With Zero approach, especially as I have no children or spouse. I'm 52 this year and hope to hand in my notice in October 2026. I've always been a saver (largely out of insecurity!), so I'd really appreciate your thoughts on whether I have "enough," and—if so—how I can become a more confident spender in the next stage of my life. Here's a brief summary of my situation: I have around £300k across my ISA, general investment account, Premium bonds and cash savings. The allocation is roughly 20% equities / 60% UK gilts / 20% cash. This pot is intended to bridge the gap until my DB pension starts at 60. My DB pension is currently valued at about £18k per year (today's terms) and is inflation‑linked. I also have a SIPP worth around £500k, invested 85% in equities and 15% in money market funds. I have no debts. A small investment property brings in about £1000 a month. My spending target in retirement is about £2,500 per month after tax. ChatGPT has told me that I likely have enough to retire, but I still worry about worst‑case scenarios—war, high inflation, very low future returns for the next 20-30 years (e.g., below 3%), or needing long‑term care since I don't have family support. I value your thoughts before I finally hand in my notice lol. Thanks again for all the work you do. Abi   32:20  Question 6 Hi Pete and Roger, I'm a long time and regular listener and can even remember the time BR (Before Roger) although the modern era partnership has been some of the most entertaining content on the channel. THE CONTEXT I'm 41, married with kids (all out of nursery so no childcare free hours), we have a house with a mortgage. I'm employed full time, putting 19% of salary into my DC pension. I maxed my employer contribution of 8% (with 6% from me) back in 2019 and have steadily increased my contribution each year up to the current 11% (19% total). Currently the pot is worth ~£140k with monthly contributions of ~ £1,550. I'm in the very fortunate position that my salary growth has outpaced inflation and I am now teetering on the edge of the £100k mark. We also receive a variable annual bonus which is targeted at 10%. Pre Covid, we started a stocks and shares ISA, contributing £300/mo but when my wife was furloughed and subsequently made redundant, we had to stop those contributions. Still, that ISA pot has grown to ~£17k. I'd like to build up the ISA to give us flexibility on draw down in retirement but struggling to find the spare cash. Also mindful of creeping over the £100k threshold and reducing my tax free allowance so considering options like sacrificing part of my bonus this year into pension. THE QUESTION So the question, is it worth continuing to increase my pension contribution to 20% and beyond at this stage or start to focus more on building up ISA contributions. Congrats on the success of the Meaningful Money podcast, it is always top of my weekly listening queue and continues to educate and inspire me. Best wishes, Ben

Ein Einser-Abi reicht mittlerweile nicht mehr aus, um damit sicher einen Medizin-Studienplatz zu bekommen. Das sagt der Ehrenpräsident des Deutschen Lehrerverbands Heinz-Peter Meidinger. Weil es einfach zu viele Einser-Abiturienten gibt, die Notenschnitte der Zeugnisse steigen seit Jahren. Ist das Abi also zu einfach und damit wertlos? Darüber sprechen wir mit Bildungsexperte Armin Himmelrath.

Abi-Feiern sind merkwürdige Veranstaltungen. In diesen Wochen sitzen wieder viele junge Menschen in feiner Kleidung zwischen Eltern, Lehrern und Freunden. Es wird applaudiert, umarmt und fotografiert. Stolz liegt in der Luft, aber auch die unausgesprochene Frage: Und jetzt? Wie soll es eigentlich weitergehen? Diese persönliche Sonderfolge ist daher eine ehrliche, motivierende Folge für alle Abiturienten, für alle Eltern und für alle, die gerade vor großen Lebensveränderungen stehen. Als Vater und Unternehmer berichte ich von meinem eigenen Abi 1995 und von dem meiner Töchter heute. Ich zeige, warum das Leben nach dem Abi selten geradlinig verläuft - und warum genau das eine Chance ist. Wir sprechen über die riesigen Veränderungen durch Künstliche Intelligenz, verschwindende und durch KI neu entstehende Berufe - und über die Frage, wie man in dieser unsicheren Welt trotzdem mutig und mit echter Sicherheit in die Zukunft gehen kann. Drei konkrete Tipps gebe ich mit: - Warum physisches Gold und Silber auch (oder gerade) nach dem Abi sinnvoll sein können - Wie du deine eigenen Ideen testest und mutig Umwege gehst - Warum du vor allem in Menschen und Beziehungen investieren solltest ___ Schreib mir gern: post@ronnywagner.com Bei meinem Familien-Unternehmen, der Noble Metal Factory, kannst du Gold und Silber kaufen sowie langfristig per Sparplan in Edelmetalle anlegen. Schau gern vorbei und buch dir ein kostenfreies Beratungsgespräch mit uns: www.anlage-in-gold.de Kostenfrei für dich: Checkliste seriöser Edelmetallkauf & seriöse Edelmetallhändler finden: https://9ytk4f2lg57.typeform.com/to/DTKWecun Gold sicher zuhause lagern: https://9ytk4f2lg57.typeform.com/to/ZkZZgvFB Gold lagern im Hochsicherheitslager: https://9ytk4f2lg57.typeform.com/to/SbJ1JkjZ Checkliste Gold kaufen: 5 Fragen, die du dir stellen solltest, bevor du in Gold investierst: https://9ytk4f2lg57.typeform.com/to/EsJkBWUN ___ Podcast-Team; Ronny Wagner (Host & Redaktion), Anja-Katharina Riesterer (Redaktion), Ulrich Allroggen (Ton & Schnitt)

Dragonflies and damselflies are voracious aerial predators that help keep populations of other insects like mosquitoes in check. These amazing insects also require aquatic habitats to complete their life cycles. Simply put, without wetlands we don't have dragonflies and damselflies. However, not all wetlands will do. My guest Dr. Mary Ann Perron is here to discuss why native aquatic plants are absolutely essential to the success of these insects. Join us as we discuss what makes a good wetland for dragonflies and damselflies and learn what you can do to help them out in your own community! This episode was produced in part by Chris, Gerald, Elise, Maggie, Mamie, A.J., Dallas, Channele, KC, Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Most investors think mid-term rentals are just another Airbnb strategy until they try it and realize the model works completely differently. In this episode, Abi Horton joins Russ and Joey to break down how mid-term rentals actually operate, who they work best for, and the systems that make them either highly profitable or a major mistake if done wrong.Abi shares why she believes mid-term rentals are the sweet spot for investors who want strong ROI without the operational intensity of short-term rentals. She explains how they create consistent occupancy while reducing turnover costs and guest management headaches.The conversation also dives into pricing strategies, property types that perform best, HOA considerations, and how landlords can avoid vacancy gaps.Top three things you will learn: -Why mid-term rentals have strong ROI potential-Why there's a huge demand for mid-term rentals-How matching systems outperform listing platformsThe Rental Strategy Most Landlords Are Missing (free webinar): https://webinar-aros-mtr.webinarninja.com/automated-webinars/24724/registerMidterm Rental Setup Checklist: Get the free checklist by sending a direct message with the word "wealth" to either the Aros Instagram page or Abi Horton's personal page.About Our Guest:Abi Horton is a voice-over artist and a mid-term rental specialist. Having worked directly with families who need housing and landlords trying to fill their properties, Abi decided to build Aros. This platform connects landlords with high-quality, long-stay housing requests from insurance and corporate clients. Disclaimer: The opinions expressed on this podcast are solely those of the hosts and guests and do not constitute financial advice. Always consult a licensed professional for financial decisions.This episode is sponsored by a podcast show partner. We may receive compensation if you use links or services mentioned in this episode.The hosts may have a financial interest in the programs or services mentioned in this episode.Connect with Abi Horton:Instagram (Aros) - https://www.instagram.com/stay.aros/Instagram (Abi Horton) - https://www.instagram.com/theabihorton/Build a Passive Income Machine in 3 Steps:Here's how to flip the script and start building wealth the way the wealthy do

Join an active community of RE investors here: https://linktr.ee/gabepetersenWHAT IS MIDTERM RENTAL INVESTING AND WHY IT MATTERS

Stroke survivor Shalini Aggarwal shares her powerful story of sudden stroke, intensive recovery, and rebuilding her life step by step. She talks about the early challenges, the importance of support, and how faith and mindset keep her moving forward. A moving reminder that recovery is ongoing, and resilience is built along the way. Guest Social Media info -  https://youtube.com/@booboowithshamuoyeah and https://www.instagram.com/shaliniaggarwal  Send us Fan MailSupport the showYou can find this episode's transcript here.New episodes drop every other Thursday everywhere you listen to podcasts. 

Topics covered in this episode: Free-threaded Python: past, present, and future django-admin-site-search Qwen 3.6 27B is the sweet spot for local development A large batch of PEPs are finalized Extras Joke Watch on YouTube Show Intro Sponsored by us! Support our work through: Our courses at Talk Python Consulting from Six Feet Up Connect with the hosts Michael: Mastodon / BlueSky / X / LinkedIn Calvin: Mastodon / BlueSky / X / LinkedIn Show: Mastodon / BlueSky / X Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Tuesday at 7am PT. Older video versions available there too. Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Calvin #1: Free-threaded Python: past, present, and future The GIL has prevented true multi-threaded parallelism in CPython since the beginning — multiple past attempts to remove it failed on performance grounds Sam Gross at Meta finally solved it; his work became PEP 703 and ships as free-threaded CPython today Python 3.13 was experimental with 20–40% single-threaded slowdown; 3.14 brought that to 0–10% Python 3.15 (October 2026) delivers a unified ABI — one extension binary works on both GIL and free-threaded builds Already >50% of the top PyPI binary wheels support free threading Wouters predicts free-threaded becomes the default between 3.16–3.20 (2027–2031), with the GIL eventually disappearing next decade Michael #2: django-admin-site-search via Adam Parkin A global/site search modal for the Django admin, by Ahmed Aljawahiry. Hit cmd+k anywhere in the admin and you get a command-palette-style search window, kind of like the one in VS Code. It doesn't just search one model's list page. It searches your entire site in one box: App labels Model labels and field attributes Actual model instances (your data) Two ways to search the instances: model_char_fields (the default): runs an __icontains across every CharField (and subclasses) on the model. Zero config, works out of the box. admin_search_fields: defers to each ModelAdmin's existing get_search_results(), so it respects the search_fields you've already set up. The part I like: it's permission-aware out of the box. Users only see results for the apps and models they actually have view permission on, so you're not leaking anything through search. Results appear as you type, with throttling/debouncing so you're not hammering the server on every keystroke, and it's full keyboard nav: cmd+k to open, up/down to move, enter to go. It's responsive, does dark and light mode, and it pulls Django's built-in admin CSS variables so it just matches whatever admin theme you're running. Under the hood it's Alpine.js, but bundled into static so there's no external CDN dependency. Setup is about what you'd expect: pip install django-admin-site-search, add it to INSTALLED_APPS, mix the AdminSiteSearchView into your AdminSite, and drop a few template includes into base_site.html. Supports Python 3.8 through 3.14 and Django 3.2 through 6.0, MIT licensed, and everything is overridable if you want to skip certain models, add TextField matching, etc. Calvin #3: Qwen 3.6 27B is the sweet spot for local development Qwen 3.6 27B is being called the first local model that genuinely competes as a general-purpose intelligence — benchmarks put it at roughly mid-2025 frontier level (comparable to GPT-5 / Claude Sonnet 4.5) Runs locally via llama.cpp; on an M5 MacBook Max with 8-bit quantization + multi-token prediction, it hits ~32 tokens/sec using ~42GB RAM 4-bit quantization gets it under 18GB, runnable on 32GB devices; Nvidia RTX cards run it even faster The dense 27B is recommended over the faster MoE 35B A3B — author prefers higher quality output over raw speed Privacy and reliability are the pitch: fine-tunable, can't be taken down, suitable for sensitive/proprietary data Author sees this as a stepping stone — frontier open-weight models like GLM 5.2 are now locally runnable with company-grade hardware, and smarter-still local models are coming Michael #4: A large batch of PEPs are finalized A bunch of PEPs went from accepted to final. 668, 687, 691, 699, 701, 703, 728, 770, 773, 829 But this wasn't them making their way into CPython. It's an admin sorta thing. (Thanks PyCoders) See the commit. Extras Calvin: More fun bling for your terminal this time - https://charm.land/ Michael: Follow up from pls, What the pls? Thanks Pito. Joke: BEMoji A production-grade utility and component framework built entirely on emoji class names via Jeff Triplett

Disturbances from fire and wind to insects and humans play a huge role in forest dynamics through time. Throw in the impacts of climate change, and these dynamics only get more complicated. Understanding how disturbances interact and influence how forests change through time is of great interest to people from all walks of life and that is why people like Dr. Kenneth Anyomi are hard at work studying them. Join us for a deep dive on how disturbances influence forest succession and the lives that depend on it. This episode was produced in part by Chris, Gerald, Elise, Maggie, Mamie, A.J., Dallas, Channele, KC, Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Abi and Matt talk about a movie they've already talked about. 

We're excited to have Databricks join us at AIEWF, among hundreds of the top companies in the AI Engineer ecosystem. LS subscribers can use their discount to get past the late bird pricing and access over $50k in sponsor offers! Everyone is still talking about Satya's Frontier Ecosystems post, but few have actually built a (now $175 billion) frontier ecosystem and cloud like our guests today.From open-sourcing the layer above coding agents to rethinking databases for the agent era, Databricks cofounders Matei Zaharia and Reynold Xin are pushing the company beyond the lakehouse into a full data-and-AI operating system. In this episode, Matei and Reynold join swyx at the 2026 Data + AI Summit to unpack Omnigent, LTAP, Lakebase, agent security, open formats, Mosaic, and why databases may matter more than ever once AI agents start doing real work.We go deep on Omnigent: Databricks' open-source meta-harness for combining, controlling, and sharing agents across Claude Code, Codex, Cursor, Pi, custom agents, and internal tools. Matei explains why coding agents and enterprise agents run into the same problems: portability, collaboration, session history, security, spend controls, and the need for a common API above every harness.Then Reynold walks through Databricks' database dream: why CDC is brittle enough to joke that it means “continuous data corruption,” why HTAP has been the holy grail of database engineering, and why Databricks thinks LTAP gets most of the benefits by unifying the storage layer instead of collapsing every query engine. We also cover Databricks' infrastructure scale, the culture behind rapid prototyping, the difference between tech and enterprise customers, Databricks vs Snowflake, whether vector databases should have ever existed, the Mosaic model strategy, Genie, AI Runtime, RL fine-tuning, and the thesis that traditional software gets rewritten once the data is in the right place and agents sit on top.Databricks began as a company for the big data era. The origination of Spark from the Berkeley AMPLab which eventually turned into the product Lakehouse convinced enterprises that they didn't need a separate data lake, warehouse, ML platform, and governance layer. They just needed one open foundation where all of their data could live and be reasoned over.Since then a lot has changed, but data has only become more important. Data is no longer something you keep track of and analyze ad hoc, it's the necessary context agents need in order to act. So the framing has shifted from “where do we put all of our data?” to “how do we expose the right slice of state, history, permissions, and business logic to an AI system at the exact moment it's doing work?”If frontier model performance becomes commoditized, the durable advantage then becomes the company-specific context around them: proprietary data, governed access, operational state, transaction logs, workflows, and feedback loops. Which makes Databricks positioned perfectly.Now coming fresh off the Data + AI Summit 2026, the company is moving just as fast to keep up, announcing Genie One, Omnigent, LTAP, and many more, indicating a central mission in its newer work: Databricks is trying to become the operating system for enterprise agents.Models are getting good enough, but agents are only useful if they have the right context, permissions, memory, state, cost controls, and access to live business data. Fundamentally it appears that significantly better model performance in production is a systems problem, one that data guys like us are remarkably well prepared to solve!We discuss:* Why Databricks built Omnigent as a meta-harness above existing AI agents* Why coding agents and custom enterprise agents need the same infrastructure* The common API for agent sessions, files, streams, tool calls, and cancellation* Why persistent sessions, cloud sandboxes, sharing, search, and collaboration matter* Why Databricks open-sourced Omnigent instead of keeping it proprietary* Databricks' internal agent usage, cloud sandboxes, and coding workflows* The scale of Databricks: 50–60 million virtual machines a day and exabytes before breakfast* Why agent security needs contextual and stateful policies* How an agent could read confidential docs, install a compromised npm package, and leak data* Why spend control matters when an agent can burn $500 reading logs* Startup opportunities around coding-agent analytics, quality, skills, and spend* LTAP, Lakebase, and why Databricks wants to rethink the database stack* OLTP vs OLAP, CDC, and why data pipelines break at 3 a.m.* Why HTAP has historically been the holy grail of database engineering* Why Databricks thinks LTAP is “HTAP done right”* How writing transactional data into column-oriented formats changes analytics* Why agents need live operational context from databases, not just telemetry* How Databricks prototypes strategic systems without endless process* Enterprise vs tech customers, governance, procurement, and DIY culture* The “second system syndrome” risk of rewriting a database engine* Building a database engine from a decade of traces and quadrillions of data points* Why vector databases should never have been a separate category* Why open formats and AI changed the race with Snowflake* The Mosaic story, DBRX, Genie, document parsing models, and specialized model training* Why model customization and RL fine-tuning may become mainstream* Why “get the data there, slap some agent on top” may rewrite traditional softwareMatei Zaharia* LinkedIn: https://www.linkedin.com/in/mateizaharia* X: https://x.com/matei_zahariaReynold Xin* LinkedIn: https://www.linkedin.com/in/rxin* X: https://x.com/rxinDatabricks* Website: https://www.databricks.com* X: https://x.com/databricksTimestamps00:00:00 Introduction00:02:22 Omnigent and the Agent Infrastructure Layer00:08:39 Agent Clouds, Common APIs, and Open Source00:16:52 Databricks Scale and Internal AI Workflows00:18:03 Agent Security, Governance, and Spend Controls00:27:34 LTAP and the Database Dream00:30:30 CDC, HTAP, and Why Data Pipelines Break00:34:05 Lakebase, Parquet, and Live Data for Agents00:36:47 Databricks' Culture of Fast Prototyping00:43:40 The Dream Engine and Rewriting the Database Stack00:51:02 Vector Databases, Query Engines, and LTAP00:52:36 Databricks vs Snowflake00:57:48 Mosaic, DBRX, Genie, and Specialized Models01:03:11 Context, AI Runtime, and RL Fine-Tuning01:06:15 Why Data + Agents May Rewrite Software01:07:09 Closing ThoughtsTranscriptIntroduction: Databricks, Data + AI Summit, and Founder DynamicsSwyx [00:00:00]: Matei and Reynold from Databricks, welcome to Latent Space.Reynold Xin [00:00:06]: Hey, thanks for having us.Swyx [00:00:07]: Yeah.Matei Zaharia [00:00:08]: Yeah, thanks so much.Swyx [00:00:09]: thanks for taking time out. You have your Databricks, Data AI Summit going on. You were just telling me how the first summit that you guys ran was just 50 peopleReynold Xin [00:00:17]: Yeah, it wasSwyx [00:00:17]: in BerkeleyReynold Xin [00:00:18]: little meetup at Berkeley, I thinkMatei Zaharia [00:00:19]: YeahReynold Xin [00:00:19]: put togetherMatei Zaharia [00:00:20]: We were doing these tutorials and, yeah, just teach people Spark.Swyx [00:00:23]: Yeah. obviously now it's like, I think like the headline number's like 100,000 people around the world, 30,000 in person.Swyx [00:00:30]: it's a crazyMatei Zaharia [00:00:31]: AmazingSwyx [00:00:31]: community. Well, I just saw the keynote.Swyx [00:00:35]: Ali's just. Did was it obvious or that back when that Ali would be, like, such a great, like, CEO? LikeReynold Xin [00:00:42]: OhSwyx [00:00:42]: such a great presenter?Reynold Xin [00:00:43]: What do you think?Matei Zaharia [00:00:44]: I think among our group of founders it was clear that, I think he'd be the best at this.Swyx [00:00:50]: Yeah.Matei Zaharia [00:00:50]: And yeah, it turned out great. And he's, he's ramped up on so many topics growing a company. He would just go in and, like, study it and, be talk to all the experts. Like, even if he can't hire the person, learn enough about, like, finance and sales and whatever it was, and, and go from there. Yeah.Swyx [00:01:09]: Yeah.Reynold Xin [00:01:10]: he's obviously very high IQ and a very high EQ, but it wasn't. Like, Ali today is quite different from Ali from, like 10 years ago. I think there's a lot of work that he put in to, get to this point.Swyx [00:01:20]: Yeah. no, to me the most appealing thing about him is that he's funny. And like, it, it's, it'Matei Zaharia [00:01:26]: It's true, yeahSwyx [00:01:26]: it's hard to make jokes about, data warehousesReynold Xin [00:01:30]: About serious topicsSwyx [00:01:31]: securityMatei Zaharia [00:01:32]: YeahSwyx [00:01:32]: what have you.Matei Zaharia [00:01:33]: Oh, yeah. That's for sure.Swyx [00:01:34]: Yeah. So you guys launched a whole bunch of things. I'll, I'll just name check briefly, the stuff because we're not gonna cover everything. Omnigentt, your baby. LTAP, your baby, your dream engine.Swyx [00:01:47]: we're also gonna cover Genie, cover CustomerLake, you acquired PantherMatei Zaharia [00:01:52]: YeahSwyx [00:01:52]: Open Sharing, and there's Unity AI Gateway. A lot of these, I think, like, are things that you would expect a Databricks to do. It's, it's like part of the roadmap. Everyone in your category has similar things. But I think, probably the two of you are leading the two most unique and differentiated initiativesOmnigent and the Agent Infrastructure LayerSwyx [00:02:09]: on, in the landscape. Maybe we'll start with, Omnigentt we'll, we'll, we'll, we'll go into it. I do think that a lot of people are exploring this meta harness concept.Matei Zaharia [00:02:21]: Yeah, totally.Swyx [00:02:21]: What led you to it?Matei Zaharia [00:02:22]: Yeah. There were a couple of, like, converging lines, which I think is a good sign that you need something new. So on the one hand, there's all the coding agent info internally. We have really great, dev infra team. they built something called Isaac, that's like a wrapper on Claude Code and Codex, and, lets you use them either on the web in, like, sandboxes or, just on your dev machine or on your laptop or whatever. And then, they were adding all kinds of stuff there. And we saw all the more advanced engineers like, were building their own workflows with tons of agents, and they were building their own UIs and stuff on top or even on top of that. And then the other one was, like, us building agents. We ship this, like, data science agent called Genie on the research team, which I lead. We also build a lot of internal ones for various things, and then we have all the customer ones. And all of them running into this thing of like, “Oh, I need to switch model and harness and so on,” every few months. Plus the agent is, like, completely useless if you can't share sessions with someone and have history and have search and all this, like, layer on top of it for collaboration. I thought a bit about it from both contexts and, at first people thought it was weird. They're like, “Why are you doing coding agents and custom agents in the same thing?” But I said it's, it's the same problems and, you just wanna build the stuff that lets you deliver the agent, maybe control it if you care about security, and, make it portable across things. And then we prototyped some things as experiments. We saw, yeah, we can make it work, and then we built that for real.Swyx [00:04:06]: I'm wondering if this let's call it architectureMatei Zaharia [00:04:11]: YeahSwyx [00:04:11]: maps to anything in your careers in the past. like I always think about how a lot of things just tie back to operating systems.Swyx [00:04:18]: A lot of operatingMatei Zaharia [00:04:19]: YeahSwyx [00:04:20]: systems tie back to databases,Matei Zaharia [00:04:21]: SoSwyx [00:04:21]: or the other way aroundMatei Zaharia [00:04:22]: so the thing, I do think it ties a lot to, like, network protocols, internet protocol. we alsoSwyx [00:04:29]: Communication between entities.Matei Zaharia [00:04:30]: Yeah. We did stuff with, like, data sharing also, which is probably, most viewers probably won't know unless they'Swyx [00:04:36]: Yeah, open protocol is the term.Matei Zaharia [00:04:37]: Yeah.Swyx [00:04:38]: Open sharing. Open sharing.Matei Zaharia [00:04:38]: Open sharing.Swyx [00:04:39]: Yes.Matei Zaharia [00:04:39]: Yeah. So it's like you have a company, you maintain some table, like let's say like a Walmart or something. They have like the, inventory and what's been sold in each store. And then you also have suppliers, and they would love to produce more things and ship them, like, exactly the moment you need them. So they would love, like, real-time access to your table. So instead of like sending emails around or Excel sheets or phone calls, why can't you share like a view of that table in real time with them? Then they query, they, join it with their data, and they decide what to send. So it's one of these things where you, like you might ask like today since we can vibe code anything so fast, why do we even need to design like protocols or APIs or software? Why can't you just vibe code things on demand? But for this type of interoperability where multiple parties that are moving at different speeds are building stuff and you still want some layer on top to coordinate, you do wanna design it and build it. So it reminds me of that, like agents talking to each other and, users talking to agents and tools.Agent Clouds, Cloud Sandboxes, and Keeping Sessions AliveSwyx [00:05:42]: Reynold, any other comments alternative viewpoints?Reynold Xin [00:05:46]: I think, by the way, we had a debate on exactly which set of benefits would, matter a lot, and I think around the time we decided to do this thing I was telling Matei, “Hey,” it just happened to be there's a particular week that I was coding nonstopSwyx [00:06:00]: from the moment I woke up to, like, the moment I went to bed, I was, like, looking at my Claude sessions, my Codex sessions. And one of the things that was particularly annoying was having to keep my laptop open.Swyx [00:06:12]: I was driving to a doctor's appointment, and I remember because I wanted to make sure the whole thing continues working.Matei Zaharia [00:06:18]: But by the way, it's so comforting to hear you say that because I'm like, “I don't know if I'm a clown and I'm doing this or like.”Swyx [00:06:25]: Yeah. Like honestly, I was driving and I was tethering my laptop to my phone.Matei Zaharia [00:06:29]: huh.Swyx [00:06:29]: Keeping it on the side. Whenever I hit a red light, I started looking at what's going on my laptop.Matei Zaharia [00:06:35]: Yeah.Swyx [00:06:35]: And I just felt that was ridiculous.Matei Zaharia [00:06:37]: Yeah.Swyx [00:06:37]: It felt like we went back to the dark agesMatei Zaharia [00:06:39]: YeahSwyx [00:06:40]: programming. the productivity you gain from all this coding age is amazing, but, yeah.Matei Zaharia [00:06:45]: Have you heard of cloud?Swyx [00:06:47]: Yeah.Swyx [00:06:48]: It was crazy to me.Matei Zaharia [00:06:49]: Oh, the thing you were working on was the sandboxes or was this before that?Swyx [00:06:52]: It was a sandbox.Matei Zaharia [00:06:53]: Okay.Swyx [00:06:54]: I was workMatei Zaharia [00:06:54]: So you were inSwyx [00:06:55]: So I was approaching from a very different angle. I wanted to, “Hey, we're gonna have cloud sandboxes that doesn't shut down. You can get one very quickly,” but not just for running agentic sessions.Matei Zaharia [00:07:06]: Yeah.Swyx [00:07:06]: It's also for running development. So I was personally building that week, and through building that, I ran into all these issues, and then I wroteMatei Zaharia [00:07:15]: YeahSwyx [00:07:15]: a document for Matei, it's like, “Here's my wish list of what the actual environment should do.” And I think he ended up almost implementingMatei Zaharia [00:07:22]: YeahSwyx [00:07:22]: every single one of them.Matei Zaharia [00:07:23]: Yeah, I remember Reynolds saying, ‘cause my first prototype of this had just chats with your agent and he said, “I have to be able to open a shell, like my own shell and like list files and like tail them and stuff.” SoSwyx [00:07:36]: So SSH into a mainframe.Matei Zaharia [00:07:37]: Yeah. it has that now.Swyx [00:07:39]: Tailing my log.Matei Zaharia [00:07:40]: Yeah.Matei Zaharia [00:07:41]: Yeah.Swyx [00:07:41]: And also another thing I think I asked was, I had. I still use cursor for the sole purpose of rendering markdown files.Matei Zaharia [00:07:48]: huh. Yes.Swyx [00:07:49]: So I said, “If you just give me a way to see my markdown files and renderMatei Zaharia [00:07:53]: YeahSwyx [00:07:53]: them properly, I don't need a separate tool anymore.”Matei Zaharia [00:07:55]: Yeah.Swyx [00:07:56]: And I think you also built that in.Matei Zaharia [00:07:57]: Yeah, we, yeah, we did that, yeah. Yeah, we had a lot of engineers building, their own vibe coding setup. But then the other thing they all said is like, “Hey, I built something that's amazing for me, but, like, no one else on the team can use it ‘cause I don't have a server to collaborate.” And this is why we tried to set up, Omnigent, so you can have a server and have the security, set up in there. So, like log in with Google or whatever and, like securely share stuff. which. And that's where we've seen a lot of other agents like hit things. Like people think they prototyped an awesome agent, but it's not allowed to connect to like some really important data or whatever because of the security team.Omnigent Architecture, Open Source, and Common APIsSwyx [00:08:38]: Yeah.Matei Zaharia [00:08:38]: So yeah.Swyx [00:08:39]: Yeah. At this point, so for those watching along on YouTube, we're gonna putting up a image of the structure here, and we can talk a little bit of the architecture. I think I just want to have people understand, ‘cause like when we're talking about software, it can be very abstract and like here is what we're talking about. You've worked out in open source this entire platform and there's a runner component and server component with a uniform API that you've, you've figured out. any other element and obviously you can plug in all this, persistence layers and compute layers. This is a whole cloud. It's an agent cloud.Matei Zaharia [00:09:12]: Yeah. It's, it's got these components to work with it. The, a lot of the action happens like on the machine where you deploy your agent too. So whatever you've got on there, you can run. But yeah, it's, I think it's the minimal thing you want to have hosted, like collaborative agents and to have that server. And one of the reasons we open sourced it is, anyone building agents, this gives them an app they can start with and customize, which we were seeing in Databricks too. Like someone would make a nice, agent app and then other teams would ask, “Oh, can I just use yours for my agent?”Swyx [00:09:45]: Yeah, I think we had like five or six different agentic frameworksMatei Zaharia [00:09:48]: YeahSwyx [00:09:48]: built by every different team. They do all do more or less the same thing. Yeah, you need to. people wanna take something that works in Forkit, and you might as well have something open source. Yeah, which also was another question, which is interesting for Databricks. Like what do you choose to open source? What do you choose to make it proprietary? It's in. this goes back to Spark, right?Matei Zaharia [00:10:05]: Yeah.Matei Zaharia [00:10:06]: One, so one of the reasons to open source something is if you think it's a layer that will there'll be some network effect, it'll benefit from many, people collaborating, on it. So, for example, with Spark, I don't know if when Spark came out, we also focused a lot on letting you have libraries on top. So like there used to be differentSwyx [00:10:28]: EcosystemMatei Zaharia [00:10:28]: distributed computing engines for like machine learning and graph computation. We said they should all be libraries that you can compose. And we made it super easy to add connectors to data sources too. And then we benefit because, we don't have the time to write like connectors to like, 1,000 like different databases and file formats, but we can just use the ones people make, and of course they benefit from joining, this thing. So that's like one of these as it. Another way to think about it is like imagine, we our thing wasn't open. We had some agent hosting thing, but it's not open and then there is an open one. if you're. Which one's gonna win in the long run? So like here, because there is this benefit from like people writing integrations, it'll be, it'll be that. And then there are other things that like you just can't, even deliver as open source that are things the company does. Like for example, how do you make sure you're like streaming, jobs or your Lakebase database doesn't like, lose all your data at night? Well, that requires an operational team that's gonna sit there. There's no way it has to be a service. So like we wanna make sure as a company we're really good at those infra services and then we're as open as we can in terms of like what you build on top.Swyx [00:11:42]: speaking from a benefits, I think we are already seeing pull requestsMatei Zaharia [00:11:45]: YeahSwyx [00:11:45]: of all kinds of ecosystem integration, even though it was only released on Saturday.Matei Zaharia [00:11:50]: Yeah, Saturday. Yeah. So someoneSwyx [00:11:51]: Let's see, let's see what's going on. Yeah, you can look at the merge ones. I asked Sam Nigon this morning aboutMatei Zaharia [00:11:59]: 400 merge already?Matei Zaharia [00:12:00]: Yeah. I think Recent quite, I would guess around half are not from our team. but for example, someone added support for running it on Kubernetesrnetes. people added, many cloud sandboxes, so this can launch a cloud sandbox and run your agent in there, which is great for sharing too, ‘cause it's not, like, on your laptop and someone's, like, running scary code on there. so yeah, many startups have put those in, and, we expect to see more of them. We also have more agent harnesses already. Cursor, CLI, and Antigravity also.The Modern Data Stack and the Emerging AI StackMatei Zaharia [00:12:34]: Yeah. That's all, beautiful. And I, I feel like the last time this happens, there was the rise of the modern data stack.Matei Zaharia [00:12:42]: I don't know if it's that useful. I'm, I'm curious in your postmortem.Matei Zaharia [00:12:46]: I think most peopleSwyx [00:12:47]: AgreeMatei Zaharia [00:12:47]: will agree that it is finally dead. but maybe this arises to a new modern AI stack that, like, does the same thing.Matei Zaharia [00:12:52]: I don't know.Reynold Xin [00:12:54]: I think the modern data stack was a pretty useful thing, probably even up until this day. I think what, maybe for the audience who don't understand the history, I think the modern data stack is effectively decomposed into you need a layer to ingest the data in, you need a layer to transform your data, and then all of this are run, and then you need a layer to maybe visualize your data. And all of this runs on some data warehouse, or later on, as we're doing data warehouse or lakehouse.Reynold Xin [00:13:21]: I think that concepts are all very powerful and very useful. They enable a lot of workloads. What people eventually run into is a question of unification and consolidation is, hey, do you really need to chop all this into different pieces and work with so many different vendors and platforms in order to get, like, a very simple visualization done, right? So I think, like, over time, everybody started realizing that customers are pushing us. We started, we can realize that, so we started building more and more capabilities and trying to consolidate. And at the end of the day now, customers don't have to worry about having me hook up five different systems in orderMatei Zaharia [00:13:55]: YeahReynold Xin [00:13:55]: produce a chart. But the. I think, honestly, something like this is probably happening, in how many different frameworks do you want to hook up together in order to produce, like do a very simple agent.Matei Zaharia [00:14:06]: Just to be clear, I would say the core of this is this common API on top of all the harnesses. So the API is like, you've got an agent session, and you can send in a message or, like, a file. That's what you can send in, and then you get out, these streams as it's streaming text or as it's doing tool calls. And, or the other thing you can send in is you can, like, tell it to cancel a turn. So that's the API. Now, the thing we did is we could get you that on top of, like, cloud code running in a terminal, Codex, Py, OpenAI SDK, all that stuff. We map them all to that same interface. So that is something that you'd have to maintain yourself if you built your own, like, agent orchestrator, and then whenever cloud changes its API, you gotta, tweak your thing or it's gonna lose some messages. So that's the thing that's valuable to maintain. Then on top of that, like, we built a few apps. I think we built a pretty cool UI and stuff, but that's, And we built a security and control piece, which I'm excited about. But it's that common interface, so we don't. We. That doesn't try to be a stack. And in fact, you could plug in your own UI on top of this, server. That, and that's one of the use cases we care a lot about, ‘cause we want to use this in our own products.Compute, Sandboxes, and Databricks ScaleSwyx [00:15:20]: Yeah. It should be everywhere.Matei Zaharia [00:15:22]: Yeah.Swyx [00:15:22]: I think one of those things that is really interesting to me is, like, well, first of all, I'll, I'll endeavor to do everything and not call it the modern AI stack because like it needs a different name.Matei Zaharia [00:15:32]: Yeah.Swyx [00:15:32]: But like, yes, like, so one of the first people that told me about compute, sandboxing was Nikita from Neon.Swyx [00:15:39]: Because a lot of people think about Neon as like, well, it's serverless Postgres with, like, the separation of compute and storage and, instant branching and all those things. But every database company is also a compute company.Matei Zaharia [00:15:51]: Yeah. Yeah.Swyx [00:15:52]: And so he was showing to me his whole, his sandboxing solution. I don't think he have ever launched it.Matei Zaharia [00:15:57]: So our sandbox solution, the reason we could build it so quickly was because we realized if you just take the actual Lakebase architectureSwyx [00:16:05]: YeahMatei Zaharia [00:16:05]: and remove the database from it, by the coming from NeonSwyx [00:16:08]: Exactly, rightMatei Zaharia [00:16:09]: you have this sandboxSwyx [00:16:09]: Every database company has it already, yeah.Matei Zaharia [00:16:11]: Now, there are some differences. For example, in the one to support this particular workflow, it's important to have local persistence,Swyx [00:16:19]: YeahMatei Zaharia [00:16:19]: because you want your state to persist. Your libraries, you don't have to install your library every time, right?Matei Zaharia [00:16:24]: whereas the Neon architecture, because of the separation of storage from compute, you don't need persistent local disk.Swyx [00:16:30]: Yeah.Matei Zaharia [00:16:30]: So there's some differences.Swyx [00:16:32]: Yeah.Matei Zaharia [00:16:32]: But the, at the end of the day, yeah, it's, Yeah, so this is when you run, like, a coding sandbox. Like, if I use it, yeah, we have the dev env internally at Databricks. There's, like, many, like, tens of gigabytes of data just for, like, all the source code and, like, artifacts and stuff that I built, and I want that to come back next time, so.Matei Zaharia [00:16:51]: Yeah.Matei Zaharia [00:16:51]: But yeah.Matei Zaharia [00:16:52]: Before the show, we was talking about some statistics that might be surprising at the adoption.Matei Zaharia [00:16:56]: It could be internal, it could be external, whatever comes to mind, just to impress people the scale this is happening.Swyx [00:17:02]: So we, on the analytics side, I think we launchedReynold Xin [00:17:06]: Maybe 50 or 60 million virtual machines a day across all three clouds, so we're one of the biggest compute orchestrators out there.Reynold Xin [00:17:13]: Stuff for sure for CPU compute.Swyx [00:17:14]: Yeah.Matei Zaharia [00:17:14]: Yeah.Reynold Xin [00:17:15]: the. And all of this process, I think exabytes of data, I joked about depending on which time zone you are, typically before you have breakfast, Databricks would have processed exabytes of data already on that day. and on Neon, it's pretty interesting, too. It's launching, I think, 13 million databasesSwyx [00:17:34]: YeahReynold Xin [00:17:34]: a day now.Swyx [00:17:35]: Yeah, to me that was, like, aReynold Xin [00:17:36]: And that's just likeSwyx [00:17:37]: Like, what do you mean?Matei Zaharia [00:17:38]: Yeah. And that's the point.Reynold Xin [00:17:40]: And a lot of those were thanks to agent- agents and branching experimentationSwyx [00:17:44]: YeahReynold Xin [00:17:44]: because we made it so easy and so quickly, and thanks a lot to Nikita's team, to launch databases. It's, the. So it's changing the way people use databases.Swyx [00:17:54]: Yeah. Okay, we're gonna go into more database talk in a bit, but I wanna make sure we close up anything on Omnigentt. you mentioned, you were excited about the securityOmnigent Security, Contextual Policies, and Spend ControlsSwyx [00:18:03]: control side.Matei Zaharia [00:18:04]: Yeah.Swyx [00:18:04]: a lot of companies are figuring that out right now, as well as the spend side.Matei Zaharia [00:18:08]: Yep.Swyx [00:18:09]: what have you found there?Matei Zaharia [00:18:11]: Yeah, so I spent quite a bit of time talking to internal users, developers, security team, managers, and also lots of customers, and there's a few things. Like, first of all, one thing, that immediately was. became obvious is for security, there's this tension between, like, usability and security. And, the way people do. Like, a lot of coding agents today have very basic things like you can tell me which tool patterns I'll allow or disallow or whatever. It's like yes or no. But that puts you in a very tough spot. So just as an example, like, should my agent be able to read, some confidential documents, or let's say, should it be able to install new packages from npm, which, maybe it's compromised. Yes or no? Like, maybe I wanna allow it. Should my agent be able to publish stuff to the company website? Well, if I'm using it to code on the website, yes. But should it be able to do both, so it can, like grab a confidential document and be prompt injected and leak it? Probably not. So the thing we decided we need is stateful or what we call contextual policies where you keep track of the state of that session. It's not like is it allowed to push to the marketing site or not, but, like, hey, if it did a risky thing, like it installed, a old package from npm, or it read, like, 1,000 confidential docs, then no. Then don't, don't do it. Otherwise, maybe it's okay. That's one example of, like, moving that trade-off so it's both more secure and more useful by having a more powerful engine, essentially. This requires tracking sessions. The other piece that was interesting there is, like, there are these very level events it's doing, and you want some libraries on top that parse them. Like, for example, we have a, MCP server on Google Drive internally. It's got 60 API calls. like, how do I know which of those, like, will share a document with stuff on the internet and which ones won't? It's, it's annoying. So we designed in Omnigentt the policy layer so that it's functions and you can have libraries. Like, someone can make something that maps the level events to high-level ones, and then you write a policy about the high-level things that came out. so and thatSwyx [00:20:25]: This is related to the Panther,Matei Zaharia [00:20:27]: Yeah, Panther is. will help with that. PantherSwyx [00:20:30]: YeahMatei Zaharia [00:20:30]: a similar idea on the event processing side, and it's Python-based versus a weird custom language. this is more, as in realSwyx [00:20:39]: I didn't even know we were good yeah.Matei Zaharia [00:20:41]: Those things are happening, yeah.Swyx [00:20:42]: Yeah.Matei Zaharia [00:20:42]: So yeah, but these are the cool things. I think the contextual or stateful part, and then the way it can be libraries, and that was another reason to make it open source because others will write libraries and, like, we and our customers can use them. And the final thing, because it's stateful, one of the states we track is how much you spent in that session. So I can. I've had, like, I ask an agent to debug something, and it spent $500 because it decided to read a lot of log files and burn a lot of tokens. but I can literally say, “Okay, launch a agent to do this and cap it to spending $5.” Like, ask me for permission if it needs more. And because we're counting that within that session, it'll pop up and tell me, “Okay, you spent five, $5. Do you wanna go on?”Reynold Xin [00:21:27]: So important context here. Matei spent the last five years, a lot of his time was architecting Unity Catalog at DatabricksMatei Zaharia [00:21:34]: YeahReynold Xin [00:21:34]: which is the governance layer for data.Matei Zaharia [00:21:35]: That's right, yeah.Reynold Xin [00:21:36]: And he's combining expertise at that layer together with all the AI governance he knows.Matei Zaharia [00:21:41]: Yeah.Swyx [00:21:41]: DoMatei Zaharia [00:21:41]: But I also spent a lot of time being annoyed by coding agents and getting prompts.Matei Zaharia [00:21:46]: And also as theReynold Xin [00:21:48]: All the aboveMatei Zaharia [00:21:48]: I don't want to end up on the front page as, like, I installed some weird npm package and leakedSwyx [00:21:53]: YeahMatei Zaharia [00:21:53]: all the code, so I'm especially paranoid. But also I have very little time, so I don't want to sit there approving, like, do you want to run a 20-line, bash script, yes or no? so that's why I spend a lot of time figuring out, like, how can I make it as safe as possible and not annoying?Swyx [00:22:10]: Yeah. Is safety and mmm, let's call it security a bigger concern than token maxing or token budgets? which one is, likeMatei Zaharia [00:22:19]: Oh, yeah, they're both there. I don't know. I guess it depends on the type of company you are. So I think, some companies, like, the budget is, limited and, they really care about thatSwyx [00:22:34]: you can be Uber and still be concerned?Matei Zaharia [00:22:36]: Yeah. Oh, yeah, totally. Yeah. If you haveReynold Xin [00:22:38]: for us, securityMatei Zaharia [00:22:39]: YeahReynold Xin [00:22:40]: super paramount.Matei Zaharia [00:22:40]: For us, security is absolutely critical as a, cloud provider. It's, it's the most important thing, and, token maxing, we're not so worried about it yet, but I've seen the Like, for example, I talked to some consulting companies. They have, like, 100,000 employees who are all coding for customers. If those each spend, like, an extra $1,000 a month, that's, that's not fun.Swyx [00:23:04]: YeahMatei Zaharia [00:23:04]: we have, like, only a few thousand engineers.Swyx [00:23:06]: What's the policy in Databricks? Is it just unlimited or what'Matei Zaharia [00:23:08]: It's, it's unlimited, but we do. we use our own product to, like, analyze the traces and stuff, and we have a team that'looking to optimize and to see if anyone's doing something weird. And, we had some really cool insights just from analyzing current traces, like whichSwyx [00:23:24]: YeahMatei Zaharia [00:23:25]: models are better at, say, Rust versus like TypeScript or whatever. So yeah, at least in our code base.Swyx [00:23:31]: Yeah. Amazing. Obviously, I have to ask the token question, obviously.Matei Zaharia [00:23:34]: Yeah.Swyx [00:23:34]: I think it'sReynold Xin [00:23:34]: YeahSwyx [00:23:34]: it's a key thing. But yes, security and control above that, and figuring out a sane layer there you can have some autonomy, but, not too much.Matei Zaharia [00:23:43]: Yeah. Yeah, and we wanna make it super easy. As a engineer, you should set a thing. So in Omnigentt, you can ask your agent, “Set a policy on yourself to do this.” So it can likeSwyx [00:23:52]: But if there's something I should be showingMatei Zaharia [00:23:53]: YeahSwyx [00:23:53]: I don't, I don't see it on the GitHub, but,Matei Zaharia [00:23:55]: Oh, yeahSwyx [00:23:56]: there's justMatei Zaharia [00:23:56]: Well, in the docs there's something.Swyx [00:23:57]: Yeah, this is it.Matei Zaharia [00:23:58]: You can look at it later.Swyx [00:23:59]: Okay. Yeah.Matei Zaharia [00:23:59]: Just look in the docsSwyx [00:24:00]: YeahMatei Zaharia [00:24:00]: contextual policies if you wanna see.Swyx [00:24:04]: I just like to point peopleMatei Zaharia [00:24:05]: look at the built-in policies.Swyx [00:24:06]: Yeah.Reynold Xin [00:24:06]: Yeah.Swyx [00:24:06]: If you want to, follow up on this is exactly where to look, right?Reynold Xin [00:24:10]: Yeah.Matei Zaharia [00:24:10]: Yeah. yeah, and the story of these is, like, I just wrote, like, I wrote a doc with like 10 ideas for things before as you were working on them. Well, that was, like, my wish list of things people asked, and I told the team, like, “Hey, can you do like at least five of these for the launch?” And then they just got back with all of them, so.Swyx [00:24:29]: Oh, wow.Matei Zaharia [00:24:29]: so you can come up with more, but them- some of them are just meant to be examples. really you can intercept, like, any event the agent is making, and you can then either block or force it to ask the user or, like, allow, and you can update state to keepSwyx [00:24:45]: YeahMatei Zaharia [00:24:45]: track stuff.Swyx [00:24:46]: Yeah, ‘cause ultimately you're, I think of you as, like, a systems designer.Swyx [00:24:50]: You let people plug in, right? That's the wholeMatei Zaharia [00:24:51]: YeahSwyx [00:24:52]: modus operandi of what you do.Matei Zaharia [00:24:53]: Yeah.Swyx [00:24:54]: It's likeMatei Zaharia [00:24:54]: And we care a lot about also composab- like, can someone else write a library that others use, whichSwyx [00:24:59]: YeahMatei Zaharia [00:24:59]: this is meant to.Reynold Xin [00:25:00]: There's also a batteries included philosophy hereMatei Zaharia [00:25:03]: YesReynold Xin [00:25:03]: probably very similar to how you did Spark, which is you could just start using.Swyx [00:25:06]: Yeah.Matei Zaharia [00:25:06]: Yeah, that's right. It has to be good out of the box at certain things, and then you can build your own things on top that, like, we don't wanna do. But in Spark, if you just wanna like, I don't know, like read a table or do, like, a aggregation, it should be awesome at that out of the box.Building on Omnigent: Contributions, Startups, and AnalyticsSwyx [00:25:23]: Yeah. People wanna catch up on Omnigentt, they should watch your keynote.Swyx [00:25:26]: they should go through the GitHub and the docs. If they wanted to contribute, or they want to build on this ecosystem what would you call out as the most high-leverage places get involved?Matei Zaharia [00:25:36]: Yeah, do get involved in the Discord and in GitHub. Our team is there, is monitoring, and, some of the things people ask for we just built ourselves. Some of them, we're, we're collaborating with them to build it. and also tell us, likeSwyx [00:25:49]: Yeah, they're gonna be veryMatei Zaharia [00:25:49]: how you would like to use it because I think especially for developers, like, everyone wants it to work their own way, and a really good developer tool, like you have to hear the feedback on all the ways and figure out the abstractions and how to let people customize. So we'd love to hear, like, if you think, “Hey, I, I don't want it to work this way,” tell us. We really just wanna get that compatibility layer across agents and then let you do stuff on top.Swyx [00:26:14]: Yeah. is there any, in terms of like the startup side, I'm, I'm a founder.Swyx [00:26:18]: I wantMatei Zaharia [00:26:18]: YeahSwyx [00:26:18]: I see an opportunity, I wanna get in front of you. What's your request for, like, a startup that, like, I wish someoneMatei Zaharia [00:26:23]: Oh, like you wanna integrate with us?Swyx [00:26:24]: someone was working on this.Matei Zaharia [00:26:26]: Oh, for a startup?Swyx [00:26:27]: Yeah.Swyx [00:26:28]: Like, your, you got your own startup. It's doing well.Matei Zaharia [00:26:30]: Yeah.Swyx [00:26:30]: But like, if you weren't working on your own startup, what is, like, obvious that you should You advise many startups too, obviously.Matei Zaharia [00:26:37]: I do think, just as a company with a lot of engineers, like anything that helps me make sense of how people are usingSwyx [00:26:46]: SpendMatei Zaharia [00:26:46]: coding agents and,Swyx [00:26:48]: Yeah. AnalyticsMatei Zaharia [00:26:48]: spend, but also quality or like you should write, you should add this skill, or you should write this thing, or your agents are really horrible at tasks involving this service, so I go spend time. That would be nice. yeah.Swyx [00:27:00]: Yeah. The closest I've found is, this team, GitAI.Matei Zaharia [00:27:03]: Oh, cool. Yeah.Swyx [00:27:04]: They started with, like, we will just do, code and human attribution, but they're building the analytics layer on top of that.Matei Zaharia [00:27:12]: Yeah.Swyx [00:27:12]: I do think, like, there are a bunch of, like, artificial analysis is obviously,Matei Zaharia [00:27:18]: Yeah, they have their benchmarksSwyx [00:27:18]: doing super wellMatei Zaharia [00:27:19]: YeahSwyx [00:27:19]: with their stuff. so there's, there will be people. I think this is like the domain of consultants first, but then peopleMatei Zaharia [00:27:26]: YeahSwyx [00:27:26]: will build software that, let's say, it's kinda like the management planeMatei Zaharia [00:27:29]: YeahSwyx [00:27:30]: for coding agents.Matei Zaharia [00:27:30]: Yeah, I think there'll be a lot of insights there. You have it in other areas.Swyx [00:27:34]: Okay. Well, and then the other, big thing is your dream engine.LTAP: Lake Transactional/Analytical ProcessingSwyx [00:27:39]: maybe you wanna tell the story of, LTAP.Reynold Xin [00:27:45]: So, and background with. I'm, I'm gonna make people listen to our Ankur Goyal episode where we talked about SingleStore, HTAPMatei Zaharia [00:27:52]: YeahReynold Xin [00:27:52]: and all that history.Matei Zaharia [00:27:52]: Yeah. The LTAP idea is pretty simple. so if people have heard of the, Ankur's, talk about HTAP, it's effectively the world of databases. Sorry, there's like maybe a lot of context needs to be injected here. The world of databasesSwyx [00:28:06]: I am happy to be the database podcast that I'm forcing people to, like, learn your databases, guys.Swyx [00:28:11]: You cannot vibe code with just markdown files.Reynold Xin [00:28:13]: Yeah.Swyx [00:28:13]: Like,Reynold Xin [00:28:14]: It's one of the most important fundamental systems technologies out there. But the world of database effectively split into roughly two halves. There's what we call OLTP databases, which are transactional, and think of your Postgres, your MySQL, your Oracle databases, and the other side is what we call analytics, and sometime might refer to term OLAP. And the difference is on OLTP, you typically have maybe run some transaction on some event that looks up at one specific row. We update that row, right? It's a very oriented data structure. And on analytics, you're trying to reason on the data. You're trying to compute, “Hey, what's my revenue per store? What's my. How's my website doing every day?” And then you, eventually want to probably end up running anal- machine learning on it to predict, “Hey, how will my maybe sales be going in the future?” they are so very different architecture, and everybody start with OLTP databases. Every app, when you become serious enough, that needs more than markdown files, you need to have a database. You want to lose your data, you want to have some transactional consistency. But once you want to reason on the data, if you only have like- A hundred rows, it's probably okay to run it on your Postgres or your own, your MySQL database. But once you have more data and want to run more complicated analysis, the very analysis might crush your Postgres database. So you start doing, getting data out of the OLTP databaseSwyx [00:29:35]: Replication.Reynold Xin [00:29:36]: Replicate them into the analytic systems and just startSwyx [00:29:39]: Yeah, which for people, Elasticsearch is, like, aReynold Xin [00:29:42]: Yeah. So some of them get into Elasticsearch for, like, blocked analysis. A lot of our customers obviously get into Databricks to run more sophisticated things.Swyx [00:29:51]: Yeah.Reynold Xin [00:29:51]: And there's this term called CDC, whichMatei Zaharia [00:29:54]: Change data captureReynold Xin [00:29:55]: change data capture. and what it does, it reads the binlog of the database, and if you don't understand what binlog is, it's fine. The, but it's a little delta of the data, and it reconstructs based on the delta, the state of the database, on the analytics side. But CDC is, like, a very painful thing. It's how standard in the industry, everybody uses it, but, it ends up being. I think many data engineers ends up being waken up at, like, 3:00 a.m, because there's some pipeline thing.Swyx [00:30:22]: my explanation is, like, Airbyte is like a, became a $5 billion company just doing CDC.Reynold Xin [00:30:27]: Yeah, exactly.Reynold Xin [00:30:28]: CDC is, like, a veryMatei Zaharia [00:30:30]: It's hard.Reynold Xin [00:30:30]: It's one of the most boring but one of the most fundamental operations, like, powering modern society.Matei Zaharia [00:30:37]: huh.Reynold Xin [00:30:37]: But it's so brittle that, we joke that it's, should be called continuous data corruption, because you might change your schema on your OLTP database, and then the CDC pipeline fails to handleSwyx [00:30:48]: YeahReynold Xin [00:30:48]: the schema change.Swyx [00:30:49]: Yeah.Reynold Xin [00:30:49]: And then everything goes out.Swyx [00:30:51]: And there's all sorts of tricks that you can do, like, you add in, like, some versioning or whatever, but yeah.Reynold Xin [00:30:55]: Yeah, but it's a very, in general, very complicated. Like, I think at my keynote, I asked the audience put up their hand if they love their CDC pipeline. Only, like, maybe two people put it up. So if single store, like, about maybe a decade ago, I think the industry had this idea, hey, what if I built a single database that can handle both workloads? Now I don't.Swyx [00:31:12]: Which, like, by the way, every database person ever has ever always dreamed about this.Reynold Xin [00:31:15]: Yes. Yes.Reynold Xin [00:31:16]: This is the holy grail of database engineering is why not build a single system that can do both of this? But it ends up just being a lot of compromises. one, I think one of the first issue is that, hey, each. they say Postgres has a massive ecosystem, right? You want to be using the tools that's built for Postgres. And Spark, for example, had a massive ecosystem. There's a lot of libraries you want to use. If you were to create now a new thing, you don't have a ecosystem. You tend to create a new, smaller proprietary API, and you're lacking both, and it's also very difficult to make it performance-wise to be, comparable on either side. So it ends up being sucking on both. And our whole idea of LTAP, it's obviously a wordplay on the term HTAP, is that we think this is HTAP done right. HTAP wants to build a single engine for both. We think you can get 99% of what you need by unifying the storage, and just have a single storage layer. And once you have the single storage layer, if your Postgres databases are writing data in a column-oriented format, everything analytics can just go read that data directly without any delay, right? There's no pipeline in between, so all the data will immediately be available for reasoning analytics. I think I was telling some customers earlier, hey, when we talked about this is gonna be super useful for agents, I at first didn't really believe in it myself, even though we wrote that positioning.Lakebase, Agents, and Live Operational DataMatei Zaharia [00:32:39]: Yeah.Reynold Xin [00:32:40]: But then last night I was having dinner with a Australian customer, and they told me, “Oh, hey, one of the big issue we have is we have all these logs from our services, and we see SLA dips and want to investigate. But then there's no way for those agents to even understand what's going on in the actual databases themselves. All we see is just, like, product telemetry of the database and the services.” It would make those agents 10 times more powerful if understand, for example, who's placing those orders, what is happening, what exactly are they doing. So now I'm sold on our own message.Swyx [00:33:13]: Yeah.Reynold Xin [00:33:14]: I think it's really. It gets you the almost all of the benefits of the HTAP holy grail, which is, hey, make the data available immediately for reasoning analyticsSwyx [00:33:26]: Yeah, I think,Reynold Xin [00:33:27]: without compromiseSwyx [00:33:28]: in the way that humans are generally intelligent and want to have the ability and access to query anythingReynold Xin [00:33:34]: YeahSwyx [00:33:35]: while they do the work, they also need history and need context.Swyx [00:33:38]: And, like, where else does they get context? That's it's an analytical workload.Reynold Xin [00:33:41]: Exactly.Matei Zaharia [00:33:42]: Yeah. Yeah. And I remember when we had incidents with our databases and engineers said, “Well, I can't just run a giant query on it to see what's going on because that's gonna bring down the database and hoard it even more.” Like, that's the stuff that this gets rid of, because you spin up a whole separate fleet of machines that's doing the analytics. You're not overloading, like, the main databaseReynold Xin [00:34:02]: RightMatei Zaharia [00:34:02]: that's still trying to serve stuff.Reynold Xin [00:34:04]: Yeah.Matei Zaharia [00:34:04]: Yeah.Why LTAP Works Now: Parquet, Postgres, and LakebaseSwyx [00:34:05]: So this has been a dream for a while. what had to get done in order to get to today? Like,Reynold Xin [00:34:11]: Yeah.Swyx [00:34:11]: I feel like, you have announced variants of this several times, but it wasn't as clear as LTAP.Reynold Xin [00:34:18]: Yeah.Swyx [00:34:18]: I think LTAP is like Like, okay, we've got it, guys.Matei Zaharia [00:34:21]: This thing, yeah.Reynold Xin [00:34:21]: I was talking to somebody at Meta, and then he was asking me, “Hey, what's the catch? Why is it possible now?” And I think the reality is we took a lot of time to work on the Lakebase architecture. obviously a lot of it came from the Neon team, which is a separation of storage from compute. And it turned out it was just a tiny little step away going from that to this LTAP idea, which is, hey, we just. in the Neon architecture and in Lakebase architecture, we're writing data in oriented format to the open data lake, but in there we're writing in Postgres pages. Ali and I were spending a lot of time debating, hey, can we just change that to write in column-oriented format? And we're just debating, and one day, one of our engineers who's, like, super smart came in, he's like, “Hey, I just prototyped it. It works.”Swyx [00:35:07]: Wait, it's, prototype what?Reynold Xin [00:35:09]: Prototype, instead of storing the data in the data lake in the oriented formatSwyx [00:35:15]: ColumnReynold Xin [00:35:15]: like Postgres pagesSwyx [00:35:15]: YeahReynold Xin [00:35:16]: write them in Parquet.Swyx [00:35:17]: Yeah.Reynold Xin [00:35:18]: and he just made the observation that, hey, our storage fleet has a lot of extra idle CPUs And we could use those CPUs to do the transcoding from row to column, where row is good for OLTP, but column is good for analytics. so let's do that transcoding at that time. And as a matter of fact, once you transcode the data compresses better. So from those services writing to, for example, S3 or other data lake, like object stores, you can write them faster ‘cause now they are now smaller.Matei Zaharia [00:35:49]: Yeah.Reynold Xin [00:35:49]: So there's no overhead, it's no compromise in performanceMatei Zaharia [00:35:52]: Some CPU overhead.Swyx [00:35:54]: Yeah, because,Matei Zaharia [00:35:55]: YeahSwyx [00:35:55]: we had extra CPUs anyway.Matei Zaharia [00:35:56]: We had that fleet anyway, yeah.Swyx [00:35:57]: so the debate ended. it's one of the classics of, tech, issue of a lot of debate, but then somebody went ahead and just tried to prototype it and it worked.Matei Zaharia [00:36:06]: But, like, something this strategicSwyx [00:36:07]: That's rightMatei Zaharia [00:36:07]: and important to the company, I expect there to be, like, a kickoff thing, like a design doc. Nothing like that.Swyx [00:36:13]: Nothing like that.Swyx [00:36:14]: He just. We were debating in many meetingsMatei Zaharia [00:36:17]: Yeah.Swyx [00:36:17]: and then we're just debating whether it's possible or not from first principle.Matei Zaharia [00:36:20]: YeahSwyx [00:36:20]: and then, somebody just did it.Matei Zaharia [00:36:23]: Yeah, if you set yourself up so people do that'll be great. And that happened a bit with Omnigentt too. I think if I just had a doc on, like, we can make these together, everyone would, would think, “Oh, what about this? What about this?” But then you. if you try it out, it helps. And then if you have real users and they bash it and, like, it's still working, or in this case, if you have the workload, what the workload looks like, you can just test the same pattern then.Databricks' Culture of Fast PrototypingSwyx [00:36:47]: Yeah.Matei Zaharia [00:36:47]: Yeah.Swyx [00:36:47]: Tech aside, which is very cool, this is, like, the most important thing, the culture of innovation, and you don't have to ask my permission, you don't have like, do a whole form- formal process, just do it?Matei Zaharia [00:36:59]: Well, especially these days, I think withSwyx [00:37:01]: YeahMatei Zaharia [00:37:01]: AI, it's easier to buildSwyx [00:37:02]: But so, likeMatei Zaharia [00:37:03]: a prototypeSwyx [00:37:03]: I think you are very I made a lot of suite of, like, large companies and, like, I think that at scale, things slow down, and I'm sure you felt it already, but somehow you have this core of people that, like, are exempt. How? I think we hire and we work with really good people, and that's a very important part of it, and empowering them, but also spending a lot of time, maybe us in the trenches matter a lot also.Matei Zaharia [00:37:28]: Yeah, I think, I think first, people can adapt to being in the larger company, so that helps. And we wanna make sure they know that they can try stuff and settle debates and have a lot of examples of how it was done before, or launch a thing in beta or whatever. and then the other thing I do think as a company, like despite the size, we don't launch that many, like, products. We try to keep it pretty coherent. That's, that was the whole, like, theory of the company, was like instead of having, like, 20 Amazon services you need to set up, like a analytics and machine learning stack, you just have one, and it's, like, the same API, the same semantics across all of them, the same copy of the data. So that requires, like, unification. And then we added one more thing at a time. Like, we added storage with Delta Lake. We didn't used to do any storage. Then we added SQL, we added, machine learning platform stuff. So, but yeah, don't, don't do too many, but do those things well and, that also helps, it helps keep it manageable.Reynold Xin [00:38:33]: Yeah. The other thing we encourage a lot is instead of building, boil the ocean for everything, let's figure out how do we do it incrementally, how do we do it very quickly. Like, many of our productsMatei Zaharia [00:38:43]: YeahReynold Xin [00:38:43]: they're built in the span of weeks, and then we go to, hey. Like, usually my first question to whoever team is building is who's the target customer? Who are you working with? Are you on a first-name basis with them? Are you texting with them? I think having that very tight loop,Matei Zaharia [00:38:59]: Can you bring up another launch that comes to mind when, in this thing? I just want to give examples.Reynold Xin [00:39:04]: Omnigentt itself happened that way.Reynold Xin [00:39:05]: Yeah.Matei Zaharia [00:39:06]: Who's the customer? That's a good oneReynold Xin [00:39:34]: storage layer we did. we had, our largest customer at the time said like, “Okay, I need some. I want something in the cloud ‘cause, I. if the rest of our network is compromised, like this thing needs to be separate to store and query the events.” And then, talked to us, he said, “Okay, this is the rate of events per second. This is, like, the freshness I want. Can you do it?” So that was, like, way larger than any workload we had, and we had our, engineer, working on that, Michael Armbrust, and he worked just to make this work. And once it worked for them, it worked for everyone else. Yeah. This was early in the company, probably like four years in or something.Matei Zaharia [00:40:24]: 20- 2018?Swyx [00:40:26]: Yeah, ‘17, ‘18.Matei Zaharia [00:40:28]: Few companiesSwyx [00:40:28]: Do you have other examples?Matei Zaharia [00:40:30]: there'Swyx [00:40:31]: Maybe you have othersMatei Zaharia [00:40:31]: yeah, Clean Room, which is how you share data in a way without sharingSwyx [00:40:35]: YeahMatei Zaharia [00:40:35]: underlying data, but you allow specific operations. Those were done effectively initially just for two customers. I think the industry has a sense of, hey, maybe if you overfit to, like, one or two customers, it's gonna be really bad for you. But I think the, downside of overfitting is much smaller than the upside itself. And if you try to be too ambitious and boil the ocean, it's a much bigger problem.Swyx [00:40:58]: Yeah. Yeah.Matei Zaharia [00:40:58]: ‘Cause you might end up having no customer.Swyx [00:41:00]: Yeah, that's more, that's the more likely outcome.Matei Zaharia [00:41:02]: Yeah.Tech Companies vs. EnterprisesSwyx [00:41:03]: than you can pivot from there. I do think there is such a thing as a bad customer that sometimes you should fire. Yeah.Matei Zaharia [00:41:08]: They could exist sometimes if you drive. well, one of the challenge I think we probably see, and maybe many AI, so newer generation companies are seeing is, so tech companies are very different from tech companies or traditional enterprises.Swyx [00:41:22]: Yeah.Matei Zaharia [00:41:22]: And, if you optimize everything just for tech companies, you might have various challengesSwyx [00:41:27]: OhMatei Zaharia [00:41:27]: scaling them outside of tech companies.Swyx [00:41:28]: Okay, what likeMatei Zaharia [00:41:30]: YeahSwyx [00:41:30]: what like top three differences that you always think about?Reynold Xin [00:41:33]: Governance is a big oneMatei Zaharia [00:41:34]: I think, yeah, a big one is like, yeah, security, data privacy, governance, all that stuff. So usually if you're building some kinda like B2B or developer tool, like your biggest market is gonna be enterprises, but it's just very different. A company that's existed for like, it's had some form of IT for like 30 years, they have so many legacy systems or they operate in a regulated space. whereas a startup or, even like a, like sorta more recent tech company, all the. everything is new and pristine. So yeah, it's just different, and if you've never worked with enterprises or been in one, you just won't know about it.Reynold Xin [00:42:13]: Yeah.Matei Zaharia [00:42:13]: Yeah.Reynold Xin [00:42:13]: And the procurement process is probably quite different. There's far more stakeholders.Matei Zaharia [00:42:17]: Yeah, that is one. Yeah.Matei Zaharia [00:42:18]: Another piece that's interesting is I think some tech companies, people, will say, “Oh, I can build that myself,” right? I'll just build that myself.Matei Zaharia [00:42:27]: So then you go,Reynold Xin [00:42:28]: I don't think people say that about Databricks, butMatei Zaharia [00:42:31]: yeah, it dependsReynold Xin [00:42:32]: They do.Matei Zaharia [00:42:32]: They do?Matei Zaharia [00:42:32]: Yeah, the. Yeah, and it depends on the teams and things. So, but, on the other hand, like many of the enterprises say, “I don't, I never wanna be in the business of building that.” Like, I don't want my, whatever, I'm a retailer or something, I never wannaReynold Xin [00:42:45]: Yeah, sell clothes,Matei Zaharia [00:42:46]: be down because like some weird like nerd like couldn't get streaming pipelines working.Matei Zaharia [00:42:51]: That is not what I'm doing.Reynold Xin [00:42:53]: Yeah.Reynold Xin [00:42:53]: Yeah. This makes them great customers, to be honest, right?Matei Zaharia [00:42:55]: Yeah. But you have to understand that it's hard without having worked there and stuff, like you may not appreciate.Reynold Xin [00:43:01]: Look, I think they're all great. don't get me wrong, they have different challenges. But the, many of the tech companies, for sure there's a lot, far more DIY.Matei Zaharia [00:43:10]: On the flip side, you have people who are. they're very much experts in their domain, like they're building airplanes, they're, designing medicines, whatever, and they just want to bridge the technology, where like they don't wanna learn, databases or whatever. As cool as we think it is, even as interesting as the average software engineer might think it is to read a little bit, like they just never wanna know. They just say, “I have a, giant like, matrix or whatever with my, clinical data, like how do I, how do I like cluster it or whatever?” So yeah.The Dream Engine and Rewriting the Database StackReynold Xin [00:43:40]: Yeah. That's true. Okay, so and then I wanted to build out the dream engine, vision. where does this all lead? So one of the thing we, realized maybe a couple years back is that every single database engine out there, especially on the analytics side, are a decade old. pretty much everything that have reasonable traction are about a decade old. And they all started targeting some very specific narrow use cases, and then over time it's become more and more successful. They have grown in their ambition, and then they try to support more and more use cases. But the fastest way to support those use cases tend to be hacked around the abstractions that were initially created, that were not for those use cases.Matei Zaharia [00:44:23]: Yeah.Reynold Xin [00:44:23]: And then, but you can support them more or less okay. And before it, after 10 years of organic evolution that way, it becomes a gigantic pile of s**t.Reynold Xin [00:44:31]: the. And, but that includes Databricks. And very few company or very few systems, I think, have the gut to say, let's go start from scratch. Let's go back to the drawing board and design, knowing everything we know today after a decade of workloads and probably billions in revenue, let's attempt to rewrite it from scratch and make sure it will work and it can support all of these use cases. So we started doing that, but it's a very ambitious project. by the way, you can search on Wikipedia, there's this thing called second system syndrome.Matei Zaharia [00:45:08]: Yeah, I know that. Yes.Reynold Xin [00:45:09]: Or second system effect.Matei Zaharia [00:45:11]: Every developer must know what a second syndrome is.Reynold Xin [00:45:12]: It's you built your first thing and it works out great, and the second one's bound to fail because you become too ambitious.Reynold Xin [00:45:19]: And then you ask so many requirements.Matei Zaharia [00:45:20]: Or like you think everythingReynold Xin [00:45:21]: YeahMatei Zaharia [00:45:21]: and then you're likeReynold Xin [00:45:22]: You justMatei Zaharia [00:45:22]: you're, “I'm gonna design the perfect system this time.”Reynold Xin [00:45:24]: Yeah. And it turned out it's not perfect, and then it start failing and you're too ambitious, never launch, and you get killed. The, and the engineering team that started this, they were brilliant. I think we hired some of the best database engineers, on the planet into Databricks, and they were brilliant. Thank God it's not their second system. Many of them have built more than two in the past.Matei Zaharia [00:45:44]: Ah, nice.Reynold Xin [00:45:45]: But they were still worried about this, hey, building a database engine from scratch, I think the conventional wisdom is gonna take like five years to mature. This would be a very long-term project. It could fail. I think one of the engineers jokingly said, “Hey, maybe we just call it Reynolds Stream Engine.” If we name after a founder, maybe we then may get canceled or killed. But I think they built something pretty remarkable. they went back to. They changed the way the database engines were built from a paradigm point of view. Usually when y

In this episode of TAB Storytellers, Abi and Jen sit down with Emily Bawol, an art teacher, artist, and art therapist at A2 STEAM in Ann Arbor, Michigan. Emily shares how her path through discipline-based art education, art therapy, motherhood, Waldorf, Montessori, Reggio-inspired learning, and project-based education helped her recognize that she was already building a TAB studio before she had the language for it. Together, the trio explores the role of the art teacher in a TAB classroom, especially around idea generation, material exploration, autonomy, and helping young artists trust that their own ideas matter. Emily talks about creating a studio rooted in wonder, where students learn that they are the most important tool in the room, while still building the skills, habits, and confidence they need to bring their ideas to life.For more information about TAB, please visit the TAB website: Teaching for Artistic Behavior. You are also invited to join us on Mighty Networks, an online platform dedicated to everything TAB.Resources:Teaching for Artistic Behavior / TABTAB ResourcesTAB Storytellers PodcastTAB Mighty Networks CommunityEmily Bawol / A2 STEAM Art & DesignA2 STEAM Project-Based LearningAmerican Art Therapy Association: About Art TherapyCASEL: Fundamentals of SELDiscipline-Based Art Education, Getty Virtual LibraryWaldorf Education, Association of Waldorf Schools of North AmericaAmerican Montessori Society: About MontessoriNorth American Reggio Emilia AlliancePBLWorks: What Is Project Based Learning?Melissa Purtee: The Difference Between TAB and Choice and Why It MattersTAB Institute at MassArtJulie Toole, MassArt TAB Institute Faculty ProfileTAB Storytellers S3E5: Meet Julie TooleHarvard Project Zero Thinking RoutinesProject Zero: See, Think, WonderStudio Thinking Books and ResourcesPeter London, No More Secondhand Art, Internet ArchiveSeymour Simmons III: The Value of DrawingArtists Mentioned:Jean-Michel Basquiat, official estate websiteFrida Kahlo Museum / Museo Frida KahloMark Rothko, National Gallery of ArtPablo Picasso, National Gallery of ArtVincent van Gogh, Van Gogh MuseumHere is a link to the lightly edited transcript of this episode. We recognize that there are probably errors and grammatical issues. If anyone with the time or inclination to edit this wants to do so, please email us at ⁠storytellers@teachingforartisticbehaviors.org⁠.

How common or rare are species in an ecosystem? The answer to this might seem simple, but as with everything in nature, it is not. This question can even complicate how we think of habitat conservation and restoration. When we refine and implement scientific tools like species diversity indices, we need to make sure we are applying them correctly. Join me and Dr. Robert Warren as we explore measures of species diversity, the issues with improper use of these tools, and what that can mean in the context of invasive species and restoration. This episode was produced in part by Chris, Gerald, Elise, Maggie, Mamie, A.J., Dallas, Channele, KC, Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Only 1% of listeners are clever enough to complete this survey: http://bit.ly/noncensored-surveyThis week, Harriet Langley-Swindon and Producer Martin talk to campaigner and old man Hugh Oldman, about why the government is right to ban under-sixteens from social media; we speak to A Suffragette From 1913 about how she feels about being compared to Palestine Action; and Eshaan Akbar walks us through a Hot & Spicy Takeaway of the Week for as long as the authorities.Thank you to Abi, who signed up to our Patreon this week. She, like all Patreons, will be getting a bonus interview with A Scammer in the middle of the show. Patreons also get every episode early and without adverts, access to the full video of all our interviews, as well as the Patreon-exclusive monthly Time For Questions podcast, where we answer your questions, so get over to Patreon.com/NonCensored and sign up for one or two pounds a week to support the show, and make it possible for us to pay our guests. (If you don't want to subscribe, but do want to give us a one-off amount, all the Patreon-exclusive videos are available for individual sale.)Please follow our social media accounts!Instagram: @noncensoredpodcastTikTok: @noncensoredpodWith thanks to Rosie Holt, Brendan Murphy, Eshaan Akbar, Justin Edwards, Sooz Kempner, John-Luke Roberts, and Ed Morrish.Rosie's sitcom, Crossing The Floor, is available now on BBC Sounds. Her play, Churchill's Urinal, will be on at the Edinburgh Festival Fringe (tickets here), where she will also be doing a new character comedy/stand-up show, The Illegal Aliens Have Landed (tickets here).Brendan is taking a brand new show, Indy, to the Edinburgh Festival Fringe in August. It's a three-man retelling of Indiana Jones, and tickets are available here.Eshaan has started a new, live podcast called The Early Evening Show, every Sunday evening on YouTube, and his latest stand-up special, Fool Moon, is also available on YouTube.Justin is returning to the Edinburgh Festival Fringe for the first time in ages, for just five dates, with his show, Jeremy Lion - My Life!, and tickets are available here.Sooz is also returning to the Edinburgh Festival Fringe, for nine dates, with her show Impostor, and tickets for that are available here.Ed produces produces P.O.V., a scripted sketch show on BBC Sounds which has NonCensored regulars like Davina, Will and Sooz in it. He also produces Sound Heap With John-Luke Roberts, an award-winning improvised sketch show that features many NonCensored regulars like Rosie, Brendan, Will, Sooz and Joz.Show photography is by Karla Gowlett and design is by Chris Barker. Original music is by Paddy Gervers and Rob Sell at Torch and Compass.NonCensored is a Lead Mojo production Hosted on Acast. See acast.com/privacy for more information.

Today on Beyond the Torch, Todd & Leslie are joined by guest co-host, Scott Ransome, a UK-based Survivor superfan who won a charity eBay bid to co-host and interview a guest and he picked today's guest, Abi-Maria Gomez, the iconic Brazilian-American villain from Survivor: Philippines and Survivor: Cambodia — Second Chances! The conversation covers Abi's unexpected journey to being cast on Survivor (including nearly appearing on Tocantins but being rejected for "not looking Brazilian enough"), her experience playing with a torn ACL throughout Philippines, reflections on being edited as a villain, her views on race and immigrant identity, her complicated relationship with former alliance partner RC, her admiration for Denise Stapley, and candid discussions about Survivor 50 casting disappointments, reality TV opportunities like The Traitors, and fond memories of Survivor legends like Courtney Yates, Amanda Kimmel, and James Clement.Our new Website is live! Check it out at: www.realityaftershow.comJoin our Patreon at RealityPatron.comIf you would like a cameo from Jonny Fairplay order one now! cameo.com/jonnyfairplayCheck us out on Tiktok @fairplaytokBecome a supporter of this podcast: https://www.spreaker.com/podcast/reality-after-show--5448874/support.

Two incredible guests join Nat for this bonus episode.The first is Gabi Field from Great Ormond Street Hospital Charity, speaking today about the importance of the charity's Build it. Beat it. fundraising appeal, which is raising vital funds for a new Children's Cancer Centre at Great Ormond Street Hospital. The second guest is Nat's very dear friend Abi, who some may recognise from episode two of Natalie Cassidy: Caring Together. Abi is also the mother of Joanie's bestie Arianna. Arianna was diagnosed with Neuroblastoma at 5 years old, and Abby has first-hand experience of what it's like to need the medical services GOSH have on offer, knows the pressure of spending lots of time in the building whilst that happens, and knows how important this new building will be to help beat cancer for more children.To support the Build it. Beat it. campaign or find out more about GOSH Charity, visit - www.gosh.orgFollow Arianna's journey www.instagram.com/ariannatherealwonderSolving Kids Cancer charity, which Nat is an ambassador of www.solvingkidscancer.org.ukGet in touch with Nat, buy tickets for upcoming live shows and find the family on Instagram: https://lifewithnatpod.komi.io/ Hosted on Acast. See acast.com/privacy for more information.

Connect with Abi: https://www.instagram.com/abistumvoll/I don't bring many women onto BraveCo, but when I do, it's because they have something that men need to hear — something they won't get anywhere else. Abby Stumble is one of my oldest and most trusted friends, and this conversation is one of the most honest ones I've ever had on this podcast. Abby grew up thinking she had a great childhood. She was wrong. A mentally ill, drug-addicted mother. A home full of chaos she internalized as her own failure. Panic attacks, suicidal thoughts, self-hatred, and a body she despised — all without a single clear explanation for why. It wasn't until she was 37 that the real story started to unravel. And what happened next changed everything she thought she knew about herself, her marriage, and what healing actually looks like.We go deep into marriage in this one — specifically what happened when two beautiful train-wrecks decided to build a life together. Abby and Justin's story is a masterclass in how broken attachment cycles play out in real relationships: the avoidant man who disappears, the anxious woman who picks fights just to pull him back, and both of them trauma-bonding through explosions they thought was just how love worked. Sound familiar? We unpack the exact moment their marriage started to change — and it wasn't a big dramatic breakthrough. It was ownership. Honesty without shame. Vulnerability that didn't demand rescue. And I share my own piece of this too, because for years I went home every night feeling like a boy, not a man — isolated, ashamed, and slowly drowning while Lauren watched me disappear. This is the conversation that brings all of that into the open.And then Abby goes somewhere I didn't expect. She tells the story of a season four years ago when she was so sick she couldn't walk ten feet, had lost thirty pounds, and begged Justin — through genuine physical torment — to end her suffering. What she learned in that dark place about present-moment living, nervous system regulation, collecting moments of good, and training your brain to attach to safety instead of pain is some of the most practical, life-changing content I've ever heard. If you're in a hard season right now — with your health, your marriage, your emotions, or your sense of who you are as a man — this episode is for you. Stay Brave.Chapters:00:00 – Welcome to BraveCo09:44 – Growing Up in Chaos19:27 – The Slow Unraveling29:11 – Two Trainwrecks, One Marriage38:54 – Jason's Story48:38 – The Vulnerability Men Fear Most 58:21 – Small Steps, Big Culture1:08:05 – When the Body Breaks Down1:17:48 – Regulating the Nervous System1:27:32 – The Tiny Things, The Future With Hope, and a Prayer Over Every Person ListeningCONNECT WITH BRAVECOJoin Our Free Community for Men (ladies, sign up your man): https://www.braveco.orgFacebook: https://www.facebook.com/braveco.menInstagram: https://www.instagram.com/braveco.men/Shop: https://shop.braveco.org/ABOUT BRAVECO: We live in a time where men are hunting for the truth and looking for the codebook to manhood. At BraveCo, we are on a mission to heal the narrative of masculinity across a generation; fighting the good fight together because every man should feel confident and capable of facing his pain, loving deeply, and leading a life that impacts the world around him.

When you start studying a group of plants, you never know what you are going to find. Sometimes it's important insights into pollination and seed dispersal. Other times it's how the uplift of mountain chains shapes wetlands and rivers. These are the kinds of discoveries that drive Dr. Ana Bedoya to study the riverweeds of the family Podostemaceae. These extreme aquatic plants are fascinating in the own right while also having a lot to teach us about a variety of scientific disciplines. This episode was produced in part by Chris, Gerald, Elise, Maggie, Mamie, A.J., Dallas, Channele, KC, Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Fr. Mike touches on King Rehobo'am's last acts and the rise of his son, Abi′jah. He also explains how the mistakes of Israel's leaders show the importance of faith over success. Today's readings are 1 Kings 13, 2 Chronicles 12-13, and Song of Solomon 2. For the complete reading plan, visit ascensionpress.com/bibleinayear. Please note: The Bible contains adult themes that may not be suitable for children - parental discretion is advised.

 Meet Angela Standridge, Director of the Texas Technology Access Program (TTAP) at the University of Texas. The program helps people with disabilities get access to assistive technology so they can live more independently.What is Assistive Technology (AT)? is any device, equipment, software program, or product that helps a person with a disability improve or maintain their ability to function.TTAP makes these tools easy to find and use. They not only have a library of available devices but also provide product demonstrations, 35-day loaner devices, recycled equipment, and information about national loan programs. Angela explains that the tool itself is not the full solution—the real solution is how the person uses it in their own environment to meet their specific needs. Listen in and find out how this amazing program allows those of us with disabilities to live a more independent life.Guest Social Media info - Website: https://ttap.disabilitystudies.utexas.edu/Facebook: https://www.facebook.com/UTTTAP @UTTTAPInsta: https://www.instagram.com/txtechaccess/?hl=en @txtechaccessYouTube : https://www.youtube.com/channel/UCZXFb_pP3efgjRrTT4nMoeQ @texastechnologyaccessprogramBluesky: https://bsky.app/profile/txtechnologyaccess.bsky.social @txtechnologyaccess.bsky.socialSend us Fan MailSupport the showYou can find this episode's transcript here.New episodes drop every other Thursday everywhere you listen to podcasts. 

Abi and Matt are stressed out. 

Abi Millar grew up in a charismatic evangelical church where faith once felt vivid, immediate and full of certainty. But as questions about science, belief, heaven and hell began to press in, that certainty slowly unravelled. In this conversation, Tim talks with Abi about what it cost to leave, the freedom and loss that followed, and the spiritual hunger that eventually re-emerged after a long season of atheism. They also talk about some of the practices Abi explores in her book The Spirituality Gap — including yoga, ayahuasca, tarot and meditation — and the tension between scepticism and openness that runs through her journey. Along the way, the conversation touches on rootedness, community, cultural integrity, and the question of whether spirituality can truly flourish without a shared story or tradition. Following the interview, Nomad hosts Tim and Nick reflect on the burden of heaven and hell, the freedom and loss of leaving evangelical faith, and the search for meaning beyond certainty. They also explore what Abi's journey raises about psychedelics, tarot, rootedness, and the limits of highly individual spirituality.Interview starts at 10m 34sBooks, quotes, links →The creation of Nomad's thoughtful, ad-free content is entirely funded by our equally thoughtful and wonderful listeners. By supporting us, you gain access to Nomad's online spaces—like the Beloved Listener Lounge, Enneagram Lounge, and Book Club—as well as bonus episodes such as Nomad Contemplations, Homegrown Conversations, and Nomad Revisited.If you'd like to join our lovely community of supporters, head over to our Patreon page. You might even be rewarded with a Nomad pen or our coveted Beloved Listener mug!If a monthly commitment isn't possible right now, a one-off donation is always deeply appreciated—you can do that here.Looking to connect with others nearby? Check out the Listener Map or join our Nomad Gathering Facebook group.And if you're up for sharing your own story, we regularly post reflections from listeners on our blog—all with the hope of fostering deeper understanding, connection and supportive relationships. If you'd like to share your story on the blog, contact us for more information here.

Recorded live at DX Annual, Abi Noda, co-founder and CEO of DX, joins Brian Houck of Microsoft to share an early look at DX's new research on AI's impact on engineering velocity.Drawing on data from a sample of DX customers, they discuss what companies are actually seeing as AI adoption matures. Most organizations in the study saw pull request throughput increase by 10 to 15 percent—far more modest than the 10x gains often promised in industry headlines.They explore why coding remains only a small part of developer work, where time saved by AI may be going, and the unintended consequences of moving faster, from shifting bottlenecks to “false velocity.” Abi also shares how engineering leaders are applying AI beyond coding and how DX is evolving its measurement framework to account for both human and agent productivity.Where to find Brian Houck: • LinkedIn: https://www.linkedin.com/in/brianhouck/ Where to find Abi Noda:• LinkedIn: https://www.linkedin.com/in/abinoda In this episode, we cover:(00:00) Intro(00:53) What motivated DX's research into AI's impact on engineering velocity(02:36) How DX designed the study and selected companies(04:54) What DX's data reveals about AI's impact on engineering throughput(06:31) Why PR throughput was the most practical metric to publish(08:21) Why AI productivity gains are lower than many leaders expected(10:24) How an all-in culture can amplify AI productivity gains(12:35) Why it's hard to track where AI-generated time savings are going(15:04) Unintended consequences of AI-driven productivity gains(17:12) Why leaders should look beyond coding to the rest of the SDLC(19:43) Cognitive debt and the human costs of AI-assisted development(21:33) How DX's AI measurement framework is evolving(24:42) How to make agents more effectiveReferenced:• DX Core 4 Productivity Framework • DORA, SPACE, and DevEx: Which framework should you use?• Time Warp: The Gap Between Developers' Ideal vs Actual Workweeks in an AI-Driven Era - Microsoft • Research• How Generative and Agentic AI Shift Concern from Technical Debt to Cognitive Debt• Measuring AI code assistants and agents

Plants are habitat. Heck, even a single leaf is habitat. Same goes for plant roots. This is especially true when we consider insects and fungi. But how do these organisms interact? How do they change over gradients of moisture, temperature, space, and time? Why do we consider some parasitic while others are mutualists? The world of ecological interactions is extremely complex but people like Dr. Chris Bivins are taking stabs at trying to gain insights piece by piece. Join us for an wonderfully deep dive on the amazing ways oaks, gall wasps, fungi, and mycoheterotrophic plants live out their mysterious lives together. This episode was produced in part by Chris, Gerald, Elise, Maggie, Mamie, A.J., Dallas, Channele, KC, Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Discover the unconventional strategies behind building a successful land investment business in this insightful conversation with Abi Asija. From direct mail marketing and owner financing to creating a customer loyalty flywheel, Abi shares the systems, mindset, and relationship-driven approach that helped him scale his business and create long-term success. Learn how focusing on customer experience, rapid response times, continuous improvement, and strategic niche marketing can help entrepreneurs build a sustainable and highly profitable business. Main Topics Abi Asija's journey from corporate IT to land investing and entrepreneurship How to buy and sell raw land in remote desert markets with limited utility Using direct mail and public records to source land deals Building goodwill and increasing customer lifetime value through exceptional service Leveraging referrals, reviews, and relationships to drive business growth The importance of niching down and targeting specific customer avatars Creating systems and processes that support scalability Practical sales strategies, including speed-to-lead, objection handling, and offer creation Hiring principles for building a high-performance team The mindset shift from side hustles to building a real business Continuous improvement as a competitive advantage The role of content marketing, community building, and reputation management Timestamps 00:00 – Introduction and podcast support note 00:30 – Abi Asija's background and transition into land investing 01:29 – Why raw desert land can be a profitable investment 02:28 – Buying tax-delinquent properties and flipping them for profit 03:25 – Using public records and software to streamline acquisitions 04:32 – The economics of direct mail campaigns in land investing 05:19 – Early success stories selling land on eBay and other platforms 06:54 – Understanding buyer motivations and land use cases 07:55 – Land as a long-term investment and speculative asset 09:21 – Challenges of selling raw land and market dynamics 10:07 – Utility companies and rare high-profit land opportunities 11:23 – Building goodwill through owner financing and customer service 12:37 – Growing through referrals and word-of-mouth marketing 14:24 – Over-delivering and strengthening customer relationships 15:08 – Why owner financing creates opportunities for buyers 16:20 – Managing tax risks, foreclosures, and customer retention 17:16 – Treating entrepreneurship as a serious business from day one 18:17 – Building scalable referral and reputation systems 19:36 – Effective upselling strategies and creating multiple offers 20:50 – Why speed-to-lead is critical in sales 22:07 – Scaling operations with offshore support teams 24:26 – Increasing customer lifetime value through systems and offers 26:07 – Continuous improvement and operational excellence 27:55 – Customer-centric lessons from successful business leaders 29:52 – Hiring and developing high-performance teams 32:19 – The power of niche marketing and focused messaging 34:48 – Future plans for scaling and building a lasting legacy 36:03 – The reality of entrepreneurship and hard work 38:22 – Fast response strategies for closing more deals 41:49 – Why relationships outperform cold outreach over time 44:48 – Creating valuable content that attracts ideal customers 55:54 – Solving specific problems through focused content marketing 58:44 – Why niching down is essential for business growth 59:02 – Abi's long-term vision and future goals 60:43 – Balancing growth, scalability, and lifestyle design 62:36 – Community, networking, and lifelong learning 63:40 – How to connect with Abi Asija and access his resources Resources & Links The Land Business by Abi Asija Abi Asija on LinkedIn Honest Wealth Builders YouTube Channel Your Business Website Connect with Abi Asija LinkedIn YouTube Channel Email

Champions Edition im Triathlon-Chat! Nach dem Neuseenman holen Nick und Nils die beiden Gewinner:innen des Pushing-Limits-Clubrennens ans Mikro: Naima und Max. Beide waren nicht nur im Club ganz vorne, sondern haben auch im Gesamtfeld richtig starke Ausrufezeichen gesetzt.In der Folge geht es um ihre ganz unterschiedlichen Wege in den Triathlon: Naima kommt aus dem Radsport und arbeitet heute als Ärztin in der Unfallchirurgie, Max ist erst seit rund dreieinhalb Jahren im Triathlon unterwegs, hat neben Abi, Barista-Job und Lebensumbruch den Sport für sich entdeckt – und fährt inzwischen Zeiten, die selbst Nick und Nils staunen lassen.Natürlich sprechen die vier auch ausführlich über das Rennen: Schwimmen, Pacing, Wattwerte, Laufbeine, die richtige Strategie und das Gefühl, wenn am Ende plötzlich ein richtig großer Tag dabei herauskommt. Dazu gibt's viel Community-Vibe, ehrliche Einblicke, Trainingsgeschichten und die Erkenntnis: In der Pushing-Limits-Bubble schlummern verdammt viele schnelle und spannende Geschichten.Themen der Folge:Neuseenman, Pushing-Limits-Clubrennen, Naima & Max, Race-Recap, Community, Triathlon-Einstieg, Training mit App, Schwimmen, Radfahren, Laufen, Pacing, Krafttraining und die Frage, wie aus ganz normalen Lebenswegen ziemlich außergewöhnliche Leistungen entstehen.Werbung: IncylenceRabattcode: pushinglimitsRabatt: 15% auf alles außer bereits reduzierte ArtikelGültig bis 21.06.26https://incylence.com/collections/laufsockenWerbung: PUSHING LIMITS CLUB30 Tage kostenlos testen

Champions Edition im Triathlon-Chat! Nach dem Neuseenman holen Nick und Nils die beiden Gewinner:innen des Pushing-Limits-Clubrennens ans Mikro: Naima und Max. Beide waren nicht nur im Club ganz vorne, sondern haben auch im Gesamtfeld richtig starke Ausrufezeichen gesetzt. In der Folge geht es um ihre ganz unterschiedlichen Wege in den Triathlon: Naima kommt aus dem Radsport und arbeitet heute als Ärztin in der Unfallchirurgie, Max ist erst seit rund dreieinhalb Jahren im Triathlon unterwegs, hat neben Abi, Barista-Job und Lebensumbruch den Sport für sich entdeckt – und fährt inzwischen Zeiten, die selbst Nick und Nils staunen lassen. Natürlich sprechen die vier auch ausführlich über das Rennen: Schwimmen, Pacing, Wattwerte, Laufbeine, die richtige Strategie und das Gefühl, wenn am Ende plötzlich ein richtig großer Tag dabei herauskommt. Dazu gibt's viel Community-Vibe, ehrliche Einblicke, Trainingsgeschichten und die Erkenntnis: In der Pushing-Limits-Bubble schlummern verdammt viele schnelle und spannende Geschichten. Themen der Folge: Neuseenman, Pushing-Limits-Clubrennen, Naima & Max, Race-Recap, Community, Triathlon-Einstieg, Training mit App, Schwimmen, Radfahren, Laufen, Pacing, Krafttraining und die Frage, wie aus ganz normalen Lebenswegen ziemlich außergewöhnliche Leistungen entstehen.

A bi-weekly news show informing you on the latest in Bitcoin, privacy and open source tech hosted by Ungovernables, Max and Q. AOBFTF with ZachQ eurotripNew Foundation websiteNEWSU.S. Treasury seizes nearly 1B in Iran-linked crypto, Tether freezes 344M USDT on Tron https://bitcoinmagazine.com/news/u-s-treasury-the-united-states-iranThe Mined in America Act would put the Bitcoin network at riskhttps://www.therage.co/mined-in-america-act-bitcoin-at-risk/CVE in Core Lightning: Optech #407 disclosurehttps://bitcoinops.org/en/newsletters/2026/05/29/Introducing Cube: Burak unveils a trustless Bitcoin smart contract L2https://medium.com/cube-bitcoin/introducing-cube-8b3702e470a5Published: May 2026Anonymous plaintiff sues for title to $293 billion in dormant Bitcoinhttps://bitcoinmagazine.com/news/anonymous-plaintiff-seeks-legal-bitcoinPublished: 2026-05-28The U.S. Constitution inscribed on the Bitcoin blockchain via expanded OP_RETURN https://bitcoinmagazine.com/news/someone-inscribed-the-constitution-bitcoinPublished: 2026-05-29RELEASESBitcoin Protocol, Core, Knots, SecurityCore Lightning v26.06rc2 — 2026-05-22Release candidate 2 for CLN 26.06. Documentation and gRPC interface refinements on top of rc1's graceful command, sendamount RPC, and BOLT12 payer-proof support. Routing-node operators should test on a non-production node before adopting.Eclair 0.14.0 — 2026-05-21Significant Lightning release from ACINQ. Final versions of channel splicing, simple taproot channels, and zero-fee commitments all ship in this version. This is the Eclair side of the same protocol work showing up in CLN and LDK. If you run an Eclair routing node, this is the upgrade to track.Hardware Signers and Hardware-Wallet AppsColdcard MK5 launch — 2026-05-29New flagship hardware. Larger Gorilla Glass screen, redesigned buttons, improved NFC, dual secure element architecture retained. Already supported in Bitcoin Safe 2.0.0rc0 from earlier this fortnight.Frostsnap 0.3.0 — 2026-05-27Headline change: deterministic firmware build with cryptographic digest verification. So end users can independently verify the firmware binary matches the source. That is the right direction for any hardware signer carrying real money.Keystone 3 v2.4.4 — 2026-05-26Wallet connection removal, Zcash SLIP39 support added, device verification fixes.Trezor Suite v26.5.1 — 2026-05-27 (FTD re-surfacing)Adds ERC-681 QR code support in the send form. Show editorial: only relevant if you use Trezor for Ethereum-side workflows, not a Bitcoin-only change.Ledger Live Desktop 4.5.0 — 2026-05-21Bridge integration refactoring across desktop and mobile.Ledger Live Mobile 4.6.0 — 2026-05-28Async API updates and bridge resolution improvements.Software WalletsSparrow Wallet 2.5.0 — 2026-05-21Headline feature: Silent Payments receiving wallets, including support for airgapped hardware wallet signers. Adds frigate.2140.dev as a Silent Payments capable public Electrum server, auto-selected when required. Plus a BIP32 derivation fallback when retrieving signing nodes for high-index inputs. This is the biggest privacy upgrade of the fortnight in any consumer-facing Bitcoin wallet, and the airgapped-signer support means Coldcard and similar users get it without going hot.Sparrow Frigate 1.5.3 — 2026-05-30Adds a privacy-preserving hourly aggregate of historical scan stats, locally generated server.features response when the backend returns a method-not-found error, improvements to the hosts field in server.features.Bitcoin Seed Tool 2.3.0 — 2026-05-19 (borderline, in grace)Educational interface redesign with violet accent color and integrated learning features.Nunchuk Android 2.5.2 — 2026-05-27"Bug fixes and improvements," nothing detailed publicly.Liana Business v0.1 — 2026-05-20First alpha of Liana's business product line. Environment variable support for signet testing. New product tier from Wizard Sardine for business-focused multisig with timelocked recovery.Peach Bitcoin 0.69.0 (build 350) — 2026-05-19Encrypted backup of custom payout addresses, restoration guidance, camera permission fix, push notification translations.Lightning, L2, ScalingPhoenix 2.8.0 — 2026-05-22UI fixes on Android: scanning inverted QR codes, a button to use the entire available balance when paying Lightning.Phoenixd 0.8.0 — 2026-05-20Upgraded lightning-kmp dependency to 1.12.0.ZEUS 13.0.2 — 2026-05-21Stable release of the RC chain we previewed last fortnight. New default RGS server at rgs.zeusln.com with 15-minute graph updates instead of 3-hour. Improved clipboard, NFC, UI improvements.Arkade arkd v0.9.6 — 2026-05-26Package and component renaming, CI workflow improvements, golang version bump.Arkade TS SDK @arkade-os/sdk 0.4.32 — 2026-05-29Maintenance bump.Arkade TS SDK @arkade-os/boltz-swap 0.3.37 — 2026-05-29Maintenance bump on the Boltz-swap helper.ThunderHub v0.18.4 — 2026-05-29Native display formatting for trading distribution, better CLTV headroom in route building.Blink Mobile 2.4.49 — 2026-05-30Bug fix: removes ABI-prefixed versionCode overrides.LNbits v1.5.5-rc1 — 2026-05-24Release candidate.Mostro v0.17.4 — 2026-05-22Payout confirmation to winner, solver-directed dispute slash, concurrent taker bonds with first-to-lock wins, MOSTRO_NSEC_PRIVKEY environment variable, Yadio price tolerance fix.Bisq v1.10.1 — 2026-05-30Raises trade amount limits to 0.250 BTC after the v1.10.0 post-exploit reset. Adjusts risk-based reduction factors. Fixes a BSQ swap validation bug.Bisq v1.10.0 — 2026-05-17 (carries over from last fortnight as final tag on cutoff day)The post-incident hardening release we covered last fortnight: trade protocol validation, PGP supply-chain verification, 0.125 BTC initial cap, macOS Apple Silicon support.EcashCashu TS v4.5.1 — 2026-05-23Deprecates the current checkProofsStates method in favour of a v5-compatible one. Wallet builders should plan the migration.Fedimint SDK canary release — 2026-05-27React Native transport: flattened RPC payload, persistent callback. Rolling canary channel.Bitcoin Dev InfrastructureBDK FFI 3.0.0 — 2026-05-29Major version of the BDK language bindings. Anyone shipping a wallet on top of BDK should read the migration notes carefully.Liquid GDK 0.77.4 — 2026-05-27Rate-limiting error handling, Rust dependency updates, UTXO retrieval fixes, build improvements.Self-Hosting and Sovereignty InfraJoinMarket-NG 0.31.1 — 2026-05-30Privacy-critical fix: prevents a Sybil DoS where relayed !hp2 floods could starve a maker's own post-ioauth commitment broadcasts. Also installs whiptail in maker and taker container images so the jm-ng TUI works out of the box. JoinMarket-NG continues to ship hardening on a tight cadence.Tor Browser 15.0.14 — 2026-05-19 (borderline, in grace)Important Firefox security updates rolled in.Mullvad Browser 15.0.14 — 2026-05-19 (borderline, in grace)Firefox 140.11.0esr base, NoScript 13.6.19.1984.Nostr (Bitcoin-relevant)Amethyst 1.11.0 — 2026-05-20Restores Lightning Address and LNURL fields in Edit Profile. Useful: those fields were missing for a stretch and creators relying on zaps as a revenue stream were getting cut off in profile edits.EDUCATIONTFTC retrospective: Why Keonne Rodriguez is in prison for building Samourai Wallet — 2026-05-28Bitcoin Optech Newsletter #407 — 2026-05-29CLN vulnerability disclosure (already in news), transcripts from a May Bitcoin Core developer meeting covering SwiftSync, cluster mempool, Erlay redesign, package relay. Eclair 0.14.0 and CLN 26.06rc2 release context.Bitcoin Optech Newsletter #406 — 2026-05-22BIP322 advances to Complete status with human-readable prefixes and PSBT support. TCP hole punching for Bitcoin nodes behind NATs (we flagged this Delving Bitcoin thread last fortnight). Services section highlights Ibis Wallet (BDK-based with coin control and Tor), LDK Server, Mempool.space taproot visualization.Bitcoin Optech #406 recap podcast — 2026-05-26Discussion of BIP322 updates, TCP hole punching, Ibis Wallet, LDK Server, Mempool.space v3.3.0, peer-observer infrastructure.Bitcoin Optech #405 recap podcast — 2026-05-19Bitcoin Core CVE-2024-52911 discussion and the UTXO-set P2P sharing draft BIP with Fabian Jahr.Rainey's book on financial censorshipMentioned by Gladstein on 2026-05-21 as quoting his work on the war on cash and the blocksize war. Plug in education / further reading.TO DONATE TO ROMAN'S DEFENSE FUND: https://freeromanstorm.com/donateHELP GET SAMOURAI A PARDONSIGN THE PETITION ----> https://www.change.org/p/stand-up-for-freedom-pardon-the-innocent-coders-jailed-for-building-privacy-tools DONATE TO THE FAMILIES ----> https://www.givesendgo.com/billandkeonneSUPPORT ON SOCIAL MEDIA ---> https://billandkeonne.org/VALUE…

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

Four years?! Somehow we've been talking about Tolkien long enough to celebrate another podcast birthday, and this year we're marking the occasion with a special bonus episode! Join us as we share our first-ever reactions to The Lord of the Rings: The War of the Rohirrim—the moments we loved, the things that surprised us, and a few thoughts that may or may not change after future rewatches. Fair warning: we intentionally recorded before diving into timelines, lore deep-dives, or research, so these are our completely unfiltered first impressions. Then the celebration continues with a Tolkien-themed game of Jeopardy! Play along with us and see if you can beat our scores. Bonus points if you immediately knew the answer to Abi's tricky question that we absolutely could not remember in the moment. Thank you for spending the last four years journeying through Middle-earth with us—we couldn't have done it without you!P.S. Ashley would like the record to show that she is aware that Thengel was Théoden's father, not his grandfather. (He was Éowyn's grandfather, which is where the wires got crossed.) Sorry! Nobody's perfect.https://linktr.ee/sistersoftheshirepodcasthttps://www.instagram.com/sistersoftheshirepodcast/https://www.patreon.com/sistersoftheshirepodcasthttps://open.spotify.com/show/1HIhmdeX6761vi7RyOjl8f?si=_qwdGdP7SbmAP2RWlji54w

In this episode of TAB Storytellers, Jen and Abi sit down with longtime TAB educator Tom Burkle and preservice art educator Liam Schneider for a beautiful full-circle conversation about teaching, mentorship, student agency, and what it means to grow into TAB over time. Liam was once Tom's elementary art student, later became Abi's student at the University of Northern Colorado, and recently returned to Tom's classroom as a student teacher. Together, they reflect on Tom's early move toward choice, the small classroom moments that can shift an educator's whole philosophy, and the power of seeing students, and future teachers, as capable artists and thinkers.The conversation moves through TAB history in Colorado, curriculum design, artist statements, classroom management, confidence-building, and the real planning and organization behind a choice-based studio. Tom and Liam also talk honestly about behavior, routines, individualized consequences, and the importance of reflective mentorship in helping new teachers stay grounded, curious, and willing to try again.Bonus update: Since this conversation was recorded in March (yes Abi was busy and yes she got behind and is playing catch up), Liam graduated and has found a job! He will be teaching high school pottery next year in the same town near Tom, and they are both excited for this next chapter. Here is a pic of Abi and Liam from the right before Liam graduated.ResourcesTeaching for Artistic Behavior / TAB: Official TAB website and starting place for learning more about TAB pedagogy, practice, professional development, and community.  https://teachingforartisticbehavior.orgTAB Community on Mighty Networks: Online community for TAB educators to connect, ask questions, and share resources. https://teaching-for-artistic-behavior-inc.mn.co/Fred Tjardes School of Innovation, Greeley, Colorado: Mentioned by Liam and Abi as a powerful example of inquiry, student agency, theme-based learning, and choice-centered practice beyond the art room.  https://ftsoi.greeleyschools.org/Understanding by Design by Grant Wiggins and Jay McTighe: Tom mentions this book as part of his early thinking around curriculum, assessment, and how students demonstrate higher-level thinking.  https://www.ascd.org/books/understanding-by-design-expanded-2nd-editionUnderstanding by Design Framework White Paper: A helpful overview of the UbD framework for curriculum planning and assessment. https://files.ascd.org/staticfiles/ascd/pdf/siteASCD/publications/UbD_WhitePaper0312.pdfOlivia Gude's “Postmodern Principles: In Search of a 21st Century Art Education”:  Liam references Connie Stewart introducing him to postmodern principles, which became a game changer in his understanding of choice, meaning-making, and contemporary art education.  https://www.tandfonline.com/doi/abs/10.1080/00043125.2004.11653528University of Northern Colorado:  Referenced as part of Liam's preservice teacher education journey and Abi's teaching context. https://www.unco.edu/pva/art-design/areas/art-education/TAB Colorado:  Mentioned in the conversation as part of the broader Colorado TAB story and community.  https://coloradotabinc.orgMassArt TAB Institute: Referenced in the conversation as part of the broader timeline of TAB professional learning and community-building.  https://pce.massart.edu/programs/tabTeaching for Artistic Behavior: A Definition and Historiography by Abi Paytoe Gbayee: Abi mentions her dissertation and Tom's connection to her research on continuums of choice. https://www.proquest.com/dissertations-theses/teaching-artistic-behavior-definition/docview/2817860186/se-2 Here is a lightly edited transcript of this episode. We recognize that there are probably errors and grammatical issues. If anyone with the time or inclination to edit this wants to do so, please email us at storytellers@teachingforartisticbehaviors.org⁠.

What could be better than a tiny plant with an outsized impact on the world around it? Hornleaf riverweed AKA Podostemum ceratophyllum is one such plant. This tiny aquatic plant has so many mysterious surrounding it but what we do know is that it is foundational to the aquatic ecosystems in which it is found. Join me and Dr. James Wood as we take a deep dive on this unique aquatic plant and learn what you can do to help us understand and conserve it a little bit better. This episode was produced in part by Elise, Maggie, Mamie, A.J., Dallas, Channele, KC, Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie. See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Welcome to the emDOCs.net podcast! Join us as we review our high-yield posts from our website emDOCs.net.Today on the emDOCs cast with Brit Long (@long_brit), we cover how to evaluate and manage acute limb ischemia. To continue to make this a worthwhile podcast for you to listen to, we appreciate any feedback and comments you may have for us. Please let us know!Subscribe to the podcast on one of the many platforms below:Apple iTunesSpotifyGoogle Play Send us Fan Mail

Our good friend Abi joins us to discuss the new EHRC guidance and the plan to spend billions of dollars on bathrooms. But first… we look to the skies. The truth is out there. In Doncaster. Get more TF episodes each week by subscribing to our Patreon here! RILEY ALERT Check out No Gods, No Mayors here! HUSSEIN ALERT Check out 10k Posts here! MILO ALERT Check out Milo's tour dates here: https://www.miloedwards.co.uk/liveshows NATE ALERT Lions Led By Donkeys will be performing live in London on 29th May and you can get tickets here! Also, Nate's band Second Homes has just released their debut album, which includes the song used in this episode's outro, and you can stream it for free here!

Seed storage is one of the most important tools in plant conservation, but did you know you can also store pollen? We still have a lot to learn about storing both pollen and seeds for most species, and people like Dr. Dustin Wolkis of the Center for Plant Conservation are hard at work doing just that. Join us for an interesting look at what he and his colleagues are doing to prevent plant extinction. This episode was produced in part by Elise, Maggie, Mamie, A.J., Dallas, Channele, KC, Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

There is a gap between where your life is and where you thought it would be. That gap has a name. It is grief. A kind of hidden, invisible grief. And most of us are walking around carrying it without ever calling it that, because we have been taught that grief belongs only to those who have lost someone to death. The rest of us are supposed to just get on with it.Dr. Lucy Hone is an adjunct senior fellow at the University of Canterbury, a leading resilience researcher, and one of the world's most trusted voices on loss and grief. Her TED talk on resilience has been viewed more than nine million times. She is also a mother who lost her 12-year-old daughter, Abi, in a car accident in 2014, and who has spent the decade since weaving her scientific training and her lived experience into tools that actually work. Her new book is How Will I Ever Get Through This?In this conversation, we go to the places most conversations about grief are afraid to go.What you will explore:Why grief is not an emotion but a full-body experience that explains the exhaustion, brain fog, and 3 am waking you may have been blaming on other thingsWhat "living losses" are, the griefs that come without a funeral, and why they may be driving far more of our suffering than we recognizeThe difference between acceptance and coming to terms with, and why one word changes everything about how you move through lossWhat the research actually shows about post-traumatic growth, including the statistic that will surprise you about how common it actually isWhy resilience is not about bouncing back, and what Dr. Hone means when she says you do not bounce back from anything that mattersThe one question she asks herself in the hardest moments, and why it is a more useful starting point than any techniqueIf you have ever minimized something you were going through because it did not feel like it counted as real loss, this conversation is for you.You can find Lucy at: Website | Instagram | Episode TranscriptNext week, I am going solo to talk about something that I think a lot of us are quietly carrying, the conversations we know we need to have with the people who matter most to us, and why we keep finding reasons not to have them. The research turns out to be really clear on this: we consistently overestimate how bad it will be and underestimate how much it costs us to stay silent. Be sure to follow Good Life Project wherever you get your podcasts so you don't miss any upcoming episodes!Check out our offerings & partners: Join My New Writing Project: Awake at the WheelVisit Our Sponsor Page For Great Resources & Discount Codes Hosted on Acast. See acast.com/privacy for more information.

Abi and Matt name boats. 

Long lived organisms like trees face a lot of challenges throughout their lifetime. Disturbances big and small coupled with climate change are going to continue to stress trees wherever they grow. Which trees have the highest capacity to deal with said stresses? We don't know until we go looking. That is what drives scientists like Dr. Jill Hamilton. Join us as we look at how she is using poplars, spruce, and ash to understand how trees and their hybrids may or may not have what it takes to survive climate stress. This episode was produced in part by Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

What can investigating the genes in flower development teach us about plant evolution? A lot! What started as a simple question about the quirky nature of flower development in the order of plants collectively referred to as "the gingers" turned into multiple threads related to plant evolution and diversity. Join me and Dr. Chelsea Specht as we take a deep dive into the wild world of Zingiberales. This episode was produced in part by Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Ste is joined by Paul and Abi as they debate the hottest topics ahead of Liverpool's match with Chelsea in the Premier League including whether Mac Allister should start after a poor performance against Man United and who should start on the wings.

Micro moths are a wonderfully diverse group of underappreciated insects living all around us. How they interact with their environment, particularly with the native plants the need to survive, is both fascinating and mysterious. Join me and Dr. Jason Dombroskie as we explore the tiny world of micro moths, their host plants, and all the natural history mysteries in between. This episode was produced in part by Andy, S Heller, Drewsophila, Sascha, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.