Podcasts about SD

Trygve Hammer tapped for another run for North Dakota US House seat, Barnes Co. fatal crash, MN AI bills, SD voter citizenship, Access to expunged records, Legislative term limits, Forecast with Chief Meteorologist Tom Szymanski.See omnystudio.com/listener for privacy information.

Welcome to the Jesus Church in Watertown, South Dakota!Join us for service at: 500 14th Ave NW, Watertown, SD 57201 https://goo.gl/maps/WgUmDc1iH7jB8za98Our Service Times: Sunday Morning Service at 10:00 am CDT Sunday Main Service at 11:00 am CDT Wednesday Service at 7:00 pm CDTYou can find us online at: Website: https://jesuschurchsd.org/

Turn your PyPortal into an IoT-connected art gallery that cycles through art, space, cats and dogs! Pull from image feeds or images from an SD card. Skip images with a tilt or shake. Guide: https://learn.adafruit.com/pyportal-art-display Tap the screen to change feeds. Customize your feed, transition animations, and even the audio chirp feedback! 3D print the melted diagonal frame to mount the PyPortal and accelerometer. Visit the Adafruit shop online - http://www.adafruit.com ----------------------------------------- LIVE CHAT IS HERE! http://adafru.it/discord Adafruit on Instagram: https://www.instagram.com/adafruit Shop for parts to build your own DIY projects http://adafru.it/3dprinting 3D Printing Projects Playlist: https://www.youtube.com/playlist?list=PLjF7R1fz_OOWD2dJNRIN46uhMCWvNOlbG 3D Hangout Show Playlist: https://www.youtube.com/playlist?list=PLjF7R1fz_OOVgpmWevin2slopw_A3-A8Y Layer by Layer CAD Tutorials Playlist: https://www.youtube.com/playlist?list=PLjF7R1fz_OOVsMp6nKnpjsXSQ45nxfORb Timelapse Tuesday Playlist: https://www.youtube.com/playlist?list=PLjF7R1fz_OOVagy3CktXsAAs4b153xpp_ Connect with Noe and Pedro on Social Media: Noe's Twitter / Instagram: @ecken Pedro's Twitter / Instagram: @videopixil ----------------------------------------- Visit the Adafruit shop online - http://www.adafruit.com/?utm_source=youtube&utm_medium=videodescrip&utm_campaign=3dprinting Subscribe to Adafruit on YouTube: http://adafru.it/subscribe Adafruit Monthly Deals & FREE Specials https://www.adafruit.com/free?utm_source=youtube&utm_medium=videodescrip&utm_campaign=3dprinting Join our weekly Show & Tell on G+ Hangouts On Air: http://adafru.it/showtell Watch our latest project videos: http://adafru.it/latest?utm_source=youtube&utm_medium=videodescrip&utm_campaign=3dprinting 3DThursday Posts: https://blog.adafruit.com/category/3d-printing?utm_source=youtube&utm_medium=videodescrip&utm_campaign=3dprinting New tutorials on the Adafruit Learning System: http://learn.adafruit.com/?utm_source=youtube&utm_medium=videodescrip&utm_campaign=3dprinting -----------------------------------------

Turn your PyPortal into an IoT-connected art gallery that cycles through art, space, cats and dogs! Pull from image feeds or images from an SD card. Skip images with a tilt or shake. Guide: https://learn.adafruit.com/pyportal-art-display Tap the screen to change feeds. Customize your feed, transition animations, and even the audio chirp feedback! 3D print the melted diagonal frame to mount the PyPortal and accelerometer. Visit the Adafruit shop online - http://www.adafruit.com ----------------------------------------- LIVE CHAT IS HERE! http://adafru.it/discord Adafruit on Instagram: https://www.instagram.com/adafruit Shop for parts to build your own DIY projects http://adafru.it/3dprinting 3D Printing Projects Playlist: https://www.youtube.com/playlist?list=PLjF7R1fz_OOWD2dJNRIN46uhMCWvNOlbG 3D Hangout Show Playlist: https://www.youtube.com/playlist?list=PLjF7R1fz_OOVgpmWevin2slopw_A3-A8Y Layer by Layer CAD Tutorials Playlist: https://www.youtube.com/playlist?list=PLjF7R1fz_OOVsMp6nKnpjsXSQ45nxfORb Timelapse Tuesday Playlist: https://www.youtube.com/playlist?list=PLjF7R1fz_OOVagy3CktXsAAs4b153xpp_ Connect with Noe and Pedro on Social Media: Noe's Twitter / Instagram: @ecken Pedro's Twitter / Instagram: @videopixil ----------------------------------------- Visit the Adafruit shop online - http://www.adafruit.com/?utm_source=youtube&utm_medium=videodescrip&utm_campaign=3dprinting Subscribe to Adafruit on YouTube: http://adafru.it/subscribe Adafruit Monthly Deals & FREE Specials https://www.adafruit.com/free?utm_source=youtube&utm_medium=videodescrip&utm_campaign=3dprinting Join our weekly Show & Tell on G+ Hangouts On Air: http://adafru.it/showtell Watch our latest project videos: http://adafru.it/latest?utm_source=youtube&utm_medium=videodescrip&utm_campaign=3dprinting 3DThursday Posts: https://blog.adafruit.com/category/3d-printing?utm_source=youtube&utm_medium=videodescrip&utm_campaign=3dprinting New tutorials on the Adafruit Learning System: http://learn.adafruit.com/?utm_source=youtube&utm_medium=videodescrip&utm_campaign=3dprinting -----------------------------------------

Top 7 RG listi vikunnar varðar slökustu hárgreiðslur knattspyrnumanna. Farið yfir bestu lögin frá Skandinavíu. Helgi A og Sdóri í spjalli um nýtt lag og komandi plötu. Kolbeinn Kristinsson að berjast fyrsta atvinnubardagann á Íslandi. Þetta og mikið meira til!

0:00 Intro2:00 Elimination Chamber Thoughts17:29 RAW thoughts including the opening of the show & CM Punk & Roman Reigns promo battle #242:02 Cody Rhodes vs Drew McIntyre this Friday on SmackDown and what WrestleMania now looks like for the SD brand1:04:25 Penta winning the IC title and getting closer to Dom Mysterio vs Finn Balor1:08:38 Jade Cargill and Rhea Ripley go at it on social media1:24:21 The podcast engagement on TIkTok this past weekend1:27:56 Fairly critiquing wrestling1:32:49 Lash Legend and Nia Jax winning the tag team titles1:35:08 Demolition being inducted into the WWE HOF and “1st ballot” Hall of Famer's+ MUCH MORE!Watch exclusive episodes and segments from the TFW Podcast:

“Something You Should Know” is brought to you by www.MyPillow.com/Happy. We share fun things that are happening in the area and from time to time invite guests in to talk about their events!

“Something You Should Know” is brought to you by www.MyPillow.com/Happy. We share fun things that are happening in the area and from time to time invite guests in to talk about their events!

“Something You Should Know” is brought to you by www.MyPillow.com/Happy. We share fun things that are happening in the area and from time to time invite guests in to talk about their events!

“Something You Should Know” is brought to you by www.MyPillow.com/Happy. We share fun things that are happening in the area and from time to time invite guests in to talk about their events!

L'autonomie totale des voitures promise par Elon Musk se heurte aujourd'hui à une réalité statistique brutale.Les robotaxis de Tesla, en test au Texas, affichent un taux d'accident quatre fois supérieur à celui d'un conducteur humain moyen. 14 accidents ont été officiellement recensésD'abord, il faut regarder les chiffres de l'expérimentation au-delà du marketing.Depuis huit mois, une flotte de 43 Tesla opérant en mode autonome a parcouru près de 1,3 millions de kilomètres. Et sur cette très longue distance, 14 accidents ont été officiellement recensés.En calculant la moyenne, cela représente une collision tous les 90 000 kilomètres.Pour mettre ce chiffre en perspective, les propres données de Tesla indiquent qu'un conducteur humain moyen ne subit un incident mineur que tous les 368 000 kilomètres.Concrètement, le système de conduite autonome de Tesla est actuellement quatre fois moins sûr que le plus banal des automobilistes texans.La courbe de progression semble s'inverserEnsuite, l'analyse de la nature des accidents révèle des lacunes technologiques inquiétantes pour un déploiement à grande échelle.Les rapports d'accidents font état de crash avec cinq autres véhicules, cinq objets fixes, mais aussi un cycliste et un animal.Plus troublant encore, la courbe de progression semble s'inverser. Alors que l'IA est censée s'améliorer par l'apprentissage continu, plus de 35 % des incidents ont été signalés sur les deux derniers mois de l'étude.Ce constat pose une question fondamentale sur la fiabilité du système vision-only de Tesla, qui refuse d'utiliser les capteurs Lidar, jugés trop chers. Sans une amélioration radicale de ces scores, le passage d'une flotte expérimentale à un service commercial semble s'éloigner.Sincérité ?Enfin, c'est la transparence de Tesla qui est aujourd'hui remise en question.Un incident survenu en juillet dernier, initialement déclaré comme un simple dommage matériel, n'a été requalifié en accident avec hospitalisation que cinq mois plus tard.Ce délai dans la déclaration soulève des interrogations sur le reporting de l'entreprise et la sincérité des promesses de son dirigeant.Surtout, la promesse d'une IA conductrice plus sûre que l'humain reste, pour l'instant, une ambition non vérifiée par les faits.Le ZD Tech est sur toutes les plateformes de podcast ! Abonnez-vous !Hébergé par Ausha. Visitez ausha.co/politique-de-confidentialite pour plus d'informations.

With data increasingly positioning thermal ablation as a viable alternative to surgery for select liver metastases, the demands on the interventional oncologist have never been higher. Mastering the nuances of patient selection and precise margin assessment is now essential for ensuring effective disease control locally. In this episode of the BackTable Podcast, interventional radiologist Dr. Jonas Redmond of UC San Diego Health joins host Dr. Sabeen Dhand to discuss the current state of microwave ablation (MWA) in the management of oligometastatic liver disease, focusing on tumor assessment, preprocedural planning, and the integration of local and systemic therapies. --- This podcast is supported by: Varian IntelliBlatehttps://www.varian.com/products/interventional-solutions/microwave-ablation-solutions --- SYNPOSIS The conversation delves into the complexities of timing systemic versus local ablative therapies and explores questions surrounding adequate treatment margins. Dr. Redmond goes on to emphasize the need for operators to approach procedures with a high level of adaptability, advocating for interdisciplinary preprocedural planning and thoughtful modality selection. Exploring the complications that could arise from injury to adjacent viscera, the physicians speak to the critical importance of rigorous intraprocedural reassessment and discuss how modern software and robotics are transforming procedural precision and safety. Framing these MWA pearls within the context of recent clinical trials like COLLISION and ACCLAIM, the episode underscores the transition of interventional oncology from providing palliative services to increasingly curative solutions that may offer better prospects for patients with metastatic disease. --- TIMESTAMPS 00:00 - Introduction04:30 - Role of Local Therapy in Systemic Disease09:49 - Patient Selection and Treatment Modalities13:15 - Challenging Lesion Characteristics and Locations19:56 - Y-90 Radioembolization versus Microwave Ablation23:04 - Intraoperative Ablation and Combining Locoregional Modalities29:36 - Complications of Microwave Ablation in the Liver36:43 - Future of Ablation and Liver Metastases Treatment39:25 - Final Thoughts and Closing Remarks --- RESOURCES UC San Diego Health. Cryoablation and Arterial Infusion of SD-101 in Combination with Durvalumab and Tremelimumab.https://clinicaltrials.ucsd.edu/trial/NCT06710223 COLLISION trialhttps://clinicaltrials.gov/study/NCT03088150 ACCLAIM trialhttps://clinicaltrials.gov/study/NCT05265169

Welcome aboard our Safe Space Ship!   Ariana Perry will be hosting this completely spoiled, totally unofficial, deep dive into Our Flag Means Death every Tuesday!   This week I'm talking to 4 fabulous podficcers! Boy, Baby_Kraken, Lindie, and SD!   Episode Mentions:  Never Left Pateron 1happydaiz on ao3 Baby_kraken on Ao3 Kninjaknitter on Ao3 SD_Ryan on Ao3   Don't forget to follow us on social media (@NeverLeftPodcast on BlueSky, @NeverLeftPod on Twitter, NeverLeftPodcast on Ig, Never Left on FB), and check out our Pateron.. The links are in our linktree!  Feel free to contact us at neverleftofmd@gmail.com with any thoughts or questions   Please remember to #DontStreamOnMax and #FireDavidZaslav If you want you can also let Netflix, Amazon Prime and Apple + know that you would still love to see Our Flag Means Death on their platforms. #SaveOFMD #AdoptOurCrew   Our artwork was created by Amy Gleason, you can see more of her art @AmysBirdHouse on instagram and in the comic series Mighty Mascots.   Our theme music is Gnossienne 5 by Erik Satie, preformed by La Pianista   Image Description: A lighthouse stands above the inn, wrapped in a purple Kraken tentacle. The text reads "Never Left: Our Flag Means Death"      

SD348 - Margem - Episódio 2. No segundo episódio da série sobre o livro Margem, Dr. Lorenzo Tomé aprofunda a discussão sobre a importância das margens na vida e na carreira dos médicos. A partir da obra de Richard Svensson, ele explora como a sobrecarga crônica, a falta de margem, seja ela de tempo, emocional, física e/ou financeira, impacta a qualidade do cuidado e o vínculo com os pacientes. Dr. Lorenzo faz um convite para refletir sobre como reestruturar o modelo de prática médica, implementando um modelo de negócios sustentável e baseado no valor real entregue aos pacientes. Entre na Comunidade SD no WhatsApp e tenha conteúdo gratuito todos os dias sobre negócios médicos. ACESSE O podcast Saúde Digital lhe ajuda a abrir a mente? Agora imagine como 3 dias de imersão com a gente pode impactar no seu negócio médico. A próxima Imersão SD já tem data: 20, 21 e 22 de março/2026. Garanta sua vaga com 10% de desconto na Imersão da SD Escola de Negócios Médicos. FAÇA CONTATO O Background do Lorenzo Casado com a Natália e pai de 3 filhos, Lorenzo é médico, Cofundador e CEO da SD Conecta e SD Escola de Negócios Médicos, host do 1º podcast do Brasil a apresentar tecnologias para médicos e que está no ar desde maio de 2018. Ele é Professor de Medicina Digital na Faculdade de Medicina São Leopoldo Mandic, fez Mestrado e MBA em negócios nas melhores escolas de negócios do país, é Internship no Hospital Center University de Rouen - França, entre várias outras atividades.  Assista este episódio também em vídeo no YouTube no nosso canal Saúde Digital Podcast! Acesse os Episódios Anteriores! SD347 - Médicos Empreendedores, o que aprender com a história da Neurogram SD346 - Margem - Espiódio 1 SD345 - Consultório cheio não é sinônimo de Medicina bem-feita Music: Raindrop | Declan DP "Music © Copyright Declan DP 2018 - Present. https://license.declandp.info | License ID: DDP1590665"  

#freshoil #praise #renewing God desires to renew us, refresh us, and pour out fresh oil for this season. Even in seasons of lack or uncertainty, Habakkuk 3:17–18 teaches us to rejoice anyway. In this message by Pastor Judy Shaw, she talks about praise is not based on what we see, it's rooted in who God is!!! Psalm 92:10, Genesis 29:16-35, Psalm 61:1, Psalm 149:6, Judges 20:18, Habakuk 3:17-18 Join our online church! Hit subscribe, leave a comment, and let us know how this message spoke to you. Please follow our websites for more! Website: http://www.newlifechurchsf.org/ Facebook: https://www.facebook.com/NewLifeSF/ Youtube: https://youtu.be/7Ig-qXgVAmE/ Pastor Alex Klimchuk New Life Church 500 S 1st Ave Sioux Falls, SD 57104

The prices of digital storage are set to climb this year because AI is eating up all the available inventory. And modern photography is entirely dependent on storage, whether it's the SD cards that store the captured images, the internal solid-state memory that stores data on your computer, or the external SSDs and traditional hard drives that keep your archive of photos. Hosts: Jeff Carlson: website, Jeff's photos, Jeff on Instagram, Jeff on Glass, Jeff on Mastodon, Jeff on Bluesky Kirk McElhearn: website, Kirk's photos, Kirk on Instagram, Kirk on Glass, Kirk on Mastodon, Kirk on Bluesky Show Notes: (View show notes with images at PhotoActive.co) Rate and Review the PhotoActive Podcast! Western Digital is out of hard drives, because Ai (of course) Take Control of Your Digital Storage Subscribe to the PhotoActive podcast newsletter at the bottom of any page at the PhotoActive web site to be notified of new episodes and be eligible for occasional giveaways. If you've already subscribed, you're automatically entered. If you like the show, please subscribe in iTunes/Apple Podcasts or your favorite podcast app, and please rate the podcast. And don't forget to join the PhotoActive Facebook group to discuss the podcast, share your photos, and more. Disclosure: Sometimes we use affiliate links for products, in which we receive small commissions to help support PhotoActive.

This message was delivered to Christ Church of Rapid City, SD, on March 1, 2026.

Your Hap I Pastor Logan Yoder by Bible Baptist Church - Brookings, SD

Rise Podcast | Mar 8, 2026 - Third Sunday of Lent by Catholic Diocese of Rapid City, SD

Made with Restream. Livestream on 30+ platforms at once via https://restream.ioWelcome to the Jesus Church in Watertown, South Dakota!Join us for service at: 500 14th Ave NW, Watertown, SD 57201 https://goo.gl/maps/WgUmDc1iH7jB8za98Our Service Times: Sunday Morning Service at 10:00 am CDT Sunday Main Service at 11:00 am CDT Wednesday Service at 7:00 pm CDTYou can find us online at: Website: https://jesuschurchsd.org/ Facebook: https://www.facebook.com/JesusChurchSD Instagram: https://www.instagram.com/jesuschurchsd/

Made with Restream. Livestream on 30+ platforms at once via https://restream.ioWelcome to the Jesus Church in Watertown, South Dakota!Join us for service at: 500 14th Ave NW, Watertown, SD 57201 https://goo.gl/maps/WgUmDc1iH7jB8za98Our Service Times: Sunday Morning Service at 10:00 am CDT Sunday Main Service at 11:00 am CDT Wednesday Service at 7:00 pm CDTYou can find us online at: Website: https://jesuschurchsd.org/ Facebook: https://www.facebook.com/JesusChurchSD Instagram: https://www.instagram.com/jesuschurchsd/

Give Me this mountain by Bible Baptist Church - Brookings, SD

Our guest this week is Matt Shepherd of Emporia, KS who is President and CEO of Midwest Evaluation & Research and father of two adopted children including one with developmental delays. Matt and his wife, Brenda, have been married for 35 years and are the proud parents of two adopted children; Jeremy (26) and Bonnie (25) who has high emotional intelligence as well as development delays.Professionally, Matt is owner of Midwest Evaluations and Research, a consulting firm that helps community-based organizations, foundations, schools, and governments evaluate and improve their programs.  Along the way he has developed a high level of experience and expertise doing research for and evaluation of fatherhood programs. Matt is also to the founder and former board chair of Social Innovation Labratory, a non-profit that drives community-led change through partnerships and research to build equitable, innovative, and sustainable systems.Matt also founded Caerus Place for Woman, based in Souix Falls, SD to provide safe housing, compassionate support, and pathways to stability and independence for women in crisis.We'll hear all about Matt's work and family on this episode of the SFN Dad to Dad Podcast.Show Notes - Phone – (620) 757-9101Email – Matt.Shepherd@Midwestevaluation.comLinkedIn –  https://www.linkedin.com/in/matthew-shepherd-86594056/Company – https://midwestevaluation.com/Social Innovation Labs – https://www.socialinnovationlab.org/Order your copy of the new 21CD book: Dads Raising Chidlren With Special Needs & Disabilities: A Guide For 21st Century Dads on Amazon: https://amzn.to/4tdvjcvSpecial Fathers Network –SFN is a dad to dad mentoring program for fathers raising children with special needs. Many of the 800+ SFN Mentor Fathers, who are raising kids with special needs, have said: “I wish there was something like this when we first received our child's diagnosis. I felt so isolated.  There was no one within my family, at work, at church or within my friend group who understood or could relate to what I was going through.”SFN Mentor Fathers share their experiences with younger dads closer to the beginning of their journey raising a child with the same or similar special needs. The SFN Mentor Fathers do NOT offer legal or medical advice, that is what lawyers and doctors do. They simply share their experiences and how they have made the most of challenging situations.Join the SFN U.S. Tour in one of 60+ locations all across the U.S. from May 21st to June 21st.  Go to www.21stCenturyDads.org for additional informaiton. Please conisder hosting, co-hosting or simoly joining the tour near your home.  Check out the 21CD YouTube Channel with dozens of videos on topics relevant to dads raising children with special needs - https://www.youtube.com/channel/UCzDFCvQimWNEb158ll6Q4cA/videosPlease support the SFN. Click here to donate: https://21stcenturydads.org/donate/Special Fathers Network: https://21stcenturydads.org/  SFN Mastermind Group - https://21stcenturydads.org/sfn-mastermind-group/Special thanks to SFN Mentor Father, SFN Mastermind Group dad and 21CD board member Shane Madden for creating the SFN jingle on the front and back end of the podcast..

Bryan Cantrill is the co-founder and CTO of Oxide Computer Company. We discuss why the biggest cloud providers don't use off the shelf hardware, how scaling data centers at samsung's scale exposed problems with hard drive firmware, how the values of NodeJS are in conflict with robust systems, choosing Rust, and the benefits of Oxide Computer's rack scale approach. This is an extended version of an interview posted on Software Engineering Radio. Related links Oxide Computer Oxide and Friends Illumos Platform as a Reflection of Values RFD 26 bhyve CockroachDB Heterogeneous Computing with Raja Koduri Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today I am talking to Bryan Cantrill. He's the co-founder and CTO of Oxide computer company, and he was previously the CTO of Joyent and he also co-authored the DTrace Tracing framework while he was at Sun Microsystems. [00:00:14] Jeremy: Bryan, welcome to Software Engineering radio. [00:00:17] Bryan: Uh, awesome. Thanks for having me. It's great to be here. [00:00:20] Jeremy: You're the CTO of a company that makes computers. But I think before we get into that, a lot of people who built software, now that the actual computer is abstracted away, they're using AWS or they're using some kind of cloud service. So I thought we could start by talking about, data centers. [00:00:41] Jeremy: 'cause you were. Previously working at Joyent, and I believe you got bought by Samsung and you've previously talked about how you had to figure out, how do I run things at Samsung's scale. So how, how, how was your experience with that? What, what were the challenges there? Samsung scale and migrating off the cloud [00:01:01] Bryan: Yeah, I mean, so at Joyent, and so Joyent was a cloud computing pioneer. Uh, we competed with the likes of AWS and then later GCP and Azure. Uh, and we, I mean, we were operating at a scale, right? We had a bunch of machines, a bunch of dcs, but ultimately we know we were a VC backed company and, you know, a small company by the standards of, certainly by Samsung standards. [00:01:25] Bryan: And so when, when Samsung bought the company, I mean, the reason by the way that Samsung bought Joyent is Samsung's. Cloud Bill was, uh, let's just say it was extremely large. They were spending an enormous amount of money every year on, on the public cloud. And they realized that in order to secure their fate economically, they had to be running on their own infrastructure. [00:01:51] Bryan: It did not make sense. And there's not, was not really a product that Samsung could go buy that would give them that on-prem cloud. Uh, I mean in that, in that regard, like the state of the market was really no different. And so they went looking for a company, uh, and bought, bought Joyent. And when we were on the inside of Samsung. [00:02:11] Bryan: That we learned about Samsung scale. And Samsung loves to talk about Samsung scale. And I gotta tell you, it is more than just chest thumping. Like Samsung Scale really is, I mean, just the, the sheer, the number of devices, the number of customers, just this absolute size. they really wanted to take us out to, to levels of scale, certainly that we had not seen. [00:02:31] Bryan: The reason for buying Joyent was to be able to stand up on their own infrastructure so that we were gonna go buy, we did go buy a bunch of hardware. Problems with server hardware at scale [00:02:40] Bryan: And I remember just thinking, God, I hope Dell is somehow magically better. I hope the problems that we have seen in the small, we just. You know, I just remember hoping and hope is hope. It was of course, a terrible strategy and it was a terrible strategy here too. Uh, and the we that the problems that we saw at the large were, and when you scale out the problems that you see kind of once or twice, you now see all the time and they become absolutely debilitating. [00:03:12] Bryan: And we saw a whole series of really debilitating problems. I mean, many ways, like comically debilitating, uh, in terms of, of showing just how bad the state-of-the-art. Yes. And we had, I mean, it should be said, we had great software and great software expertise, um, and we were controlling our own system software. [00:03:35] Bryan: But even controlling your own system software, your own host OS, your own control plane, which is what we had at Joyent, ultimately, you're pretty limited. You go, I mean, you got the problems that you can obviously solve, the ones that are in your own software, but the problems that are beneath you, the, the problems that are in the hardware platform, the problems that are in the componentry beneath you become the problems that are in the firmware. IO latency due to hard drive firmware [00:04:00] Bryan: Those problems become unresolvable and they are deeply, deeply frustrating. Um, and we just saw a bunch of 'em again, they were. Comical in retrospect, and I'll give you like a, a couple of concrete examples just to give, give you an idea of what kinda what you're looking at. one of the, our data centers had really pathological IO latency. [00:04:23] Bryan: we had a very, uh, database heavy workload. And this was kind of right at the period where you were still deploying on rotating media on hard drives. So this is like, so. An all flash buy did not make economic sense when we did this in, in 2016. This probably, it'd be interesting to know like when was the, the kind of the last time that that actual hard drives made sense? [00:04:50] Bryan: 'cause I feel this was close to it. So we had a, a bunch of, of a pathological IO problems, but we had one data center in which the outliers were actually quite a bit worse and there was so much going on in that system. It took us a long time to figure out like why. And because when, when you, when you're io when you're seeing worse io I mean you're naturally, you wanna understand like what's the workload doing? [00:05:14] Bryan: You're trying to take a first principles approach. What's the workload doing? So this is a very intensive database workload to support the, the object storage system that we had built called Manta. And that the, the metadata tier was stored and uh, was we were using Postgres for that. And that was just getting absolutely slaughtered. [00:05:34] Bryan: Um, and ultimately very IO bound with these kind of pathological IO latencies. Uh, and as we, you know, trying to like peel away the layers to figure out what was going on. And I finally had this thing. So it's like, okay, we are seeing at the, at the device layer, at the at, at the disc layer, we are seeing pathological outliers in this data center that we're not seeing anywhere else. [00:06:00] Bryan: And that does not make any sense. And the thought occurred to me. I'm like, well, maybe we are. Do we have like different. Different rev of firmware on our HGST drives, HGST. Now part of WD Western Digital were the drives that we had everywhere. And, um, so maybe we had a different, maybe I had a firmware bug. [00:06:20] Bryan: I, this would not be the first time in my life at all that I would have a drive firmware issue. Uh, and I went to go pull the firmware, rev, and I'm like, Toshiba makes hard drives? So we had, I mean. I had no idea that Toshiba even made hard drives, let alone that they were our, they were in our data center. [00:06:38] Bryan: I'm like, what is this? And as it turns out, and this is, you know, part of the, the challenge when you don't have an integrated system, which not to pick on them, but Dell doesn't, and what Dell would routinely put just sub make substitutes, and they make substitutes that they, you know, it's kind of like you're going to like, I don't know, Instacart or whatever, and they're out of the thing that you want. [00:07:03] Bryan: So, you know, you're, someone makes a substitute and like sometimes that's okay, but it's really not okay in a data center. And you really want to develop and validate a, an end-to-end integrated system. And in this case, like Toshiba doesn't, I mean, Toshiba does make hard drives, but they are a, or the data they did, uh, they basically were, uh, not competitive and they were not competitive in part for the reasons that we were discovering. [00:07:29] Bryan: They had really serious firmware issues. So the, these were drives that would just simply stop a, a stop acknowledging any reads from the order of 2,700 milliseconds. Long time, 2.7 seconds. Um. And that was a, it was a drive firmware issue, but it was highlighted like a much deeper issue, which was the simple lack of control that we had over our own destiny. [00:07:53] Bryan: Um, and it's an, it's, it's an example among many where Dell is making a decision. That lowers the cost of what they are providing you marginally, but it is then giving you a system that they shouldn't have any confidence in because it's not one that they've actually designed and they leave it to the customer, the end user, to make these discoveries. [00:08:18] Bryan: And these things happen up and down the stack. And for every, for whether it's, and, and not just to pick on Dell because it's, it's true for HPE, it's true for super micro, uh, it's true for your switch vendors. It's, it's true for storage vendors where the, the, the, the one that is left actually integrating these things and trying to make the the whole thing work is the end user sitting in their data center. AWS / Google are not buying off the shelf hardware but you can't use it [00:08:42] Bryan: There's not a product that they can buy that gives them elastic infrastructure, a cloud in their own DC The, the product that you buy is the public cloud. Like when you go in the public cloud, you don't worry about the stuff because that it's, it's AWS's issue or it's GCP's issue. And they are the ones that get this to ground. [00:09:02] Bryan: And they, and this was kind of, you know, the eye-opening moment. Not a surprise. Uh, they are not Dell customers. They're not HPE customers. They're not super micro customers. They have designed their own machines. And to varying degrees, depending on which one you're looking at. But they've taken the clean sheet of paper and the frustration that we had kind of at Joyent and beginning to wonder and then Samsung and kind of wondering what was next, uh, is that, that what they built was not available for purchase in the data center. [00:09:35] Bryan: You could only rent it in the public cloud. And our big belief is that public cloud computing is a really important revolution in infrastructure. Doesn't feel like a different, a deep thought, but cloud computing is a really important revolution. It shouldn't only be available to rent. You should be able to actually buy it. [00:09:53] Bryan: And there are a bunch of reasons for doing that. Uh, one in the one we we saw at Samsung is economics, which I think is still the dominant reason where it just does not make sense to rent all of your compute in perpetuity. But there are other reasons too. There's security, there's risk management, there's latency. [00:10:07] Bryan: There are a bunch of reasons why one might wanna to own one's own infrastructure. But, uh, that was very much the, the, so the, the genesis for oxide was coming out of this very painful experience and a painful experience that, because, I mean, a long answer to your question about like what was it like to be at Samsung scale? [00:10:27] Bryan: Those are the kinds of things that we, I mean, in our other data centers, we didn't have Toshiba drives. We only had the HDSC drives, but it's only when you get to this larger scale that you begin to see some of these pathologies. But these pathologies then are really debilitating in terms of those who are trying to develop a service on top of them. [00:10:45] Bryan: So it was, it was very educational in, in that regard. And you're very grateful for the experience at Samsung in terms of opening our eyes to the challenge of running at that kind of scale. [00:10:57] Jeremy: Yeah, because I, I think as software engineers, a lot of times we, we treat the hardware as a, as a given where, [00:11:08] Bryan: Yeah. [00:11:08] Bryan: Yeah. There's software in chard drives [00:11:09] Jeremy: It sounds like in, in this case, I mean, maybe the issue is not so much that. Dell or HP as a company doesn't own every single piece that they're providing you, but rather the fact that they're swapping pieces in and out without advertising them, and then when it becomes a problem, they're not necessarily willing to, to deal with the, the consequences of that. [00:11:34] Bryan: They just don't know. I mean, I think they just genuinely don't know. I mean, I think that they, it's not like they're making a deliberate decision to kind of ship garbage. It's just that they are making, I mean, I think it's exactly what you said about like, not thinking about the hardware. It's like, what's a hard drive? [00:11:47] Bryan: Like what's it, I mean, it's a hard drive. It's got the same specs as this other hard drive and Intel. You know, it's a little bit cheaper, so why not? It's like, well, like there's some reasons why not, and one of the reasons why not is like, uh, even a hard drive, whether it's rotating media or, or flash, like that's not just hardware. [00:12:05] Bryan: There's software in there. And that the software's like not the same. I mean, there are components where it's like, there's actually, whether, you know, if, if you're looking at like a resistor or a capacitor or something like this Yeah. If you've got two, two parts that are within the same tolerance. Yeah. [00:12:19] Bryan: Like sure. Maybe, although even the EEs I think would be, would be, uh, objecting that a little bit. But the, the, the more complicated you get, and certainly once you get to the, the, the, the kind of the hardware that we think of like a, a, a microprocessor, a a network interface card, a a, a hard driver, an NVME drive. [00:12:38] Bryan: Those things are super complicated and there's a whole bunch of software inside of those things, the firmware, and that's the stuff that, that you can't, I mean, you say that software engineers don't think about that. It's like you, no one can really think about that because it's proprietary that's kinda welded shut and you've got this abstraction into it. [00:12:55] Bryan: But the, the way that thing operates is very core to how the thing in aggregate will behave. And I think that you, the, the kind of, the, the fundamental difference between Oxide's approach and the approach that you get at a Dell HP Supermicro, wherever, is really thinking holistically in terms of hardware and software together in a system that, that ultimately delivers cloud computing to a user. [00:13:22] Bryan: And there's a lot of software at many, many, many, many different layers. And it's very important to think about, about that software and that hardware holistically as a single system. [00:13:34] Jeremy: And during that time at Joyent, when you experienced some of these issues, was it more of a case of you didn't have enough servers experiencing this? So if it would happen, you might say like, well, this one's not working, so maybe we'll just replace the hardware. What, what was the thought process when you were working at that smaller scale and, and how did these issues affect you? UEFI / Baseboard Management Controller [00:13:58] Bryan: Yeah, at the smaller scale, you, uh, you see fewer of them, right? You just see it's like, okay, we, you know, what you might see is like, that's weird. We kinda saw this in one machine versus seeing it in a hundred or a thousand or 10,000. Um, so you just, you just see them, uh, less frequently as a result, they are less debilitating. [00:14:16] Bryan: Um, I, I think that it's, when you go to that larger scale, those things that become, that were unusual now become routine and they become debilitating. Um, so it, it really is in many regards a function of scale. Uh, and then I think it was also, you know, it was a little bit dispiriting that kind of the substrate we were building on really had not improved. [00:14:39] Bryan: Um, and if you look at, you know, the, if you buy a computer server, buy an x86 server. There is a very low layer of firmware, the BIOS, the basic input output system, the UEFI BIOS, and this is like an abstraction layer that has, has existed since the eighties and hasn't really meaningfully improved. Um, the, the kind of the transition to UEFI happened with, I mean, I, I ironically with Itanium, um, you know, two decades ago. [00:15:08] Bryan: but beyond that, like this low layer, this lowest layer of platform enablement software is really only impeding the operability of the system. Um, you look at the baseboard management controller, which is the kind of the computer within the computer, there is a, uh, there is an element in the machine that needs to handle environmentals, that needs to handle, uh, operate the fans and so on. [00:15:31] Bryan: Uh, and that traditionally has this, the space board management controller, and that architecturally just hasn't improved in the last two decades. And, you know, that's, it's a proprietary piece of silicon. Generally from a company that no one's ever heard of called a Speed, uh, which has to be, is written all on caps, so I guess it needs to be screamed. [00:15:50] Bryan: Um, a speed has a proprietary part that has a, there is a root password infamously there, is there, the root password is encoded effectively in silicon. So, uh, which is just, and for, um, anyone who kind of goes deep into these things, like, oh my God, are you kidding me? Um, when we first started oxide, the wifi password was a fraction of the a speed root password for the bmc. [00:16:16] Bryan: It's kinda like a little, little BMC humor. Um, but those things, it was just dispiriting that, that the, the state-of-the-art was still basically personal computers running in the data center. Um, and that's part of what, what was the motivation for doing something new? [00:16:32] Jeremy: And for the people using these systems, whether it's the baseboard management controller or it's the The BIOS or UF UEFI component, what are the actual problems that people are seeing seen? Security vulnerabilities and poor practices in the BMC [00:16:51] Bryan: Oh man, I, the, you are going to have like some fraction of your listeners, maybe a big fraction where like, yeah, like what are the problems? That's a good question. And then you're gonna have the people that actually deal with these things who are, did like their heads already hit the desk being like, what are the problems? [00:17:06] Bryan: Like what are the non problems? Like what, what works? Actually, that's like a shorter answer. Um, I mean, there are so many problems and a lot of it is just like, I mean, there are problems just architecturally these things are just so, I mean, and you could, they're the problems spread to the horizon, so you can kind of start wherever you want. [00:17:24] Bryan: But I mean, as like, as a really concrete example. Okay, so the, the BMCs that, that the computer within the computer that needs to be on its own network. So you now have like not one network, you got two networks that, and that network, by the way, it, that's the network that you're gonna log into to like reset the machine when it's otherwise unresponsive. [00:17:44] Bryan: So that going into the BMC, you can are, you're able to control the entire machine. Well it's like, alright, so now I've got a second net network that I need to manage. What is running on the BMC? Well, it's running some. Ancient, ancient version of Linux it that you got. It's like, well how do I, how do I patch that? [00:18:02] Bryan: How do I like manage the vulnerabilities with that? Because if someone is able to root your BMC, they control the system. So it's like, this is not you've, and now you've gotta go deal with all of the operational hair around that. How do you upgrade that system updating the BMC? I mean, it's like you've got this like second shadow bad infrastructure that you have to go manage. [00:18:23] Bryan: Generally not open source. There's something called open BMC, um, which, um, you people use to varying degrees, but you're generally stuck with the proprietary BMC, so you're generally stuck with, with iLO from HPE or iDRAC from Dell or, or, uh, the, uh, su super micros, BMC, that H-P-B-M-C, and you are, uh, it is just excruciating pain. [00:18:49] Bryan: Um, and that this is assuming that by the way, that everything is behaving correctly. The, the problem is that these things often don't behave correctly, and then the consequence of them not behaving correctly. It's really dire because it's at that lowest layer of the system. So, I mean, I'll give you a concrete example. [00:19:07] Bryan: a customer of theirs reported to me, so I won't disclose the vendor, but let's just say that a well-known vendor had an issue with their, their temperature sensors were broken. Um, and the thing would always read basically the wrong value. So it was the BMC that had to like, invent its own ki a different kind of thermal control loop. [00:19:28] Bryan: And it would index on the, on the, the, the, the actual inrush current. It would, they would look at that at the current that's going into the CPU to adjust the fan speed. That's a great example of something like that's a, that's an interesting idea. That doesn't work. 'cause that's actually not the temperature. [00:19:45] Bryan: So like that software would crank the fans whenever you had an inrush of current and this customer had a workload that would spike the current and by it, when it would spike the current, the, the, the fans would kick up and then they would slowly degrade over time. Well, this workload was spiking the current faster than the fans would degrade, but not fast enough to actually heat up the part. [00:20:08] Bryan: And ultimately over a very long time, in a very painful investigation, it's customer determined that like my fans are cranked in my data center for no reason. We're blowing cold air. And it's like that, this is on the order of like a hundred watts, a server of, of energy that you shouldn't be spending and like that ultimately what that go comes down to this kind of broken software hardware interface at the lowest layer that has real meaningful consequence, uh, in terms of hundreds of kilowatts, um, across a data center. So this stuff has, has very, very, very real consequence and it's such a shadowy world. Part of the reason that, that your listeners that have dealt with this, that our heads will hit the desk is because it is really aggravating to deal with problems with this layer. [00:21:01] Bryan: You, you feel powerless. You don't control or really see the software that's on them. It's generally proprietary. You are relying on your vendor. Your vendor is telling you that like, boy, I don't know. You're the only customer seeing this. I mean, the number of times I have heard that for, and I, I have pledged that we're, we're not gonna say that at oxide because it's such an unaskable thing to say like, you're the only customer saying this. [00:21:25] Bryan: It's like, it feels like, are you blaming me for my problem? Feels like you're blaming me for my problem? Um, and what you begin to realize is that to a degree, these folks are speaking their own truth because the, the folks that are running at real scale at Hyperscale, those folks aren't Dell, HP super micro customers. [00:21:46] Bryan: They're actually, they've done their own thing. So it's like, yeah, Dell's not seeing that problem, um, because they're not running at the same scale. Um, but when you do run, you only have to run at modest scale before these things just become. Overwhelming in terms of the, the headwind that they present to people that wanna deploy infrastructure. The problem is felt with just a few racks [00:22:05] Jeremy: Yeah, so maybe to help people get some perspective at, at what point do you think that people start noticing or start feeling these problems? Because I imagine that if you're just have a few racks or [00:22:22] Bryan: do you have a couple racks or the, or do you wonder or just wondering because No, no, no. I would think, I think anyone who deploys any number of servers, especially now, especially if your experience is only in the cloud, you're gonna be like, what the hell is this? I mean, just again, just to get this thing working at all. [00:22:39] Bryan: It is so it, it's so hairy and so congealed, right? It's not designed. Um, and it, it, it, it's accreted it and it's so obviously accreted that you are, I mean, nobody who is setting up a rack of servers is gonna think to themselves like, yes, this is the right way to go do it. This all makes sense because it's, it's just not, it, I, it feels like the kit, I mean, kit car's almost too generous because it implies that there's like a set of plans to work to in the end. [00:23:08] Bryan: Uh, I mean, it, it, it's a bag of bolts. It's a bunch of parts that you're putting together. And so even at the smallest scales, that stuff is painful. Just architecturally, it's painful at the small scale then, but at least you can get it working. I think the stuff that then becomes debilitating at larger scale are the things that are, are worse than just like, I can't, like this thing is a mess to get working. [00:23:31] Bryan: It's like the, the, the fan issue that, um, where you are now seeing this over, you know, hundreds of machines or thousands of machines. Um, so I, it is painful at more or less all levels of scale. There's, there is no level at which the, the, the pc, which is really what this is, this is a, the, the personal computer architecture from the 1980s and there is really no level of scale where that's the right unit. Running elastic infrastructure is the hardware but also, hypervisor, distributed database, api, etc [00:23:57] Bryan: I mean, where that's the right thing to go deploy, especially if what you are trying to run. Is elastic infrastructure, a cloud. Because the other thing is like we, we've kinda been talking a lot about that hardware layer. Like hardware is, is just the start. Like you actually gotta go put software on that and actually run that as elastic infrastructure. [00:24:16] Bryan: So you need a hypervisor. Yes. But you need a lot more than that. You, you need to actually, you, you need a distributed database, you need web endpoints. You need, you need a CLI, you need all the stuff that you need to actually go run an actual service of compute or networking or storage. I mean, and for, for compute, even for compute, there's a ton of work to be done. [00:24:39] Bryan: And compute is by far, I would say the simplest of the, of the three. When you look at like networks, network services, storage services, there's a whole bunch of stuff that you need to go build in terms of distributed systems to actually offer that as a cloud. So it, I mean, it is painful at more or less every LE level if you are trying to deploy cloud computing on. What's a control plane? [00:25:00] Jeremy: And for someone who doesn't have experience building or working with this type of infrastructure, when you talk about a control plane, what, what does that do in the context of this system? [00:25:16] Bryan: So control plane is the thing that is, that is everything between your API request and that infrastructure actually being acted upon. So you go say, Hey, I, I want a provision, a vm. Okay, great. We've got a whole bunch of things we're gonna provision with that. We're gonna provision a vm, we're gonna get some storage that's gonna go along with that, that's got a network storage service that's gonna come out of, uh, we've got a virtual network that we're gonna either create or attach to. [00:25:39] Bryan: We've got a, a whole bunch of things we need to go do for that. For all of these things, there are metadata components that need, we need to keep track of this thing that, beyond the actual infrastructure that we create. And then we need to go actually, like act on the actual compute elements, the hostos, what have you, the switches, what have you, and actually go. [00:25:56] Bryan: Create these underlying things and then connect them. And there's of course, the challenge of just getting that working is a big challenge. Um, but getting that working robustly, getting that working is, you know, when you go to provision of vm, um, the, all the, the, the steps that need to happen and what happens if one of those steps fails along the way? [00:26:17] Bryan: What happens if, you know, one thing we're very mindful of is these kind of, you get these long tails of like, why, you know, generally our VM provisioning happened within this time, but we get these long tails where it takes much longer. What's going on? What, where in this process are we, are we actually spending time? [00:26:33] Bryan: Uh, and there's a whole lot of complexity that you need to go deal with that. There's a lot of complexity that you need to go deal with this effectively, this workflow that's gonna go create these things and manage them. Um, we use a, a pattern that we call, that are called sagas, actually is a, is a database pattern from the eighties. [00:26:51] Bryan: Uh, Katie McCaffrey is a, is a database reCrcher who, who, uh, I, I think, uh, reintroduce the idea of, of sagas, um, in the last kind of decade. Um, and this is something that we picked up, um, and I've done a lot of really interesting things with, um, to allow for, to this kind of, these workflows to be, to be managed and done so robustly in a way that you can restart them and so on. [00:27:16] Bryan: Uh, and then you guys, you get this whole distributed system that can do all this. That whole distributed system, that itself needs to be reliable and available. So if you, you know, you need to be able to, what happens if you, if you pull a sled or if a sled fails, how does the system deal with that? [00:27:33] Bryan: How does the system deal with getting an another sled added to the system? Like how do you actually grow this distributed system? And then how do you update it? How do you actually go from one version to the next? And all of that has to happen across an air gap where this is gonna run as part of the computer. [00:27:49] Bryan: So there are, it, it is fractally complicated. There, there is a lot of complexity here in, in software, in the software system and all of that. We kind of, we call the control plane. Um, and it, this is the what exists at AWS at GCP, at Azure. When you are hitting an endpoint that's provisioning an EC2 instance for you. [00:28:10] Bryan: There is an AWS control plane that is, is doing all of this and has, uh, some of these similar aspects and certainly some of these similar challenges. Are vSphere / Proxmox / Hyper-V in the same category? [00:28:20] Jeremy: And for people who have run their own servers with something like say VMware or Hyper V or Proxmox, are those in the same category? [00:28:32] Bryan: Yeah, I mean a little bit. I mean, it kind of like vSphere Yes. Via VMware. No. So it's like you, uh, VMware ESX is, is kind of a key building block upon which you can build something that is a more meaningful distributed system. When it's just like a machine that you're provisioning VMs on, it's like, okay, well that's actually, you as the human might be the control plane. [00:28:52] Bryan: Like, that's, that, that's, that's a much easier problem. Um, but when you've got, you know, tens, hundreds, thousands of machines, you need to do it robustly. You need something to coordinate that activity and you know, you need to pick which sled you land on. You need to be able to move these things. You need to be able to update that whole system. [00:29:06] Bryan: That's when you're getting into a control plane. So, you know, some of these things have kind of edged into a control plane, certainly VMware. Um, now Broadcom, um, has delivered something that's kind of cloudish. Um, I think that for folks that are truly born on the cloud, it, it still feels somewhat, uh, like you're going backwards in time when you, when you look at these kind of on-prem offerings. [00:29:29] Bryan: Um, but, but it, it, it's got these aspects to it for sure. Um, and I think that we're, um, some of these other things when you're just looking at KVM or just looks looking at Proxmox you kind of need to, to connect it to other broader things to turn it into something that really looks like manageable infrastructure. [00:29:47] Bryan: And then many of those projects are really, they're either proprietary projects, uh, proprietary products like vSphere, um, or you are really dealing with open source projects that are. Not necessarily aimed at the same level of scale. Um, you know, you look at a, again, Proxmox or, uh, um, you'll get an OpenStack. [00:30:05] Bryan: Um, and you know, OpenStack is just a lot of things, right? I mean, OpenStack has got so many, the OpenStack was kind of a, a free for all, for every infrastructure vendor. Um, and I, you know, there was a time people were like, don't you, aren't you worried about all these companies together that, you know, are coming together for OpenStack? [00:30:24] Bryan: I'm like, haven't you ever worked for like a company? Like, companies don't get along. By the way, it's like having multiple companies work together on a thing that's bad news, not good news. And I think, you know, one of the things that OpenStack has definitely struggled with, kind of with what, actually the, the, there's so many different kind of vendor elements in there that it's, it's very much not a product, it's a project that you're trying to run. [00:30:47] Bryan: But that's, but that very much is in, I mean, that's, that's similar certainly in spirit. [00:30:53] Jeremy: And so I think this is kind of like you're alluding to earlier, the piece that allows you to allocate, compute, storage, manage networking, gives you that experience of I can go to a web console or I can use an API and I can spin up machines, get them all connected. At the end of the day, the control plane. Is allowing you to do that in hopefully a user-friendly way. [00:31:21] Bryan: That's right. Yep. And in the, I mean, in order to do that in a modern way, it's not just like a user-friendly way. You really need to have a CLI and a web UI and an API. Those all need to be drawn from the same kind of single ground truth. Like you don't wanna have any of those be an afterthought for the other. [00:31:39] Bryan: You wanna have the same way of generating all of those different endpoints and, and entries into the system. Building a control plane now has better tools (Rust, CockroachDB) [00:31:46] Jeremy: And if you take your time at Joyent as an example. What kind of tools existed for that versus how much did you have to build in-house for as far as the hypervisor and managing the compute and all that? [00:32:02] Bryan: Yeah, so we built more or less everything in house. I mean, what you have is, um, and I think, you know, over time we've gotten slightly better tools. Um, I think, and, and maybe it's a little bit easier to talk about the, kind of the tools we started at Oxide because we kind of started with a, with a clean sheet of paper at oxide. [00:32:16] Bryan: We wanted to, knew we wanted to go build a control plane, but we were able to kind of go revisit some of the components. So actually, and maybe I'll, I'll talk about some of those changes. So when we, at, For example, at Joyent, when we were building a cloud at Joyent, there wasn't really a good distributed database. [00:32:34] Bryan: Um, so we were using Postgres as our database for metadata and there were a lot of challenges. And Postgres is not a distributed database. It's running. With a primary secondary architecture, and there's a bunch of issues there, many of which we discovered the hard way. Um, when we were coming to oxide, you have much better options to pick from in terms of distributed databases. [00:32:57] Bryan: You know, we, there was a period that now seems maybe potentially brief in hindsight, but of a really high quality open source distributed databases. So there were really some good ones to, to pick from. Um, we, we built on CockroachDB on CRDB. Um, so that was a really important component. That we had at oxide that we didn't have at Joyent. [00:33:19] Bryan: Um, so we were, I wouldn't say we were rolling our own distributed database, we were just using Postgres and uh, and, and dealing with an enormous amount of pain there in terms of the surround. Um, on top of that, and, and, you know, a, a control plane is much more than a database, obviously. Uh, and you've gotta deal with, uh, there's a whole bunch of software that you need to go, right. [00:33:40] Bryan: Um, to be able to, to transform these kind of API requests into something that is reliable infrastructure, right? And there, there's a lot to that. Uh, especially when networking gets in the mix, when storage gets in the mix, uh, there are a whole bunch of like complicated steps that need to be done, um, at Joyent. [00:33:59] Bryan: Um, we, in part because of the history of the company and like, look. This, this just is not gonna sound good, but it just is what it is and I'm just gonna own it. We did it all in Node, um, at Joyent, which I, I, I know it sounds really right now, just sounds like, well, you, you built it with Tinker Toys. You Okay. [00:34:18] Bryan: Uh, did, did you think it was, you built the skyscraper with Tinker Toys? Uh, it's like, well, okay. We actually, we had greater aspirations for the Tinker Toys once upon a time, and it was better than, you know, than Twisted Python and Event Machine from Ruby, and we weren't gonna do it in Java. All right. [00:34:32] Bryan: So, but let's just say that that experiment, uh, that experiment did ultimately end in a predictable fashion. Um, and, uh, we, we decided that maybe Node was not gonna be the best decision long term. Um, Joyent was the company behind node js. Uh, back in the day, Ryan Dahl worked for Joyent. Uh, and then, uh, then we, we, we. [00:34:53] Bryan: Uh, landed that in a foundation in about, uh, what, 2015, something like that. Um, and began to consider our world beyond, uh, beyond Node. Rust at Oxide [00:35:04] Bryan: A big tool that we had in the arsenal when we started Oxide is Rust. Um, and so indeed the name of the company is, is a tip of the hat to the language that we were pretty sure we were gonna be building a lot of stuff in. [00:35:16] Bryan: Namely Rust. And, uh, rust is, uh, has been huge for us, a very important revolution in programming languages. you know, there, there, there have been different people kind of coming in at different times and I kinda came to Rust in what I, I think is like this big kind of second expansion of rust in 2018 when a lot of technologists were think, uh, sick of Node and also sick of Go. [00:35:43] Bryan: And, uh, also sick of C++. And wondering is there gonna be something that gives me the, the, the performance, of that I get outta C. The, the robustness that I can get out of a C program but is is often difficult to achieve. but can I get that with kind of some, some of the velocity of development, although I hate that term, some of the speed of development that you get out of a more interpreted language. [00:36:08] Bryan: Um, and then by the way, can I actually have types, I think types would be a good idea? Uh, and rust obviously hits the sweet spot of all of that. Um, it has been absolutely huge for us. I mean, we knew when we started the company again, oxide, uh, we were gonna be using rust in, in quite a, quite a. Few places, but we weren't doing it by fiat. [00:36:27] Bryan: Um, we wanted to actually make sure we're making the right decision, um, at, at every different, at every layer. Uh, I think what has been surprising is the sheer number of layers at which we use rust in terms of, we've done our own embedded firmware in rust. We've done, um, in, in the host operating system, which is still largely in C, but very big components are in rust. [00:36:47] Bryan: The hypervisor Propolis is all in rust. Uh, and then of course the control plane, that distributed system on that is all in rust. So that was a very important thing that we very much did not need to build ourselves. We were able to really leverage, uh, a terrific community. Um. We were able to use, uh, and we've done this at Joyent as well, but at Oxide, we've used Illumos as a hostos component, which, uh, our variant is called Helios. [00:37:11] Bryan: Um, we've used, uh, bhyve um, as a, as as that kind of internal hypervisor component. we've made use of a bunch of different open source components to build this thing, um, which has been really, really important for us. Uh, and open source components that didn't exist even like five years prior. [00:37:28] Bryan: That's part of why we felt that 2019 was the right time to start the company. And so we started Oxide. The problems building a control plane in Node [00:37:34] Jeremy: You had mentioned that at Joyent, you had tried to build this in, in Node. What were the, what were the, the issues or the, the challenges that you had doing that? [00:37:46] Bryan: Oh boy. Yeah. again, we, I kind of had higher hopes in 2010, I would say. When we, we set on this, um, the, the, the problem that we had just writ large, um. JavaScript is really designed to allow as many people on earth to write a program as possible, which is good. I mean, I, I, that's a, that's a laudable goal. [00:38:09] Bryan: That is the goal ultimately of such as it is of JavaScript. It's actually hard to know what the goal of JavaScript is, unfortunately, because Brendan Ike never actually wrote a book. so that there is not a canonical, you've got kind of Doug Crockford and other people who've written things on JavaScript, but it's hard to know kind of what the original intent of JavaScript is. [00:38:27] Bryan: The name doesn't even express original intent, right? It was called Live Script, and it was kind of renamed to JavaScript during the Java Frenzy of the late nineties. A name that makes no sense. There is no Java in JavaScript. that is kind of, I think, revealing to kind of the, uh, the unprincipled mess that is JavaScript. [00:38:47] Bryan: It, it, it's very pragmatic at some level, um, and allows anyone to, it makes it very easy to write software. The problem is it's much more difficult to write really rigorous software. So, uh, and this is what I should differentiate JavaScript from TypeScript. This is really what TypeScript is trying to solve. [00:39:07] Bryan: TypeScript is like. How can, I think TypeScript is a, is a great step forward because TypeScript is like, how can we bring some rigor to this? Like, yes, it's great that it's easy to write JavaScript, but that's not, we, we don't wanna do that for Absolutely. I mean that, that's not the only problem we solve. [00:39:23] Bryan: We actually wanna be able to write rigorous software and it's actually okay if it's a little harder to write rigorous software that's actually okay if it gets leads to, to more rigorous artifacts. Um, but in JavaScript, I mean, just a concrete example. You know, there's nothing to prevent you from referencing a property that doesn't actually exist in JavaScript. [00:39:43] Bryan: So if you fat finger a property name, you are relying on something to tell you. By the way, I think you've misspelled this because there is no type definition for this thing. And I don't know that you've got one that's spelled correctly, one that's spelled incorrectly, that's often undefined. And then the, when you actually go, you say you've got this typo that is lurking in your what you want to be rigorous software. [00:40:07] Bryan: And if you don't execute that code, like you won't know that's there. And then you do execute that code. And now you've got a, you've got an undefined object. And now that's either gonna be an exception or it can, again, depends on how that's handled. It can be really difficult to determine the origin of that, of, of that error, of that programming. [00:40:26] Bryan: And that is a programmer error. And one of the big challenges that we had with Node is that programmer errors and operational errors, like, you know, I'm out of disk space as an operational error. Those get conflated and it becomes really hard. And in fact, I think the, the language wanted to make it easier to just kind of, uh, drive on in the event of all errors. [00:40:53] Bryan: And it's like, actually not what you wanna do if you're trying to build a reliable, robust system. So we had. No end of issues. [00:41:01] Bryan: We've got a lot of experience developing rigorous systems, um, again coming out of operating systems development and so on. And we want, we brought some of that rigor, if strangely, to JavaScript. So one of the things that we did is we brought a lot of postmortem, diagnos ability and observability to node. [00:41:18] Bryan: And so if, if one of our node processes. Died in production, we would actually get a core dump from that process, a core dump that we could actually meaningfully process. So we did a bunch of kind of wild stuff. I mean, actually wild stuff where we could actually make sense of the JavaScript objects in a binary core dump. JavaScript values ease of getting started over robustness [00:41:41] Bryan: Um, and things that we thought were really important, and this is the, the rest of the world just looks at this being like, what the hell is this? I mean, it's so out of step with it. The problem is that we were trying to bridge two disconnected cultures of one developing really. Rigorous software and really designing it for production, diagnosability and the other, really designing it to software to run in the browser and for anyone to be able to like, you know, kind of liven up a webpage, right? [00:42:10] Bryan: Is kinda the origin of, of live script and then JavaScript. And we were kind of the only ones sitting at the intersection of that. And you begin when you are the only ones sitting at that kind of intersection. You just are, you're, you're kind of fighting a community all the time. And we just realized that we are, there were so many things that the community wanted to do that we felt are like, no, no, this is gonna make software less diagnosable. It's gonna make it less robust. The NodeJS split and why people left [00:42:36] Bryan: And then you realize like, I'm, we're the only voice in the room because we have got, we have got desires for this language that it doesn't have for itself. And this is when you realize you're in a bad relationship with software. It's time to actually move on. And in fact, actually several years after, we'd already kind of broken up with node. [00:42:55] Bryan: Um, and it was like, it was a bit of an acrimonious breakup. there was a, uh, famous slash infamous fork of node called IoJS Um, and this was viewed because people, the community, thought that Joyent was being what was not being an appropriate steward of node js and was, uh, not allowing more things to come into to, to node. [00:43:19] Bryan: And of course, the reason that we of course, felt that we were being a careful steward and we were actively resisting those things that would cut against its fitness for a production system. But it's some way the community saw it and they, and forked, um, and, and I think the, we knew before the fork that's like, this is not working and we need to get this thing out of our hands. Platform is a reflection of values node summit talk [00:43:43] Bryan: And we're are the wrong hands for this? This needs to be in a foundation. Uh, and so we kind of gone through that breakup, uh, and maybe it was two years after that. That, uh, friend of mine who was um, was running the, uh, the node summit was actually, it's unfortunately now passed away. Charles er, um, but Charles' venture capitalist great guy, and Charles was running Node Summit and came to me in 2017. [00:44:07] Bryan: He is like, I really want you to keynote Node Summit. And I'm like, Charles, I'm not gonna do that. I've got nothing nice to say. Like, this is the, the, you don't want, I'm the last person you wanna keynote. He's like, oh, if you have nothing nice to say, you should definitely keynote. You're like, oh God, okay, here we go. [00:44:22] Bryan: He's like, no, I really want you to talk about, like, you should talk about the Joyent breakup with NodeJS. I'm like, oh man. [00:44:29] Bryan: And that led to a talk that I'm really happy that I gave, 'cause it was a very important talk for me personally. Uh, called Platform is a reflection of values and really looking at the values that we had for Node and the values that Node had for itself. And they didn't line up. [00:44:49] Bryan: And the problem is that the values that Node had for itself and the values that we had for Node are all kind of positives, right? Like there's nobody in the node community who's like, I don't want rigor, I hate rigor. It's just that if they had the choose between rigor and making the language approachable. [00:45:09] Bryan: They would choose approachability every single time. They would never choose rigor. And, you know, that was a, that was a big eye-opener. I do, I would say, if you watch this talk. [00:45:20] Bryan: because I knew that there's, like, the audience was gonna be filled with, with people who, had been a part of the fork in 2014, I think was the, the, the, the fork, the IOJS fork. And I knew that there, there were, there were some, you know, some people that were, um, had been there for the fork and. [00:45:41] Bryan: I said a little bit of a trap for the audience. But the, and the trap, I said, you know what, I, I kind of talked about the values that we had and the aspirations we had for Node, the aspirations that Node had for itself and how they were different. [00:45:53] Bryan: And, you know, and I'm like, look in, in, in hindsight, like a fracture was inevitable. And in 2014 there was finally a fracture. And do people know what happened in 2014? And if you, if you, you could listen to that talk, everyone almost says in unison, like IOJS. I'm like, oh right. IOJS. Right. That's actually not what I was thinking of. [00:46:19] Bryan: And I go to the next slide and is a tweet from a guy named TJ Holloway, Chuck, who was the most prolific contributor to Node. And it was his tweet also in 2014 before the fork, before the IOJS fork explaining that he was leaving Node and that he was going to go. And you, if you turn the volume all the way up, you can hear the audience gasp. [00:46:41] Bryan: And it's just delicious because the community had never really come, had never really confronted why TJ left. Um, there. And I went through a couple folks, Felix, bunch of other folks, early Node folks. That were there in 2010, were leaving in 2014, and they were going to go primarily, and they were going to go because they were sick of the same things that we were sick of. [00:47:09] Bryan: They, they, they had hit the same things that we had hit and they were frustrated. I I really do believe this, that platforms do reflect their own values. And when you are making a software decision, you are selecting value. [00:47:26] Bryan: You should select values that align with the values that you have for that software. That is, those are, that's way more important than other things that people look at. I think people look at, for example, quote unquote community size way too frequently, community size is like. Eh, maybe it can be fine. [00:47:44] Bryan: I've been in very large communities, node. I've been in super small open source communities like AUMs and RAs, a bunch of others. there are strengths and weaknesses to both approaches just as like there's a strength to being in a big city versus a small town. Me personally, I'll take the small community more or less every time because the small community is almost always self-selecting based on values and just for the same reason that I like working at small companies or small teams. [00:48:11] Bryan: There's a lot of value to be had in a small community. It's not to say that large communities are valueless, but again, long answer to your question of kind of where did things go south with Joyent and node. They went south because the, the values that we had and the values the community had didn't line up and that was a very educational experience, as you might imagine. [00:48:33] Jeremy: Yeah. And, and given that you mentioned how, because of those values, some people moved from Node to go, and in the end for much of what oxide is building. You ended up using rust. What, what would you say are the, the values of go and and rust, and how did you end up choosing Rust given that. Go's decisions regarding generics, versioning, compilation speed priority [00:48:56] Bryan: Yeah, I mean, well, so the value for, yeah. And so go, I mean, I understand why people move from Node to Go, go to me was kind of a lateral move. Um, there were a bunch of things that I, uh, go was still garbage collected, um, which I didn't like. Um, go also is very strange in terms of there are these kind of like. [00:49:17] Bryan: These autocratic kind of decisions that are very bizarre. Um, there, I mean, generics is kind of a famous one, right? Where go kind of as a point of principle didn't have generics, even though go itself actually the innards of go did have generics. It's just that you a go user weren't allowed to have them. [00:49:35] Bryan: And you know, it's kind of, there was, there was an old cartoon years and years ago about like when a, when a technologist is telling you that something is technically impossible, that actually means I don't feel like it. Uh, and there was a certain degree of like, generics are technically impossible and go, it's like, Hey, actually there are. [00:49:51] Bryan: And so there was, and I just think that the arguments against generics were kind of disingenuous. Um, and indeed, like they ended up adopting generics and then there's like some super weird stuff around like, they're very anti-assertion, which is like, what, how are you? Why are you, how is someone against assertions, it doesn't even make any sense, but it's like, oh, nope. [00:50:10] Bryan: Okay. There's a whole scree on it. Nope, we're against assertions and the, you know, against versioning. There was another thing like, you know, the Rob Pike has kind of famously been like, you should always just run on the way to commit. And you're like, does that, is that, does that make sense? I mean this, we actually built it. [00:50:26] Bryan: And so there are a bunch of things like that. You're just like, okay, this is just exhausting and. I mean, there's some things about Go that are great and, uh, plenty of other things that I just, I'm not a fan of. Um, I think that the, in the end, like Go cares a lot about like compile time. It's super important for Go Right? [00:50:44] Bryan: Is very quick, compile time. I'm like, okay. But that's like compile time is not like, it's not unimportant, it's doesn't have zero importance. But I've got other things that are like lots more important than that. Um, what I really care about is I want a high performing artifact. I wanted garbage collection outta my life. Don't think garbage collection has good trade offs [00:51:00] Bryan: I, I gotta tell you, I, I like garbage collection to me is an embodiment of this like, larger problem of where do you put cognitive load in the software development process. And what garbage collection is saying to me it is right for plenty of other people and the software that they wanna develop. [00:51:21] Bryan: But for me and the software that I wanna develop, infrastructure software, I don't want garbage collection because I can solve the memory allocation problem. I know when I'm like, done with something or not. I mean, it's like I, whether that's in, in C with, I mean it's actually like, it's really not that hard to not leak memory in, in a C base system. [00:51:44] Bryan: And you can. give yourself a lot of tooling that allows you to diagnose where memory leaks are coming from. So it's like that is a solvable problem. There are other challenges with that, but like, when you are developing a really sophisticated system that has garbage collection is using garbage collection. [00:51:59] Bryan: You spend as much time trying to dork with the garbage collector to convince it to collect the thing that you know is garbage. You are like, I've got this thing. I know it's garbage. Now I need to use these like tips and tricks to get the garbage collector. I mean, it's like, it feels like every Java performance issue goes to like minus xx call and use the other garbage collector, whatever one you're using, use a different one and using a different, a different approach. [00:52:23] Bryan: It's like, so you're, you're in this, to me, it's like you're in the worst of all worlds where. the reason that garbage collection is helpful is because the programmer doesn't have to think at all about this problem. But now you're actually dealing with these long pauses in production. [00:52:38] Bryan: You're dealing with all these other issues where actually you need to think a lot about it. And it's kind of, it, it it's witchcraft. It, it, it's this black box that you can't see into. So it's like, what problem have we solved exactly? And I mean, so the fact that go had garbage collection, it's like, eh, no, I, I do not want, like, and then you get all the other like weird fatwahs and you know, everything else. [00:52:57] Bryan: I'm like, no, thank you. Go is a no thank you for me, I, I get it why people like it or use it, but it's, it's just, that was not gonna be it. Choosing Rust [00:53:04] Bryan: I'm like, I want C. but I, there are things I didn't like about C too. I was looking for something that was gonna give me the deterministic kind of artifact that I got outta C. But I wanted library support and C is tough because there's, it's all convention. you know, there's just a bunch of other things that are just thorny. And I remember thinking vividly in 2018, I'm like, well, it's rust or bust. Ownership model, algebraic types, error handling [00:53:28] Bryan: I'm gonna go into rust. And, uh, I hope I like it because if it's not this, it's gonna like, I'm gonna go back to C I'm like literally trying to figure out what the language is for the back half of my career. Um, and when I, you know, did what a lot of people were doing at that time and people have been doing since of, you know, really getting into rust and really learning it, appreciating the difference in the, the model for sure, the ownership model people talk about. [00:53:54] Bryan: That's also obviously very important. It was the error handling that blew me away. And the idea of like algebraic types, I never really had algebraic types. Um, and the ability to, to have. And for error handling is one of these really, uh, you, you really appreciate these things where it's like, how do you deal with a, with a function that can either succeed and return something or it can fail, and the way c deals with that is bad with these kind of sentinels for errors. [00:54:27] Bryan: And, you know, does negative one mean success? Does negative one mean failure? Does zero mean failure? Some C functions, zero means failure. Traditionally in Unix, zero means success. And like, what if you wanna return a file descriptor, you know, it's like, oh. And then it's like, okay, then it'll be like zero through positive N will be a valid result. [00:54:44] Bryan: Negative numbers will be, and like, was it negative one and I said airo, or is it a negative number that did not, I mean, it's like, and that's all convention, right? People do all, all those different things and it's all convention and it's easy to get wrong, easy to have bugs, can't be statically checked and so on. Um, and then what Go says is like, well, you're gonna have like two return values and then you're gonna have to like, just like constantly check all of these all the time. Um, which is also kind of gross. Um, JavaScript is like, Hey, let's toss an exception. If, if we don't like something, if we see an error, we'll, we'll throw an exception. [00:55:15] Bryan: There are a bunch of reasons I don't like that. Um, and you look, you'll get what Rust does, where it's like, no, no, no. We're gonna have these algebra types, which is to say this thing can be a this thing or that thing, but it, but it has to be one of these. And by the way, you don't get to process this thing until you conditionally match on one of these things. [00:55:35] Bryan: You're gonna have to have a, a pattern match on this thing to determine if it's a this or a that, and if it in, in the result type that you, the result is a generic where it's like, it's gonna be either the thing that you wanna return. It's gonna be an okay that contains the thing you wanna return, or it's gonna be an error that contains your error and it forces your code to deal with that. [00:55:57] Bryan: And what that does is it shifts the cognitive load from the person that is operating this thing in production to the, the actual developer that is in development. And I think that that, that to me is like, I, I love that shift. Um, and that shift to me is really important. Um, and that's what I was missing, that that's what Rust gives you. [00:56:23] Bryan: Rust forces you to think about your code as you write it, but as a result, you have an artifact that is much more supportable, much more sustainable, and much faster. Prefer to frontload cognitive load during development instead of at runtime [00:56:34] Jeremy: Yeah, it sounds like you would rather take the time during the development to think about these issues because whether it's garbage collection or it's error handling at runtime when you're trying to solve a problem, then it's much more difficult than having dealt with it to start with. [00:56:57] Bryan: Yeah, absolutely. I, and I just think that like, why also, like if it's software, if it's, again, if it's infrastructure software, I mean the kinda the question that you, you should have when you're writing software is how long is this software gonna live? How many people are gonna use this software? Uh, and if you are writing an operating system, the answer for this thing that you're gonna write, it's gonna live for a long time. [00:57:18] Bryan: Like, if we just look at plenty of aspects of the system that have been around for a, for decades, it's gonna live for a long time and many, many, many people are gonna use it. Why would we not expect people writing that software to have more cognitive load when they're writing it to give us something that's gonna be a better artifact? [00:57:38] Bryan: Now conversely, you're like, Hey, I kind of don't care about this. And like, I don't know, I'm just like, I wanna see if this whole thing works. I've got, I like, I'm just stringing this together. I don't like, no, the software like will be lucky if it survives until tonight, but then like, who cares? Yeah. Yeah. [00:57:52] Bryan: Gar garbage clock. You know, if you're prototyping something, whatever. And this is why you really do get like, you know, different choices, different technology choices, depending on the way that you wanna solve the problem at hand. And for the software that I wanna write, I do like that cognitive load that is upfront. With LLMs maybe you can get the benefit of the robust artifact with less cognitive load [00:58:10] Bryan: Um, and although I think, I think the thing that is really wild that is the twist that I don't think anyone really saw coming is that in a, in an LLM age. That like the cognitive load upfront almost needs an asterisk on it because so much of that can be assisted by an LLM. And now, I mean, I would like to believe, and maybe this is me being optimistic, that the the, in the LLM age, we will see, I mean, rust is a great fit for the LLMH because the LLM itself can get a lot of feedback about whether the software that's written is correct or not. [00:58:44] Bryan: Much more so than you can for other environments. [00:58:48] Jeremy: Yeah, that is a interesting point in that I think when people first started trying out the LLMs to code, it was really good at these maybe looser languages like Python or JavaScript, and initially wasn't so good at something like Rust. But it sounds like as that improves, if. It can write it then because of the rigor or the memory management or the error handling that the language is forcing you to do, it might actually end up being a better choice for people using LLMs. [00:59:27] Bryan: absolutely. I, it, it gives you more certainty in the artifact that you've delivered. I mean, you know a lot about a Rust program that compiles correctly. I mean, th there are certain classes of errors that you don't have, um, that you actually don't know on a C program or a GO program or a, a JavaScript program. [00:59:46] Bryan: I think that's gonna be really important. I think we are on the cusp. Maybe we've already seen it, this kind of great bifurcation in the software that we writ

BUFFALO, NY — February 27, 2026 — A new #research paper was #published in Volume 18 of Aging-US on February 6, 2026, titled “Causal effects of inflammation on long-term mortality: a Mendelian randomization study.” Led by Eliano P. Navarese from Department of Life and Health Sciences, Link Campus University and SIRIO MEDICINE Research Network, Nicolaus Copernicus University, who is also the corresponding author — the study used large-scale Mendelian randomization (MR) to test whether genetically proxied levels of inflammatory biomarkers causally influence long-term all-cause mortality. The analysis combined genome-wide association instruments from more than 750,000 individuals and used FinnGen mortality data (median follow-up 11.7 years) to assess effects on overall survival and major cardiovascular endpoints. Using robust MR methods and multiple sensitivity analyses, the authors report that genetically higher IL6R (soluble IL-6 receptor) levels were associated with reduced all-cause mortality (odds ratio per 1-SD increase: 0.95; 95% CI: 0.91–0.98), and with lower risk of atrial fibrillation, coronary artery disease, stroke, and lung cancer. By contrast, genetically higher IL6 levels were associated with increased mortality (OR 1.05; 95% CI: 1.02–1.08). No significant causal effects were observed for CRP or GDF15, suggesting those markers more likely reflect disease burden than drive it. “These results support IL6R antagonism as a potential strategy for cardiovascular disease prevention.” The authors emphasize that the opposing directions for IL6 and IL6R point to distinct biological mechanisms: IL6 likely promotes chronic pro-inflammatory states that increase cardiovascular risk, while higher circulating IL6R (reflecting altered receptor shedding and signaling) appears to dampen harmful IL6 activity at the vessel wall and myocardium, yielding cardiovascular protection. Sensitivity and cis-MR analyses reinforced the IL6R protective signal and showed minimal evidence of directional pleiotropy. Together, the genetic evidence aligns with clinical trial data for IL6R antagonists in other settings and supports further evaluation of IL6R-targeted strategies for cardiovascular prevention. The paper also notes important limitations and next steps. Analyses were restricted to individuals of European ancestry, so results require replication in other ancestries. Translating genetic evidence into preventive therapies will need careful clinical evaluation, long-term safety assessment, and trials designed for primary prevention in high-risk populations. The authors also call for additional mechanistic work to map how IL6/IL6R modulation alters vascular inflammation and downstream disease processes. DOI - https://doi.org/10.18632/aging.206352 Corresponding author - Eliano P. Navarese - elianonavarese@gmail.com Abstract video - https://www.youtube.com/watch?v=Br1A0jgU-4M Sign up for free Altmetric alerts about this article - https://aging.altmetric.com/details/email_updates?id=10.18632%2Faging.206352 Subscribe for free publication alerts from Aging - https://www.aging-us.com/subscribe-to-toc-alerts Keywords - aging, mendelian randomization, inflammatory biomarkers, mortality, cardiovascular disease To learn more about the journal, please visit https://www.Aging-US.com​​ and connect with us on social media at: Bluesky - https://bsky.app/profile/aging-us.bsky.social ResearchGate - https://www.researchgate.net/journal/Aging-1945-4589 X - https://twitter.com/AgingJrnl Facebook - https://www.facebook.com/AgingUS/ Instagram - https://www.instagram.com/agingjrnl/ LinkedIn - https://www.linkedin.com/company/aging/ Reddit - https://www.reddit.com/user/AgingUS/ Pinterest - https://www.pinterest.com/AgingUS/ YouTube - https://www.youtube.com/@Aging-US Spotify - https://open.spotify.com/show/1X4HQQgegjReaf6Mozn6Mc MEDIA@IMPACTJOURNALS.COM

In this episode, host Jason Pritchard sits down with Tomohiro Fukuzawa, Founder and CEO of SkyDrive, to reflect on a landmark year for the Japanese eVTOL OEM and what's next in 2026. Tomohiro shares how 2025 marked a breakthrough year for SkyDrive, with hundreds of successful flight tests, large-scale public demo flights and more than 400 pre-orders for its SD-05 aircraft. A major highlight last year was showcasing the aircraft at the World Expo in Osaka, where more than one million visitors saw the aircraft up close, many for the first time. The conversation dives into the technology behind SkyDrive's compact, 12-rotor multicopter design, purpose-built for rooftop operations and short urban hops, as well as its progress toward simultaneous certification with Japan's JCAB and the Federal Aviation Administration. Tomohiro also discusses strategic partnerships, including manufacturing collaboration with Suzuki and operational partnerships across Japan, Southeast Asia, India, and the U.S. From alleviating traffic congestion in cities like Jakarta to transporting organs for urgent medical procedures, the episode explores compelling real-world use cases that highlight the aircraft's potential impact. Looking ahead, 2026 will focus on certification milestones, global market expansion, and further public demonstration flights to accelerate adoption.

Made with Restream. Livestream on 30+ platforms at once via https://restream.ioWelcome to the Jesus Church in Watertown, South Dakota!Join us for service at: 500 14th Ave NW, Watertown, SD 57201 https://goo.gl/maps/WgUmDc1iH7jB8za98Our Service Times: Sunday Morning Service at 10:00 am CDT Sunday Main Service at 11:00 am CDT Wednesday Service at 7:00 pm CDTYou can find us online at: Website: https://jesuschurchsd.org/ Facebook: https://www.facebook.com/JesusChurchSD Instagram: https://www.instagram.com/jesuschurchsd/

The Danger of Hasty Decisions, Feb. 25, 2026 by Bible Baptist Church - Brookings, SD

Varför röstar så många på SD? Vem är riksdagens sista arbetare? Och vad händer med Ebba Busch om KD inte klarar riksdagsspärren? Politikrummet svarar på lyssnarnas frågor. I studion: Max V Karlsson, Anette Holmqvist, Anna Gullberg och Viktor Barth-Kron. Ansvarig utgivare: Klas Granström, Expressen AB.

Real Presence Live - Bishop Scott Bullock + Zena Hitz | Feb 25, 2026 by Catholic Diocese of Rapid City, SD

Catholic Daughters of America and their work in Rapid City, SD

Moderaterna leder regeringen men vem har fått igenom flest hjärtefrågor? Och hur mycket har småpartierna kompromissat? Vi utvärderar Tidöavtalet. Lyssna på alla avsnitt i Sveriges Radios app. Efter snart fyra år med Tidöavtalet är det dags att utvärdera samarbetet. Mycket pekar mot att samarbetspartiet Sverigedemokraterna är Tidögängets stora vinnare. De har fått igenom mycket av sin politik utan att behöva stå till svars för regeringens misstag. Jimmie Åkessons gäng har också fått större legitimitet bland borgliga väljare, men frågan är vad de väljarna tycker om SD:s krav att få sitta med i regeringen om högersidan vinner valet i höst?Enligt Tidögänget själva så kommer nästan alla avtalets punkter att hinna genomföras innan valet. Frågan är nu om det går att kalla Tidösamarbetet för lyckat? Om, har det i så falla varit lika gynnsamt för alla Tidögängets fyra partier? Har Liberalerna fått kompromissa mest och är allt verkligen frid och fröjd när det gäller relationen mellan Kristdemokraterna och Moderaterna? Och, vilka frågor blir viktigast om det kommer ett Tidöavtal 2.0?I avsnittet pratar vi om Pontus Mattsons dokumentär. Här hittar du den P1 Dokumentär Uppförsbacken – Moderaterna inför valet 2026Medverkande: Fredrik Furtenbach, politisk kommentator och Pontus Mattsson, politikreporter på Ekot.Programledare: Parisa HöglundProducent: Mattias Dellert

SD347 - Médicos Empreendedores, o que aprender com a história da Neurogram. Neste episódio, Dr. Lorenzo Tomé conversa com o neurologista e cofundador da Neurogram, Dr. Heitor Éttori, sobre sua trajetória profissional, desde o interesse por tecnologia até a decisão de empreender, passando pela criação da startup e pelo desafio de digitalizar uma especialidade ainda marcada por processos fragmentados.  O episódio mostra como a organização de dados é o primeiro passo para a inteligência artificial e como a interoperabilidade pode mudar o futuro da neurologia; reflete sobre o papel do médico empreendedor; a importância de sair da zona de conforto e o impacto que soluções tecnológicas bem estruturadas podem gerar na prática clínica, na pesquisa e na sustentabilidade dos sistemas de saúde. Entre na Comunidade SD no WhatsApp e tenha conteúdo gratuito todos os dias sobre negócios médicos. ACESSE O podcast Saúde Digital lhe ajuda a abrir a mente? Agora imagine como 3 dias de imersão com a gente pode impactar no seu negócio médico. A próxima Imersão SD já tem data: 20, 21 e 22 de março/2026. Garanta sua vaga com 10% de desconto na Imersão da SD Escola de Negócios Médicos. FAÇA CONTATO O Background do Heitor Médico Neurologista e neurofisiologista, Heitor gosta de tecnologia desde adolescente, o que contribui muito na sua área de atuação. Ele se interessou mais pela parte de dados da sua formação, trabalhando com neurofisiologia. Atuando por anos, ele identificou muito atritos de barreira tecnológica, o que o levou a se associar a uma neurocientista, a Dani de Mari, para trabalharem em pesquisa e IA dentro de sua startup, a Neurogram. Assista este episódio também em vídeo no YouTube no nosso canal Saúde Digital Podcast! Acesse os Episódios Anteriores! SD346 - Margem - Espiódio 1 SD345 - Consultório cheio não é sinônimo de Medicina bem-feita SD344 - Solidariedade no setor saúde: como os médicos podem gerar impacto real Music: Fantasy | Declan DP "Music © Copyright Declan DP 2018 - Present. https://license.declandp.info | License ID: DDP1590665"  

 #spiritualinfant #growup Are you growing spiritual as a believer? It's okay to start out as a spiritual baby, but it's not okay to stay that way. In this message by Pastor Alex Klimchuk, he talks about what staying a spiritual infant looks like and how to grow up. Ephesians 4:14-16, 1 Corinthians 3:1-2, Hebrews 5:12, 1 Peter 2:2, Acts 20:28-31 Join our online church! Hit subscribe, leave a comment, and let us know how this message spoke to you.   Please follow our websites for more! Website: http://www.newlifechurchsf.org/ Facebook: https://www.facebook.com/NewLifeSF/ Youtube: https://youtu.be/7Ig-qXgVAmE/ Pastor Alex Klimchuk New Life Church 500 S 1st Ave Sioux Falls, SD 57104

Stories we're following this morning at Progress Texas:With only six voting days remaining, Democratic early voting primary turnout continues far outpacing that of the Republicans: https://votehub.com/early-vote-tracker-tx-primary-26?state=tx-sen-26-dem...All of this is great fun for Dems, but there are reasons to maintain objectivity and focus: https://www.lonestarleft.com/p/is-something-happening-in-texas...Tarrant County Democratic Party Chair Dr. Allison Campolo credits new Texas Democratic Party Chair Kendall Scudder for meeting the moment: https://x.com/AllisonCampolo/status/2025669257993081275...Union involvement, including the opening victory of Taylor Rehmet in SD 9, is apparent this cycle: https://www.houstonchronicle.com/politics/texas/article/union-members-democrats-election-21358617.phpDemocratic leaders Gina Hinojosa, Joaquin Castro and Gina Ortiz Jones have all called for investigations of the ICE-involved shooting death of Ruben Ray Martinez last March - and the coverup that appears to have persisted since: https://www.texastribune.org/2026/02/20/texas-ice-fatal-shooting-south-padre-island/As the trial of protesters under terrorism charges framed as "Antifa" restarts today, Judge Mark Pittman is involving himself unusually in the jury selection process, possibly affecting the trial's eventual outcome: https://www.keranews.org/criminal-justice/2026-02-23/prairieland-detention-center-shooting-trial-antifa-jury-selection-judge-mark-pittman-fort-worth-texas?_amp=true...Trump DOJ prosecutors are highlighting black clothing, first aid kits, and encrypted Signal messaging as hallmarks of "Antifa" involvement, attempting to criminalize a decentralized ideology: https://www.texasobserver.org/antifa-scare-prairieland-19-trial-ice-detention/Early voting in the March primary is underway! Research your ballot here: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://apps.texastribune.org/features/2026/texas-march-2026-primary-ballot/?_bhlid=7d8eca3d2a16adc7c9b44185414443fa32be6d84⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠All about voting in Texas can be found at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠GoVoteTexas.org⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠. Progress Texas is expanding into both broadcast radio - including a new partnership with ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠KPFT-FM in Houston⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ - and into Spanish language media! Make a tax-deductible contribution to our radio initiative ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠HERE⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, and to our Spanish expansion ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠HERE⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠.Find our web store and other ways to support our important work at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://progresstexas.org⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠.

In His final hours before His crucifixion, Jesus demonstrates the humble, serving attitude He wants His followers to emulate.Pastor Garvon delivered this message on February 22, 2026 to Christ Church of Rapid City, SD.

Rise Podcast | March 1, 2026 - Second Sunday of Lent by Catholic Diocese of Rapid City, SD

Made with Restream. Livestream on 30+ platforms at once via https://restream.ioWelcome to the Jesus Church in Watertown, South Dakota!Join us for service at: 500 14th Ave NW, Watertown, SD 57201 https://goo.gl/maps/WgUmDc1iH7jB8za98Our Service Times: Sunday Morning Service at 10:00 am CDT Sunday Main Service at 11:00 am CDT Wednesday Service at 7:00 pm CDTYou can find us online at: Website: https://jesuschurchsd.org/ Facebook: https://www.facebook.com/JesusChurchSD Instagram: https://www.instagram.com/jesuschurchsd/

Fear in the Face of a Miracle by Bible Baptist Church - Brookings, SD

PreachTheWord by Bible Baptist Church - Brookings, SD

Party On The Pipes, St. Louis 2026 Start Name Artist Album Year Comments Two Hearts In Three Quarter Time Donna Parker Powerhouse [DPP 101-A] 1985 4-42 Wurlitzer, Paramount Music Palace, Indianapolis, IN 2:00 Almost Like Being In Love Ashley Miller Showtime [Command RS 881 SD] 1963 4-36 Wurlitzer, Paramount Theatre, New York; last commercial recording made on Paramount; ABC reissue in 1972 5:49 Why Did I Kiss That Girl? Bob Mitchell Bob Mitchell's Theatre Organ Favorites [Cassette] 4-30 Kimball, St. James' Episcopal Church, Wilshire Blvd., Los Angeles 7:58 Hopelessly Devoted To You David Ashby Concert: Wurlitzer Building, DeKalb, IL 5-65 Wurlitzer, Wurlitzer Building, DeKalb, IL; origin Our Lady of Victory Basilica, Lackawanna, NY; Proctors Theater, Troy, NY; Radio Station WCCO, Minneapolis, MN; recorded by Christopher Camalick 12:28 Whispering Arnold Loxam Blackpool Magic - Music For Dancing [CDGRS 1215] 1988 3-14 Wurlitzer, Tower Ballroom, Blackpool 16:46 I Only Have Eyes For You Joseph Seal The Mighty Wurlitzer [Castle CD] 3-12 Wurlitzer plus grand piano, Musical Museum, Brentford, Middx; ex-Regal, Kingston-upon-Thames (2445 seats); CD released 1992 20:41 Bring Your Kisses To Me Barry Baker For The Very First Time 1995 4-36 Wurlitzer, Ronald Wehmeier Residence, Cincinnati, OH 23:22 If There is Someone Lovelier Than You Bill Field Downey Ice Rink 27:00 I Love You (And Don't You Forget It) Steve Schlesing Paramount 341 30:03 Don't Take Your Love From Me Bob Ralston Concert: Keystone Oaks High School 2007-09-15 2007 3-19 Wurlitzer, Keystone Oaks High School, Dormont, PA 33:04 When Your Lover Has Gone Buddy Cole Buddy Cole Remembered [Doric DO 1421] 1980 3-27 Wurlitzer-Morton, Buddy Cole Studio, Gentry Ave., North Hollywood (3-17 Wurlitzer Ex United Artists Theatre, Los Angeles & 3-9 Robert Morton from Capitol Theatre, Marshalltown, Iowa) 36:46 Kiss Me, Honey Honey, Kiss Me Phil Kelsall Come Dancing At The Tower Ballroom [Grasmere GRCD 50] 1992 3-14 Wurlitzer, Tower Ballroom, Blackpool 38:49 When You Tell Me That You Love Me Nicholas Martin, Ian Darlington Wurlitzer Wonderland, Vol 3 [Sovereign SOV012CD] 1992 3-19 Wurlitzer, Turner's Musical Merry-Go-Round; Ian Darlington, Yamaha keyboard 43:21 Love Me Or Leave Me Stephen Vincent Yamaha EL90 with Paramount 450 2018 47:26 A Kiss In The Dark; I'm Confessin' (That I Love You) Dave Wickerham Party On The Pipes, St. Louis 2024 - Fox Theatre 2024 4-36 Wurlitzer, Fox Theatre, St. Louis, MO; Party On The Pipes 2024-04-15 57:37 Lover Charlie Balogh Spectacular! [OSP ERB 106] 2000 4-78 Wurlitzer, Organ Stop Pizza, Mesa AZ

A long overdue catch-up with friend of the pod Lukas Michel, who has spent the past three years building his career in golf design while also keeping his hand in competitive amateur golf.From helping to build 7 Mile Beach to working on a couple of course's in people's backyards, and testing his construction skills at Royal Perth, Lukas has had plenty to keep him busy.And in between all that, he's still holding his own in Aussie amateur golf.We put this podcast together with thanks to Matt Burns and his staff at Angus And Grace Go Golfing. Check their insta page and website for some of the best golf apparel on the planet. The latest Australian Golf Passport cap has almost sold out - grab one while you can.  And check out the latest refresh of the classic AAGGG shorts – perfect for summer golf!Thanks to Dean and everyone at Seed Golf – they continue to provide 20% off for Australian Golf Passport listeners via the code AGP at checkout. Get your hands on some premium golf balls at a super low price. Check their website for Seed merch too – caps, gloves and other goodies available, as well as the new model of the SD-02.Images related to this episode can be found on our Instagram page (@AustralianGolfPassport) and on Twitter / X (@AusGolfPassport). Images accompanied by attribution to their owners / creators.Podcast intro music - Nbhd Nick / Stop Playing With Me -Instrumental / courtesy of ⁠⁠⁠⁠⁠⁠⁠www.epidemicsound.com

Bishop's Book Club - February 2026 - Letters to a Young Catholic - George Weigel by Catholic Diocese of Rapid City, SD

Welcome to the Jesus Church in Watertown, South Dakota!Join us for service at: 500 14th Ave NW, Watertown, SD 57201 https://goo.gl/maps/WgUmDc1iH7jB8za98Our Service Times: Sunday Morning Service at 10:00 am CDT Sunday Main Service at 11:00 am CDT Wednesday Service at 7:00 pm CDTYou can find us online at: Website: https://jesuschurchsd.org/ Facebook: https://www.facebook.com/JesusChurchSD Instagram: https://www.instagram.com/jesuschurchsd/

Are we being left behind...Let's think about this for a moment.Architects have AutoCAD. Finance folks have Excel. Sales teams have Salesforce. The list goes on.But what do we as service design professionals have? If we're a bit cynical, you could say that often it's a wall of sticky notes (that the cleaners throw away at night).This brings up a deep and often unspoken insecurity in our field. Could it be that our work is seen as "fluffy" or "invisible" because we lack the "hard" tools that other departments have? That is the provocative question Maxe van Heeswijk brought to the Circle community recently. She challenged us to think about whether having "our own software" would help us claim our territory and be taken more seriously by stakeholders.But to which extent can a tool be the answer to our problems?Will Sharples joined the conversation with a different take. He argues that stakeholders don't actually care about our process or our "proper" service design tools, they just want their problems solved.So in this episode of Inside Service Design, we explore this tension between wanting to be "seen" as experts and the messy reality of getting work done in-house.This conversation is packed with spicy topics like:Whether having a dedicated tool makes you more legitimate, or does it just create new silos? Why our most important work is often the hardest to measure (and get budget for).A brutal method for stripping away busy work to focus on the assets that actually tell a story.And why you are "always selling" the value of service design, even years after you've been hired.So, if you've ever felt like you're doing important work... that nobody sees, this episode is for you.What do you feel is the service design tool at the moment? Do we even have one?Let me know, I'm really curious to hear your take!Be well, ~ Marc--- [ 1. GUIDE ] --- 00:00 Welcome to December Round Up01:00 Meet the Guests 04:00 From Physical Engineering to Digital Services 06:30 From Philosophy & Advertising to SD 10:15 Balancing Financial Goals vs. Trust 15:15 Securing Long-Term Funding 18:00 Why Patience is a Superpower 21:45 Thought Experiment26:30 Do We Need Professional Software?35:00 Is Design Too Democratized 44:15 Relationship Building is Slow Farming51:00 Pragmatism vs. The Design Bibles52:45 The Hidden Skill55:45 Navigating Company Politics59:30 Wrap-Up --- [ 2. LINKS ] --- https://www.linkedin.com/in/maxevanheeswijk/https://www.linkedin.com/in/will-sharples-85a40580/ --- [ 3. CIRCLE ] --- If you're an in-house service design professional and want to learn from the stories of your peers, take a look at the Circle, it might just be the thing you're looking for.Join our private community for in-house service design professionals:⁠https://servicedesignshow.com/circle--- [4. FIND THE SHOW ON] ---Youtube ~ https://go.servicedesignshow.com/inside-service-design-09-youtubeSpotify ~ https://go.servicedesignshow.com/inside-service-design-09-spotifyApple ~ https://go.servicedesignshow.com/inside-service-design-09-appleSnipd ~ https://go.servicedesignshow.com/inside-service-design-09-snipd

First off news of a new pork packing plant in Sioux Falls, SD. In addition we hit all the restrictions that are proposed to be funed in the new Farm Bill. Trent reminds you he wants NO FARM BILL.

Lolly Anderson of Sioux Falls, SD shares how cookies literally changed her life and led her to build a successful cottage food bakery and a digital product business that has done over $1M in salesGet full show notes and transcript here: https://forrager.com/podcast/161

#growth #healthybelievers #spiritualmaturity Healthy believers grow in three ways, they grow together in unity keeping us connected to Jesus. They grow up in maturity keeping us reliant on Jesus, and they grow deeper in their spiritual lives making us more like Jesus. We hope you enjoy this message by Pastor Andre Sushchik, on maturing in the faith. Ephesians 4:12-13, Hebrews 10:25, Matthew 20:28, 1 Corinthians 3:2 Don't forget to LIKE, COMMENT, & SUBSCRIBE for more biblical teachings!   Please follow our websites for more! Website: http://www.newlifechurchsf.org/ Facebook: https://www.facebook.com/NewLifeSF/ Youtube: https://youtu.be/7Ig-qXgVAmE/ Pastor Alex Klimchuk New Life Church 500 S 1st Ave Sioux Falls, SD 57104

Welcome everyone to the weekly San Diego Tech News!I'm Neal Bloom from Rising Tide Partners.My co-host in this episode is Fred Grier, journalist and author of The Business of San Diego substack. He covers the ins-and-outs of the startup world including breaking news, IPOs, fundraising rounds, and M&A through his newsletter.Before we dive in, we wanted to thank and ask our listeners to help us grow the show, leave a review and share with one other person who should be more plugged in with the SD Tech Scene. Thank you for the support and for helping us build the San Diego Startup Community!2/13Super Bowl ads worth mentioning:Rain Drop Agency. Manscape, TurboTax/Intuit, Poppi/Pepsi (local investors)SD Regional GDP/Economics report & event debriefUCSD leading NASA missionsBiotechIambic inks $1.7B deal with TakedaFormer DermTech CEO launched a new co.Neomorph Signed New Lease - 83,000 SFTTechNatilus Raised $28M in Fresh FundingHauler raised $16MOpaque raised, CEO is in SD, team is in SFDrata Opens SF officeCurated Events List – For full list – check The Social CoyoteAlliance Societal Impact - Family Office Summit March 15-16March Mingle March 25 This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit risingtidepartners.substack.com/subscribe

Derek Ramirez, the first ESD (Electronic Storage Device) K9 handler in his large Southern California agency, breaks down why electronic detection is the most challenging discipline in K9 work. Despite working in a major metro area with high demand, Derek's biggest hurdle wasn't finding work—it was educating decision-makers about what ESD dogs can do.Unlike narcotics or explosives with consistent target odors, electronic devices present massive challenges: thousands of manufacturers, constantly evolving technology, and micro-level odor signatures from SD cards and circuit components. Derek explains why handlers must become experts at reading subtle behavioral changes, why "interest" often matters more than full alerts, and how missing a hidden device can mean lost evidence in child exploitation cases.Key Topics:Why the nonprofit model creates handler limitationsESD vs. narcotics detection: fundamental differencesGeneralization training across device types and manufacturersReading dogs in low-odor scenariosWhy double-blind testing is essential for ESD teamsSearch methodology: how hiding spots affect successBuilding an ESD program from 5 to 16 dogsEssential for anyone considering ESD capabilities for event security, corporate environments, or law enforcement applications where electronic device detection matters.Derek Ramirez Background: First ESD K9 handler in major SoCal agency, built program from ground up, now manages growing unit of 16 dogs, works both ESD and narcotics detection.________________________________________