Podcasts about LM

LM publica cómo Red Eléctrica forma parte del organismo internacional que supuestamente va a investigar el apagón en España.

LM publica cómo Corredor y la cúpula de REE pueden pagar penal y patrimonialmente si se certifica oficialmente el abuso de renovables.

Laudetur Jesus Christus - Ngợi khen Chúa Giêsu KitôRadio Vatican hằng ngày của Vatican News Tiếng Việt.Nội dung chương trình hôm nay:0:00 Bản tin12:38 Chia sẻ Lời Chúa : Lm Đaminh Vũ Duy Cường, SJ, chia sẻ Lời Chúa Chúa Nhật thứ 4 Phục Sinh.21:09 Suy tư : Từ Đức Phanxicô đến Đức Lêô XIV, một Chúa Thánh Thần luôn bất ngờ và mới mẻ---Liên lạc và hỗ trợ Vatican News Tiếng Việt qua email: tiengviet@vaticannews.va

LM publica cómo Fernando Ferrando insiste en que "mantengamos la calma" y "aprendamos de esto".

LM publica cómo documentos de Red Eléctrica advierten desde 2024 sobre riesgos en el suministro eléctrico por la integración masiva de renovables.

LM publica cómo tras un examen eterno de la CNMC y los cambios de criterio del Gobierno, Sánchez anuncia una consulta pública sobre la OPA.

Lethal Mullet Podcast: Special: Lord of the Rings with Adam Bray On tonight's episode The Mullet catches up with his dear friend Adam Bray, Star Wars author, and Marvel author as they look into the world of pugs, Star Wars, live actions series, and a deep look at the world of Tolkien's Lord of the Rings.  Find Lethal Mullet Podcast on: Apple / Stitcher / Spotify / Google Play / Podbean / IheartRadio / YouTube Contact: Site: fpnet.podbean.com Twitter: @fanpodnetwork Facebook & Instagram: Fandom Podcast Network Adam: @thelethalmullet (Twitter/Facebook/Instagram) Check out the Video Show on YouTube: www.youtube.com/@fandompodcastnetwork FPN Master Feed: fpnet.podbean.com Catch the flagship show: Culture Clash, Blood of Kings, and the host of amazing podcasts covering all of Lethal Mullet Podcast  Tee public: Grab all kinds of LM merchandise @ teepublic.com #adambray #lordoftherings #starwars #marvel #tolkien  #fandompodcastnetwork #lethalmulletpodcast #adamobrien #australia

Folks this one's a fun one. Strap in. Join Spencer, Ty and Andy -- along with friend of the show Griffin -- as they sit down to write a television show... and maybe more. Support us on Patreon for $5, $7, or $10: www.patreon.com/tgofv. A big shout-out to our $10/month patrons: Abbie Phelps, Adam W, Anthony Cabrera, asdf, Axon, Baylor Thornton, Bedi, bernventers, bunknown, Celeste, Charles Doyle, Dane Stephen, Dave Finlay, David Gebhardt, Dean, Francis Wolf, Heather-Pleather, Jacob Sauber-Cavazos, James Lloyd-Jones, Jennifer Knowles, Jeremy-Alice, Josh O'Brien, Kilo, LM, Lawrence, Louis Ceresa, Malek Douglas, Newmans Own, Packocamels, Phat Ass Cyberman, Rach, raouldyke, Rebecca Kimpel, revidicism, Sam Thomas, T, Tash Diehart, Themandme, Tomix, weedworf, William Copping, and Yung Zoe!

LM publica cómo el documento se encuentra disponible en la propia web de Red Eléctrica.

LM publica cómo según el borrador de actualización del PNIEC, la generación eléctrica renovable en 2030 será el 81% y del 100% en el año 2050.

Em semana de apagão, a Rádio manteve o país conectado. É neste meio de excelência que comentamos o debate LM e PNS, o aproveitamento político de temas como a saúde mental e as comemorações da Liberdade.See omnystudio.com/listener for privacy information.

LM publica cómo el día después al apagón, la hidráulica generaba 40 veces más energía que la que generó a las 12:30 del fatídico lunes.

LM publica cómo a la vista está que las alertas no fueron escuchadas. Los "ciclos combinados" pueden ser "inviables".

LM publica cómo las centrales nucleares y otras tecnologías garantizan la estabilidad del sistema.

The return of everybody's favorite new series! Yippee! Join Spencer, Ty and Andy as they pit characters from all across fiction against each other... in order to test their abilities. Support us on Patreon for $5, $7, or $10: www.patreon.com/tgofv. A big shout-out to our $10/month patrons: Abbie Phelps, Adam W, Anthony Cabrera, asdf, Axon, Baylor Thornton, Bedi, bernventers, bunknown, Celeste, Charles Doyle, Dane Stephen, Dave Finlay, David Gebhardt, Dean, Francis Wolf, Heather-Pleather, Jacob Sauber-Cavazos, James Lloyd-Jones, Jennifer Knowles, Jeremy-Alice, Josh O'Brien, Kilo, LM, Lawrence, Louis Ceresa, Malek Douglas, Newmans Own, Packocamels, Phat Ass Cyberman, Rach, raouldyke, Rebecca Kimpel, revidicism, Sam Thomas, T, Tash Diehart, Themandme, Tomix, weedworf, William Copping, and Yung Zoe!

LM publica un nuevo lunes negro de Rotellar en el que analiza cómo el Gobierno quiere convertir el INE en un CIS estadístico.

Review các phim ra rạp từ ngày 25/04 và dịp lễ 30/04/2025THÁM TỬ KIÊN: KỲ ÁN KHÔNG ĐẦU – T16Đạo diễn: Victor VũDiễn viên: Quốc Huy, Đinh Ngọc Diệp, Quốc Anh, Minh Anh, Anh Phạm,Thể loại: Kinh DịThám Tử Kiên là một nhân vật được yêu thích trong tác phẩm điện của ăn khách của NGƯỜI VỢ CUỐI CÙNG của Victor Vũ, Thám Tử Kiên: Kỳ Không Đầu sẽ là một phim Victor Vũ trở về với thể loại sở trường Kinh Dị - Trinh Thám sau những tác phẩm tình cảm lãng mạn trước đó.LẬT MẶT 8: VÒNG TAY NẮNG – T13Đạo diễn: Lý HảiDiễn viên: NSƯT Kim Phương, Long Đẹp Trai, NSƯT Tuyết Thu, Quách Ngọc Tuyên, Đoàn Thế Vinh, Hồng Thu,.... Thể loại: Gia đình, Tâm LýMột bộ phim về sự khác biệt quan điểm giữa ba thế hệ ông bà cha mẹ con cháu. Ai cũng đúng ở góc nhìn của mình nhưng đứng trước hoài bão của tuổi trẻ, cuối cùng thì ai sẽ là người phải nghe theo người còn lại? Và nếu ước mơ của những đứa trẻ bị cho là viển vông, thì cơ hội nào và bao giờ tuổi trẻ mới được tự quyết định tương lai của mình?MẬT DANH: KẾ TOÁN 2 – T18Đạo diễn: Gavin O'ConnorDiễn viên: Ben Affleck, Jon Bernthal, J.K. Simmons, ...Thể loại: Hành Động, Tâm Lý, Tội phạmChristian Wolff (Ben Affleck) sở hữu tài năng giải quyết những vấn đề phức tạp. Khi một người bạn cũ bị ám sát, để lại một thông điệp mơ hồ yêu cầu "truy tìm kế toán", Wolff bị cuốn vào việc giải quyết vụ án. Nhận ra rằng cần phải có những biện pháp cực đoan, Wolff đã liên lạc với người anh trai xa cách và vô cùng nguy hiểm của mình, Brax (Jon Bernthal), để cùng nhau điều tra. Cùng với Phó Giám đốc Cục Tài chính Marybeth Medina (Cynthia Addai-Robinson), họ phát hiện ra một âm mưu chết người, trở thành mục tiêu của một mạng lưới sát thủ tàn bạo, sẵn sàng làm mọi thứ để chôn vùi những bí mật của mình.Phim Shin Cậu Bé Bút Chì: Bí Ẩn! Học Viện Hoa Lệ TenkasuĐạo diễn: Wataru TakahashiThể loại: Hoạt Hình, Thần thoạiCâu chuyện của bộ phim bắt đầu với Shinnosuke và những người bạn của Shin thuộc Đội đặc nhiệm Kasukabe trải qua một tuần ở lại "Học viện Tư nhân Tenkasu Kasukabe" (Còn gọi là "Học viện Tenkasu"), một trường nội trú ưu tú được quản lý bởi một AI hiện đại, "Otsmun". CHUYỆN MUÔNG THÚ DẠY BÉ CỪU BAYĐạo diễn: Meisam Hosseini, Hossein SaffarzadeganDiễn viên: Figen Aksoy, Funda Askin, Didem Atlihan,...Thể loại: Hoạt HìnhSống trong thế giới nơi chỉ có loài chim mới được phép bay đã giới hạn ước mơ của biết bao giống loài, điển hình là bé cừu nhỏ Woolina.Trên hành trình chinh phục giấc mơ không tưởng, Woolina đã sát cánh cùng hội bạn Beep Beep, Momo,..dù nhận lấy sự phản đối từ mọi người. LOONEY TUNES: NGÀY TRÁI ĐẤT NỔ TUNGĐạo diễn: Peter BrowngardtThể loại: Hoạt HìnhVịt Daffy và heo Porky, bộ đôi lắm chiêu trong loạt phim hoạt hình kinh điển Looney Tunes, chính thức bước lên màn ảnh rộng với một phi vụ bùng nổ chưa từng có. Khi phát hiện nhà máy kẹo cao su trong thị trấn dính líu đến âm mưu thao túng Trái đất của người ngoài hành tinh, cả hai trở thành những anh hùng bất đắc sĩ và lao vào một hành trình hài hước, đầy hỗn loạn để cứu thế giới khỏi âm mưu xấu xa của kẻ thù.Khủng Long Xanh Du Hành Thế Giới Truyện TranhĐạo diễn: Wojtek WawszczykThể loại: Hoạt HìnhKhủng Nhong - một chú khủng long xanh với tính cách hiếu động, tò mò bị lạc mất cha mẹ và buộc phải lên đường tìm lại gia đình. Là một sinh vật sống trong cuốn truyện tranh do hoạ sĩ Tét vẽ - người đang muốn tẩy xóa những trang truyện tranh của mình sau lời phê bình từ nhà xuất bản, Khủng Nhong bắt đầu dịch chuyển từ cuốn truyện này sang cuốn truyện khác. Trên hành trình phiêu lưu qua những thế giới kỳ diệu, Khủng Nhong lần lượt gặp gỡ Phù Thuỷ Tinh Tú, Tiến Sĩ Tóc Búi và Giáo Sư Đầu Xù. Để cứu cha mẹ của Khủng Nhong, tất cả các nhân vật hoạt hình phải tin tưởng vào chính mình và thuyết phục hoạ sĩ Tét giữ lại “đứa con tinh thần” thay vì cố gắng sáng tác những gì ông không hề yêu thích.

Notre interlocuteur de la marque, nous a alors trouvé une solution de repli originale et très sympathique, essayer à la place du LM le duo haut de gamme de chez Lexus; la berline LS500h et le Suv RX500h, deux hybrides non rechargeables offrant une réponse client totalement différente.Distribué par Audiomeans. Visitez audiomeans.fr/politique-de-confidentialite pour plus d'informations.

LM publica cómo precisamente, Escribano M&E es la empresa familiar del actual presidente de Indra, Ángel Escribano.

Thank you for listening! @RunDFF & @ffLarryMonkey are joined by LM's daughter Cassidy and the IDP Legend Hollywood Titan and The Angry Sports Couple!  Click LIKE/SUBSCRIBE/FOLLOW and maybe give us a 5 STAR RATING and a sweet REVIEW! We also launched a Patreon! (link below) Check it out and if you'd like to support the show for as little as $1 per month and that gets you into our GroupMe chat where we get into everything Dynasty football literally 24/7/265! We love you! - Join the Hot Sauce listener League! (dm the show @DynastyHotSauce or @RunDFF or @ffLarryMonkey) - Check out our MERCH it's the cheapest around! https://dynasty-hot-sauce-pod.printify.me/products Patreon link: https://www.patreon.com/user?u=13685080&utm_medium=clipboard_copy&utm_source=copyLink&utm_campaign=creat  

Laudetur Jesus Christus - Ngợi khen Chúa Giêsu KitôRadio Vatican hằng ngày của Vatican News Tiếng Việt.Nội dung chương trình hôm nay:00:00 Bản tin17:00 Chia sẻ lời Chúa: Lm. Gioan Baotixita Phương Đình Toại, dòng Camilo, chia sẻ Lời Chúa Chúa Nhật thứ 2 Phục Sinh28:05 Suy tư về Đức Thánh Cha: 6 năm cuối của Đức Phanxicô: Đại dịch, lữ hành đến vùng ngoại vi thế giới, cải cách Giáo triều, kêu gọi hòa bình, đau bệnh---Liên lạc và hỗ trợ Vatican News Tiếng Việt qua email: tiengviet@vaticannews.va

LM publica cómo García envía un borrador de decreto a Bruselas que prohíbe las bolsas de nicotina mientras ultima otro borrador con lo contrario.

LM publica cómo "Malas lenguas" ya ha perdido el 72% de la audiencia de su estreno.

LM publica cómo Sánchez quitó a los españoles 222 millones adicionales en impuestos en 2024 con cargo a los pocos ahorros que lograron.

On tonight's episode The Mullet does the first of three episodes looking at the amazing life of director Quentin Tarantino, with his first film: RESERVOIR DOGS. Join us as we look at this great classic cult film, and see why it still holds up in this time of superhero film as a far more interesting film.  Find Lethal Mullet Podcast on: Apple / Stitcher / Spotify / Google Play / Podbean / IheartRadio / YouTube Contact: Site: fpnet.podbean.com Twitter: @fanpodnetwork Facebook & Instagram: Fandom Podcast Network Adam: @thelethalmullet (Twitter/Facebook/Instagram) Check out the Video Show on YouTube: www.youtube.com/@fandompodcastnetwork FPN Master Feed: fpnet.podbean.com Catch the flagship show: Culture Clash, Blood of Kings, and the host of amazing podcasts covering all of Lethal Mullet Podcast  Tee public: Grab all kinds of LM merchandise @ teepublic.com #eighties #nineties #seventies #tarantino #revervoirdogs #fandompodcastnetwork #lethalmulletpodcast #adamobrien #australia   New boost

Who? What? Where? And others. Join Spencer, Ty and Andy as they answer questions posed by the podcast's most loyal and curiosity-filled fans, on the one and only beautiful TGOFV Discord. Support us on Patreon for $5, $7, or $10: www.patreon.com/tgofv. A big shout-out to our $10/month patrons: Abbie Phelps, Adam W, Anthony Cabrera, asdf, Axon, Baylor Thornton, Bedi, bernventers, bunknown, Celeste, Charles Doyle, Dane Stephen, Dave Finlay, David Gebhardt, Dean, Francis Wolf, Heather-Pleather, Jacob Sauber-Cavazos, James Lloyd-Jones, Jennifer Knowles, Jeremy-Alice, Josh O'Brien, Kilo, LM, Lawrence, Louis Ceresa, Malek Douglas, Newmans Own, Packocamels, Phat Ass Cyberman, Rach, raouldyke, Rebecca Kimpel, revidicism, Sam Thomas, T, Tash Diehart, Themandme, Tomix, weedworf, William Copping, and Yung Zoe!

LM publica la ‘chapuza' de Hacienda con el SMI se traducirá en niveles de imposición confiscatorios para rentas de entre 16.575 y 17.256 euros.

*Content warning: medical trauma and neglect, threat of life, mature and stressful themes, pregnancy and infant loss. *Free + Confidential Resources + Safety Tips: somethingwaswrong.com/resources Moms Advocating For MomsS23 survivors Markeda, Kristen and Amanda have created a nonprofit, Moms Advocating for Moms, in hopes to create a future where maternal well-being is prioritized, disparities are addressed, and every mother has the resources and support she needs to thrive: https://www.momsadvocatingformoms.org/take-actionhttps://linktr.ee/momsadvocatingformoms Please sign the survivors petitions below to improve midwifery education and regulation in Texashttps://www.change.org/p/improve-midwifery-education-and-regulation-in-texas?recruiter=1336781649&recruited_by_id=74bf3b50-fd98-11ee-9e3f-a55a14340b5a&utm_source=share_petition&utm_campaign=share_for_starters_page&utm_medium=copylink Malik's Law https://capitol.texas.gov/BillLookup/History.aspx?LegSess=89R&Bill=HB4553 M.A.M.A. has helped file a Texas bill called Malik's Law, which is intended to implement requirements for midwives in Texas to report birth outcomes in hopes of improving transparency and data collection in the midwifery field in partnership with Senator Claudia Ordaz. *Sources:American College of Nurse Midwiveshttps://midwife.org/ American College of Obstetricians and Gynecologists (ACOG)https://www.acog.org/ ACOG, Fetal Heart Rate Monitoring During Laborhttps://www.acog.org/womens-health/faqs/fetal-heart-rate-monitoring-during-labor Amniotomyhttps://www.ncbi.nlm.nih.gov/books/NBK470167/#:~:text=Amniotomy%2C%20also%20known%20as%20artificial,commonly%20performed%20during%20labor%20management. March of Dimeshttps://www.marchofdimes.org/peristats/about-us National Midwifery Institutehttps://www.nationalmidwiferyinstitute.com/midwifery North American Registry of Midwives (NARM)https://narm.org/ The Second Trimesterhttps://www.hopkinsmedicine.org/health/wellness-and-prevention/the-second-trimester#:~:text=The%20second%20trimester%20is%20the,grow%20in%20length%20and%20weight. Stages of labor and birthhttps://www.mayoclinic.org/healthy-lifestyle/labor-and-delivery/in-depth/stages-of-labor/art-20046545 State investigating Dallas birth center and midwives, following multiple complaints from patientshttps://www.wfaa.com/article/news/local/investigates/state-investigating-dallas-birth-center-midwives-following-multiple-complaints-from-patients/287-ea77eb18-c637-44d4-aaa2-fe8fd7a2fcef Texas Department of Licensing and Regulation (TDLR)https://www.tdlr.texas.gov/ What to Know About Cervical Dilationhttps://www.healthline.com/health/pregnancy/cervix-dilation-chart Zucker School of Medicine, Amos Grunebaum, MDhttps://faculty.medicine.hofstra.edu/13732-amos-grunebaum/publications *SWW S23 Theme Song & Artwork: Thank you so much to Emily Wolfe for covering Glad Rag's original song, U Think U for us this season!Hear more from Emily Wolfe:On SpotifyOn Apple Musichttps://www.emilywolfemusic.com/instagram.com/emilywolfemusicGlad Rags: https://www.gladragsmusic.com/ The S23 cover art is by the Amazing Sara StewartFollow Something Was Wrong:Website: somethingwaswrong.com IG: instagram.com/somethingwaswrongpodcastTikTok: tiktok.com/@somethingwaswrongpodcast Follow Tiffany Reese:Website: tiffanyreese.me IG: instagram.com/lookiebooThe Webby Awards (2025)Exciting news! Something Was Wrong is nominated for Best Crime & Justice Podcast at the 2025 Webby Awards. We'd love and appreciate your support—cast your vote today!https://vote.webbyawards.com/PublicVoting#/2025/podcasts/shows/crime-justice*Please note: the first airing of this episode stated that Rachel was a CNM, she is a CPM and LM so we corrected this error within an hour of release. See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

For those who haven't lived through them, this is the definitive ranking of all the years. For those who did live through them, just chill out and let us do our thing. Join Spencer, Ty and Andy as they take a look back at the past 20-odd years through the lens of movies, music, video games, and historical events recorded on Wikipedia. Support us on Patreon for $5, $7, or $10: www.patreon.com/tgofv. A big shout-out to our $10/month patrons: Abbie Phelps, Adam W, Anthony Cabrera, asdf, Axon, Baylor Thornton, Bedi, bernventers, bunknown, Celeste, Charles Doyle, Dane Stephen, Dave Finlay, David Gebhardt, Dean, Francis Wolf, Heather-Pleather, Jacob Sauber-Cavazos, James Lloyd-Jones, Jennifer Knowles, Jeremy-Alice, Josh O'Brien, Kilo, LM, Lawrence, Louis Ceresa, Malek Douglas, Newmans Own, Packocamels, Phat Ass Cyberman, Rach, raouldyke, Rebecca Kimpel, revidicism, Sam Thomas, T, Tash Diehart, Themandme, Tomix, weedworf, William Copping, and Yung Zoe!

LM publica cómo los desplazamientos costaron 29.186,10 euros y se sufragaron gastos de artistas que no trabajaban en el CNIO.

Đi tìm người môn đệ ẩn danh - Lm. Barthôlômêô Nguyễn Anh Huy, SJ | Lời Vào Đời ✅Link YouTube: https://youtu.be/JFKVTDVJHJ0 #tgpsg #loivaodoi Tham gia làm hội viên của kênh này để ủng hộ chúng tôi: https://www.youtube.com/channel/UCtoQh7mQikZsztA1OQRSFvw/join

LM publica cómo la UE tiene ante sí una oportunidad estratégica: completar su mercado único y liderar la liberalización global del comercio.

LM publica los detalles del plan de Sánchez contra los aranceles que certifican que es puro humo: sólo 400 millones son a fondo perdido.

Okay so they're pirates. But they're also robots? And skeletons? And scantily-clad women? Too rich for my blood! Join Ty and Andy as they explore the crazy mixed-up world of crime on the high seas that your most annoying friend can't stop yelling at you about. Support us on Patreon for $5, $7, or $10: www.patreon.com/tgofv. A big shout-out to our $10/month patrons: Abbie Phelps, Adam W, Anthony Cabrera, asdf, Axon, Baylor Thornton, Bedi, bernventers, bunknown, Celeste, Charles Doyle, Dane Stephen, Dave Finlay, David Gebhardt, Dean, Francis Wolf, Heather-Pleather, Jacob Sauber-Cavazos, James Lloyd-Jones, Jennifer Knowles, Jeremy-Alice, Josh O'Brien, Kilo, LM, Lawrence, Louis Ceresa, Malek Douglas, Newmans Own, Packocamels, Phat Ass Cyberman, Rach, raouldyke, Rebecca Kimpel, revidicism, Sam Thomas, T, Tash Diehart, Themandme, Tomix, weedworf, William Copping, and Yung Zoe!

LM publica cómo los casos abiertos pendientes de resolución pueden elevar más aún una deuda que ya supera los 1.836 millones.

LM publica cómo la economía de la UE se verá afectada por los aranceles de Trump, pero los estadounidenses pagarán los productos más caros.

LM publica cómo la presidenta de la CE dice que los aranceles de EEUU son "un duro golpe para la economía mundial". Pide a EEUU negociar.

Lm publica cómo sumando el IBI, el efecto del déficit y otros gravámenes, la carga fiscal llegaría ya al 54,7% del coste laboral.

We gotta talk about this

LM publica cómo la Airef dice que el Gobierno merma su capacidad de supervisión y su independencia pero le obliga a modificar la reforma de pensiones.

Lethal Mullet Podcast: Episode 275 Unforgiven & The life & times of Gene Hackman On tonight's episode The Mullet goes over the life and times of the late Gene Hackman, a mainstay of action, thriller, drama films of the 1970s and beyond. With the sad news of his passing here on LM we have decided to go through some of his most celebrated performances and also some of the more amazing films he was involved in. Please join us tonight as we celebrate not only one fo the greatest revisionist westerns ever made but also the work of the greatest actor of our time - Gene Hackman. Find Lethal Mullet Podcast on: Apple / Stitcher / Spotify / Google Play / Podbean / IheartRadio / YouTube Contact: Site: fpnet.podbean.com Twitter: @fanpodnetwork Facebook & Instagram: Fandom Podcast Network Adam: @thelethalmullet (Twitter/Facebook/Instagram) Check out the Video Show on YouTube: www.youtube.com/@fandompodcastnetwork FPN Master Feed: fpnet.podbean.com Catch the flagship show: Culture Clash, Blood of Kings, and the host of amazing podcasts covering all of Lethal Mullet Podcast  Tee public: Grab all kinds of LM merchandise @ teepublic.com #eighties #nineties #seventies #genehackman #unforgiven #fandompodcastnetwork #lethalmulletpodcast #adamobrien #australia

That's right, folks. We know the content that you want, that you crave. Never say we don't give you anything. Join Spencer, Ty, and Andy as they buckle down and review the newest season of Family Guy. Support us on Patreon for $5, $7, or $10: www.patreon.com/tgofv. A big shout-out to our $10/month patrons: Firebirb42069, Matthew Smith, Josh O'Brien,Tash Diehart, Rach, Phraja, Abbie Phelps, Celeste, Themandme, Jacob Sauber-Cavasos, Yung Zoe, L M, April Harley, Sweat, Baylor Thornton, Glinko Drool, Axon, Lawrence LaValle, Luke Eakin, Declineofskating, MakingSomeCrap, Sam Thomas, Matthew Ferrie, Tommy, Dane Stephen, Adam W, Jeremy-Alice Long, Louis Ceresa, Rebecca Kimpel, Jennifer Knowles, Revidicism, Dean, Stubbuhdub, Kyle, Travis, Kilo, David Gebhardt, and James Lloyd-Jones!

LM publica un nuevo artítculo de los lunes negros de Rotellar sobre cómo Sánchez ha hecho dispararse la deuda pública española.

LM publica cómo para 2025, María Jesús Montero aseguró que va a "seguir intentando subir el diésel".

If you're in SF: Join us for the Claude Plays Pokemon hackathon this Sunday!If you're not: Fill out the 2025 State of AI Eng survey for $250 in Amazon cards!We are SO excited to share our conversation with Dharmesh Shah, co-founder of HubSpot and creator of Agent.ai.A particularly compelling concept we discussed is the idea of "hybrid teams" - the next evolution in workplace organization where human workers collaborate with AI agents as team members. Just as we previously saw hybrid teams emerge in terms of full-time vs. contract workers, or in-office vs. remote workers, Dharmesh predicts that the next frontier will be teams composed of both human and AI members. This raises interesting questions about team dynamics, trust, and how to effectively delegate tasks between human and AI team members.The discussion of business models in AI reveals an important distinction between Work as a Service (WaaS) and Results as a Service (RaaS), something Dharmesh has written extensively about. While RaaS has gained popularity, particularly in customer support applications where outcomes are easily measurable, Dharmesh argues that this model may be over-indexed. Not all AI applications have clearly definable outcomes or consistent economic value per transaction, making WaaS more appropriate in many cases. This insight is particularly relevant for businesses considering how to monetize AI capabilities.The technical challenges of implementing effective agent systems are also explored, particularly around memory and authentication. Shah emphasizes the importance of cross-agent memory sharing and the need for more granular control over data access. He envisions a future where users can selectively share parts of their data with different agents, similar to how OAuth works but with much finer control. This points to significant opportunities in developing infrastructure for secure and efficient agent-to-agent communication and data sharing.Other highlights from our conversation* The Evolution of AI-Powered Agents – Exploring how AI agents have evolved from simple chatbots to sophisticated multi-agent systems, and the role of MCPs in enabling that.* Hybrid Digital Teams and the Future of Work – How AI agents are becoming teammates rather than just tools, and what this means for business operations and knowledge work.* Memory in AI Agents – The importance of persistent memory in AI systems and how shared memory across agents could enhance collaboration and efficiency.* Business Models for AI Agents – Exploring the shift from software as a service (SaaS) to work as a service (WaaS) and results as a service (RaaS), and what this means for monetization.* The Role of Standards Like MCP – Why MCP has been widely adopted and how it enables agent collaboration, tool use, and discovery.* The Future of AI Code Generation and Software Engineering – How AI-assisted coding is changing the role of software engineers and what skills will matter most in the future.* Domain Investing and Efficient Markets – Dharmesh's approach to domain investing and how inefficiencies in digital asset markets create business opportunities.* The Philosophy of Saying No – Lessons from "Sorry, You Must Pass" and how prioritization leads to greater productivity and focus.Timestamps* 00:00 Introduction and Guest Welcome* 02:29 Dharmesh Shah's Journey into AI* 05:22 Defining AI Agents* 06:45 The Evolution and Future of AI Agents* 13:53 Graph Theory and Knowledge Representation* 20:02 Engineering Practices and Overengineering* 25:57 The Role of Junior Engineers in the AI Era* 28:20 Multi-Agent Systems and MCP Standards* 35:55 LinkedIn's Legal Battles and Data Scraping* 37:32 The Future of AI and Hybrid Teams* 39:19 Building Agent AI: A Professional Network for Agents* 40:43 Challenges and Innovations in Agent AI* 45:02 The Evolution of UI in AI Systems* 01:00:25 Business Models: Work as a Service vs. Results as a Service* 01:09:17 The Future Value of Engineers* 01:09:51 Exploring the Role of Agents* 01:10:28 The Importance of Memory in AI* 01:11:02 Challenges and Opportunities in AI Memory* 01:12:41 Selective Memory and Privacy Concerns* 01:13:27 The Evolution of AI Tools and Platforms* 01:18:23 Domain Names and AI Projects* 01:32:08 Balancing Work and Personal Life* 01:35:52 Final Thoughts and ReflectionsTranscriptAlessio [00:00:04]: Hey everyone, welcome back to the Latent Space podcast. This is Alessio, partner and CTO at Decibel Partners, and I'm joined by my co-host Swyx, founder of Small AI.swyx [00:00:12]: Hello, and today we're super excited to have Dharmesh Shah to join us. I guess your relevant title here is founder of Agent AI.Dharmesh [00:00:20]: Yeah, that's true for this. Yeah, creator of Agent.ai and co-founder of HubSpot.swyx [00:00:25]: Co-founder of HubSpot, which I followed for many years, I think 18 years now, gonna be 19 soon. And you caught, you know, people can catch up on your HubSpot story elsewhere. I should also thank Sean Puri, who I've chatted with back and forth, who's been, I guess, getting me in touch with your people. But also, I think like, just giving us a lot of context, because obviously, My First Million joined you guys, and they've been chatting with you guys a lot. So for the business side, we can talk about that, but I kind of wanted to engage your CTO, agent, engineer side of things. So how did you get agent religion?Dharmesh [00:01:00]: Let's see. So I've been working, I'll take like a half step back, a decade or so ago, even though actually more than that. So even before HubSpot, the company I was contemplating that I had named for was called Ingenisoft. And the idea behind Ingenisoft was a natural language interface to business software. Now realize this is 20 years ago, so that was a hard thing to do. But the actual use case that I had in mind was, you know, we had data sitting in business systems like a CRM or something like that. And my kind of what I thought clever at the time. Oh, what if we used email as the kind of interface to get to business software? And the motivation for using email is that it automatically works when you're offline. So imagine I'm getting on a plane or I'm on a plane. There was no internet on planes back then. It's like, oh, I'm going through business cards from an event I went to. I can just type things into an email just to have them all in the backlog. When it reconnects, it sends those emails to a processor that basically kind of parses effectively the commands and updates the software, sends you the file, whatever it is. And there was a handful of commands. I was a little bit ahead of the times in terms of what was actually possible. And I reattempted this natural language thing with a product called ChatSpot that I did back 20...swyx [00:02:12]: Yeah, this is your first post-ChatGPT project.Dharmesh [00:02:14]: I saw it come out. Yeah. And so I've always been kind of fascinated by this natural language interface to software. Because, you know, as software developers, myself included, we've always said, oh, we build intuitive, easy-to-use applications. And it's not intuitive at all, right? Because what we're doing is... We're taking the mental model that's in our head of what we're trying to accomplish with said piece of software and translating that into a series of touches and swipes and clicks and things like that. And there's nothing natural or intuitive about it. And so natural language interfaces, for the first time, you know, whatever the thought is you have in your head and expressed in whatever language that you normally use to talk to yourself in your head, you can just sort of emit that and have software do something. And I thought that was kind of a breakthrough, which it has been. And it's gone. So that's where I first started getting into the journey. I started because now it actually works, right? So once we got ChatGPT and you can take, even with a few-shot example, convert something into structured, even back in the ChatGP 3.5 days, it did a decent job in a few-shot example, convert something to structured text if you knew what kinds of intents you were going to have. And so that happened. And that ultimately became a HubSpot project. But then agents intrigued me because I'm like, okay, well, that's the next step here. So chat's great. Love Chat UX. But if we want to do something even more meaningful, it felt like the next kind of advancement is not this kind of, I'm chatting with some software in a kind of a synchronous back and forth model, is that software is going to do things for me in kind of a multi-step way to try and accomplish some goals. So, yeah, that's when I first got started. It's like, okay, what would that look like? Yeah. And I've been obsessed ever since, by the way.Alessio [00:03:55]: Which goes back to your first experience with it, which is like you're offline. Yeah. And you want to do a task. You don't need to do it right now. You just want to queue it up for somebody to do it for you. Yes. As you think about agents, like, let's start at the easy question, which is like, how do you define an agent? Maybe. You mean the hardest question in the universe? Is that what you mean?Dharmesh [00:04:12]: You said you have an irritating take. I do have an irritating take. I think, well, some number of people have been irritated, including within my own team. So I have a very broad definition for agents, which is it's AI-powered software that accomplishes a goal. Period. That's it. And what irritates people about it is like, well, that's so broad as to be completely non-useful. And I understand that. I understand the criticism. But in my mind, if you kind of fast forward months, I guess, in AI years, the implementation of it, and we're already starting to see this, and we'll talk about this, different kinds of agents, right? So I think in addition to having a usable definition, and I like yours, by the way, and we should talk more about that, that you just came out with, the classification of agents actually is also useful, which is, is it autonomous or non-autonomous? Does it have a deterministic workflow? Does it have a non-deterministic workflow? Is it working synchronously? Is it working asynchronously? Then you have the different kind of interaction modes. Is it a chat agent, kind of like a customer support agent would be? You're having this kind of back and forth. Is it a workflow agent that just does a discrete number of steps? So there's all these different flavors of agents. So if I were to draw it in a Venn diagram, I would draw a big circle that says, this is agents, and then I have a bunch of circles, some overlapping, because they're not mutually exclusive. And so I think that's what's interesting, and we're seeing development along a bunch of different paths, right? So if you look at the first implementation of agent frameworks, you look at Baby AGI and AutoGBT, I think it was, not Autogen, that's the Microsoft one. They were way ahead of their time because they assumed this level of reasoning and execution and planning capability that just did not exist, right? So it was an interesting thought experiment, which is what it was. Even the guy that, I'm an investor in Yohei's fund that did Baby AGI. It wasn't ready, but it was a sign of what was to come. And so the question then is, when is it ready? And so lots of people talk about the state of the art when it comes to agents. I'm a pragmatist, so I think of the state of the practical. It's like, okay, well, what can I actually build that has commercial value or solves actually some discrete problem with some baseline of repeatability or verifiability?swyx [00:06:22]: There was a lot, and very, very interesting. I'm not irritated by it at all. Okay. As you know, I take a... There's a lot of anthropological view or linguistics view. And in linguistics, you don't want to be prescriptive. You want to be descriptive. Yeah. So you're a goals guy. That's the key word in your thing. And other people have other definitions that might involve like delegated trust or non-deterministic work, LLM in the loop, all that stuff. The other thing I was thinking about, just the comment on Baby AGI, LGBT. Yeah. In that piece that you just read, I was able to go through our backlog and just kind of track the winter of agents and then the summer now. Yeah. And it's... We can tell the whole story as an oral history, just following that thread. And it's really just like, I think, I tried to explain the why now, right? Like I had, there's better models, of course. There's better tool use with like, they're just more reliable. Yep. Better tools with MCP and all that stuff. And I'm sure you have opinions on that too. Business model shift, which you like a lot. I just heard you talk about RAS with MFM guys. Yep. Cost is dropping a lot. Yep. Inference is getting faster. There's more model diversity. Yep. Yep. I think it's a subtle point. It means that like, you have different models with different perspectives. You don't get stuck in the basin of performance of a single model. Sure. You can just get out of it by just switching models. Yep. Multi-agent research and RL fine tuning. So I just wanted to let you respond to like any of that.Dharmesh [00:07:44]: Yeah. A couple of things. Connecting the dots on the kind of the definition side of it. So we'll get the irritation out of the way completely. I have one more, even more irritating leap on the agent definition thing. So here's the way I think about it. By the way, the kind of word agent, I looked it up, like the English dictionary definition. The old school agent, yeah. Is when you have someone or something that does something on your behalf, like a travel agent or a real estate agent acts on your behalf. It's like proxy, which is a nice kind of general definition. So the other direction I'm sort of headed, and it's going to tie back to tool calling and MCP and things like that, is if you, and I'm not a biologist by any stretch of the imagination, but we have these single-celled organisms, right? Like the simplest possible form of what one would call life. But it's still life. It just happens to be single-celled. And then you can combine cells and then cells become specialized over time. And you have much more sophisticated organisms, you know, kind of further down the spectrum. In my mind, at the most fundamental level, you can almost think of having atomic agents. What is the simplest possible thing that's an agent that can still be called an agent? What is the equivalent of a kind of single-celled organism? And the reason I think that's useful is right now we're headed down the road, which I think is very exciting around tool use, right? That says, okay, the LLMs now can be provided a set of tools that it calls to accomplish whatever it needs to accomplish in the kind of furtherance of whatever goal it's trying to get done. And I'm not overly bothered by it, but if you think about it, if you just squint a little bit and say, well, what if everything was an agent? And what if tools were actually just atomic agents? Because then it's turtles all the way down, right? Then it's like, oh, well, all that's really happening with tool use is that we have a network of agents that know about each other through something like an MMCP and can kind of decompose a particular problem and say, oh, I'm going to delegate this to this set of agents. And why do we need to draw this distinction between tools, which are functions most of the time? And an actual agent. And so I'm going to write this irritating LinkedIn post, you know, proposing this. It's like, okay. And I'm not suggesting we should call even functions, you know, call them agents. But there is a certain amount of elegance that happens when you say, oh, we can just reduce it down to one primitive, which is an agent that you can combine in complicated ways to kind of raise the level of abstraction and accomplish higher order goals. Anyway, that's my answer. I'd say that's a success. Thank you for coming to my TED Talk on agent definitions.Alessio [00:09:54]: How do you define the minimum viable agent? Do you already have a definition for, like, where you draw the line between a cell and an atom? Yeah.Dharmesh [00:10:02]: So in my mind, it has to, at some level, use AI in order for it to—otherwise, it's just software. It's like, you know, we don't need another word for that. And so that's probably where I draw the line. So then the question, you know, the counterargument would be, well, if that's true, then lots of tools themselves are actually not agents because they're just doing a database call or a REST API call or whatever it is they're doing. And that does not necessarily qualify them, which is a fair counterargument. And I accept that. It's like a good argument. I still like to think about—because we'll talk about multi-agent systems, because I think—so we've accepted, which I think is true, lots of people have said it, and you've hopefully combined some of those clips of really smart people saying this is the year of agents, and I completely agree, it is the year of agents. But then shortly after that, it's going to be the year of multi-agent systems or multi-agent networks. I think that's where it's going to be headed next year. Yeah.swyx [00:10:54]: Opening eyes already on that. Yeah. My quick philosophical engagement with you on this. I often think about kind of the other spectrum, the other end of the cell spectrum. So single cell is life, multi-cell is life, and you clump a bunch of cells together in a more complex organism, they become organs, like an eye and a liver or whatever. And then obviously we consider ourselves one life form. There's not like a lot of lives within me. I'm just one life. And now, obviously, I don't think people don't really like to anthropomorphize agents and AI. Yeah. But we are extending our consciousness and our brain and our functionality out into machines. I just saw you were a Bee. Yeah. Which is, you know, it's nice. I have a limitless pendant in my pocket.Dharmesh [00:11:37]: I got one of these boys. Yeah.swyx [00:11:39]: I'm testing it all out. You know, got to be early adopters. But like, we want to extend our personal memory into these things so that we can be good at the things that we're good at. And, you know, machines are good at it. Machines are there. So like, my definition of life is kind of like going outside of my own body now. I don't know if you've ever had like reflections on that. Like how yours. How our self is like actually being distributed outside of you. Yeah.Dharmesh [00:12:01]: I don't fancy myself a philosopher. But you went there. So yeah, I did go there. I'm fascinated by kind of graphs and graph theory and networks and have been for a long, long time. And to me, we're sort of all nodes in this kind of larger thing. It just so happens that we're looking at individual kind of life forms as they exist right now. But so the idea is when you put a podcast out there, there's these little kind of nodes you're putting out there of like, you know, conceptual ideas. Once again, you have varying kind of forms of those little nodes that are up there and are connected in varying and sundry ways. And so I just think of myself as being a node in a massive, massive network. And I'm producing more nodes as I put content or ideas. And, you know, you spend some portion of your life collecting dots, experiences, people, and some portion of your life then connecting dots from the ones that you've collected over time. And I found that really interesting things happen and you really can't know in advance how those dots are necessarily going to connect in the future. And that's, yeah. So that's my philosophical take. That's the, yes, exactly. Coming back.Alessio [00:13:04]: Yep. Do you like graph as an agent? Abstraction? That's been one of the hot topics with LandGraph and Pydantic and all that.Dharmesh [00:13:11]: I do. The thing I'm more interested in terms of use of graphs, and there's lots of work happening on that now, is graph data stores as an alternative in terms of knowledge stores and knowledge graphs. Yeah. Because, you know, so I've been in software now 30 plus years, right? So it's not 10,000 hours. It's like 100,000 hours that I've spent doing this stuff. And so I've grew up with, so back in the day, you know, I started on mainframes. There was a product called IMS from IBM, which is basically an index database, what we'd call like a key value store today. Then we've had relational databases, right? We have tables and columns and foreign key relationships. We all know that. We have document databases like MongoDB, which is sort of a nested structure keyed by a specific index. We have vector stores, vector embedding database. And graphs are interesting for a couple of reasons. One is, so it's not classically structured in a relational way. When you say structured database, to most people, they're thinking tables and columns and in relational database and set theory and all that. Graphs still have structure, but it's not the tables and columns structure. And you could wonder, and people have made this case, that they are a better representation of knowledge for LLMs and for AI generally than other things. So that's kind of thing number one conceptually, and that might be true, I think is possibly true. And the other thing that I really like about that in the context of, you know, I've been in the context of data stores for RAG is, you know, RAG, you say, oh, I have a million documents, I'm going to build the vector embeddings, I'm going to come back with the top X based on the semantic match, and that's fine. All that's very, very useful. But the reality is something gets lost in the chunking process and the, okay, well, those tend, you know, like, you don't really get the whole picture, so to speak, and maybe not even the right set of dimensions on the kind of broader picture. And it makes intuitive sense to me that if we did capture it properly in a graph form, that maybe that feeding into a RAG pipeline will actually yield better results for some use cases, I don't know, but yeah.Alessio [00:15:03]: And do you feel like at the core of it, there's this difference between imperative and declarative programs? Because if you think about HubSpot, it's like, you know, people and graph kind of goes hand in hand, you know, but I think maybe the software before was more like primary foreign key based relationship, versus now the models can traverse through the graph more easily.Dharmesh [00:15:22]: Yes. So I like that representation. There's something. It's just conceptually elegant about graphs and just from the representation of it, they're much more discoverable, you can kind of see it, there's observability to it, versus kind of embeddings, which you can't really do much with as a human. You know, once they're in there, you can't pull stuff back out. But yeah, I like that kind of idea of it. And the other thing that's kind of, because I love graphs, I've been long obsessed with PageRank from back in the early days. And, you know, one of the kind of simplest algorithms in terms of coming up, you know, with a phone, everyone's been exposed to PageRank. And the idea is that, and so I had this other idea for a project, not a company, and I have hundreds of these, called NodeRank, is to be able to take the idea of PageRank and apply it to an arbitrary graph that says, okay, I'm going to define what authority looks like and say, okay, well, that's interesting to me, because then if you say, I'm going to take my knowledge store, and maybe this person that contributed some number of chunks to the graph data store has more authority on this particular use case or prompt that's being submitted than this other one that may, or maybe this one was more. popular, or maybe this one has, whatever it is, there should be a way for us to kind of rank nodes in a graph and sort them in some, some useful way. Yeah.swyx [00:16:34]: So I think that's generally useful for, for anything. I think the, the problem, like, so even though at my conferences, GraphRag is super popular and people are getting knowledge, graph religion, and I will say like, it's getting space, getting traction in two areas, conversation memory, and then also just rag in general, like the, the, the document data. Yeah. It's like a source. Most ML practitioners would say that knowledge graph is kind of like a dirty word. The graph database, people get graph religion, everything's a graph, and then they, they go really hard into it and then they get a, they get a graph that is too complex to navigate. Yes. And so like the, the, the simple way to put it is like you at running HubSpot, you know, the power of graphs, the way that Google has pitched them for many years, but I don't suspect that HubSpot itself uses a knowledge graph. No. Yeah.Dharmesh [00:17:26]: So when is it over engineering? Basically? It's a great question. I don't know. So the question now, like in AI land, right, is the, do we necessarily need to understand? So right now, LLMs for, for the most part are somewhat black boxes, right? We sort of understand how the, you know, the algorithm itself works, but we really don't know what's going on in there and, and how things come out. So if a graph data store is able to produce the outcomes we want, it's like, here's a set of queries I want to be able to submit and then it comes out with useful content. Maybe the underlying data store is as opaque as a vector embeddings or something like that, but maybe it's fine. Maybe we don't necessarily need to understand it to get utility out of it. And so maybe if it's messy, that's okay. Um, that's, it's just another form of lossy compression. Uh, it's just lossy in a way that we just don't completely understand in terms of, because it's going to grow organically. Uh, and it's not structured. It's like, ah, we're just gonna throw a bunch of stuff in there. Let the, the equivalent of the embedding algorithm, whatever they called in graph land. Um, so the one with the best results wins. I think so. Yeah.swyx [00:18:26]: Or is this the practical side of me is like, yeah, it's, if it's useful, we don't necessarilyDharmesh [00:18:30]: need to understand it.swyx [00:18:30]: I have, I mean, I'm happy to push back as long as you want. Uh, it's not practical to evaluate like the 10 different options out there because it takes time. It takes people, it takes, you know, resources, right? Set. That's the first thing. Second thing is your evals are typically on small things and some things only work at scale. Yup. Like graphs. Yup.Dharmesh [00:18:46]: Yup. That's, yeah, no, that's fair. And I think this is one of the challenges in terms of implementation of graph databases is that the most common approach that I've seen developers do, I've done it myself, is that, oh, I've got a Postgres database or a MySQL or whatever. I can represent a graph with a very set of tables with a parent child thing or whatever. And that sort of gives me the ability, uh, why would I need anything more than that? And the answer is, well, if you don't need anything more than that, you don't need anything more than that. But there's a high chance that you're sort of missing out on the actual value that, uh, the graph representation gives you. Which is the ability to traverse the graph, uh, efficiently in ways that kind of going through the, uh, traversal in a relational database form, even though structurally you have the data, practically you're not gonna be able to pull it out in, in useful ways. Uh, so you wouldn't like represent a social graph, uh, in, in using that kind of relational table model. It just wouldn't scale. It wouldn't work.swyx [00:19:36]: Uh, yeah. Uh, I think we want to move on to MCP. Yeah. But I just want to, like, just engineering advice. Yeah. Uh, obviously you've, you've, you've run, uh, you've, you've had to do a lot of projects and run a lot of teams. Do you have a general rule for over-engineering or, you know, engineering ahead of time? You know, like, because people, we know premature engineering is the root of all evil. Yep. But also sometimes you just have to. Yep. When do you do it? Yes.Dharmesh [00:19:59]: It's a great question. This is, uh, a question as old as time almost, which is what's the right and wrong levels of abstraction. That's effectively what, uh, we're answering when we're trying to do engineering. I tend to be a pragmatist, right? So here's the thing. Um, lots of times doing something the right way. Yeah. It's like a marginal increased cost in those cases. Just do it the right way. And this is what makes a, uh, a great engineer or a good engineer better than, uh, a not so great one. It's like, okay, all things being equal. If it's going to take you, you know, roughly close to constant time anyway, might as well do it the right way. Like, so do things well, then the question is, okay, well, am I building a framework as the reusable library? To what degree, uh, what am I anticipating in terms of what's going to need to change in this thing? Uh, you know, along what dimension? And then I think like a business person in some ways, like what's the return on calories, right? So, uh, and you look at, um, energy, the expected value of it's like, okay, here are the five possible things that could happen, uh, try to assign probabilities like, okay, well, if there's a 50% chance that we're going to go down this particular path at some day, like, or one of these five things is going to happen and it costs you 10% more to engineer for that. It's basically, it's something that yields a kind of interest compounding value. Um, as you get closer to the time of, of needing that versus having to take on debt, which is when you under engineer it, you're taking on debt. You're going to have to pay off when you do get to that eventuality where something happens. One thing as a pragmatist, uh, so I would rather under engineer something than over engineer it. If I were going to err on the side of something, and here's the reason is that when you under engineer it, uh, yes, you take on tech debt, uh, but the interest rate is relatively known and payoff is very, very possible, right? Which is, oh, I took a shortcut here as a result of which now this thing that should have taken me a week is now going to take me four weeks. Fine. But if that particular thing that you thought might happen, never actually, you never have that use case transpire or just doesn't, it's like, well, you just save yourself time, right? And that has value because you were able to do other things instead of, uh, kind of slightly over-engineering it away, over-engineering it. But there's no perfect answers in art form in terms of, uh, and yeah, we'll, we'll bring kind of this layers of abstraction back on the code generation conversation, which we'll, uh, I think I have later on, butAlessio [00:22:05]: I was going to ask, we can just jump ahead quickly. Yeah. Like, as you think about vibe coding and all that, how does the. Yeah. Percentage of potential usefulness change when I feel like we over-engineering a lot of times it's like the investment in syntax, it's less about the investment in like arc exacting. Yep. Yeah. How does that change your calculus?Dharmesh [00:22:22]: A couple of things, right? One is, um, so, you know, going back to that kind of ROI or a return on calories, kind of calculus or heuristic you think through, it's like, okay, well, what is it going to cost me to put this layer of abstraction above the code that I'm writing now, uh, in anticipating kind of future needs. If the cost of fixing, uh, or doing under engineering right now. Uh, we'll trend towards zero that says, okay, well, I don't have to get it right right now because even if I get it wrong, I'll run the thing for six hours instead of 60 minutes or whatever. It doesn't really matter, right? Like, because that's going to trend towards zero to be able, the ability to refactor a code. Um, and because we're going to not that long from now, we're going to have, you know, large code bases be able to exist, uh, you know, as, as context, uh, for a code generation or a code refactoring, uh, model. So I think it's going to make it, uh, make the case for under engineering, uh, even stronger. Which is why I take on that cost. You just pay the interest when you get there, it's not, um, just go on with your life vibe coded and, uh, come back when you need to. Yeah.Alessio [00:23:18]: Sometimes I feel like there's no decision-making in some things like, uh, today I built a autosave for like our internal notes platform and I literally just ask them cursor. Can you add autosave? Yeah. I don't know if it's over under engineer. Yep. I just vibe coded it. Yep. And I feel like at some point we're going to get to the point where the models kindDharmesh [00:23:36]: of decide where the right line is, but this is where the, like the, in my mind, the danger is, right? So there's two sides to this. One is the cost of kind of development and coding and things like that stuff that, you know, we talk about. But then like in your example, you know, one of the risks that we have is that because adding a feature, uh, like a save or whatever the feature might be to a product as that price tends towards zero, are we going to be less discriminant about what features we add as a result of making more product products more complicated, which has a negative impact on the user and navigate negative impact on the business. Um, and so that's the thing I worry about if it starts to become too easy, are we going to be. Too promiscuous in our, uh, kind of extension, adding product extensions and things like that. It's like, ah, why not add X, Y, Z or whatever back then it was like, oh, we only have so many engineering hours or story points or however you measure things. Uh, that least kept us in check a little bit. Yeah.Alessio [00:24:22]: And then over engineering, you're like, yeah, it's kind of like you're putting that on yourself. Yeah. Like now it's like the models don't understand that if they add too much complexity, it's going to come back to bite them later. Yep. So they just do whatever they want to do. Yeah. And I'm curious where in the workflow that's going to be, where it's like, Hey, this is like the amount of complexity and over-engineering you can do before you got to ask me if we should actually do it versus like do something else.Dharmesh [00:24:45]: So you know, we've already, let's like, we're leaving this, uh, in the code generation world, this kind of compressed, um, cycle time. Right. It's like, okay, we went from auto-complete, uh, in the GitHub co-pilot to like, oh, finish this particular thing and hit tab to a, oh, I sort of know your file or whatever. I can write out a full function to you to now I can like hold a bunch of the context in my head. Uh, so we can do app generation, which we have now with lovable and bolt and repletage. Yeah. Association and other things. So then the question is, okay, well, where does it naturally go from here? So we're going to generate products. Make sense. We might be able to generate platforms as though I want a platform for ERP that does this, whatever. And that includes the API's includes the product and the UI, and all the things that make for a platform. There's no nothing that says we would stop like, okay, can you generate an entire software company someday? Right. Uh, with the platform and the monetization and the go-to-market and the whatever. And you know, that that's interesting to me in terms of, uh, you know, what, when you take it to almost ludicrous levels. of abstract.swyx [00:25:39]: It's like, okay, turn it to 11. You mentioned vibe coding, so I have to, this is a blog post I haven't written, but I'm kind of exploring it. Is the junior engineer dead?Dharmesh [00:25:49]: I don't think so. I think what will happen is that the junior engineer will be able to, if all they're bringing to the table is the fact that they are a junior engineer, then yes, they're likely dead. But hopefully if they can communicate with carbon-based life forms, they can interact with product, if they're willing to talk to customers, they can take their kind of basic understanding of engineering and how kind of software works. I think that has value. So I have a 14-year-old right now who's taking Python programming class, and some people ask me, it's like, why is he learning coding? And my answer is, is because it's not about the syntax, it's not about the coding. What he's learning is like the fundamental thing of like how things work. And there's value in that. I think there's going to be timeless value in systems thinking and abstractions and what that means. And whether functions manifested as math, which he's going to get exposed to regardless, or there are some core primitives to the universe, I think, that the more you understand them, those are what I would kind of think of as like really large dots in your life that will have a higher gravitational pull and value to them that you'll then be able to. So I want him to collect those dots, and he's not resisting. So it's like, okay, while he's still listening to me, I'm going to have him do things that I think will be useful.swyx [00:26:59]: You know, part of one of the pitches that I evaluated for AI engineer is a term. And the term is that maybe the traditional interview path or career path of software engineer goes away, which is because what's the point of lead code? Yeah. And, you know, it actually matters more that you know how to work with AI and to implement the things that you want. Yep.Dharmesh [00:27:16]: That's one of the like interesting things that's happened with generative AI. You know, you go from machine learning and the models and just that underlying form, which is like true engineering, right? Like the actual, what I call real engineering. I don't think of myself as a real engineer, actually. I'm a developer. But now with generative AI. We call it AI and it's obviously got its roots in machine learning, but it just feels like fundamentally different to me. Like you have the vibe. It's like, okay, well, this is just a whole different approach to software development to so many different things. And so I'm wondering now, it's like an AI engineer is like, if you were like to draw the Venn diagram, it's interesting because the cross between like AI things, generative AI and what the tools are capable of, what the models do, and this whole new kind of body of knowledge that we're still building out, it's still very young, intersected with kind of classic engineering, software engineering. Yeah.swyx [00:28:04]: I just described the overlap as it separates out eventually until it's its own thing, but it's starting out as a software. Yeah.Alessio [00:28:11]: That makes sense. So to close the vibe coding loop, the other big hype now is MCPs. Obviously, I would say Cloud Desktop and Cursor are like the two main drivers of MCP usage. I would say my favorite is the Sentry MCP. I can pull in errors and then you can just put the context in Cursor. How do you think about that abstraction layer? Does it feel... Does it feel almost too magical in a way? Do you think it's like you get enough? Because you don't really see how the server itself is then kind of like repackaging theDharmesh [00:28:41]: information for you? I think MCP as a standard is one of the better things that's happened in the world of AI because a standard needed to exist and absent a standard, there was a set of things that just weren't possible. Now, we can argue whether it's the best possible manifestation of a standard or not. Does it do too much? Does it do too little? I get that, but it's just simple enough to both be useful and unobtrusive. It's understandable and adoptable by mere mortals, right? It's not overly complicated. You know, a reasonable engineer can put a stand up an MCP server relatively easily. The thing that has me excited about it is like, so I'm a big believer in multi-agent systems. And so that's going back to our kind of this idea of an atomic agent. So imagine the MCP server, like obviously it calls tools, but the way I think about it, so I'm working on my current passion project is agent.ai. And we'll talk more about that in a little bit. More about the, I think we should, because I think it's interesting not to promote the project at all, but there's some interesting ideas in there. One of which is around, we're going to need a mechanism for, if agents are going to collaborate and be able to delegate, there's going to need to be some form of discovery and we're going to need some standard way. It's like, okay, well, I just need to know what this thing over here is capable of. We're going to need a registry, which Anthropic's working on. I'm sure others will and have been doing directories of, and there's going to be a standard around that too. How do you build out a directory of MCP servers? I think that's going to unlock so many things just because, and we're already starting to see it. So I think MCP or something like it is going to be the next major unlock because it allows systems that don't know about each other, don't need to, it's that kind of decoupling of like Sentry and whatever tools someone else was building. And it's not just about, you know, Cloud Desktop or things like, even on the client side, I think we're going to see very interesting consumers of MCP, MCP clients versus just the chat body kind of things. Like, you know, Cloud Desktop and Cursor and things like that. But yeah, I'm very excited about MCP in that general direction.swyx [00:30:39]: I think the typical cynical developer take, it's like, we have OpenAPI. Yeah. What's the new thing? I don't know if you have a, do you have a quick MCP versus everything else? Yeah.Dharmesh [00:30:49]: So it's, so I like OpenAPI, right? So just a descriptive thing. It's OpenAPI. OpenAPI. Yes, that's what I meant. So it's basically a self-documenting thing. We can do machine-generated, lots of things from that output. It's a structured definition of an API. I get that, love it. But MCPs sort of are kind of use case specific. They're perfect for exactly what we're trying to use them for around LLMs in terms of discovery. It's like, okay, I don't necessarily need to know kind of all this detail. And so right now we have, we'll talk more about like MCP server implementations, but We will? I think, I don't know. Maybe we won't. At least it's in my head. It's like a back processor. But I do think MCP adds value above OpenAPI. It's, yeah, just because it solves this particular thing. And if we had come to the world, which we have, like, it's like, hey, we already have OpenAPI. It's like, if that were good enough for the universe, the universe would have adopted it already. There's a reason why MCP is taking office because marginally adds something that was missing before and doesn't go too far. And so that's why the kind of rate of adoption, you folks have written about this and talked about it. Yeah, why MCP won. Yeah. And it won because the universe decided that this was useful and maybe it gets supplanted by something else. Yeah. And maybe we discover, oh, maybe OpenAPI was good enough the whole time. I doubt that.swyx [00:32:09]: The meta lesson, this is, I mean, he's an investor in DevTools companies. I work in developer experience at DevRel in DevTools companies. Yep. Everyone wants to own the standard. Yeah. I'm sure you guys have tried to launch your own standards. Actually, it's Houseplant known for a standard, you know, obviously inbound marketing. But is there a standard or protocol that you ever tried to push? No.Dharmesh [00:32:30]: And there's a reason for this. Yeah. Is that? And I don't mean, need to mean, speak for the people of HubSpot, but I personally. You kind of do. I'm not smart enough. That's not the, like, I think I have a. You're smart. Not enough for that. I'm much better off understanding the standards that are out there. And I'm more on the composability side. Let's, like, take the pieces of technology that exist out there, combine them in creative, unique ways. And I like to consume standards. I don't like to, and that's not that I don't like to create them. I just don't think I have the, both the raw wattage or the credibility. It's like, okay, well, who the heck is Dharmesh, and why should we adopt a standard he created?swyx [00:33:07]: Yeah, I mean, there are people who don't monetize standards, like OpenTelemetry is a big standard, and LightStep never capitalized on that.Dharmesh [00:33:15]: So, okay, so if I were to do a standard, there's two things that have been in my head in the past. I was one around, a very, very basic one around, I don't even have the domain, I have a domain for everything, for open marketing. Because the issue we had in HubSpot grew up in the marketing space. There we go. There was no standard around data formats and things like that. It doesn't go anywhere. But the other one, and I did not mean to go here, but I'm going to go here. It's called OpenGraph. I know the term was already taken, but it hasn't been used for like 15 years now for its original purpose. But what I think should exist in the world is right now, our information, all of us, nodes are in the social graph at Meta or the professional graph at LinkedIn. Both of which are actually relatively closed in actually very annoying ways. Like very, very closed, right? Especially LinkedIn. Especially LinkedIn. I personally believe that if it's my data, and if I would get utility out of it being open, I should be able to make my data open or publish it in whatever forms that I choose, as long as I have control over it as opt-in. So the idea is around OpenGraph that says, here's a standard, here's a way to publish it. I should be able to go to OpenGraph.org slash Dharmesh dot JSON and get it back. And it's like, here's your stuff, right? And I can choose along the way and people can write to it and I can prove. And there can be an entire system. And if I were to do that, I would do it as a... Like a public benefit, non-profit-y kind of thing, as this is a contribution to society. I wouldn't try to commercialize that. Have you looked at AdProto? What's that? AdProto.swyx [00:34:43]: It's the protocol behind Blue Sky. Okay. My good friend, Dan Abramov, who was the face of React for many, many years, now works there. And he actually did a talk that I can send you, which basically kind of tries to articulate what you just said. But he does, he loves doing these like really great analogies, which I think you'll like. Like, you know, a lot of our data is behind a handle, behind a domain. Yep. So he's like, all right, what if we flip that? What if it was like our handle and then the domain? Yep. So, and that's really like your data should belong to you. Yep. And I should not have to wait 30 days for my Twitter data to export. Yep.Dharmesh [00:35:19]: you should be able to at least be able to automate it or do like, yes, I should be able to plug it into an agentic thing. Yeah. Yes. I think we're... Because so much of our data is... Locked up. I think the trick here isn't that standard. It is getting the normies to care.swyx [00:35:37]: Yeah. Because normies don't care.Dharmesh [00:35:38]: That's true. But building on that, normies don't care. So, you know, privacy is a really hot topic and an easy word to use, but it's not a binary thing. Like there are use cases where, and we make these choices all the time, that I will trade, not all privacy, but I will trade some privacy for some productivity gain or some benefit to me that says, oh, I don't care about that particular data being online if it gives me this in return, or I don't mind sharing this information with this company.Alessio [00:36:02]: If I'm getting, you know, this in return, but that sort of should be my option. I think now with computer use, you can actually automate some of the exports. Yes. Like something we've been doing internally is like everybody exports their LinkedIn connections. Yep. And then internally, we kind of merge them together to see how we can connect our companies to customers or things like that.Dharmesh [00:36:21]: And not to pick on LinkedIn, but since we're talking about it, but they feel strongly enough on the, you know, do not take LinkedIn data that they will block even browser use kind of things or whatever. They go to great, great lengths, even to see patterns of usage. And it says, oh, there's no way you could have, you know, gotten that particular thing or whatever without, and it's, so it's, there's...swyx [00:36:42]: Wasn't there a Supreme Court case that they lost? Yeah.Dharmesh [00:36:45]: So the one they lost was around someone that was scraping public data that was on the public internet. And that particular company had not signed any terms of service or whatever. It's like, oh, I'm just taking data that's on, there was no, and so that's why they won. But now, you know, the question is around, can LinkedIn... I think they can. Like, when you use, as a user, you use LinkedIn, you are signing up for their terms of service. And if they say, well, this kind of use of your LinkedIn account that violates our terms of service, they can shut your account down, right? They can. And they, yeah, so, you know, we don't need to make this a discussion. By the way, I love the company, don't get me wrong. I'm an avid user of the product. You know, I've got... Yeah, I mean, you've got over a million followers on LinkedIn, I think. Yeah, I do. And I've known people there for a long, long time, right? And I have lots of respect. And I understand even where the mindset originally came from of this kind of members-first approach to, you know, a privacy-first. I sort of get that. But sometimes you sort of have to wonder, it's like, okay, well, that was 15, 20 years ago. There's likely some controlled ways to expose some data on some member's behalf and not just completely be a binary. It's like, no, thou shalt not have the data.swyx [00:37:54]: Well, just pay for sales navigator.Alessio [00:37:57]: Before we move to the next layer of instruction, anything else on MCP you mentioned? Let's move back and then I'll tie it back to MCPs.Dharmesh [00:38:05]: So I think the... Open this with agent. Okay, so I'll start with... Here's my kind of running thesis, is that as AI and agents evolve, which they're doing very, very quickly, we're going to look at them more and more. I don't like to anthropomorphize. We'll talk about why this is not that. Less as just like raw tools and more like teammates. They'll still be software. They should self-disclose as being software. I'm totally cool with that. But I think what's going to happen is that in the same way you might collaborate with a team member on Slack or Teams or whatever you use, you can imagine a series of agents that do specific things just like a team member might do, that you can delegate things to. You can collaborate. You can say, hey, can you take a look at this? Can you proofread that? Can you try this? You can... Whatever it happens to be. So I think it is... I will go so far as to say it's inevitable that we're going to have hybrid teams someday. And what I mean by hybrid teams... So back in the day, hybrid teams were, oh, well, you have some full-time employees and some contractors. Then it was like hybrid teams are some people that are in the office and some that are remote. That's the kind of form of hybrid. The next form of hybrid is like the carbon-based life forms and agents and AI and some form of software. So let's say we temporarily stipulate that I'm right about that over some time horizon that eventually we're going to have these kind of digitally hybrid teams. So if that's true, then the question you sort of ask yourself is that then what needs to exist in order for us to get the full value of that new model? It's like, okay, well... You sort of need to... It's like, okay, well, how do I... If I'm building a digital team, like, how do I... Just in the same way, if I'm interviewing for an engineer or a designer or a PM, whatever, it's like, well, that's why we have professional networks, right? It's like, oh, they have a presence on likely LinkedIn. I can go through that semi-structured, structured form, and I can see the experience of whatever, you know, self-disclosed. But, okay, well, agents are going to need that someday. And so I'm like, okay, well, this seems like a thread that's worth pulling on. That says, okay. So I... So agent.ai is out there. And it's LinkedIn for agents. It's LinkedIn for agents. It's a professional network for agents. And the more I pull on that thread, it's like, okay, well, if that's true, like, what happens, right? It's like, oh, well, they have a profile just like anyone else, just like a human would. It's going to be a graph underneath, just like a professional network would be. It's just that... And you can have its, you know, connections and follows, and agents should be able to post. That's maybe how they do release notes. Like, oh, I have this new version. Whatever they decide to post, it should just be able to... Behave as a node on the network of a professional network. As it turns out, the more I think about that and pull on that thread, the more and more things, like, start to make sense to me. So it may be more than just a pure professional network. So my original thought was, okay, well, it's a professional network and agents as they exist out there, which I think there's going to be more and more of, will kind of exist on this network and have the profile. But then, and this is always dangerous, I'm like, okay, I want to see a world where thousands of agents are out there in order for the... Because those digital employees, the digital workers don't exist yet in any meaningful way. And so then I'm like, oh, can I make that easier for, like... And so I have, as one does, it's like, oh, I'll build a low-code platform for building agents. How hard could that be, right? Like, very hard, as it turns out. But it's been fun. So now, agent.ai has 1.3 million users. 3,000 people have actually, you know, built some variation of an agent, sometimes just for their own personal productivity. About 1,000 of which have been published. And the reason this comes back to MCP for me, so imagine that and other networks, since I know agent.ai. So right now, we have an MCP server for agent.ai that exposes all the internally built agents that we have that do, like, super useful things. Like, you know, I have access to a Twitter API that I can subsidize the cost. And I can say, you know, if you're looking to build something for social media, these kinds of things, with a single API key, and it's all completely free right now, I'm funding it. That's a useful way for it to work. And then we have a developer to say, oh, I have this idea. I don't have to worry about open AI. I don't have to worry about, now, you know, this particular model is better. It has access to all the models with one key. And we proxy it kind of behind the scenes. And then expose it. So then we get this kind of community effect, right? That says, oh, well, someone else may have built an agent to do X. Like, I have an agent right now that I built for myself to do domain valuation for website domains because I'm obsessed with domains, right? And, like, there's no efficient market for domains. There's no Zillow for domains right now that tells you, oh, here are what houses in your neighborhood sold for. It's like, well, why doesn't that exist? We should be able to solve that problem. And, yes, you're still guessing. Fine. There should be some simple heuristic. So I built that. It's like, okay, well, let me go look for past transactions. You say, okay, I'm going to type in agent.ai, agent.com, whatever domain. What's it actually worth? I'm looking at buying it. It can go and say, oh, which is what it does. It's like, I'm going to go look at are there any published domain transactions recently that are similar, either use the same word, same top-level domain, whatever it is. And it comes back with an approximate value, and it comes back with its kind of rationale for why it picked the value and comparable transactions. Oh, by the way, this domain sold for published. Okay. So that agent now, let's say, existed on the web, on agent.ai. Then imagine someone else says, oh, you know, I want to build a brand-building agent for startups and entrepreneurs to come up with names for their startup. Like a common problem, every startup is like, ah, I don't know what to call it. And so they type in five random words that kind of define whatever their startup is. And you can do all manner of things, one of which is like, oh, well, I need to find the domain for it. What are possible choices? Now it's like, okay, well, it would be nice to know if there's an aftermarket price for it, if it's listed for sale. Awesome. Then imagine calling this valuation agent. It's like, okay, well, I want to find where the arbitrage is, where the agent valuation tool says this thing is worth $25,000. It's listed on GoDaddy for $5,000. It's close enough. Let's go do that. Right? And that's a kind of composition use case that in my future state. Thousands of agents on the network, all discoverable through something like MCP. And then you as a developer of agents have access to all these kind of Lego building blocks based on what you're trying to solve. Then you blend in orchestration, which is getting better and better with the reasoning models now. Just describe the problem that you have. Now, the next layer that we're all contending with is that how many tools can you actually give an LLM before the LLM breaks? That number used to be like 15 or 20 before you kind of started to vary dramatically. And so that's the thing I'm thinking about now. It's like, okay, if I want to... If I want to expose 1,000 of these agents to a given LLM, obviously I can't give it all 1,000. Is there some intermediate layer that says, based on your prompt, I'm going to make a best guess at which agents might be able to be helpful for this particular thing? Yeah.Alessio [00:44:37]: Yeah, like RAG for tools. Yep. I did build the Latent Space Researcher on agent.ai. Okay. Nice. Yeah, that seems like, you know, then there's going to be a Latent Space Scheduler. And then once I schedule a research, you know, and you build all of these things. By the way, my apologies for the user experience. You realize I'm an engineer. It's pretty good.swyx [00:44:56]: I think it's a normie-friendly thing. Yeah. That's your magic. HubSpot does the same thing.Alessio [00:45:01]: Yeah, just to like quickly run through it. You can basically create all these different steps. And these steps are like, you know, static versus like variable-driven things. How did you decide between this kind of like low-code-ish versus doing, you know, low-code with code backend versus like not exposing that at all? Any fun design decisions? Yeah. And this is, I think...Dharmesh [00:45:22]: I think lots of people are likely sitting in exactly my position right now, coming through the choosing between deterministic. Like if you're like in a business or building, you know, some sort of agentic thing, do you decide to do a deterministic thing? Or do you go non-deterministic and just let the alum handle it, right, with the reasoning models? The original idea and the reason I took the low-code stepwise, a very deterministic approach. A, the reasoning models did not exist at that time. That's thing number one. Thing number two is if you can get... If you know in your head... If you know in your head what the actual steps are to accomplish whatever goal, why would you leave that to chance? There's no upside. There's literally no upside. Just tell me, like, what steps do you need executed? So right now what I'm playing with... So one thing we haven't talked about yet, and people don't talk about UI and agents. Right now, the primary interaction model... Or they don't talk enough about it. I know some people have. But it's like, okay, so we're used to the chatbot back and forth. Fine. I get that. But I think we're going to move to a blend of... Some of those things are going to be synchronous as they are now. But some are going to be... Some are going to be async. It's just going to put it in a queue, just like... And this goes back to my... Man, I talk fast. But I have this... I only have one other speed. It's even faster. So imagine it's like if you're working... So back to my, oh, we're going to have these hybrid digital teams. Like, you would not go to a co-worker and say, I'm going to ask you to do this thing, and then sit there and wait for them to go do it. Like, that's not how the world works. So it's nice to be able to just, like, hand something off to someone. It's like, okay, well, maybe I expect a response in an hour or a day or something like that.Dharmesh [00:46:52]: In terms of when things need to happen. So the UI around agents. So if you look at the output of agent.ai agents right now, they are the simplest possible manifestation of a UI, right? That says, oh, we have inputs of, like, four different types. Like, we've got a dropdown, we've got multi-select, all the things. It's like back in HTML, the original HTML 1.0 days, right? Like, you're the smallest possible set of primitives for a UI. And it just says, okay, because we need to collect some information from the user, and then we go do steps and do things. And generate some output in HTML or markup are the two primary examples. So the thing I've been asking myself, if I keep going down that path. So people ask me, I get requests all the time. It's like, oh, can you make the UI sort of boring? I need to be able to do this, right? And if I keep pulling on that, it's like, okay, well, now I've built an entire UI builder thing. Where does this end? And so I think the right answer, and this is what I'm going to be backcoding once I get done here, is around injecting a code generation UI generation into, the agent.ai flow, right? As a builder, you're like, okay, I'm going to describe the thing that I want, much like you would do in a vibe coding world. But instead of generating the entire app, it's going to generate the UI that exists at some point in either that deterministic flow or something like that. It says, oh, here's the thing I'm trying to do. Go generate the UI for me. And I can go through some iterations. And what I think of it as a, so it's like, I'm going to generate the code, generate the code, tweak it, go through this kind of prompt style, like we do with vibe coding now. And at some point, I'm going to be happy with it. And I'm going to hit save. And that's going to become the action in that particular step. It's like a caching of the generated code that I can then, like incur any inference time costs. It's just the actual code at that point.Alessio [00:48:29]: Yeah, I invested in a company called E2B, which does code sandbox. And they powered the LM arena web arena. So it's basically the, just like you do LMS, like text to text, they do the same for like UI generation. So if you're asking a model, how do you do it? But yeah, I think that's kind of where.Dharmesh [00:48:45]: That's the thing I'm really fascinated by. So the early LLM, you know, we're understandably, but laughably bad at simple arithmetic, right? That's the thing like my wife, Normies would ask us, like, you call this AI, like it can't, my son would be like, it's just stupid. It can't even do like simple arithmetic. And then like we've discovered over time that, and there's a reason for this, right? It's like, it's a large, there's, you know, the word language is in there for a reason in terms of what it's been trained on. It's not meant to do math, but now it's like, okay, well, the fact that it has access to a Python interpreter that I can actually call at runtime, that solves an entire body of problems that it wasn't trained to do. And it's basically a form of delegation. And so the thought that's kind of rattling around in my head is that that's great. So it's, it's like took the arithmetic problem and took it first. Now, like anything that's solvable through a relatively concrete Python program, it's able to do a bunch of things that I couldn't do before. Can we get to the same place with UI? I don't know what the future of UI looks like in a agentic AI world, but maybe let the LLM handle it, but not in the classic sense. Maybe it generates it on the fly, or maybe we go through some iterations and hit cache or something like that. So it's a little bit more predictable. Uh, I don't know, but yeah.Alessio [00:49:48]: And especially when is the human supposed to intervene? So, especially if you're composing them, most of them should not have a UI because then they're just web hooking to somewhere else. I just want to touch back. I don't know if you have more comments on this.swyx [00:50:01]: I was just going to ask when you, you said you got, you're going to go back to code. What

LM publican cómo la medida comprometida impedirá que los propietarios mantengan a sus inquiokupas después de cinco años.

Lethal Mullet Podcast: Episode #274: Classic Eighties Chat with Dee Tails   On tonight's episode we are heading to the eighties with my dear pal: DEE TAILS. A great pal who loves all the greatness, movies, TV, and nostalgia from the eighties. Over the next two hours listen to us as we reminisce some of the greatest films of the era, while also letting you all know some new ones you may never have heard of or seen. Dee Tails is well known for his work as a rapper, dancer, actor and creature performer and has starred in: Star Wars: The Force Awakens, The Last Jedi, Rogue One, Solo a Star Wars Story and The Acolyte. He's also worked in Willow, and Captain Phillips. Join us as we head back in time for a treat of eighties nostalgia.  Find Lethal Mullet Podcast on: Apple / Stitcher / Spotify / Google Play / Podbean / IheartRadio / YouTube Contact: Site: fpnet.podbean.com Twitter: @fanpodnetwork Facebook & Instagram: Fandom Podcast Network Adam: @thelethalmullet (Twitter/Facebook/Instagram) Dee Tails: @dee_tails_official (Instagram Check out the Video Show on YouTube: www.youtube.com/@fandompodcastnetwork FPN Master Feed: fpnet.podbean.com Catch the flagship show: Culture Clash, Blood of Kings, and the host of amazing podcasts covering all of Lethal Mullet Podcast  Tee public: Grab all kinds of LM merchandise @ teepublic.com #starwars #eighties #deetails #nostalgia #thebest #movies  #fandompodcastnetwork #lethalmulletpodcast #adamobrien #australia  

LM publica cómo Sumar ha reclamado dos medidas muy concretas para salvar al cachalote y al rorcual en el Mediterráneo.

LM publica cómo la inflación ahoga a las familias: Leche, naranjas, tomates... así se empobrecen las familias españolas con Sánchez.

Originally aired in June 2019 as our 73rd episode, we still often think back to this amazing first conversation we had with Dr. Stuart Fischbein and Midwife Blyss Young!Now, almost 6 years later, the information is just as relevant and impactful as it was then. This episode was a Q&A from our Facebook followers and touches on topics like statistics surrounding VBAC, uterine rupture, uterine abnormalities, insurance companies, breech vaginal delivery, high-risk pregnancies, and a powerful analogy about VBACs and weddings!Birthing Instincts PatreonBirthing BlyssNeeded WebsiteHow to VBAC: The Ultimate Prep Course for ParentsFull Transcript under Episode Details Meagan: Hey, guys. This is one of our re-broadcasted episodes. This is an episode that, in my opinion, is a little gem in the podcast world of The VBAC Link. I really have loved this podcast ever since the date we recorded it. I am a huge fan of Dr. Stu Fischbein and Midwife Blyss and have been since the moment I knew that they existed. I absolutely love listening to their podcast and just all of the amazing things that they have and that they offer. So I wanted to rebroadcast this episode because it was quite down there. It was like our 73rd episode or something like that. And yeah, I love it so much. This week is OB week, and so I thought it'd be fun to kick-off the week with one of my favorite OB doctor's, Stuart Fischbein. So, a little recap of what this episode covers. We go over a lot. We asked for our community to ask questions for these guys, and we went through them. We didn't get to everything, so that was a bummer, but we did get to quite a bit. We talked about things like the chances of VBAC. We talked about the chances of uterine rupture and the signs of uterine rupture. We talked about inducing VBAC. We talked about uterine abnormalities, the desire of where you want to birth and figuring that out. And also, Blyss had a really great analogy to talk about what to do and how we're letting the medical world and insurance and things like that really contemplate where we or dictate where we are birthing. I love that analogy. You guys, seriously, so many questions. It's an episode that you'll probably want to put on repeat because it really is so great to listen to them, and they just speak so directly. I can't get enough of it. So I'm really excited for you guys to dive in today on this. However, I wanted to bring to your attention a couple of the new things that they've had since we recorded this way back when. I also wanted to point out that we will have updated notes in the show notes or updated links in the show notes so you can go check, them out. But one of the first things I wanted to mention was their Patreon. They have a Patreon these days, and I think that it just sounds dreamy. I think you should definitely go find in their Patreon their community through their Patreon. You can check it out at patreon.com, birthinginsinctspodcast.com and of course, you can find them on social media. You can find Dr. Stu at Birthing Instincts or his website at birthinginsincts.com. You can find Blyss and that is B-L-Y-S-S if you are looking for her at birthingblyss on Instagram or birthinblyss.com, and then of course, you can email them. They do take emails with questions and sometimes they even talk about it on their podcast. Their podcast is birthinginsinctspodcast.com, and then you can email them at birthinginsinctspodcast@gmail.com, so definitely check them out. Also, Dr. Stu offers some classes and workshops and things like that throughout the years on the topic of breech. You guys, I love them and really can't wait for you to listen to today's episode.Ladies, I cannot tell you how giddy and excited I have been for the last couple weeks since we knew that these guys were going to record with us. But we have some amazing, special guests today. We have Dr. Stuart Fischbein and Midwife Blyss Young, and we want to share a little bit about them before we get into the questions that all of you guys have asked on our social media platforms.Julie: Absolutely. And when Meagan says we're excited, we are really excited.Meagan: My face is hot right now because I'm so excited.Julie: I'm so excited. Meagan was texting me last night at 11:00 in all caps totally fan-girling out over here. So Dr. Stu and midwife Blyss are pretty amazing and we know that you are going to love them just as much as we do. But before we get into it, and like Meagan said, I'm just going to read their bios so you can know just how legit they really are. First, up. Dr. Stuart Fischbein, MD is a fellow of the American College of Obstetrics and Gynecology, and how much we love ACOG over here at The VBAC Link He's a published author of the book Fearless Pregnancy: Wisdom and Reassurance from a Doctor, a Midwife, and a Mom. He has peer-reviewed papers Home Birth with an Obstetrician, A Series of 135 Out-of-Hospital Births and Breech Births at Home, Outcomes of 60 Breech and 109 Cephalic Planned Home and Birth Center Births. Dr. Stu is a lecturer and advocate who now works directly with home birthing midwives. His website is www.birthinginsincts.com, and his podcast is Dr. Stu's Podcast. Seriously guys, you need to subscribe.Meagan: Go subscribe right now to their podcast.Yeah. The website for his podcast is drstuspodcast.com. He has an international following. He offers hope for women who cannot find supportive practitioners for VBAC and twin and breech deliveries. Guys, this is the home birth OB. He is located in California. So if you are in California hoping for VBAC, especially if you have any special circumstance like after multiple Cesareans, twins or breech presentation, run to him. Run. Go find him. He will help you. Go to that website. Blyss, Midwife Blyss. We really love them. If you haven't had a chance to hear their podcast guys, really go and give them a listen because this duo is on point. They are on fire, and they talk about all of the real topics in birth. So his partner on the podcast is Blyss Young, and she is an LM and CPM. She has been involved in the natural birth world since the birth of her first son in 1992, first as an advocate, and then as an educator. She is a mother of three children, and all of her pregnancies were supported by midwives, two of which were triumphant, empowering home births. In 2006, Blyss co-founded the Sanctuary Birth and Family Wellness Center. This was the culmination of all of her previous experience as a natural birth advocate, educator and environmentalist. The Sanctuary was the first of its kind, a full-spectrum center where midwives, doctors, and other holistic practitioners collaborated to provide thousands of Los Angeles families care during their prenatal and postpartum periods. Blyss closed the Sanctuary in 2015 to pursue her long-held dream of becoming a midwife and care for her clients in an intimate home birth practice similar to the way she was cared for during her pregnancies. I think that's , why Meagan and I both became doulas. Meagan: That's exactly why I'm a doula. Julie: We needed to provide that care just like we had been cared for. Anyway, going on. Currently, Blyss, AKA Birthing Blyss, supports families on their journey as a birth center educator, placenta encapsulator and a natural birth and family consultant and home birth midwife. She is also co-founder of Just Placentas, a company servicing all of Southern California and placenta encapsulation and other postpartum services. And as ,, she's a co-host on Dr. Stu's Podcast. Meagan: And she has a class. Don't you have a class that you're doing? Don't you have a class? Midwife Blyss: Yeah. Meagan: Yeah. She has a class that she's doing. I want to just fly out because I know you're not doing it online and everything. I just want to fly there just to take your class.Midwife Blyss: Yeah, it's coming online.Meagan: It is? Yay! Great. Well, I'll be one of those first registering. Oh, did you put it in there?Julie: No, there's a little bit more.Meagan: Oh, well, I'm just getting ahead.Julie: I just want to read more of Blyss over here because I love this and I think it's so important. At the heart of all Blyss's work is a deep-rooted belief in the brilliant design of our bodies, the symbiotic relationship between baby and mother, the power of the human spirit and the richness that honoring birth as the rite of passage and resurrecting lost traditions can bring to our high-tech, low-touch lives. And isn't that true love? I love that language. It is so beautiful. If I'm not mistaken, Midwife Blyss's website is birthingblyss.com.Is that right? And Blyss is spelled with a Y. So B-L-Y-S-S, birthingblyss.com, and that's where you can find her.Midwife Blyss: Just to make it more complicated, I had to put a Y in there.Julie: Hey. I love it.Meagan: That's okay.Julie: We're in Utah so we have all sorts of weird names over here.Meagan: Yep. I love it. You're unique. Awesome. Well, we will get started.Midwife Blyss: I did read through these questions, and one of the things that I wanted to say that I thought we could let people know is that of course there's a little bit more that we need to take into consideration when we have a uterus that's already had a scar.There's a small percentage of a uterine rupture that we need to be aware of, and we need to know what are the signs and symptoms that we would need to take a different course of action. But besides that, I believe that, and Dr. Stu can speak for himself because we don't always practice together. I believe that we treat VBAC just like any other mom who's laboring. So a lot of these questions could go into a category that you could ask about a woman who is having her first baby. I don't really think that we need to differentiate between those.Meagan: I love it. Midwife Blyss: But I do think that in terms of preparation, there are some special considerations for moms who have had a previous Cesarean, and probably the biggest one that I would point to is the trauma.Julie: Yes.Midwife Blyss: And giving space to and processing the trauma and really helping these moms have a provider that really believes in them, I think is one of the biggest factors to them having success. Meagan: Absolutely. Midwife Blyss: So that's one I wanted to say before you started down the question.Meagan: Absolutely. We have an online class that we provide for VBAC prep, and that's the very first section. It's mentally preparing and physically preparing because there's so much that goes into that. So I love that you started out with that.Julie: Yeah. A lot of these women who come searching for VBAC and realize that there's another way besides a repeat Cesarean are processing a lot of trauma, and a lot of them realized that their Cesarean might have been prevented had they known better, had a different provider, prepared differently, and things like that. Processing that and realizing that is heavy, and it's really important to do before getting into anything else, preparation-wise.Meagan: Yeah.Midwife Blyss: One of the best things I ever had that was a distinction that one of my VBAC moms made for me, and I passed it on as I've cared for other VBAC mom is for her, the justification, or I can't find the right word for it, but she basically said that that statement that we hear so often of, "Yeah, you have trauma from this, or you're not happy about how your birth went, but thank God your baby is healthy." And she said it felt so invalidating for her because, yes, she also was happy, of course, that her baby was safe, but at the same time, she had this experience and this trauma that wasn't being acknowledged, and she felt like it was just really being brushed away.Julie: Ah, yeah.Midwife Blyss: I think really giving women that space to be able to say, "Yes, that's valid. It's valid how you feel." And it is a really important part of the process and having a successful vaginal delivery this go around.Dr. Stu: I tend to be a lightning rod for stories. It's almost like I have my own personal ICAN meeting pretty much almost every day, one-on-one. I get contacted or just today driving. I'm in San Diego today and just driving down here, I talked to two people on the phone, both of whom Blyss really just touched on it is that they both are wanting to have VBACs with their second birth. They were seeing practitioners who are encouraging them to be induced for this reason or that reason. And they both have been told the same thing that Blyss just mentioned that if you end up with a repeat Cesarean, at least you're going to have a healthy baby. Obviously, it's very important. But the thing is, I know it's a cliche, but it's not just about the destination. It's about the journey as well. And one of the things that we're not taught in medical school and residency program is the value of the process. I mean, we're very much mechanical in the OB world, and our job is to get the baby out and head it to the pediatric department, and then we're done with it. If we can get somebody induced early, if we can decide to do a C-section sooner than we should, there's a lot of incentives to do that and to not think about the process and think about the person. There's another cliche which we talk about all the time. Blyss, and I've said it many times. It's that the baby is the candy and the mother's the wrapper. I don't know if you've heard that one, but when the baby comes out, the mother just gets basically tossed aside and her experience is really not important to the medical professionals that are taking care of her in the hospital setting, especially in today's world where you have a shift mentality and a lot of people are being taken care of by people they didn't know.You guys mentioned earlier the importance of feeling safe and feeling secure in whatever setting you're in whether that's at home or in the hospital. Because as Blyss knows, I get off on the mammalian track and you talk about mammals. They just don't labor well when they're anxious.Julie: Yep.Dr. Stu: When the doctor or the health professional is anxious and they're projecting their anxiety onto the mom and the family, then that stuff is brewing for weeks, if not months and who knows what it's actually doing inside, but it's certainly not going to lead to the likelihood of or it's going to diminish the likelihood of a successful labor.Julie: Yeah, absolutely. We talk about that. We go over that a lot. Like, birth is very instinctual and very primal, and it operates a very fundamental core level. And whenever mom feels threatened or anxious or, or anything like that, it literally can st or stop labor from progressing or even starting.Meagan: Yeah, exactly. When I was trying to VBAC with my first baby, my doctor came in and told my husband to tell me that I needed to wake up and smell the coffee because it wasn't happening for me. And that was the last, the last contraction I remember feeling was right before then and my body just shut off. I just stopped because I just didn't feel safe anymore or protected or supported. Yeah, it's very powerful which is something that we love so much about you guys, because I don't even know you. I've just listened to a million of your podcasts, and I feel so safe with you right now. I'm like, you could fly here right now and deliver my baby because so much about you guys, you provide so much comfort and support already, so I'm sure all of your clients can feel that from you.Julie: Absolutely.Dr. Stu: Yeah. I just would like to say that, know, I mean, the introduction was great. Which one of you is Julie? Which one's Meagan?Julie: I'm Julie.Meagan: And I'm Meagan.Dr. Stu: Okay, great. All right, so Julie was reading the introduction that she was talking about how if you have a breech, you have twins, if you have a VBAC, you have all these other things just come down to Southern California and care of it. But I'm not a cowboy. All right? Even though I do more things than most of my colleagues in the profession do, I also say no to people sometimes. I look at things differently. Just because someone has, say chronic hypertension, why can't they have a home birth? The labor is just the labor. I mean, if her blood pressure gets out of control, yeah, then she has to go to the hospital. But why do you need to be laboring in the hospital or induced early if everything is fine? But this isn't for everybody.We want to make that very clear. You need to find a supportive team or supportive practitioner who's willing to be able to say yes and no and give you it with what we call a true informed consent, so that you have the right to choose which way to go and to do what's reasonable. Our ethical obligation is to give you reasonable choices and then support your informed decision making. And sometimes there are things that aren't reasonable. Like for instance, an example that I use all the time is if a woman has a breech baby, but she has a placenta previa, a vaginal delivery is not an option for you. Now she could say, well, I want one and I'm not going to have a C-section.Julie: And then you have the right to refuse that.Dr. Stu: Yeah, yeah, but I mean, that's never going to happen because we have a good communication with our patients. Our communication is such that we develop a trust over the period of time. Sometimes I don't meet people until I'm actually called to their house by a midwife to come assist with a vacuum or something like that. But even then, the midwives and stuff, because I'm sort of known that people have understanding. And then when I'm sitting there, as long as the baby isn't trouble, I will explain to them, here's what's going to happen. Here's how we're going to do it. Here's what's going on. The baby's head to look like this. It not going be a problem. It'll be better in 12 hours. But I go through all this stuff and I say, I'm going to touch you now. Is that okay? I ask permission, and I do all the things that the midwives have taught me, but I never really learned in residency program. They don't teach this stuff.Julie: Yeah, yeah, yeah, absolutely. One of the things that we go over a lot to in our classes is finding a provider who has a natural tendency to treat his patients the way that you want to be treated. That way, you'll have a lot better time when you birth because you're not having to ask them to do anything that they're not comfortable with or that they're not prepared for or that they don't know how to do. And so interviewing providers and interview as many as you need to with these women. And find the provider whose natural ways of treating his clients are the ways that you want to be treated.Dr. Stu: And sometimes in a community, there's nobody.Julie: Yeah, yeah, that's true.Meagan: That's what's so hard.Dr. Stu: And if it's important to you, if it's important to you, then you have to drive on. Julie: Or stand up for yourself and fight really hard.Meagan: I have a client from Russia. She's flying here in two weeks. She's coming all the way to Salt Lake City, Utah to have her baby. We had another client from Russia.Julie: You have another Russian client?Meagan: Yeah. Julie: That's awesome. Meagan: So, yeah. It's crazy. Sometimes you have to go far, far distances, and sometimes you've got them right there. You just have to search. You just have to find them.So it's tricky.Midwife Blyss: Maybe your insurance company is not gonna pay for it.Meagan: Did you say my company's not gonna pay for it?Midwife Blyss: And maybe your insurance company.Meagan: Oh, sure. Yeah, exactly.Midwife Blyss: You can't rely on them to be the ones who support some of these decisions that are outside of the standards of care. You might have to really figure out how to get creative around that area.Meagan: Absolutely.Yeah. So in the beginning, Blyss, you talked about noticing the signs, and I know that's one of the questions that we got on our Instagram, I believe. Birthing at home for both of you guys, what signs for a VBAC mom are signs enough where you talk about different care?.Dr. Stu: I didn't really understand that. Say that again what you were saying.Meagan: Yep. Sorry. So one of the questions on our Instagram was what are the signs of uterine rupture when you're at home that you look for and would transfer care or talk about a different plan of action?Dr. Stu: Okay. Quite simply, some uterine ruptures don't have any warning that they're coming.There's nothing you can do about those. But before we get into what you can feel, just let's review the numbers real briefly so that people have a realistic viewpoint. Because I'm sure if a doctor doesn't want to do a VBAC, you'll find a reason not to do a VBAC. You'll use the scar thickness or the pregnancy interval or whatever. They'll use something to try to talk you out of it or your baby's too big or this kind of thing. We can get into that in a little bit. But when there are signs, the most common sign you would feel is that there'd be increasing pain super-cubically that doesn't go away between contractions. It's a different quality of pain or sensation. It's pain. It's really's becoming uncomfortable. You might start to have variables when you didn't have them before. So the baby's heart rate, you might see heart rate decelerations. Rarely, you might find excessive bleeding, but that's usually not a sign of I mean that's a sign of true rupture.Midwife Blyss: Loss of station.Dr. Stu: Those are things you look for, but again, if you're not augmenting someone, if someone doesn't have an epidural where they don't have sensation, if they're not on Pitocin, these things are very unlikely to happen. I was going to get to the numbers. The numbers are such that the quoted risk of uterine rupture, which is again that crappy word. It sounds like a tire blowing out of the freeway. It is about 1 in 200. But only about 5 to 16%. And even one study said 3%. But let's just even take 16% of those ruptures will result in an outcome that the baby is damaged or dead. Okay, that's about 1 in 6. So the actual risk is about 1 in 6 times 1 in 200 or 1 in 1200 up to about 1 in 4000.Julie: Yep.Dr. Stu: So those are, those are the risks. They're not the 1 in 200 or the 2%. I actually had someone tell some woman that she had a 30% chance of rupture.Julie: We've had somebody say 50%.Meagan: We have?Julie: Yeah. Jess, our 50 copy editor-- her doctor told her that if she tries to VBAC, she has a 50% chance of rupture and she will die. Yeah.Meagan: Wow.Julie: Pretty scary. Dr. Stu: And by the way, a maternal mortality from uterine rupture is extremely rare.Julie: Yeah, we were just talking about that.Dr. Stu: That doctor is wrong on so many accounts. I don't even know where to begin on that.Julie: I know.Dr. Stu: Yeah. See that's the thing where even if someone has a classical Cesarean scar, the risk of rupture isn't 50%.Julie: Yep.Dr. Stu: So I don't know where they come up with those sorts of numbers.Julie: Yeah, I think it's just their comfort level and what they're familiar with and what they know and what they understand. I think a lot of these doctors, because she had a premature Cesarean, and so that's why he was a little, well, a lot more fear-based. Her Cesarean happened, I think, around 32 weeks. We still know that you can still attempt to VBAC and still have a really good chance of having a successful one. But a lot of these providers just don't do it.Dr. Stu: Yeah. And another problem is you can't really find out what somebody's C-section rate is. I mean, you can find out your hospital C-section rate. They can vary dramatically between different physicians, so you really don't know. You'd like to think that physicians are honest. You'd like to think that they're going to tell you the truth. But if they have a high C-section rate and it's a competitive world, they're not going to. And if you're with them, you don't really have a choice anyway.Julie: So there's not transparency on the physician level.Dr. Stu: So Blyss was talking briefly about the fact that your insurance may not pay for it. Blyss, why don't you elaborate on that because you do that point so well.Midwife Blyss: Are you talking about the wedding?Dr. Stu: I love your analogy. It's a great analogy.Midwife Blyss: I'm so saddened sometimes when people talk to me about that they really want this option and especially VBACs. I just have a very special tender place in my heart for VBAC because I overcame something from my first to second birth that wasn't a Cesarean. But it felt like I had been led to mistrust my body, and then I had a triumphant second delivery. So I really understand how that feels when a woman is able to reclaim her body and have a vaginal delivery. But just in general, in terms of limiting your options based on what your insurance will pay for, we think about the delivery of our baby and or something like a wedding where it's this really special day. I see that women or families will spend thousands and thousands of dollars and put it on a credit card and figure out whatever they need to do to have this beautiful wedding. But somehow when it comes to the birth of their baby, they turn over all their power to this insurance company.And so we used to do this talk at the sanctuary and I used to say, "What if we had wedding insurance and you paid every year into this insurance for your wedding, and then when the wedding came, they selected where you went and you didn't like it and they put you in a dress that made you look terrible and the food was horrible and the music was horrible and they invited all these people you didn't want to be there?"Julie: But it's a network.Midwife Blyss: Would you really let that insurance company, because it was paid for, dictate how your wedding day was? Julie: That's a good analogy.Midwife Blyss: You just let it all go.Meagan: Yeah. That's amazing. I love that. And it's so true. It is so true.Julie: And we get that too a lot about hiring a doula. Oh, I can't hire a doula. It's too expensive. We get that a lot because people don't expect to pay out-of-pocket for their births. When you're right, it's just perceived completely differently when it should be one of the biggest days of your life. I had three VBACs at home. My first was a necessary, unnecessary Cesarean.I'm still really uncertain about that, to be honest with you. But you better believe my VBACs at home, we paid out of pocket for a midwife. Our first two times, it was put on a credit card. I had a doula, I had a birth photographer, I had a videographer. My first VBAC, I had two photographers there because it was going to be documented because it was so important to me. And we sold things on eBay. We sold our couches, and I did some babysitting just to bring in the money.Obviously, I hired doulas because it was so important to me to not only have the experience that I wanted and that I deserved, but I wanted it documented and I wanted it to be able to remember it well and look back on it fondly. We see that especially in Utah. I think we have this culture where women just don't-- I feel like it's just a national thing, but I think in Utah, we tend to be on the cheap side just culturally and women don't see the value in that. It's hard because it's hard to shift that mindset to see you are important. You are worth it. What if you could have everything you wanted and what if you knew you could be treated differently? Would you think about how to find the way to make that work financially? And I think if there's just that mindset shift, a lot of people would.Meagan: Oh, I love that.Dr. Stu: If you realize if you have to pay $10,000 out of pocket or $5,000 or whatever to at least have the opportunity, and you always have the hospital as a backup. But 2 or 3 years from now, that $5,000 isn't going to mean anything.Julie: Yeah, nothing.Meagan: But that experience is with you forever.Dr. Stu: So yeah, women may have to remember the names of their children when they're 80 years old, but they'll remember their birth.Julie: Well, with my Cesarean baby, we had some complications and out-of-pocket, I paid almost $10,000 for him and none of my home births, midwives, doula, photography and videography included cost over $7,000.Meagan: My Cesarean births in-hospital were also more expensive than my birth center births.Julie: So should get to questions.Dr. Stu: Let's get to some of the questions because you guys some really good questions.Meagan: Yes.Dr. Stu: Pick one and let's do it.Meagan: So let's do Lauren. She was on Facebook. She was our very first question, and she said that she has some uterine abnormalities like a bicornuate uterus or a separate uterus or all of those. They want to know how that impacts VBAC. She's had two previous Cesareans due to a breech presentation because of her uterine abnormality.Julie: Is that the heart-shaped uterus? Yeah.Dr. Stu: Yeah. You can have a septate uterus. You can have a unicornuate uterus. You can have a double uterus.Julie: Yeah. Two separate uteruses.Dr. Stu: Right. The biggest problem with a person with an abnormal uterine shape or an anomaly is a couple of things. One is malpresentation as this woman experienced because her two babies were breech. And two, is sometimes a retained placenta is more common than women that have a septum, that sort of thing. Also, it can cause preterm labor and growth restriction depending on the type of anomaly of the uterus. Now, say you get to term and your baby is head down, or if it's breech in my vicinity. But if it's head down, then the chance of VBAC for that person is really high. I mean, it might be a slightly greater risk of Cesarean section, but not a statistically significant risk. And then the success rate for home birth VBACs, if you look at the MANA stats or even my own stats which are not enough to make statistical significance in a couple of papers that I put out, but the MANA stats show that it's about a 93% success rate for VBACS in the midwifery model, whereas in the hospital model, it can be as low as 17% up to the 50s or 60%, but it's not very high. And that's partly because of the model by which you're cared for. So the numbers that I'm quoting and the success rates I'm quoting are again, assuming that you have a supportive practitioner in a supportive environment, every VBAC is going to have diminished chance of success in a restrictive or tense environment. But unicornuate uterus or septate uterus is not a contraindication to VBAC, and it's not an indication of breech delivery if somebody knows how to do a breech VBAC too.Julie: Right.Dr. Stu: So Lauren, that would be my answer to to your question is that no, it's not a contraindication and that if you have the right practitioner you can certainly try to labor and your risk of rupture is really not more significant than a woman who has a normal-shaped uterus.Julie: Good answer.Meagan: So I want to spin off that really quick. It's not a question, but I've had a client myself that had two C-sections, and her baby was breech at 37 weeks, and the doctor said he absolutely could not turn the baby externally because her risk of rupture was so increasingly high. So would you agree with that or would you disagree with that?D No, no, no. Even an ACOG statement on external version and breech says that a previous uterine scar is not a contraindication to attempting an external version.Meagan: Yeah.Dr. Stu: Now actually, if we obviously had more breech choices, then there'd be no reason to do an external version.The main reason that people try an external version which can sometimes be very uncomfortable, and depending on the woman and her parody and certain other factors, their success rate cannot be very good is the only reason they do it because the alternative is a Cesarean in 95% of locations in the country.Meagan: Okay, well that's good to know.Dr. Stu: But again, one of the things I would tell people to do is when they're hearing something from their position that just sort of rocks the common sense vote and doesn't sort of make sense, look into it. ACOG has a lot. I think you can just go Google some of the ACOG clinical guidelines or practice guidelines or clinical opinions or whatever they call them. You can find and you can read through, and they summarize them at the end on level A, B, and C evidence, level A being great evidence level C being what's called consensus opinion. The problem with consensus, with ACOG's guidelines is that about 2/3 of them are consensus opinion because they don't really have any data on them. When you get bunch of academics together who don't like VBAC or don't like home birth or don't like breech, of course a consensus opinion is going to be, "Well, we're not going to think those are a good idea." But much to their credit lately, they're starting to change their tune. Their most recent VBAC guideline paper said that if your hospital can do labor and delivery, your hospital can do VBAC.Julie: Yes.Dr. Stu: That's huge. There was immediately a whole fiasco that went on. So any hospital that's doing labor and delivery should be able to do a VBAC. When they say they can't or they say our insurance company won't let them, it's just a cowardly excuse because maybe it's true, but they need to fight for your right because most surgical emergencies in labor delivery have nothing to do with a previous uterine scar.Julie: Absolutely.Dr. Stu: They have to do with people distress or placental abruption or cord prolapse. And if they can handle those, they can certainly handle the one in 1200. I mean, say a hospital does 20 VBACs a year or 50 VBACs a year. You'll take them. Do the math. It'll take them 25 years to have a rupture.Meagan: Yeah. It's pretty powerful stuff.Midwife Blyss: I love when he does that.Julie: Me too. I'm a huge statistics junkie and data junkie. I love the numbers.Meagan: Yeah. She loves numbers.Julie: Yep.Meagan: I love that.Julie: Hey, and 50 VBACs a year at 2000, that would be 40 years actually, right?Dr. Stu: Oh, look at what happened. So say that again. What were the numbers you said?Julie: So 1 in 2000 ruptures are catastrophic and they do 50 VBACs a year, wouldn't that be 40 years?Dr. Stu: But I was using the 1200 number.Julie: Oh, right, right, right, right.Dr. Stu: So that would be 24 years.Julie: Yeah. Right. Anyways, me and you should sit down and just talk. One day. I would love to have lunch with you.Dr. Stu: Let's talk astrology and astronomy.Yes.Dr. Stu: Who's next?Midwife Blyss: Can I make a suggestion?There was another woman. Let's see where it is. What's the likelihood that a baby would flip? And is it reasonable to even give it a shot for a VBA2C. How do you guys say that?Meagan: VBAC after two Cesareans.Midwife Blyss: I need to know the lingo. So, I would say it's very unlikely for a baby to flip head down from a breech position in labor. It doesn't mean it's impossible.Dr. Stu: With a uterine septum, it's almost never going to happen. Bless is right on. Even trying an external version on a woman with the uterine septum when the baby's head is up in one horn and the placenta in the other horn and they're in a frank breech position, that's almost futile to do that, especially if a woman is what I call a functional primary, or even a woman who's never labored before.Julie: Right. That's true.Meagan: And then Napoleon said, what did she say? Oh, she was just talking about this. She's planning on a home birth after two Cesareans supported by a midwife and a doula. Research suggests home birth is a reasonable and safe option for low-risk women. And she wants to know in reality, what identifies low risk?Midwife Blyss: Well, I thought her question was hilarious because she says it seems like everybody's high-risk too. Old, overweight.Julie: Yeah, it does. It does, though.Dr. Stu: Well, immediately, when you label someone high-risk, you make them high-risk.Julie: Yep.Dr. Stu: Because now you've planted seeds of doubt inside their head. So I would say, how do you define high-risk? I mean, is 1 in 1200 high risk?Julie: Nope.Dr. Stu: It doesn't seem high-risk to me. But again, I mean, we do a lot of things in our life that are more dangerous than that and don't consider them high-risk. So I think the term high-risk is handed about way too much.And it's on some false or just some random numbers that they come up with. Blyss has heard this before. I mean, she knows everything I say that comes out of my mouth. The numbers like 24, 35, 42. I mean, 24 hours of ruptured membranes. Where did that come from? Yeah, or some people are saying 18 hours. I mean, there's no science on that. I mean, bacteria don't suddenly look at each other and go, "Hey Ralph, it's time to start multiplying."Julie: Ralph.Meagan: I love it.Julie: I'm gonna name my bacteria Ralph.Meagan: It's true. And I was told after 18 hours, that was my number.Dr. Stu: Yeah, again, so these numbers, there are papers that come out, but they're not repetitive. I mean, any midwife worth her salt has had women with ruptured membranes for sometimes two, three, or four days.Julie: Yep.Midwife Blyss: And as long as you're not sticking your fingers in there, and as long as their GBS might be negative or that's another issue.Meagan: I think that that's another question. That's another question. Yep.Dr. Stu: Yeah, I'll get to that right now. I mean, if some someone has a ruptured membrane with GBS, and they don't go into labor within a certain period of time, it's not unreasonable to give them the pros and cons of antibiotics and then let them make that decision. All right? We don't force people to have antibiotics. We would watch for fetal tachycardia or fever at that point, then you're already behind the eight ball. So ideally, you'd like to see someone go into labor sooner. But again, if they're still leaking, if there are no vaginal exams, the likelihood of them getting group B strep sepsis or something on the baby is still not very high. And the thing about antibiotics that I like to say is that if I was gonna give antibiotics to a woman, I think it's much better to give a woman an antibiotics at home than in the hospital. And the reason being is because at home, the baby's still going to be born into their own environment and mom's and dad's bacteria and the dog's bacteria and the siblings' bacteria where in the hospital, they're going to go to the nursery for observation like they generally do, and they're gonna be exposed to different bacteria unless they do these vaginal seeding, which isn't really catching on universally yet where you take a swab of mom's vaginal bacteria before the C-section.Midwife Blyss: It's called seeding.Dr. Stu: Right. I don't consider ruptured membrane something that again would cause me to immediately say something where you have to change your plan. You individualize your care in the midwifery model.Julie: Yep.Dr. Stu: You look at every patient. You look at their history. You look at their desires. You look at their backup situation, their transport situation, and that sort of thing. You take it all into account. Now, there are some women in pregnancy who don't want to do a GBS culture.Ignorance is bliss. The other spelling of bliss.Julie: Hi, Blyss.Dr. Stu: But the reason that at least I still encourage people to do it is because for any reason, if that baby gets transferred to the hospital during labor or after and you don't have a GBS culture on the chart, they're going to give antibiotics. They're going to treat it as GBS positive and they're also going to think you're irresponsible.And they're going to have that mentality that of oh, here's another one of those home birth crazy people, blah, blah, blah.Julie: That just happened to me in January. I had a client like that. I mean, anyways, never mind. It's not the time. Midwife Blyss: Can I say something about low-risk?Julie: Yes. Midwife Blyss: I think there are a lot of different factors that go into that question. One being what are the state laws? Because there are things that I would consider low-risk and that I feel very comfortable with, but that are against the law. And I'm not going to go to jail.Meagan: Right. We want you to still be Birthing Bless.Midwife Blyss: As, much as I believe in a woman's right to choose, I have to draw the line at what the law is. And then the second is finding a provider that-- obviously, Dr. Stu feels very comfortable with things that other providers may not necessarily feel comfortable with.Julie: Right.Midwife Blyss: And so I think it's really important, as you said in the beginning of the show, to find a provider who takes the risk that you have and feels like they can walk that path with you and be supportive. I definitely agree with what Dr. Stu was saying about informed consent. I had a client who was GBS positive, declined antibiotics and had a very long rupture. We continued to walk that journey together. I kept giving informed consent and kept giving informed consent. She had such trust and faith that it actually stretched my comfort level. We had to continually talk about where we were in this dance. But to me, that feels like what our job is, is to give them information about the pros and cons and let them decide for themselves.And I think that if you take a statistic, I'm picking an arbitrary number, and there's a 94% chance of success and a 4% chance that something could go really wrong, one family might look at that and say, "Wow, 94%, this is neat. That sounds like a pretty good statistic," and the other person says, "4% makes me really uncomfortable. I need to minimize." I think that's where you have to have the ability, given who you surround yourself with and who your provider is, to be able to say, "This is my choice," and it's being supported. So it is arbitrary in a lot of ways except for when it comes to what the law is.Julie: Yeah, that makes sense.Meagan: I love that. Yeah. Julie: Every state has their own law. Like in the south, it's illegal like in lots of places in the South, I think in Washington too, that midwives can't support home birth if you're VBAC. I mean there are lots of different legislative rules. Why am I saying legislative? Look at me, I'm trying to use fancy words to impress you guys. There are lots of different laws in different states and, and some of them are very evidence-based and some laws are broad and they leave a lot of room for practices, variation and gray areas. Some are so specific that they really limit a woman's option in that state.Dr. Stu: We can have a whole podcast on the legal decision-making process and a woman's right to autonomy of her body and the choices and who gets to decide that would be. Right now, the vaccine issue is a big issue, but also pregnancy and restricting women's choices of these things. If you want to do another one down the road, I would love to talk on that subject with you guys.Julie: Perfect.Meagan: We would love that.Julie: Yeah. I think it's your most recent episode. I mean as of the time of this recording. Mandates Kill Medicine. What is that the name?Dr. Stu: Mandates Destroy Medicine.Julie: Yeah. Mandates Destroy Medicine. Dr. Stu: It's wonderful.Julie: Yeah, I love it. I was just listening to it today again.Dr. Stu: well it does because it makes the physicians agents of the state.Julie: Yeah, it really does.Meagan: Yeah. Well. And if you give us another opportunity to do this with you, heck yeah.Julie: Yeah. You can just be a guest every month.Meagan: Yeah.Dr. Stu: So I don't think I would mind that at all, actually.Meagan: We would love it.Julie: Yeah, we would seriously love it. We'll keep in touch.Meagan: So, couple other questions I'm trying to see because we jumped through a few that were the same. I know one asks about an overactive pelvic floor, meaning too strong, not too weak. She's wondering if that is going to affect her chances of having a successful VBAC.Julie: And do you see that a lot with athletes, like people that are overtrained or that maybe are not overtrained, but who train a lot and weightlifters and things like that, where their pelvic floor is too strong? I've heard of that before.Midwife Blyss: Yep, absolutely. there's a chiropractor here in LA, Dr. Elliot Berlin, who also has his own podcast and he talks–Meagan: Isn't Elliott Berlin Heads Up?Dr. Stu: Yeah. He's the producer of Heads Up.Meagan: Yeah, I listened to your guys' special episode on that too. But yeah, he's wonderful.Midwife Blyss: Yeah. So, again, I think this is a question that just has more to do with vaginal delivery than it does necessarily about the fact that they've had a previous Cesarean. So I do believe that the athletic pelvis has really affected women's deliveries. I think that during pregnancy we can work with a pelvic floor specialist who can help us be able to realize where the tension is and how to do some exercises that might help alleviate some of that. We have a specialist here in L.A. I don't know if you guys do there that I would recommend people to. And then also, maybe backing off on some of the athletic activities that that woman is participating in during her pregnancy and doing things more like walking, swimming, yoga, stretching, belly dancing, which was originally designed for women in labor, not to seduce men. So these are all really good things to keep things fluid and soft because you want things to open and release rather than being tense.Meagan: I love that.Dr. Stu: I agree. I think sometimes it leads more to not generally so much of dilation. Again, a friend of mine, David Hayes, he's a home birth guy in South Carolina, doesn't like the idea of using stages of labor. He wants to get rid of that. I think that's an interesting thought. We have a meeting this November in Wisconsin. We're gonna have a bunch of thought-provoking things going on over there.Dr. Stu: Is it all men talking about this? Midwife Blyss: Oh, hell no.Julie: Let's get more women. Dr. Stu: No, no, no, no, no.Being organized By Cynthia Calai. Do you guys know who Cynthia is? She's been a midwife for 50 years. She's in Wisconsin. She's done hundreds of breeches. Anyway, the point being is that I think that I find that a lot of those people end up getting instrumented like vacuums, more commonly. Yeah. So Blyss is right. I mean, if there are people who are very, very tight down there. The leviators and the muscles inside are very tight which is great for life and sex and all that other stuff, but yeah, you need to learn how to be able to relax them too.Julie: Yeah.Meagan: So I know we're running short on time, but this question that came through today, I loved it. It said, "Could you guys both replicate your model of care nationwide somehow?" She said, "How do I advocate effectively for home birth access and VBAC access in a state that actively prosecutes home birth and has restrictions on midwifery practice?" She specifically said she's in Nebraska, but we hear this all over the place. VBAC is not allowed. You cannot birth at home, and people are having unassisted births.Julie: Because they can't find the support.Meagan: They can't find the support and they are too scared to go to the hospital or birth centers. And so, yeah, the question is--Julie: What can women do in their local communities to advocate for positive change and more options in birth where they are more restricted?Dr. Stu: Blyss. Midwife Blyss: I wish I had a really great answer for this. I think that the biggest thing is to continue to talk out loud. And I'm really proud of you ladies for creating this podcast and doing the work that you do. Julie: Thanks.Midwife Blyss: I always believed when we had the Sanctuary that it really is about the woman advocating for herself. And the more that hospitals and doctors are being pushed by women to say, "We need this as an option because we're not getting the work," I think is really important. I support free birth, and I think that most of the women and men who decide to do that are very well educated.Julie: Yeah, for sure.Midwife Blyss: It is actually really very surprising for midwives to see that sometimes they even have better statistics than we do. But it saddens me that there's no choice. And, a woman who doesn't totally feel comfortable with doing that is feeling forced into that decision. So I think as women, we need to support each other, encourage each other, continue to talk out loud about what it is that we want and need and make this be a very important decision that a woman makes, and it's a way of reclaiming the power. I'm not highly political. I try and stay out of those arenas. And really, one of my favorite quotes from a reverend that I have been around said, "Be for something and against nothing." I really believe that the more. Julie: I like that.Midwife Blyss: Yeah, the more that we speak positively and talk about positive change and empowering ourselves and each other, it may come slowly, but that change will continue to come.Julie: Yeah, yeah.Dr. Stu: I would only add to that that I think unfortunately, in any country, whether it's a socialist country or a capitalist country, it's economics that drives everything. If you look at countries like England or the Netherlands, you find that they have, a really integrated system with midwives and doctors collaborating, and the low-risk patients are taken care of by the midwives, and then they consult with doctors and midwives can transfer from home to hospital and continue their care in that system, the national health system. I'm not saying that's the greatest system for somebody who's growing old and has arthritis or need spinal surgery or something like that, but for obstetrics, that sort of system where you've taken out liability and you've taken out economic incentive. All right, so how do you do that in our system? It's not very easy to do because everything is economically driven. One of the things that I've always advocated for is if you want to lower the C-section rate, increase the VBAC rate. It would be really simple for insurance companies, until we have Bernie Sanders with universal health care. But while we have insurance companies, if they would just pay twice as much for a vaginal birth and half as much for a Cesarean birth, then finally, VBACS and breech deliveries would be something. Oh, maybe we should start. We should be more supportive of those things because it's all about the money. But as long as the hospital gets paid more, doctors don't really get paid more. It's expediency for the doctor. He gets it done and goes home. But the hospital, they get paid a lot more, almost twice as much for a C-section than you do for vaginal birth. What's the incentive for the chief financial officer of any hospital to say to the OB department, "We need to lower our C-section rate?" One of the things that's happening are programs that insurance, and I forgot what it's called, but where they're trying, in California, they're trying to lower the primary C-section rate. There's a term for it where it's an acronym with four initials. Blyss, do you know what I'm talking about?Midwife Blyss: No. Dr. Stu: It's an acronym about a first-time mom. We're trying to avoid those C-sections.Julie: Yeah, the primary Cesarean.Dr. Stu: It's an acronym anyway, nonetheless. So they're in the right direction. Most hospitals are in the 30% range. They'd like to lower to 27%. That's a start.One of the ways to really do that is to support VBAC, and treat VBAC as Blyss said at the very beginning of the podcast is that a VBAC is just a normal labor. When people lump VBAC in with breech in twins, it's like, why are you doing that? Breech in twins requires special skill. VBAC requires a special skill also, which is a skill of doing nothing.Julie: Yeah, it's hard.Dr. Stu: It's hard for obstetricians and labor and delivery nurses and stuff like that to do nothing. But ultimately, VBAC is just a vaginal birth and doesn't require any special skill. When a doctor says, "We don't do VBAC, what he's basically saying, or she, is that I don't do vaginal deliveries," which is stupid because VBAC is just a vaginal delivery.Julie: Yeah, that's true.Meagan: Such a powerful point right there.Julie: Guys. We loved chatting with you so much. We wish we could talk with you all day long.Meagan: I would. All day long. I just want to be a fly on your walls if I could.Julie: If you're ever in Salt Lake City again--Meagan: He just was. Did you know about this?Julie: Say hi to Adrienne, but also connect with us because we would love to meet you. All right, well guys, everyone, all of our listeners, Women of Strength, we are going to drop all the information that you need to find Midwife Blyss and Dr. Stu-- their website, their podcast, and all of that in our show notes. So yeah, now you can find our podcast. You can even listen to our podcast on our website at thevbaclink.com/podcast. You can play episodes right from there. So if you don't know-- well, if you're listening to this podcast, then you probably have a podcast player already. But you know what? My mom still doesn't know what a podcast is, so I'm just gonna have to start sending her links right to our page.Meagan: Yep, just listen to us wherever and leave us a review and head over to Dr. Stu's Podcast and leave them a review.Julie: Subscribe because you're gonna love him, but don't stop listening to him us because you love us too. Remember that.Dr. Stu: I want to thank everybody who wrote in, and I'm sorry we didn't get to answer every question. We tend to blabber on a little bit asking these important questions, and hopefully you guys will have us back on again.Meagan: We would love to have you.Julie: Absolutely.Meagan: Yep, we will.Julie: Absolutely.Meagan: YeahClosingWould you like to be a guest on the podcast? Tell us about your experience at thevbaclink.com/share. For more information on all things VBAC including online and in-person VBAC classes, The VBAC Link blog, and Meagan's bio, head over to thevbaclink.com. Congratulations on starting your journey of learning and discovery with The VBAC Link.Support this podcast at — https://redcircle.com/the-vbac-link/donationsAdvertising Inquiries: https://redcircle.com/brands