Podcasts about Fluid

The Moon pulls the tides of the ocean, but the question that won't let us go is simpler and stranger: what is it pulling in us? Melanie Reinhart joins me for a wide, grounded, moonlit ramble through lunar consciousness, astrology, and the body. We start with the moon as a constant companion for earthlings, a reliable rhythm of waxing and waning that can steady us when life feels politically, personally, and collectively turbulent.From there, we drop into somatic territory. We talk craniosacral therapy and the experience of “tides” in the system, from surface noise to the deeper mid tide and the long tide where time feels different. That becomes a living metaphor for the lunar path: not a heroic push to achieve, but a deepening that restores life force. We also bring in the Orphic Hymn to the Moon as an invocation practice and explore why reverence matters, not as an antique idea but as a way to relate to powers we still live inside.We get practical about moon phases too: the dark of the moon as a window for retreat, the full moon as an emotional amplifier, and how lunar timing can support better choices in work, conflict, learning, and creativity. We move into dreams as night-world digestion, why forcing interpretations can block the nourishment, and how light pollution mirrors a cultural forgetting of darkness, sleep, and imagination. If you care about the lunar cycle, dreamwork, depth psychology, the Jungian unconscious, or the roots of astrology in the night sky, this conversation is for you.*the above blurb was auto-generated by Buzzsprout's AI.Cover Artwork is The Fairy of the moon by Hermann Kaulbach (b&w) circa 1891 with a background extension from Canva.The Orphic Hymns including the one in this episode dedicated to the moon, and the invocation with Musaeus. It's the Thomas Taylor translation from 1792. Melanie's personal favourite.Find out more about Melanie and her work here. She has many great books including, famously, Chiron and the Healing Journey.Melanie reads from:Dane Rudhyar, The Lunation Cycle: A Key to the Understanding of Personality, from the section “The Pattern of the Lunation Cycle.”Rudolf Steiner, “In Pure Rays of Light” The verse appears in Esoteric Instructions (GA 264), with related commentary in an esoteric lesson of 5 December 1907 (GA 266/I).We discuss:Iain McGilchrist's book: The Master and his Emissary and associate right brain activity with the moon and left brain with Mercury.Jung, obviously, comes up a lot. I paraphrase this quotation from him.We also talk about the Tides in Biodynamic Craniosacral Therapy. If you'd like to know more about that the work of Franklyn Sills (may he rest in peace) is a good starting point.Clearing up the confusion of the 'far side' vs the 'dark side' of the moon we go to NASA...But always appreciative to Pink Floyd for creating such confusion but also such a cracking album.Melanie also mentions the Dark Sky Movement. Such important work. Have a look at darksky.org.We also acknowledge that "mentor" is not etymologically related to Mene or taurus. What we're engaging in during that section is a nice bit of folk etymology.Join the Newsletter!Podcast Musician: Marlia CoeurPlease consider becoming a Patron to support the show!Go to OnTheSoulsTerms.com for more.

In this episode of the Prolonged Field Care Podcast, Dennis sits down with Alex to break down a hot-off-the-press retrospective study from the Journal of the American College of Surgeons titled “Challenging Legacy Burn Resuscitation Paradigms with Fluid Restriction and Early Plasma.”They dismantle the decades-old “swell to get well” mentality and the classic Parkland formula that has led to dangerous fluid overload, massive edema, and compartment syndromes in burn patients. Instead, they explore a more physiologic approach using lower crystalloid volumes (starting at 2 mL/kg adjusted body weight) plus early fresh frozen plasma (FFP) for patients with larger burns.Key Takeaways:The Parkland formula (4 mL/kg/%TBSA) frequently causes massive over-resuscitation; the new restrictive approach delivered significantly less fluid while maintaining (and often improving) urine output.Capillary leak from glycocalyx damage is the real enemy in burn shock — plasma helps restore oncotic pressure and may reduce third-spacing.Titrate everything to urine output (target 0.3–0.5 mL/kg/hr). Formulas are only a starting point.Use adjusted body weight (ideal body weight + 0.4 × [actual – ideal]) instead of actual body weight for fluid calculations.Early plasma (1–2 units for >30% TBSA) showed a strong signal toward lower mortality, less ventilator days, and reduced renal failure in this study.The Joint Trauma System (JTS) Burn Care CPG still emphasizes early consultation with a burn center — phone a friend early.This approach has direct application for prolonged field care and austere environments, though the study is retrospective and should be implemented thoughtfully.Whether you're a special operations medic, flight paramedic, or managing burns in a resource-limited setting, this conversation will fundamentally change how you think about burn shock resuscitation.Resources:prolongedfieldcare.org (free downloads, worksheets & more)Follow @prolonged_field_care on InstagramJTS Burn Care CPG (CPG #12) – includes the excellent burn resuscitation worksheetChapters: 00:00 – Introduction: Why Burn Care Still Terrifies Experienced Medics03:09 – The Horrifying Reality of Over-Resuscitation (Edema Photos & Leaky Pipe Analogy)05:30 – Understanding the Glycocalyx and Why Crystalloid Leaks So Fast09:05 – The One-Third Rule Myth & Why Fluids Disappear in Sick Burn Patients11:14 – Parkland Formula Breakdown: History, Math & Its Biggest Flaw13:00 – The New Study: PICO, Methods & the Shift to 2 mL/kg + Early Plasma16:54 – Elevator Pitch: What This Paper Actually Found20:06 – Primary Results: Dramatically Less Fluid with the Restrictive Protocol21:24 – Urine Output Reality Check: Why the “Less Fluid” Group Still Hit Targets24:23 – Practical Protocol Breakdown: Who Gets 2 mL vs 3 mL + When to Give Plasma25:30 – Adjusted Body Weight Calculation Explained (and Why It Matters)27:26 – Titration to Urine Output is King – Stop Chasing Vitals29:55 – Dennis Rates the Evidence on the PFC Gestalt Scale30:38 – Why Plasma Makes Physiologic Sense (and Whole Blood May Be Next)35:30 – Study Limitations & Provider Bias Discussion37:30 – Can We Implement This in Prolonged Field Care Right Now?38:38 – JTS Burn Care CPG: The Burn Center Contact You Need to Save42:53 – Final Advice: Titrate Aggressively, Phone a Friend Early, Close the GapFor more content, go to ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠www.prolongedfieldcare.org⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Consider supporting us: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠patreon.com/ProlongedFieldCareCollective⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ or ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠www.lobocoffeeco.com/product-page/prolonged-field-care⁠⁠

Conviértete en miembro de este canal para disfrutar de ventajas:https://www.youtube.com/channel/UCxz7sBKlpcpyCiPwXupRymw/joinNo te pierdas de ningún contenido:https://isamarcial.com.mxhttps://instagram.com/isa_marcialhttps://twitter.com/isa_marcial/https://facebook.com/isaias.marcialhttps://twitch.tv/isa_marcialhttps://www.tiktok.com/@isa_marcialhttp://s.kw.ai/u/@isa_marcial/9LxCxlEHhttps://anchor.fm/isamarcialhttps://t.me/isa_marcialÍndice00:00 Intro y agradecimiento a miembros01:35 Motorola lanza de forma oficial el nuevo Edge 70 Max portando una batería de 7,100 mAh04:45 Samsung presenta Flex Titanium, una tecnología para reducir la arruga en pantallas plegables06:49 Renders filtrados revelan los tamaños y opciones de color del próximo Google Pixel Watch 508:43 Xiaomi introduce el REDMI Note 17 Pro con una batería masiva de 9,000 mAh y alta resistencia12:28 El nuevo REDMI Note 17 debutará en el mercado con una enorme pantalla de 7 pulgadas15:03 Samsung devela Fluid AI Design System, su futura filosofía de interfaz basada en tarjetas inteligentesSegundo canal: https://www.youtube.com/channel/UCbWK7ENMKOhJDPm0Tew0eOw/featuredNegocios: contacto@isamarcial.com.mxDisfruta de más contenido:

Kass and Syd are back to spill the tee on another wild week in golf! They break down Tom Kim's long-awaited win at the Genesis Scottish Open (we know what changed!), Scottie Scheffler's shocking first missed cut in nearly four years, and Steven Fisk's playoff victory at the ISCO Championship. Plus, they preview The Open Championship and share the story of one underdog who literally drove trucks before driving his way into the field. This week's guest is America Nicholas, who gives listeners a behind-the-scenes look at life alongside her husband, James Nicholas, as he chases his PGA TOUR dreams. From caddying during major qualifiers to celebrating emotional moments like making the cut at the U.S. Open, America shares what it's really like to be the ultimate golf wife, travel partner, hype woman, and occasional caddie.  Between hot takes, laughs, and a little harmless gossip, Kass and Syd cover everything you need to know before The Open. Grab your favorite drink, settle in, and get ready for another episode packed with birdies, bogeys, and all the little secrets. Follow us on Instagram and TikTok @birdielittlesecretspod.  

Date: July 9, 2026 Reference: The ARISE FLUIDS Investigators. Vasopressors or Fluids in Early Septic Shock. NEJM June 2026.  Guest Skeptic: Dr. Aaron Skolnik is an Assistant Professor of Emergency Medicine at the Mayo Clinic Alix School of Medicine and Vice Chair of Critical Care Medicine at Mayo Clinic Arizona.  He is board-certified in Emergency […] The post SGEM#514: Every Time You Go Away (and survive alive for 90 days) – Is It Due To A Restricted Fluid Strategy with Early Vasopressors? first appeared on The Skeptics Guide to Emergency Medicine.

Haldane first-grader pulled from pool The end of the school year is always a big day, but for a 6-year-old Cold Spring boy, it almost marked the end of his life. Haldane kindergarteners and first graders, along with their parents, celebrated the start of summer at a backyard pool party in the village on the afternoon of June 24, the Wednesday of the final week of school. Bethany Califano said that when she picked up her son, Georgie, from his first-grade classroom at Haldane Elementary that day, "he said everyone was talking about the party, and he really wanted to go." By 2 p.m., the party was in full swing; Georgie was standing by the shallow end of the in-ground pool. "He was waving at me, and I took a picture of him," Califano recalled. But things quickly became a blur for the mother of three. Moments later, while tending to her 1-year-old, she heard someone say, "Are you OK?" "I just knew they were talking about Georgie," she remembers thinking. Stephen Selman, one of the fathers at the party, noticed a boy at the bottom of the deep end of the pool. Because his arms were moving, Selman hesitated. Before he could remove his shoes, Stefanie Kean, a mom, dove in and brought Georgie to the surface. Selman helped her pull him out. Georgie was not breathing. His eyes were open, his lips and eyelids were blue, his skin was gray and his tongue was sticking out, Selman said. Selman, who was a lifeguard as a teenager and trained in CPR, gave Georgie rescue breaths. He was joined by two other dads with CPR training, Aaron Ernst and Aaron Bartkiw, and the three worked as a team, doing chest compressions and mouth-to-mouth. "I pinched his nose, pulled his head back and blew as hard as I could into him," said Bartkiw, also a former lifeguard. "He threw up all over me." Ernst said Georgie, after vomiting four times, started screaming. "It was the best scream that I've ever heard!" Ernst said. "I was just crying and praying; I've never prayed so hard in my whole life," Bethany Califano said. "I've never been so happy to hear him scream; I held him, and he didn't want to let go." After a call to 911, first responders arrived within minutes, Selman said. At that point, a frightened Georgie was talking coherently. He was taken by the Philipstown Volunteer Ambulance Corps, with his mother, to Mid-Hudson Hospital in Poughkeepsie. "We walked into about 20 doctors and nurses," she said. "It was pretty intense." After doctors examined Georgie, he was transferred to Maria Fareri Children's Hospital in Westchester County because of concerns about "secondary" or "delayed" drowning, which can occur up to 24 hours after a near drowning. Fluid builds in irritated and inflamed lungs, potentially causing respiratory failure. After his father, Bobby, and two sisters visited with Georgie, Bethany spent the night with him. He answered all the medical staff's questions quickly and alertly, allaying concerns about possible brain damage due to oxygen deprivation. "They kept giving him random prompts; in the middle of talking to me they'd ask him his favorite color, and he'd answer 'blue' immediately," his mother said. Georgie told his mother that he remembered standing in the shallow end and taking a step "and then it was deep," Bethany said. It isn't clear how long he was underwater. Children typically lose consciousness in 30 to 60 seconds, and brain damage can occur within four to six minutes. "I'm always watching the water, and every time I looked around there were two or three sets of eyes on that pool," Selman said. "There wasn't any neglect, but there is a lesson here about how quickly it can happen." Bethany said hospital staff emphasized that drowning doesn't usually occur as depicted on TV. A victim doesn't scream and splash. "It was so quick, so quiet," she said. "And he's a loud kid." After Georgie spent the night at the hospital, his classmates visited him via Zoom before he was released. Three days later, he spotted a children's inflatable...

Most people never start because they want something.Simon Squibb says that is the problem. Wanting is not enough. You have to need it.In this Founder Classic episode of Screw It Just DO It, Simon explains the single mindset shift that has driven every successful business he has built, invested in, or watched succeed. Turn your want into a need. And once you have done that, learn the three things that will multiply your luck: take more risk, know your destination, and never stop.Simon went from homeless at 15 to building and selling his agency Fluid to PwC. He has invested in 76 businesses. He has 23 million followers. And he believes that entrepreneurs, not politicians, are the ones who will fix the world.This is a tight, single-lesson episode. One idea. Applied properly, it changes everything.Key Takeaways• How to turn a want into a need and why it changes your behaviour immediately• The three-part formula for luck: risk, destination, and persistence• Why leaning into fear is a superpower, not a weakness• Why the harder I work, the luckier I get is actually not true

In this episode, Professor Paola Cinnella - Professor of Fluid Mechanics at Sorbonne University and Director of the Sorbonne Cluster for Artificial Intelligence (SCAI) - joins Neil to discuss her path from classical fluid mechanics and high-order numerical methods into uncertainty quantification, Bayesian methods, data-driven turbulence modeling and AI for Science.Paola has built a career at the intersection of CFD, compressible and turbulent flows, dense gas dynamics, uncertainty quantification, robust optimization and machine learning. We discuss academic careers, dense gases, RANS uncertainty, AirfRANS, surrogate modeling, scientific publishing, education in the age of AI, and the idea of the "centaur scientist".Key topicsFluid mechanics, CFD and high-order schemesDense gases, real-gas effects and expansion shockwavesUncertainty quantification and Bayesian methodsRANS turbulence-model uncertaintyAirfRANS and CFD datasets for machine learningTurbulence modeling vs surrogate modelingScientific publishing and ML-for-CFD standardsSCAI and AI for ScienceEducation, ChatGPT and centaur scientistsPapersQuantification of model uncertainty in RANS simulations: A review - Heng Xiao, Paola Cinnellahttps://doi.org/10.1016/j.paerosci.2018.10.001Discovery of Algebraic Reynolds-Stress Models Using Sparse Symbolic Regression - Martin Schmelzer, Richard P. Dwight, Paola Cinnellahttps://doi.org/10.1007/s10494-019-00089-xBayesian estimates of parameter variability in the k-epsilon turbulence model - W.N. Edeling, P. Cinnella, R.P. Dwight, H. Bijlhttps://doi.org/10.1016/j.jcp.2013.10.027AirfRANS: High Fidelity Computational Fluid Dynamics Dataset for Approximating Reynolds-Averaged Navier-Stokes Solutionshttps://arxiv.org/abs/2212.07564Data-driven turbulence modeling - Paola Cinnellahttps://arxiv.org/abs/2404.09074Direct numerical simulations of supersonic turbulent channel flows of dense gases - Luca Sciacovelli, Paola Cinnella, Xavier Gloerfelthttps://doi.org/10.1017/jfm.2017.237LinksPaola Cinnella named Director of SCAIhttps://scai.sorbonne-universite.fr/news/paola-cinnella-new-directorSCAIhttps://scai.sorbonne-universite.fr/Paola Cinnella - HAL publicationshttps://cv.hal.science/paola-cinnellaPaola Cinnella - Google Scholarhttps://scholar.google.com/citations?hl=fr&user=wBRA0JAAAAAJERCOFTAC SIG 54 - Machine Learning for Fluid Dynamicshttps://www.ercoftac.org/special_interest_groups/54-machine-learning-for-fluid-dynamics/master-of-science-internships/Chapters00:00 Podcast intro00:39 Introducing Prof. Paola Cinnella03:28 Conversation begins03:56 How Paola found fluid mechanics07:09 Moving from Italy to France08:37 High-order schemes and compressible flows09:30 Building an academic career12:06 Dense gases and uncertainty quantification15:16 Expansion shockwaves and real-gas effects19:17 Returning to Paris and academic mobility24:52 Academia, passion and persistence27:51 Bayesian methods and turbulence uncertainty30:47 Learning statistics across disciplines33:07 LearnFluidS, AirfRANS and CFD datasets36:33 Skepticism and physics in ML turbulence modeling40:41 Could ML lead to a universal turbulence model?42:59 Turbulence models, surrogate models and RANS45:03 Why LES alone cannot solve optimization47:15 Multi-fidelity modeling49:08 What Computers & Fluids looks for in ML-for-CFD papers54:05 CFD metrics vs machine-learning metrics57:13 Overselling, publication pressure and quality62:22 SCAI and AI for Science66:07 Cross-disciplinary AI for Science69:26 Education in the AI era72:44 Critical thinking and AI outputs78:15 AI as a companion, not a replacement81:42 AlphaFold and the future of discovery83:43 Training centaur scientists85:11 Closing thoughts

Un viaggio tra i suoni attuali ed i successi che hanno fatto la storia della House Music e dell'old style inglese

Discover how PRW Power is reinventing its performance engine components with smarter engineering, improved manufacturing, and race-proven technology.In this episode of EPARTRADE Race Industry Now, host Brad Gillie (SiriusXM Ch. 90, Late Shift) sits down with Cary Redman, Vice President & Chief Revenue Officer of PRW Power, for an in-depth technical discussion covering the company's latest innovations in high-performance engine components.Whether you're an engine builder, racer, machine shop, performance parts distributor, or serious enthusiast, this webinar dives into the engineering behind today's most critical engine components.Topics include:✅ New direct-oiling roller rocker arms✅ SFI-certified billet flexplates rated up to 3,500 HP✅ Modular flexplate designs that reduce inventory complexity✅ Fluid harmonic balancers for high-performance engines✅ Finite Element Analysis (FEA) and product development✅ Valvetrain durability under extreme spring pressures✅ Manufacturing quality control and product validation✅ Performance aftermarket trends and future product developmentLearn how PRW Power is combining advanced engineering, precision manufacturing, and real-world racing experience to develop reliable components for street performance, drag racing, circle track, road racing, endurance racing, and other high-horsepower applications.If you build engines, tune race cars, or simply enjoy learning the technology behind today's performance parts, this is an episode you won't want to miss.

Elle spoke to Ryan Berkeley on his latest EP release 'Fluid Echoes Dance.' The seven tracks delve into the depths of the ambient space, moving through a collection of distinct soundscapes. A single phrase expanding and then transfigured as each track draws to a close. Placing emphasis on analogue technology to create the work, this release is also available on a limited run of cassette tapes. Thanks to NZ On Air!

This month on the Bluegrass Beat, we look at Kentucky's Roadside Oral Fluid Testing Program with Office of Highway Safety Federal Program Specialist Matt McCoy and Traffic Safety Resource Prosecutor Jenny True Reed. Listen as we discuss what the program is, how the rollout took place, how testing works, the legal side, and how to get involved. To learn more about the Kentucky Office of Highway Safety, click here.For more information about the Kentucky Traffic Safety Resource Prosecutor, click here.…The Bluegrass Beat is recorded and produced by the Kentucky Department of Criminal Justice Training's Public Information Office, a proud member of Team Kentucky. Like what you hear? We appreciate everyone who takes the time to subscribe and rate this podcast.Have a suggestion? Email host Critley King-Smith at critley.kingsmith@ky.gov to share feedback. Music by Music for Creators from Pixabay.‍ ‍

David D. Friedman is an anarcho-capitalist economist. He is the author of The Machinery of Freedom, Future Imperfect, and several other books. Topics we discuss are well captured by the timestamps below.Watch on YouTube or X. Listen on Apple Podcasts, Spotify, or any other podcast platform. Follow me on X for updates on future episodes.Timestamps0:00 – The economics of longevity8:05 – Epigenetic reprogramming12:37 – Overpopulation and the “ultimate resource”16:33 – Fluid vs. crystallized intelligence, aging and political power20:46 – Cryonics24:35 – AI, open source, and the surveillance state28:29 – Zcash, privacy, and cryptocurrency41:12 – Taxes, government, and money supply50:27 – A poem about tyranny and benevolence56:42 – Education and its resistance to change1:05:42 – Argentina, Milei, and planning for an uncertain future This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.arjunkhemani.com

Send us Fan MailIn this double-blind randomized controlled trial from northern India, Nim and Adrianne review whether early hydrocortisone reduces 14-day all-cause mortality in preterm infants with fluid-refractory shock. The primary outcome showed no statistically significant difference between groups, though an 11 percent absolute reduction in mortality in the hydrocortisone group raised clinical interest. A major limitation was the high rate of open-label steroid crossover, with over 70 percent of both groups ultimately receiving hydrocortisone. The study highlights the difficulty of achieving equipoise when clinicians already believe strongly in a therapy, and raises important questions about study design in neonatal shock research.----Early hydrocortisone verses placebo in neonatal shock- a double blind Randomized controlled trial. Dudeja S, Saini SS, Sundaram V, Dutta S, Sachdeva N, Kumar P.J Perinatol. 2025 Mar;45(3):342-349. doi: 10.1038/s41372-025-02222-3. Epub 2025 Feb 13.PMID: 39948354 Clinical Trial.Support the showAs always, feel free to send us questions, comments, or suggestions to our email: nicupodcast@gmail.com. You can also contact the show through Instagram or Twitter, @nicupodcast. Or contact Ben and Daphna directly via their Twitter profiles: @drnicu and @doctordaphnamd. The papers discussed in today's episode are listed and timestamped on the webpage linked below.Enjoy!

What to listen for:“We are very good at selectively breeding, obviously to drive change in the shape, but not necessarily to drive performance.”Robin and Stacy continue their conversation with Dr. Lindsay Waldrop, a Chapman University fluid dynamicist who secured Navy funding to build the world's largest collection of micro-CT-scanned domestic dog skulls.Dr. Waldrop discusses why skull morphology offers no reliable prediction of scent detection performance. Breed shape, muzzle length, turbinate density… she says that none of it predicts which dogs will find the tin.She cites a study that scanned roughly 125 museum skulls, landmarked them geometrically, and mapped the variation against breeds with historically scent-focused versus bite-work roles.The answer was flat. No morphological feature sorted reliably by task. A Labrador has approximately the same mechanical bite leverage as a Malinois, yet nobody uses Labradors as patrol dogs, because that's behavior and genetics, not skull shape.And the pug? In a separate Nathan Hall study, the pug outperformed German shepherds on a basic odor detection task. The greyhounds couldn't be bothered to participate.Bloodhound ears sit in the same category. It's a story told often enough to feel true, but never actually tested. From a fluid dynamics standpoint, Stacy says she'd be shocked if those ear flaps were routing scent toward the nose in any meaningful way.The same applies to the claim (circulating on social media) that early scent initiation protocols increase the number of olfactory receptors in developing puppies. Specific, testable, evidence-free.It's important to distinguish science-based reasoning versus evidence-based claims. Dr. Waldrop's flow visualization work is science-based, informed by expertise, probably accurate, not publishable as proof. But claiming a puppy protocol rewires the olfactory system is an evidence-based claim with almost no data behind it. Key Topics:When the Dog Is Right and the Handler Is Wrong (01:36)The Pug That Beat the German Shepherd (12:54)What Skull Shape Actually Tells Us About Scent Work (14:02)A Navy-Funded Micro-CT Scan of 125 Dog Skulls (15:37)The Bloodhound Ear Story No One Has Tested (23:08)Science-Based vs. Evidence-Based: Why the Difference Matters (30:01)The Essential Oil Claim That Doesn't Hold Up to Physics (36:50)Can Nose Work Dogs Learn to Sniff Bigger? (46:37)Takeaways (49:20) Resources:Connect to Dr. Waldrop!:·      https://waldroplab.com/·      https://www.chapman.edu/our-faculty/lindsay-waldrop.aspx We want to hear from you:Check out the K9 Detection Collaborative FB page and comment on the episode post!K9Sensus Detection Dog Trainer AcademyK9Sensus Foundation can be found on Facebook and Instagram. We have a Trainer's Group on Facebook!Scentsabilities Nosework is also on Facebook. Here is a Facebook group you should join!You can follow us for notifications of upcoming episodes, find us at k9detectioncollaborative.com to enjoy the freebies, and tell your friends so you can keep the conversations going.And don't forget to check out the YouTube Channel!

Laura "LauraKBuzz" Kate Dale strikes a dastardly deal to portray The Baron, a harvestkin (goliath) barbarian.   STARRING - Laura Kate Dale: https://bsky.app/profile/laurakbuzz.bsky.social   SUPPORT - Patreon.com/LauraKBuzz   AUDIO - "Monster Beach Party" - Gio   COMMUNITY - Discord: https://discord.gg/YMU3qUH Wiki: https://dicefunk.ludo.au/

Check out the episode in its original version here : https://www.gdiy.fr/podcast/simon-squibb-vo/"C'est quoi ton rêve ?"Une simple question que Simon Squibb a posée à plus de 10 000 inconnus dans la rue, devant des banques alimentaires, ou dans des aéroports aux quatre coins du monde.Mais la plupart des gens se figent.Ce silence, c'est exactement le problème auquel Simon consacre sa vie depuis dix ans.À 15 ans, son père décède, sa mère le met à la porte et il quitte l'école.S'en suivent 8 semaines à dormir dans des cages d'escalier ou dans la rue qui réveillent en lui une envie d'entreprendre et de créer à chaque instant.Alors il frappe à la porte d'un inconnu et lui propose de tondre son jardin pour 200 livres par mois alors qu'il n'y connaît rien.Il crée, ferme et revend ensuite plusieurs entreprises jusqu'à Fluid, une agence créative qu'il développe pendant vingt ans depuis Hong Kong avant de la céder à PwC.Puis il prend sa retraite et alors qu'il a tout, il manque de se perdre.En 2019, il commence à aborder des inconnus dans la rue pour les questionner sur leur rêve.Aujourd'hui, Simon totalise 15 millions d'abonnés sur les réseaux. Il est le premier résultat sur TikTok quand on cherche "angel investor". Il a donné plus de 426 000 £ pour aider des gens à lancer leur entreprise et sa vidéo YouTube de deux heures sur la construction d'une marque a été vue 17 millions de fois.Pour Simon, le système éducatif est devenu obsolète le jour où Google est né donc il ne cherche pas à le changer, mais à construire une alternative.Dans cet épisode, Simon explique :Pourquoi TikTok a rendu les diplômes de marketing inutilesComment réveiller son cerveau d'entrepreneurPourquoi il a abandonné la politique pour changer le système éducatifComment trouver son rêve quand on est trop occupé à survivre pour y penserUn épisode pour tous ceux qui se sont déjà figés quand quelqu'un leur a demandé ce qu'ils voulaient vraiment.Vous pouvez suivre Simon sur Instagram et TikTok.TIMELINE:00:00:00 : La promesse des emplois qui n'existent pas00:13:21 : TikTok rend les diplômes de marketing inutiles00:19:28 : L'école vous prépare à l'échec dans le monde réel00:26:30 : Le muscle que l'école passe 10 ans à détruire00:36:46 : L'addiction au salaire ne construit pas un patrimoine00:48:45 : Offrir des formations à 10 millions01:00:52 : On ne peut pas rêver quand on fuit01:10:07 : Son meilleur échec à un million de dollars01:16:44 : L'argent ne change jamais ce que vous ressentez déjà01:23:06 : Personne ne s'est fait tout seul01:30:17 : Le mensonge du Brexit01:38:53 : La plupart des gens n'ont pas besoin d'argent01:45:49 : Seuls les rêves achètent la loyauté01:54:22 : Créer une entreprise pour réserver des hôtels avant InternetLes anciens épisodes de GDIY mentionnés : #527 - Céline Chung - Bao Family - La reine de la street food asiatique#525 - Joseph Lasserre - Groupe Doumer - Racheter des entreprises dont personne ne veut#507 - Laurent Alexandre - Vers la fin des études supérieures ?#487 - VO - Anton Osika - Lovable - Internet, Business, and AI: Nothing Will Ever Be the Same Again#487 - VF - Anton Osika - Lovable - Internet, Business et IA : rien ne sera jamais plus comme avant#327 - Laurent Alexandre - Auteur - ChatGPT & IA : "Dans 6 mois, il sera trop tard pour s'y intéresser"#165 - Laurent Alexandre - Doctissimo - La nécessité d'affirmer ses idéesNous avons parlé de :Université HarvardYC transforme des bâtisseurs en fondateurs redoutablesAnthropic AcademyLe biais du survivant30 ans de savoir entrepreneurial en 2h26Les jumelles MakaLes recommandations de lecture :What's Your Dream?, by Simon Squibb

Retrouvez l'épisode en version française ici : https://www.gdiy.fr/podcast/simon-squibb-vf/"What's your dream?"Four words that Simon Squibb has asked over 10,000 strangers on street corners, outside food banks, in airports all around the world.Most people freeze.That moment of blankness is exactly the problem he has spent the last decade trying to fix.Simon dropped out of school at 15 when his father died and his mother kicked him out.Then came eight weeks sleeping in stairwells and on the streets, which lit in him a relentless drive to build and create.So he knocked on a stranger's door, announced he was starting a gardening company, and charged £200 a month for a garden he didn't know how to tend.That business lasted eight months before the English winter killed it.After that, Simon builds, shuts down and resells several businesses, leading up to Fluid, a creative agency he grows for twenty years out of Hong Kong before handing it over to PwC.Then he retires, and despite having everything, he nearly loses himself.In 2019, he starts approaching strangers in the street to ask them about their dream.Today Simon has 15 million followers across platforms and he is the number one result on TikTok when you search "angel investor."He has given away over £426,000 to help people start businesses.His two-hour YouTube video on building a brand has been watched 17 million times.For Simon, the education system became obsolete the day Google was born, so he isn't trying to change it, he's building an alternative.In this conversation, Simon shares:Why TikTok made marketing degrees worthlessHow to wake up your entrepreneur's brainWhy he gave up on politics to try to change the education systemHow to find your dream when you're too busy surviving to think about itWhy your purpose in life comes from your painAn episode for anyone who's ever frozen when someone asked what they really wanted.You can follow Simon on Instagram and TikTok.TIMELINE:00:00:00 : They Were Promised Jobs That Don't Exist00:13:21 : TikTok Made Marketing Degrees Worthless00:19:28 : School Trains You to Fail in the Real World00:26:30 : The Muscle School Spends 10 Years Killing00:36:46 : The Salary Addiction Builds Nothing You Own00:48:45 : Giving Away a £10 Million Course for Free01:00:52 : You Can't Dream While Running From the Lion01:10:07 : The Million-Dollar Failure He's Grateful For01:16:44 : Money Won't Fix What You Already Feel01:23:06 : No One Is Self-Made01:30:17 : Brexit Was a Lie01:38:53 : Most People Don't Need Money01:45:49 : Only Dreams Can Buy Loyalty01:54:22 : Building a Hotel Booking Business Before the InternetWe referred to previous GDIY episodes : #527 - Céline Chung - Bao Family - La reine de la street food asiatique#525 - Joseph Lasserre - Groupe Doumer - Racheter des entreprises dont personne ne veut#507 - Laurent Alexandre - Vers la fin des études supérieures ?#487 - VO - Anton Osika - Lovable - Internet, Business, and AI: Nothing Will Ever Be the Same Again#487 - VF - Anton Osika - Lovable - Internet, Business et IA : rien ne sera jamais plus comme avant#327 - Laurent Alexandre - Auteur - ChatGPT & IA : "Dans 6 mois, il sera trop tard pour s'y intéresser"#165 - Laurent Alexandre - Doctissimo - La nécessité d'affirmer ses idéesA few recent episodes in English : #542 - VO - Yoni Assia - eToro - “AI Will Replace Most Traders in 18 Months”#513 - VO - Jesper Brodin - IKEA - 40 billion in revenue empire with no bank loan#500 - VO - Reid Hoffman - LinkedIn, Paypal - How to master humanity's most powerful invention#487 - VO - Anton Osika - Lovable - Internet, Business, and AI: Nothing Will Ever Be the Same Again#475 - VO - Shane Parrish - Farnam Street - Clear Thinking: The Decision-Making Expert#473 - VO - Brian Chesky - Airbnb - « We're just getting started »#452 - VO - Reid Hoffman - LinkedIn, Paypal - L'humanité 2.0 : Homo technicus plus qu'Homo sapiens#437 - James Dyson - Dyson - “Failure is more exciting than success”#431 - Sean Rad - Tinder - How the swipe fever took over the worldWe spoke about :Harvard UniversityYC turns builders into formidable foundersAnthropic AcademyThe Survivorship bias30 Years of Business Knowledge in 2hrs 26minsThe Maka TwinsReading Recommendations :What's Your Dream?, by Simon Squibb

Grammy-winning singer-songwriter Judith Hill returned to KNKX, showcasing her powerful take on modern blues in a captivating three-song set with her family band.

In this episode of The Sports Nutrition Playbook Podcast, Amy tackles a challenge every summer athlete faces: how to fuel your body when the heat kills your appetite. Amy breaks down why staying properly nourished matters even when you don't feel hungry, and shares practical, easy-to-implement strategies for getting the energy and recovery support your body needs through fluid-based fueling. Whether you're a high school athlete juggling double practices or a fitness enthusiast trying to keep performing at your best, you'll walk away with simple, actionable ideas to stay energized and recover stronger all summer long.To learn more visit @thesportsnutritionplaybook and thesportsnutritionplaybook.com.Check out our YouTube channel for more sports nutrition tips and tricks.  Have questions to ask our sports dietitians? email us at info@thesportsnutritionplaybook.com

In this episode, Professor Ricardo Vinuesa - Associate Chair for Research and Associate Professor of Aerospace Engineering at the University of Michigan - explores with Neil one of the biggest questions in modern fluid mechanics: can AI help us move beyond faster CFD and toward genuine autonomous scientific discovery? Drawing on his work at the intersection of turbulence, machine learning, explainable AI, reduced-order modeling, and flow control, Neil and Prof. Vineusa discusses the promise and limits of foundation models for fluids, why the right latent representations may matter more than simply scaling data, and how agentic AI systems could uncover physical mechanisms that humans might otherwise miss.Agentic Exploration of PDE Spaces using Latent Foundation Models for Parameterized Simulations — Abhijeet Vishwasrao et al.https://arxiv.org/abs/2604.09584The episode's most direct follow-up: multi-agent LLMs and latent foundation models autonomously explore flow physics in a tandem-cylinder setup.Enhancing computational fluid dynamics with machine learning — Ricardo Vinuesa, Steven L. Bruntonhttps://doi.org/10.1038/s43588-022-00264-7A concise roadmap for useful ML in CFD, from faster simulations and turbulence modelling to reduced-order models.Identifying regions of importance in wall-bounded turbulence through explainable deep learning — Andrés Cremades et al.https://doi.org/10.1038/s41467-024-47954-6Uses explainable AI to identify flow structures that matter for prediction and control, not just visually striking turbulence features.β-Variational autoencoders and transformers for reduced-order modelling of fluid flows — Alberto Solera-Rico et al.https://doi.org/10.1038/s41467-024-45578-4Shows how disentangled latent spaces, autoencoders, and transformers can support interpretable reduced-order models of nonlinear flows.Improving turbulence control through explainable deep learning — Miguel Beneitez et al.https://arxiv.org/abs/2504.02354Links explainable AI with deep reinforcement learning to target turbulence-sustaining mechanisms, with relevance for flow control, drag reduction, and energy efficiency.LinksVinuesaLabhttps://www.vinuesalab.com/Ricardo Vinuesa — University of Michigan Aerospace Engineeringhttps://aero.engin.umich.edu/people/ricardo-vinuesa/AI and ML for Fluid Dynamics course — Ricardo Vinuesa & Sergio Hoyashttps://www.flowthermolab.com/courses/ai-ml-for-fluids/VinuesaLab YouTube channelhttps://www.youtube.com/@VinuesaLabAI for Fluid Mechanics, Sustainability & XAI — Ricardo Vinuesahttps://www.youtube.com/watch?v=TOfwf4ffPnURicardo Vinuesa — Modelling and controlling turbulent flows through deep learninghttps://www.youtube.com/watch?v=0AOY_agZ8WMChapters00:00 Podcast Intro03:20 The Evolution of Foundation Models in Fluid Dynamics10:22 Understanding Explainable AI in Fluid Mechanics15:34 Challenges in Data Fidelity for Foundation Models20:29 Machine Learning vs. Reduced Order Modeling24:22 The Shift in Focus: Turbulence Modeling to Surrogate Models29:48 Exploring Agentic Systems for Scientific Discovery37:21 Exploring Latent Representations in Fluid Dynamics40:40 The Role of AI in Autonomous Discovery41:57 Bridging Fluid Mechanics and Computer Science45:28 Data-Driven vs Physics-Driven Models51:34 The Role of Academia in AI and Fluid Mechanics56:27 Optimization and Control in Machine Learning01:00:28 Future of AI in Fluid Dynamics: Beyond ChatGPT

Nick Hodge, Co-Owner of Digest Publishing and editor of Foundational Profits and Underground Alpha, joins us for our monthly longer-format discussion on assortment of messy macroeconomic factors, how he is navigating the bearish metals price trends, and portfolio management strategies in select gold, copper, lithium, rare earths, and uranium stocks.   We start off reviewing the mix of messy macroeconomic movers like: Market effects from the rising US Dollar – over 100 and climbing Rising short-term interest rates at the short-end of the yield curve due to Fed policy and Warsh's meeting and press conference last week; contrasted against flattening rates at the long-end of the curve Rising inflation readings, but wild fluctuations between monthly and quarterly trends Knock-on effects from geopolitics and continued uncertainty around the US/Iran MOU and supposed reopening of the Strait of Hormuz. Fluid situation causing increased volatility and impulsive reactions in both directions Sovereign debt loads and how rising rates will pressure global governments Capex investments in AI data-center build-outs are ongoing.      The majority of the macro news has been a headwind to the commodities sector, but it is a messy situation because there are positive tailwinds present at the same time.  We discussed the pullback in oil prices, in precious metals prices, and copper prices and how Nick is navigating these markets. After touching the hot stove in a few instances, (after taking a nibble at the GDXJ only to see it fall a bit further), he is not interested in trying to pick a bottom or “catch the falling knife” in most commodities. Nick would prefer to see a sustainable real low put in for each respective commodity, like the PMs or Oil or Copper, and for a new uptrend to assert itself before deploying any more new capital. He is more than happy to have a certain portfolio weighting to cash to wait out any more near-term market corrections, and is willing to deploy more cash once the turn higher is more clear.   With regards to portfolio management, Nick is concentrating his portfolio into less positions and fortifying his highest conviction investment stories with compelling catalysts.  He is more likely to trim or sell positions that were picked up based on bullish metals price direction, or as a result of spinouts, or where he is not as confident on the assets or management teams.  He recommends investors take inventory of what they own, and the investment case for why they own it and only be in the higher conviction stories.   Nick highlighted Gladiator Metals Corp. (TSXV: GLAD) (OTCQB: GDTRF) for copper, and Revival Gold Inc. (TSXV: RVG) (OTCQX: RVLGF) for gold as 2 positions he has held for some time in his portfolio that he is happy to hold through any more volatility and even add to in their weighting.  He points out that both companies have solid management teams and projects, and both still have a lot of drilling on tap for this season as a catalyst. There are also gold stocks on his watchlist that are becoming more attractive during this ongoing sector correction, like Mayfair Gold Corp. (TSXV: MFG) (NYSE American: MINE), Tiernan Gold Corp. (TSXV : TNGD), or copper stocks like Amerigo Resources Ltd. (TSX: ARG) (OTCQX: ARREF) or Ero Copper Corp. (TSX: ERO, NYSE: ERO) that he is keeping a close eye on for a potential future position.   When reviewing where he is seeing the most strength in the commodities sector, Nick highlights the Critical Minerals as having been the most resilient. He points out that the Global X Lithium and Battery ETF (NYSE: LIT) and lithium developers like Q2 Metals Corp. (TSX.V: QTWO) (OTCQB: QUEXF) and PMET Resources Inc. (TSX: PMET) (ASX: PMT) (OTCQX: PMETF) have held up better than most other metals or resource stocks. Nick highlights the ongoing direct investment and policy initiatives into the rare earths processors, separators, recyclers, noting prior investments into USA Rare Earth, Inc. (Nasdaq: USAR), MP Materials (NYSE: MP), or the news this week where Energy Fuels Inc. (NYSE American: UUUU) (TSX: EFR) was approved for a $725 million financing commitment from the Department of War, U.S. Office of Strategic Capital, to support infrastructure and capacity to process rare earth elements and other critical materials. Uranium and nuclear stocks have also been soft ever since the big move up in January, but Nick outlined the continued support from many sovereign nations to invest in both their nuclear infrastructure as well as uranium miners with projects of significance. Cameco Corporation (TSX: CCO; NYSE: CCJ) announced yesterday a conditional commitment for a loan package of up to US$17.5 billion by the US Department of Energy's (DOE) Office of Energy Dominance Financing (EDF) to reenergize the large-scale nuclear reactor supply chain, drive down costs, and accelerate the deployment of AP1000 reactors in the US and globally.   Click here to follow Nick's analysis and publications over at Digest Publishing     For more market commentary & interview summaries, subscribe to our Substacks:   The KE Report: https://kereport.substack.com/ Shad's resource market commentary: https://excelsiorprosperity.substack.com/     Investment disclaimer: This content is for informational and educational purposes only and does not constitute investment advice, an offer, or a solicitation to buy or sell any security. Investing in equities and commodities involves risk, including the possible loss of principal. Do your own research and consult a licensed financial advisor before making any investment decisions. Guests and hosts may own shares in companies mentioned.    

What if everything you've been told about AI and your job is wrong? Sharon Gai sits down with host and producer Dr. Tom Dutta on The Quiet Warrior Show, and this one is going to stop you in your tracks. Sharon moved to Vancouver at age 7 from China, not speaking a word of English. She hid her dumpling lunches so the other kids wouldn't stare. She hid who she was. Then, 18 years later, she moved back to China for work, only to be told she wasn't Chinese enough. Between those two worlds she forged a philosophy she calls Culture Fluid, and a career at the cutting edge of global AI and commerce. A TEDx speaker. A Wiley author. Named Top AI Voice 2026. Sharon has advised Walmart, LVMH, Coca-Cola, and heads of state. And she's here to say what most people are afraid to: AI doesn't replace jobs. It slices off tasks. And knowing the difference is everything. In this episode you'll discover: ✓  Why being different is your biggest AI advantage, not your liability ✓  How to split your job into 'AI tasks' and 'human tasks' right now ✓  The 'Busy Bee to Beekeeper' shift that changes how leaders think about productivity ✓  What the West is still missing from China's AI playbook ✓  Why doing more with less starts with clarity, not hustle Sharon's new book HOW TO DO MORE WITH LESS (Wiley, March 2026) is out now. This is the conversation the whole world needs. www.sharongai.com #TheQuietWarriorShow #SharonGai #AILeadership #FutureOfWork #DoMoreWithLess #AILiteracy #Leadership #Podcast #Livestream #CultureFluid #Innovation #BusinessStrategy #DrTomDutta #FinalCutPremiere

That softer jaw and heavier under-eye you meet in the mirror most mornings usually isn't new fat, and it isn't only sagging. A lot of it is fluid that pooled overnight in a system that only really moves when you do. In this episode, I  break down why your face puffs while you sleep, what menopause has to do with it, and the honest truth about what facial massage can and can't do. Then I  give  you the one move most people get backwards, so the rest of your routine finally works. In this episode: Why your lymphatic system has no central pump like your heart, and what that means for your morning face The difference between a real morning depuff and the "facelift" claims that oversell it Where to start, and it isn't your face, so fluid actually has somewhere to drain The full step-by-step routine, plus a diagram of the actual moves, is in this week's article inside the Skin Scholar Society.  Listen above, then go grab the guide.   I'm a Menopause Skin Specialist and Master Esthetician with 16+ years of hands-on practice, helping women recalibrate their skincare to restore firmness, clarity, and glow without Botox or fillers.  

The show was released late because Erick had a birthday party to attend and Zack had to finish up some work. Erick talks about the new game he's playing and why he thinks people shouldn't buy it on the Nintendo Switch 2. He also talks about a Juneteenth BBQ where a woman had a nip slip. Who is Dan Castellaneta, and what does he have to do with Aladdin? You'll find out on the show. Plus, Zack has some fluid in his knee, which Erick has actually touched. All of that and so much more on the show today.

In this second part of our investigation into the Tao Te Ching, we cover some of the many, many, many shapes its teachings have been bent into over the last 2,500 years—from the inspiration for an alchemy-and-sex cult that accidentally invented gunpowder to the basis for the most popular science fiction film franchise in history. Join us as we discuss Chinese demon hunters, bad management advice, and—yes—Star Wars.Need a transcript of this episode, or want to see the reading list? Click here. Thanks for listening! Don't forget to share us with friends. Hosted on Acast. See acast.com/privacy for more information.

Dive into an moving audio journey with Chris Tennant's latest DJ mix on the EarTheater podcast. The seamless blend of clubby drum programming and big melodic synths sets the stage. The inviting 120 BPM, which gradually builds to a vibrant 123 BPM over three captivating hours, runs circles around songs at 130. Fluid mixes of beats and impeccable harmonic transitions coupled with a curated selection of high-quality tracks, this mix promises an immersive experience of edgy and lush sounds keeping listeners engaged from start to finish. Perfect for both avid house enthusiasts and casual listeners, Chris Tennant's sets are drifts and dances wrapped in the dynamics of an underground club. Track List 01 - Fede Archdale & Alex Ellis - Opacarophile (Gerardo Portilla Remix) 02 - Andrea Cassino & Lio Q - Asante (Andrés Moris Remix) 03 - Solis [US] - Cosec (Extended Mix) 04 - Redspace & Shell Robinson - Fusion 05 - RYAN (CU) - Sounds Of Gaia 06 - PAUL (AR) - White Dust (Dhany G Remix) 07 - Chris Doppler - Future Is Our Past 08 - Meeting Molly & Maze 28 - Oceans in Between (GMJ & Matter Remix) 09 - Jadon Fonka - Reminder (Albano Bastonero Remix) 10 - Agustin Delsoglio - Rampage 11 - Kebin Van Reeken - Liminal (Sam Hopgood Remix) 12 - Marsh - Warrior (Extended Mix) 13 - Erich LH & Valen Gonzalez - On Board 14 - Hakan Ozurun - Got the Mood 15 - Forty Cats - Savant (Anton Make Remix) 16 - Kamilo Sanclemente - Mistika 17 - Loveclub & Domingo + - Firmament (Fran Garay Remix) 18 - Juan Lagisquet - Night Finds You 19 - Enzo Paradiso - Rhythm Reverie 20 - KAZKO - Last Runner (YANIQ Remix) 21 - K Loveski, Ewan Rill & Bondarev - Proxymates 22 - Luciano Scheffer - J's Odyssey (Weird Sounding Dude Remix) 23 - Donny Carr - Mysterium 24 - Ruben Karapetyan & Maze 28 - Cosmic Dot (Yonsh Remix) 25 - Francesco Pico - State Of The Wave (K Loveski Remix) 26 - Thomas Ferell - Willow 27 - Solis [US] - Solstice (Extended Mix) 28 - Ewan Rill - Mental Activity (ISMAIL.M Remix) 29 - Agustin Pietrocola - Endeavor 30 - Mika D - Tokyo 31 - Rod V - Floating Lotus (Papai ACCI Attila Remix) 32 - Ramiro Alvarez - Muktab 33 - ISMAIL.M & Redspace - Talk About Style 34 - The Prodigy - Smack My Bitch Up (Maze 28 Remix) 35 - ISMAIL.M & Redspace - Avenue   #FedeArchdale #AlexEllis #GerardoPortilla #AndreaCassino #LioQ AndrésMoris #ShellRobinson #RYAN #PAUL #DhanyG #ChrisDoppler #MeetingMolly #GMJ #Matter #JadonFonka #AlbanoBastonero #AgustinDelsoglio #KebinVanReeken #SamHopgood #Marsh #ErichLH #ValenGonzalez #HakanOzurun #FortyCats #AntonMake #KamiloSanclemente #Loveclub #Domingo #FranGaray #JuanLagisquet #EnzoParadiso #KAZKO #YANIQ #KLoveski #Bondarev #LucianoScheffer #WeirdSoundingDude #DonnyCarr #RubenKarapetyan #Yonsh #FrancescoPico #KLoveski #ThomasFerell #Solis #EwanRill #AgustinPietrocola #MikaD #RodV #PapaiACCIAttila #RamiroAlvarez #TheProdigy #Mazz28 #ISMAILM & #Redspace #christennant

Hiten Sonpal is the CEO of RISE Robotics and a robotics industry veteran with over 20 years of experience. He helped generate $2B in revenue and ship 9M units at iRobot, and now leads the company behind the Beltdraulic system, a patented fluid-free alternative to traditional hydraulics that operates at 75% efficiency versus hydraulics' 25%. In this episode, Hiten covers the technology, the commercialization strategy, the defense contracts, and the crowdfunding playbook that made RISE Robotics the #1 Regulation Crowdfunding campaign of 2025 according to KingsCrowd. What We Cover: - How robots deployed at Ground Zero on 9/11 shaped Hiten's entire career - Why hydraulic systems are 75% inefficient and what that costs operators every day - How Beltdraulic enables drive-by-wire control and fully autonomous heavy machinery - Predictive maintenance: how RISE monitors belt health in real time to eliminate unplanned downtime - The MVP framework: desirability, feasibility, and viability for deep tech products - Why mid-market customers beat enterprise for early-stage startups - The Tesla stepping stone strategy: start niche, expand to adjacent markets - RISE's first commercial customer in oil and gas and the Air Force $3M contract extension - How RiISE raised $5M from over 2,500 investors and was named the #1 Reg CF campaign of 2025 by KingsCrowd - The three-channel marketing approach: retargeting, new investor acquisition, and earned media - Why crowdfunding investors are also becoming product customers - What founders need to know before launching a Reg CF campaign Connect with Hiten Sonpal: LinkedIn: https://www.linkedin.com/in/hiten-sonpal/ RISE Robotics: https://www.riserobotics.com/ Invest: https://invest.riserobotics.com/ Subscribe to Test. Optimize. Scale. for weekly conversations on growth marketing, business strategy, and what is actually working right now. CHAPTER TIMESTAMPS 0:00 - Intro 1:30 - How Hiten got into robotics as a kid in India 4:00 - 9/11 and the robots deployed at Ground Zero 7:00 - iRobot: $2B in revenue and 9M units shipped 9:00 - Why robotics companies fail to make it from research to commercialization 11:00 - The MVP framework: desirability, feasibility, and viability 15:00 - Why mid-market beats enterprise for deep tech startups 18:00 - The hydraulics problem: 25% efficiency and unpredictable failures 22:00 - How Beltdraulic works and why it enables machine autonomy 25:30 - Fluid-free: predictive maintenance and the end of unplanned downtime 28:00 - Rise's first commercial customer in oil and gas 31:00 - Scaling strategy: the Tesla stepping stone approach 34:00 - The Air Force $3M contract extension for munitions handling 36:30 - Why Rise chose Reg CF over traditional VC 40:00 - Testing the waters: $800K in interest in Q4 2024 42:00 - The $5M raise: what worked and what surprised them 45:00 - The three marketing channels behind the campaign 49:00 - 20x ROAS and how they think about spend efficiency 52:00 - What founders should do before launching a crowdfunding campaign 55:00 - Where to find Rise Robotics and how to invest

The Fat One is back with a recap of the first part of his weekend which included sportsball, quiz programs, a HoBO movie, a gentleman caller, Friday at Fatty's, some Nip shenanigans and much more. Happy National Lobster Day.

In this Fluid Power Forum episode, NFPA host Eric Lanke shares a recorded NFPA webinar on advancing technologies for controls, IoT, and data—featuring Scanreco Director of Sales Andy Gray.   Gray explains how Scanreco's professional radio remote controls serve OEMs and system integrators for mobile and industrial machinery in harsh environments, translating operator intent into hydraulic actuator motion from simple on/off to highly proportional control to improve safety, precision, and productivity. Discussion covers operating at safer distances, integrating camera feedback and Human Machine Interface, HMI, information onto remotes, and the growing role of assisted operation and autonomy across applications like agriculture, forklifts, drilling, demolition, forestry, and fire equipment.   Gray describes field research with operators, integration via CAN and software tools, OEM preference for open integration ecosystems, and progress to unify remote control, advanced displays, and onboard computing amid trends of digitalization, electrification, automation, and usability. Subscribe to the Fluid Power Forum today to never miss an episode. The podcast is available on all of your favorite podcast platforms, including YouTube, Apple Podcasts, Spotify, and iHeart Radio.   Connect with our host, Eric Lanke, at elanke@nfpa.com.   Connect with our guest, Andy Gray, at andy.gray@scanreco.com.   Learn more about the company at www.scanreco.com.   Find and share more interesting fluid power technologies and unique applications using #onlyfluidpowercan and follow podcast and other fluid power industry-related updates at @TheNFPA.   #FluidPowerForum #Controls #Safety #Autonomy #CID

"

In this CIRS Group Podcast episode, Jacie and Barbara cover phase four of the Shoemaker Protocol, focused on restoring normal metabolic function after biotoxin elimination. They explain that this phase may include supporting detox pathways for “normal” toxins and heavy metals (e.g., daily bowel movements, B vitamins, methylation support, sauna or hot baths, lymphatic techniques, and using binders like charcoal or clay for inorganic toxins), addressing androgen/sex hormone imbalance linked to low MSH (including signs of low testosterone or estrogen dominance, supplementing DHEA), and correcting fluid/electrolyte balance via ADH regulation (symptoms like thirst, frequent urination, nocturia, and static shocks). They discuss electrolyte options, a DIY recipe, and provider-monitored desmopressin if needed, and note this phase can also involve investigating other lingering issues or co-infections before moving to phase five. For more information and support, join us at https://thecirsgroup.com TIMESTAMPS 00:00 Welcome to Phase Four 01:00 The purpose of repairing damage done by CIRS 03:14 Detox Pathways basics 05:33 Binders for heavy metals 07:05 Androgen & hormone balance 09:40 Fluid and Electrolyte Issues: ADH/Osmolality 12:21 Electrolyte options 14:12 Desmopressin reset explained 15:41 Tidying up and co-infections 17:22 Next Phase and wrap up For more information and support, join us at https://thecirsgroup.com LINKS MENTIONED IN THE EPISODE: Electrolyte caps Barbara uses: https://redmond.life/products/re-lyte-hydration-support-plus-caps LMNT Recipe (check FAQ): https://drinklmnt.com/pages/ingredients Order Jacie's book! The 30 Day Carnivore Bootcamp: https://a.co/d/7MgHrRs The CIRS Group: Support Community: https://thecirsgroup.com Instagram: https://www.instagram.com/thecirsgroup/ Find Jacie for carnivore, lifestyle and limbic resources: Jacie's book on the Carnivore diet!  https://a.co/d/8ZKCqz0 Instagram: https://www.instagram.com/ladycarnivory YouTube: https://www.youtube.com/@LadyCarnivory Blog: https://www.ladycarnivory.com/ Find Barbara for business/finance tips and coaching: Website: https://www.actlikebarbara.com/ Instagram: https://www.instagram.com/actlikebarbara/ YouTube: https://www.youtube.com/@actlikebarbara Jacie is a Shoemaker certified Proficiency Partner, NASM certified nutrition coach, author, and carnivore recipe developer determined to share the life changing information of carnivore and CIRS to anyone who will listen. Barbara is a business and fitness coach, CIRS and ADHD advocate, writer, speaker, and a big fan of health and freedom. Together, they co-founded The CIRS Group, an online support community to help people that are struggling with their CIRS diagnosis and treatment.

This week, Jason Howell and Jeff Jarvis dig into Apple's biggest AI reveal yet: the company rebuilt Apple Intelligence on top of Google Gemini, Siri AI finally works according to early reviewers, and the EU is blocked from getting any of it. Anthropic released Fable 5, the first publicly available model in its Mythos frontier tier, safety-locked and twice the price of Opus. OpenAI filed its S-1 and is planning a super app.Also in this episode: A Trump administration equity stake in OpenAI, Perplexity targeting a 2028 IPO, Google paying SpaceX $920 million a month for compute, AI agents now accounting for more web traffic than humans, and the debate over AI degrees. New episodes every Wednesday at aiinside.show. Note: Time codes subject to change depending on dynamic ad insertion by the distributor. CHAPTERS: 0:00 - Start 0:02:51 - Apple Reveals New AI Architecture Built Around Google Gemini Models 0:23:47 - Anthropic Releases New ‘Mythos-Class' Model to General Public With Guardrails 0:40:24 - OpenAI confidentially filed for an offering, but said ‘it may be a while' before it goes public 0:46:05 - Trump administration, OpenAI discussing possible government stake in the AI startup 0:50:07 - Google to pay SpaceX $920 million a month for compute capacity at xAI data centers 0:50:53 - Colleges Are Building A.I. Degrees, Hoping Students Will Come 0:56:43 - AI Agents Now Generate More Web Traffic Than Humans 1:00:38 - Fluid, natural voice translation with Gemini 3.5 Live Translate 1:02:41 - Meta Launches ‘Workforce Academy' to Train Workers to Build Data Centers 1:03:27 - Amazon launches AI image generator to narrow search queries 1:07:13 - Cancer vaccines using AI gets research funding 1:08:26 - Landmark German ruling declares Google's AI Overviews are Google's own words and makes it liable for false answers Hosts: Jason Howell and Jeff Jarvis Download and subscribe to AI Inside in audio and video: https://aiinside.show/  Support the podcast on Patreon for special perks: https://www.patreon.com/aiinsideshow. You'll get ad-free episodes, members-only Discord, T-shirts and stickers you love, and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Learn more about your ad choices. Visit megaphone.fm/adchoices

White letters on a tire sidewall look like a small detail, but they carry decades of meaning. That bold ring of text became a calling card of 1960s and 1970s muscle cars, street racing, and the idea that performance should look like performance. We break down why the trend exploded, why it's showing up again in today's vintage and retro builds, and how branding and aesthetics can steer a tire choice just as much as the practical stuff. We also get specific about how white letter tires are actually made. Raised white lettering is built into the tire during manufacturing, using white rubber that's molded and cured with the rest of the sidewall for long-term durability. Painted white lettering is applied after the tire is cured, which opens the door for customization but usually demands more maintenance. From smart cleaning habits to avoiding harsh chemicals, we talk about what keeps letters bright, what makes them yellow, and the modern options like temporary decals or having a pro apply custom sidewall designs. Then we take a fun left turn through automotive history, from the Going-to-the-Sun Road and early road-trip culture to landmark moments tied to Healey, Porsche, Le Mans, and Ford's “win on Sunday, sell on Monday” era. We follow that with Houston driving destinations featuring hidden speakeasies, and wrap with Don's drive of the 2026 GMC Sierra EV Denali Max Range, including range expectations, tech choices, weight, and what EV mileage testing really means on the road. If you like practical car talk mixed with history and real-world opinions, subscribe, share this with a friend, and leave us a review with your take: raised white letters, painted letters, or no letters at all?Be sure to subscribe for more In Wheel Time Car Talk!The Lupe' Tortilla RestaurantsLupe Tortilla in Katy, Texas Gulf Coast Auto ShieldPaint protection, tint, and more!Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.----  ----- Want more In Wheel Time car talk any time?     In Wheel Time is now available on Audacy!  Just go to Audacy.com/InWheelTime where ever you are.-----   -----Be sure to subscribe on your favorite podcast provider for the next episode of In Wheel Time Podcast and check out our live multiplatform broadcast every Saturday, 10a - 12nCT simulcasting on Audacy, YouTube, Facebook, Twitter, Twitch and InWheelTime.com.In Wheel Time Podcast can be heard on you mobile device from providers such as:Apple Podcasts, Amazon Music Podcast, Spotify, SiriusXM Podcast, iHeartRadio podcast, TuneIn + Alexa, Podcast Addict, Castro, Castbox, YouTube Podcast and more on your mobile device.Follow InWheelTime.com for the latest updates!Twitter: https://twitter.com/InWheelTimeInstagram: https://www.instagram.com/inwheeltime/https://www.youtube.com/inwheeltimehttps://www.Facebook.com/InWheelTimeFor more information about In Wheel Time Podcast, email us at info@inwheeltime.com

In this high-signal PFC Podcast episode, Dennis sits down with Dr. John Wightman — former 24th Special Operations Wing Surgeon, emergency physician, and one of the world's leading experts on blast injuries. Drawing from decades of clinical, combat, and academic experience (including co-authoring a seminal paper on blast injuries just before 9/11 and multiple combat deployments), Dr. Wightman breaks down the unique pathophysiology, recognition, and prolonged field care management of blast lung injury — the often-hidden threat that can kill even when penetrating trauma doesn't.From the physics of the supersonic pressure wave to practical field decisions on tension pneumothorax, ventilation strategies, fluid management, and avoiding air embolism, this is essential listening for medics, operators, and anyone preparing for large-scale combat operations, urban warfare, or confined-space blasts.Key Takeaways:Primary blast lung injury is caused by the blast wave itself — not fragments or being thrown — and creates unique pulmonary contusions, air leaks, and arterial air emboli risks.Most significant blast lung develops within the first 1–6 hours; subtle dyspnea on exertion can be an early warning.MARCH priorities still rule — aggressively rule out (or treat) tension pneumothorax, even bilaterally, before assuming blast lung.Positive pressure ventilation can worsen outcomes (especially air embolism risk) — use judiciously; CPAP or PEEP may be better bridges when possible.PAO₂/FiO₂ ratio (or SpO₂ on room air) helps stratify severity and predict need for advanced support.Tympanic membrane rupture proves blast exposure but is not required for blast lung.Fluid management must be careful — permissive hypotension may be dangerous in blast lung + shock.Don't forget occult blast bowel injury — delayed perforation is real (up to 8 days).Whether you're running a team in Ukraine-style trench warfare, preparing for mass casualty events, or just want to stay on the bleeding edge of combat medicine, this episode delivers critical, actionable knowledge.Chapters:00:43 - John Wightman Introduction: 32 Years as Air Force EM Physician & Blast Injury Expert02:54 - What Is Blast Lung? Defining Primary vs Secondary, Tertiary, Quaternary & Collateral Injuries05:23 - The Physics of the Blast Wave: Overpressure, Stress Waves & Alveolar Damage09:50 - Pathophysiology: Pulmonary Contusion, Pneumothorax, Air Embolism & Traumatic Pseudocysts12:30 - Timelines: When Does Blast Lung Declare Itself? (Israeli & Combat Data)15:56 - Epidemiology: Confined Spaces, Buses, Buildings vs Open-Air Blasts23:12 - Field Diagnosis & MARCH Priorities — Tension Pneumothorax First28:30 - Advanced Assessment: P/F Ratio, Ultrasound Findings, SpO₂ Guidance35:55 - Ventilation Strategies: When to Intubate, CPAP/PEEP, Lung Protective Settings41:18 - Oxygenation Goals, Fluid Management & Permissive Hypotension Risks52:16 - Air Embolism Management & Patient Positioning56:12 - Other Critical Considerations: Blast Bowel Injury, TM Rupture, Resource Triage01:04:36 - Final Thoughts & Key Advice for Deploying MedicsFor more content, go to ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠www.prolongedfieldcare.org⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Consider supporting us: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠patreon.com/ProlongedFieldCareCollective⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ or ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠www.lobocoffeeco.com/product-page/prolonged-field-care⁠

Pockets Malone lives in a small town with big secrets, but the most pressing issue today - one foretold in Pockets' own horoscope article - is the sudden failure of almost every clock in town. The only working clock? The Grandfathers Clock at the center of town. That's meant to be plural. Thanks for listening!

Throughout this series we have pulled apart science by science to show how the Aryan hypothesis works. We have now reached the continent of the unconscious, with it, neurology, psychiatry and psychology etc. We are getting ready to storm the castle that is Carl Gustav Jung.We start with the "invention of the self" during the Sturm & Drang, Goethe‘s urtype and degeneration theory, introduce Schelling as the first irrationalist continue with the forbidden secrets Mesmer revealed about the ancien régime and the role he played in the french revolution.We also present and I read in full a forgotten fragment of Hölderlin, Marx' favorite poet and best friend of Hegel, who it would seem, before the Nazis deemed it a fake, first coined the term Communism, 236 years ago at a small chapel on a romantic hill at the feet of the alps.

What does ancient wisdom actually look like in everyday life? In this episode, we sit with Verse 15 of the Tao Te Ching to explore why the modern obsession with constant action and "mountain-top" achievements might be keeping us stuck. Through Lao Tzu's imagery of crossing thin ice, becoming like a valley, and letting muddy water settle, we learn that sometimes the most powerful action we can take is to step back, put the glass down, and let clarity happen on its own.Grab a warm drink, take a deep breath, and let's slow down for a few minutes.**** Intro: The mistake of "stirring the pot" when we need answers.**** The Verse: A slow reading of Verse 15.**** The Ice: Why walking on thin ice demands an absolute honesty that can't be faked.**** The Valley: Shifting away from a culture that worships the mountain, and finding the quiet power of receptivity.**** Mud & Water: Why a glass of muddy water doesn't need to be fixed—it just needs to be set down.**** Releasing the Grip: Living in the present instead of waiting for life to "finally arrive."The ancient Masters were profound and subtle.Their wisdom was unfathomable.There is no way to describe it; all we can describe is their appearance. They were careful as someone crossing an iced-over stream.Alert as a warrior in enemy territory.Courteous as a guest.Fluid as melting ice.Shapable as a block of wood.Receptive as a valley.Clear as a glass of water.Do you have the patience to wait till your mud settles and the water is clear?Can you remain unmoving till the right action arises by itself?The Master doesn't seek fulfillment.Not seeking, not expecting, she is present, and can welcome all things.Where in your life right now are you desperately stirring the water? What would happen if you just set the glass down and let gravity do its work?If you enjoyed this episode, please consider subscribing, leaving a review, or sharing it with someone who needs a few quiet minutes today.In This Episode, We Discuss:The Verse: Verse Fifteen (The Ancient Masters)A Question to Carry With You This Week:

With an abundance of therapeutic options for managing diabetic macular edema (DME), what patient characteristics inform your treatment decisions? Does the number of loading doses influence long-term macular fluid outcomes? How are you managing insurance-mandated step-therapy in your patients? In today's episode, host Dr. Jay Sridhar invites Drs. Durga Borkar and Carl Danzig to share how they've integrated new anti-VEGF therapies into clinical practice. For all episodes or to claim CME credit for selected episodes, visit www.aao.org/podcasts.

Take the 2026 AI Engineering Survey and get >$2k in credits and AIE WF tickets!This was recorded before Railway suffered a major GCP outage on May 19, despite being a multi-AZ, multi-zone mesh ring, with HA fiber interconnects between their Metal GCP AWS, because workload discoverability was unintentionally still tied to GCP. All has been resolved with a post-mortem.Railway did not start as an AI infrastructure company.It was founded in 2020 years before agents became the default way people thought about deploying software. Jake Cooper, formerly at Bloomberg and Uber, started Railway with a simple obsession: the activation energy to ship something to production should be near zero. Push code, get a URL, iterate. No Docker files, no Kubernetes manifests, no Ansible scripts stacked on Ansible scripts.For years, this was a slow grind. Railway spent its first 18 months hand-acquiring its first 100 users with Jake personally greeting every Discord signup on a second monitor.Today, Railway has raised $124m and is growing very fast. A 35-person team supports 3 million users, adding roughly 100,000 signups a week. Their bare metal data centers have a 3-month payback period vs. renting in the cloud, with 70% margins funding aggressive cloud bursting when needed. The servers they own have actually appreciated in value as RAM prices have climbed basically meaning the value of their hardware now exceeds the capital they've raised.From rebuilding Railway's network overlay over a weekend to moving the vast majority of workloads onto its own bare metal data centers, Jake Cooper is trying to build a new cloud for an agent-native world. In this episode, Railway's founder and “conductor” joins swyx and Alessio to unpack why the next era of software infrastructure is not just “Heroku but newer,” what agents need that humans did not, and why the old deployment loop of Git, PRs, CI/CD, and static cloud resources may be heading for a rewrite.We go deep on Railway's infrastructure stack: own-metal data centers, three-month cloud payback periods, cloud bursting, data center debt, Railpack, Nixpacks, Temporal, feature flags, Central Station, content-addressable filesystems, agent-safe production forks, and why the CLI may become more important than the canvas in an agent world. Jake also shares the founder journey behind Railway, how the company survived losing $500K/month, why it now serves millions of users with only 35 people, and why he believes the pull request is dying.We discuss:* How Railway went from a slow six-year grind to adding 100,000 users a week* How Railway thinks about agents as the next dominant software species* Why agents need version control, observability, compute, storage, and orchestration at 1000x scale* The economics of Railway's own-metal data centers and three-month payback* How Railway uses cloud bursting while scaling its own infrastructure* Why data center debt can be a better tool than venture debt for infra startups* Central Station, Railway's internal system for clustering customer feedback and incidents* Why responsible disclosure and over-communication matter for platforms* Why feature flags, progressive rollouts, and shadow traffic are essential for agents* Temporal's strengths, pain points, and why workflows matter for agents* Railpack, Nixpacks, Nix, and lazy-loaded content-addressable filesystems* Why “cattle, not pets” may change if you can clone the pets* Why Railway is building a new cloud from scratch instead of copying hyperscalers* The solo founder path, focus, writing, and how Jake thinks about company buildingRailway:* Website: https://railway.com/* X: https://x.com/RailwayJake Cooper:* LinkedIn: https://www.linkedin.com/in/thejakecooper/* X: https://x.com/JustJakeTimestamps00:00:00 Introduction: What Is Railway?00:02:07 Jake's Path to Railway00:06:13 Railway's Six-Year Growth Story00:08:52 Rebuilding the Business After the Free Tier00:11:17 Agents as the Next Software Platform00:13:29 Railway's Infrastructure Philosophy00:15:42 Bare Metal, Cloud Economics, and the Compute Crunch00:17:22 Cloud Bursting and Five-Cloud Networking00:20:20 Data Center Debt and Infra Financing00:23:31 Data Centers in Space00:25:24 What Agents Need From Infrastructure00:28:24 CLIs, Canvas, and Agent-Native UX00:35:15 Central Station, Incidents, and Responsible Disclosure00:40:30 Safe Rollouts, SRE Agents, and Production Forks00:45:00 AI SRE, Specs, Code, and Tests00:48:24 Self-Replicating Infrastructure and the New Serverless00:53:18 Heroku, Temporal, and Workflow Engines01:04:07 Railpack, Nixpacks, and Lazy-Loaded Filesystems01:06:01 Coding Agents, Token Spend, and Roadmap Acceleration01:10:56 The Pull Request Is Dying01:12:28 Feature Flags and the Agent-Era SDLC01:16:15 Cattle, Pets, and Cloning Machines01:19:29 Solo Founder Lessons01:24:12 Focus, GPUs, and Building a New Cloud01:28:20 Closing ThoughtsTranscriptAlessio [00:00:00]: Hey, everyone. Welcome to the Latent Space Podcast. This is Alessio, founder of Kernel Labs, and I'm joined by Swyx, editor of Latent Space.Swyx [00:00:10]: Hey, hey, hey. Today we're in the studio with Jake Cooper of Railway.Alessio [00:00:14]: Conductor of Railway.Swyx [00:00:15]: Conductor at Railway. Yeah.Alessio [00:00:16]: Choo-choo.Swyx [00:00:17]: Do you actually have that anywhere, like on your business card?Jake [00:00:20]: We call some of our volunteer moderators conductors. I don't have a business card. We're not that big yet. At some point I will. I got handed a nice business card from the Supermicro folks, and I was like, “Damn, this is pretty official.”Swyx [00:00:30]: Business cards are coming back.Jake [00:00:32]: They're cool. They're hip. The conductor thing is good. We're trying to figure out what we want to call each other internally. Some people think it's super cringe and say, “You don't need a name for people internally.” Some people want to call each other something. We still don't have a really good one.Jake [00:00:55]: We've got New Railcrews, Trainiacs. Nothing has stuck yet.Swyx [00:01:00]: I like Trainiac. Trainiac sounds good. Railwayians. For those who don't know, what is Railway? Let's give people a crisp definition up front.Jake [00:01:09]: Railway is the easiest way to ship anything. You go to the canvas, or you talk with Claude, and you say, “Deploy a Postgres instance, deploy my GitHub repository, run this code,” and you're off to the races.Swyx [00:01:22]: You've got a nice animation on the landing page.Jake [00:01:24]: Thank you. None of my work, by the way. They don't let me touch the design stuff anymore.Jake [00:01:25]: We want to make it trivially easy not just to deploy things, but to evolve applications over time. Most tooling right now stacks entropy on top of entropy: Docker, Kubernetes, Ansible scripts, and all these other things. If we can version all of your software and keep track of all the changes, then we can make it trivial to clone environments, fork into a parallel universe, get copies of production data, get copies of any services, make changes, validate them, and collapse them back in without reproducing everything across a staging environment.The Railway Origin Story: From Uber Systems to a New CloudSwyx [00:02:07]: I was looking at your background: Bloomberg, Uber. Nothing immediately stands out as, “This guy is going to found the next great platform as a service.” What prepared you for Railway?Jake [00:02:21]: It was curiosity to keep going deeper. I started out on front-end stuff, working on Wolfram Mathematica and porting it over. Then I briefly moved to Bloomberg, then toward Uber and distributed systems, taking the Jump Bikes systems and moving them to a distributed system built on top of Cadence, the pre-Temporal Temporal.Swyx [00:02:44]: Which, by the way, I'm happy to talk about, pros and cons.Jake [00:02:48]: Totally.Swyx [00:02:51]: But let's do the Railway story.Jake [00:02:52]: It has been a continual step of wanting an experience. Whether it's walking up to a bike, unlocking it, and having it work frictionlessly, or something else, the depth required to make that happen follows from the experience. A lot of the work I do, and a lot of the team does, is in service of that experience. We fundamentally don't care how deep we have to go. We will swim to the bottom of the swimming pool to get the experience.Jake [00:03:17]: I don't have a physics PhD. I did an EECS degree. It has always been about figuring out the next step: how do we get there? That's what led to starting Railway for that experience and then moving all the way to bare metal data centers. I was adding patches to the kernel this week to get the experience there because I can see how much better it can be.Swyx [00:03:49]: Other patches to the Linux kernel this week?Jake [00:03:51]: Yeah. Not upstream. Our fork.Swyx [00:03:52]: That's a flex. Railpack? No, this is different. This is the OS on top of Railpack?Jake [00:03:57]: No, this is an actual kernel patch. It's always literally: what do we have to do to get that experience? Then figure it out. Anything is figureoutable.Swyx [00:04:10]: Would you send the patch upstream, or does it not fit other use cases?Jake [00:04:13]: Maybe. We have to work out the experience internally. It has to do with the storage layer we're building for some of the agentic stuff. Maybe it'll be useful upstream, but it's deeply useful for us internally.Open Source, Forks, and Non-Deterministic VersioningSwyx [00:04:29]: You mentioned open source before. How do you think about starting from open source, and then coding agents letting you do a lot more from forks of it?Jake [00:04:38]: GitHub's original sin is that it's almost a series of broken pointers. You have this thing, then you clone it, and now you've lost the whole upstream. How do we make it trivial for people to modify really small pieces of it?Jake [00:04:51]: We think of Git in a discrete sense: I've either made a change and merged upstream, or I haven't. What would it look like if it were percentage-based, a little more non-deterministic, or a stream of changes that users traverse as a percentage rolled out in general and then rolled all the way up?Jake [00:05:13]: We have the open-source kickback program and let you deploy templates because we want to make it trivial for people to version these shards over time. It solves a large problem around authentication, authorization, and security. NPM has a way to define, “Don't take any new packages.” The ideal end state is that you roll out progressively to users with the minimum impact zone and continue rolling up. JPMorgan should probably be the last one on the patch line, for all our sakes, because our money and livelihoods are there.Jake [00:05:53]: It's okay if Johnny Vibe Coder gets a broken patch because there's so much entropy in the system that the rubber has to meet the road at some point. You have to test at varying levels.The Long Grind: First Users, Free Tier, and Making the Business WorkSwyx [00:06:13]: I wanted to pull up this glorious chart, which is your usage or number of daily signups?Jake [00:06:22]: Daily signups, I think.Swyx [00:06:24]: You started six years ago. It was a slow grind, and now you're on a rocket ship. You say, “Don't doubt your fight and don't quit.” Maybe pick out certain points that were key inflections for the company.Jake [00:06:40]: At the start, it's about getting your first 100 users, hell or high water. We had a website and a support link. The support link was the Discord channel. I had notifications on with two monitors: the monitor I was working on and the other monitor with Discord. If anybody came in, I was immediately like, “Hey, how's it going?” It was rare, so getting those first 100 users to come back was the start.Jake [00:07:14]: Then you build a consultancy factory because users want all these things. You have to go back to the board and ask, “What is the actual product offering I want to build on top of this?”Jake [00:07:28]: VCs want charts that always go up and to the right, but in reality you don't necessarily want charts that look like that. For us, there have been periods of expansion where we add features to test use cases, and periods of compaction where we ask, “If the experience we have is good, how do we make it significantly better?” Maybe we strip out features that don't fit our ICP anymore.Jake [00:07:57]: The boom from 2022 to 2023 came from the free tier. Everybody under the sun was using it.Swyx [00:08:09]: A lot of Reddit bots and Discord bots.Jake [00:08:12]: And crypto miners. When you build an open product on the internet where anybody can sign up, the internet is a horrible place with so many things. You go through periods of asking, “How do I reach as many people as possible?” Then, “How do I fit the exact use case for the people who really matter and are really excited about this specific thing?”Jake [00:08:39]: Then there was a two-year period of making the actual business work. During the free-tier era, we were losing about half a million dollars a month.Swyx [00:08:59]: On a $20 million bank account.Jake [00:09:02]: On a $20 million bank account with maybe $50,000 a month in revenue. That's a horrible business. I don't know how anybody invested. But you have to go through it and say, “We have an experience people love, but the business has to work.”Jake [00:09:17]: There are two schools of thought. You can run the horrible business all the way up with bad margins, or you can go back and make it work. We've always wanted a super lean team. We're 35 people right now. It's very small.Swyx [00:09:36]: Supporting three million already?Jake [00:09:38]: Yeah. We're adding 100,000 users a week right now, so it's growing fast. We don't want to add headcount for the sake of headcount or throw bodies at problems. We want to build systems. It's hard to build systems during expansion because you're adding things to the system because people are asking for them or things are breaking.Jake [00:10:00]: We had to cut off the free users for a little while, rebuild the business, and make sure it worked. We want to reach as many people as possible because software is important. It's become difficult to create things in the physical world, so it's important to make it easy for people to build in the virtual world and have access to creation. But there are legs to that journey.Jake [00:10:30]: You can see divots in the charts. If you follow between 2025 and 2026, it's either summer or winter. People go on holiday with family.Swyx [00:10:50]: It affects that much?Jake [00:10:51]: Yeah. It's kind of B2C and kind of B2B. People are shipping constantly, then they stop. Our activation curve now shows more people activating on weekdays because we have more business users, so it smooths out over time.Agents as the New Interface to DeploymentSwyx [00:11:17]: Was there a point where you started prioritizing AI development or agent development?Jake [00:11:24]: We've prioritized agentic as a top-of-funnel thing. Over the last six months, we've deeply prioritized agentic as a mechanism to build and deploy things because we believe the curve is so steep and that is how people will build and deploy software.Jake [00:11:42]: It almost fundamentally doesn't matter whether this is dot-com or not because we're all on the internet anyway. If agents are going to deploy a bunch of things and we hit an inference wall at some point, we'll fix those problems. The dominant species over the next 10 years is that we've moved from assembly to C to C++ to JavaScript to words. You're going to need to close that loop.Swyx [00:12:13]: When you say this is dot-com, did you mean buying the domain, or the general case?Jake [00:12:17]: I mean the dot-com era, when companies had a huge run-up because people understood the internet was important. Then they hit bottlenecks, fundamental laws of physics, math didn't work, and everybody came back down to earth. But it didn't matter because the internet became so impactful. If you operate on a long enough time horizon, you should build these things anyway because you can see where it's going.Jake [00:12:45]: That's where I think a lot of agent stuff is. You get to a point where you're running thousands of agents in parallel. What is the inference cost? What is the compute cost? How do you make that efficient? How do you coordinate all this? We have issues coordinating humans; we don't even have good tooling for that. Now we have to figure out how to get agents to coordinate, safely version changes, and know when to raise their hand for someone to intervene. Otherwise it becomes an interrupt factory.Railway's Infrastructure Thesis: Network, Compute, Storage, and MetalSwyx [00:13:19]: Let's go right into the technical side. What are the core infrastructure or architectural beliefs of Railway that allow you to do what you do?Jake [00:13:29]: The primitives matter a lot for us. We need network, compute, storage, and orchestration around it. You need control over a lot of those things. We've talked a lot about how we don't really use Kubernetes because we want higher-order control to place workloads in very specific places.Jake [00:13:48]: The reason is that you have to be very efficient with agents: memory reuse and all these other things, or you're going to massively blow up your cost structure. Being able to rack and stack your own servers and build your own metal unlocks performance and cost. Experiences where you're running 1,000 agents in parallel are not massively cost prohibitive.Jake [00:14:13]: Token use and compute use are blowing up. Over time, those things have to get a lot more efficient. You can get a lot of margin to make those experiences solid by building your own metal. That's all in service of offering a differentiated experience to as many people as humanly possible.Swyx [00:14:51]: You have a data center in Singapore.Jake [00:14:53]: Yeah. We have two in every other region now. In Singapore, we're adding a second one in Q3.Swyx [00:14:58]: What's it like? I've never built a data center. Do you go to Equinix and say, “I want some slots?”Jake [00:15:05]: Yeah. Equinix. You basically go and say, “I want power and I want a cage.” They say, “Great, here's what it's going to be.” You rent the cage for a period of time, fill it with racks and servers, and hook up internet to it. That's all the pieces.Swyx [00:15:36]: Then you handle everything else.Jake [00:15:37]: You handle everything else.Swyx [00:15:39]: What's the math versus clouds doing it for you?Jake [00:15:43]: If we rented in the cloud, our payback period when we go to metal is about three months.Swyx [00:15:50]: Which is crazy.Jake [00:15:51]: It's nuts. That's four years of depreciated hardware. You're going to see a lot of this compute crunch because hyperscalers are buying up a lot of stuff. We're working directly with OEMs, resellers, and people building these machines: Supermicro, Dell, and others.Jake [00:16:11]: Upstream, there's a bunch of supply pressure. When we raised our last round, between deploying capital for servers and now, the amount of money we've raised is less than the amount of money we have in the bank plus the value of the servers because the servers have appreciated as RAM has gone up. It's nuts how valuable hardware has become.Jake [00:16:50]: If you look at hyperscalers, they deployed around $80 billion of capital expenditures this year, and next year will be more. That's a massive infrastructure build-out. You look at that and think it's crazy that they're spending way more than the Manhattan Project. But if every person is going to run dozens or hundreds of agents in parallel, you have no conceptual idea how much compute is required to make that experience happen, even if you're deeply efficient and sharing resources. And that doesn't even count inference.Swyx [00:17:22]: How do you plan the build-out? The growth chart is so vertical. Are you usually at 100% utilization as soon as racks are live? How far ahead are you planning?Jake [00:17:33]: We still maintain cloud presence for bursting. We work with AWS, GCP, and a few other clouds. We can rent, and then the moment we get space or power, we compact those workloads off the cloud. We started on the clouds, then built a system to migrate to our own metal. There's nothing that says you can't continually do that again, and that's exactly what we do. We never want to be compute constrained.Jake [00:18:09]: At the start of the year, we actually became compute constrained because one upstream provider wasn't able to give us quota at the rate we needed, and the hardware was slower. I spent a weekend rebuilding our entire network overlay so we could straddle five clouds: Oracle, AWS, ourselves, GCP, and one other one. We can do more than that now.Jake [00:18:38]: We got into a spot where we were trying to pack instances tight because we couldn't get enough compute. That led to a few reliability issues, which are now past us. I made a tweet pointing out that it's becoming harder and harder to acquire compute at the rate these models need to acquire compute. We got bit by it.Swyx [00:19:15]: How do you think about pricing knowing you might not have your own metal available at all times? Are you pricing assuming you need extra margin if you end up going into the cloud?Jake [00:19:26]: Because we've built out our metal data centers, our margins on metal are around 70%. We can deeply subsidize the cloud business if we want to scale at a reasonable rate. We have a few levers: metal, which makes the margins; cloud burst; debt to buy servers; and venture capital. It's an interesting operational problem: how much cash do we have, how much should we raise, how quickly can we deploy it, and can we scale revenue as quickly as we scale compute?Jake [00:20:05]: If we continue making it trivially easy for people to build and deploy, then the faster we close that loop and the more operationally excellent we are with capital, the faster the business can scale. It's almost a straight linear deployment rate.Financing Infrastructure: Hardware Debt, VC, and Operational LeverageSwyx [00:20:20]: I think infra startups raising debt is a tool people don't utilize enough or know enough about. What can you tell us about that? Is it secured against your CPUs?Jake [00:20:32]: It's secured against our hardware.Swyx [00:20:37]: What rates do you get? Who are the lenders?Jake [00:20:39]: We pay prime plus a spread, and we can refinance any of the debt as rates go down. The terms are pretty good. The unfortunate thing is that Twitter has no nuance, so people say, “Venture debt bad.” But as with all things, there are specific tools and areas where you can be deliberate instead of using one tool as a hammer. Venture capital is not the hammer for everything. You have to explore and figure out what works.Swyx [00:21:12]: VC is usually the most expensive financing you can get.Jake [00:21:15]: Yeah. I also think people think about VC incorrectly from a capital-raising perspective. Most people think, “How do I raise as much money as possible from whoever is probably the best I can get at that time?” That's close to right, but what we've tried to do is figure out what unfair advantage we can buy with that equity.Jake [00:21:34]: It's the most expensive equity you're going to give away at that point in time, assuming the company keeps getting better. How do you use it to work with someone stellar who complements you? In the seed stage, I had never started a company. Ray Tonsing had good advice, and I could text him all the time. He was really fast. Awesome.Jake [00:22:01]: Then with John and Erica at Unusual, they said, “You roughly know what you're doing building a product. We'll mostly leave you alone and be available for advice.” Amazing. Then we got to Series A and the business was an operational tire fire because we didn't know how to scale a business. Work with Erica, and Jordan is over at Redpoint, so bonus.Jake [00:22:28]: Now we've raised from TQ and FPV as we're moving into enterprises. Every step of the way, we've asked: who can we partner with at this specific time to unlock the next section of the journey? I don't know enterprise sales. As an engineer, I can eyeball what features we might need, and we have wonderful people internally who can help. But you want boardroom dynamics where everyone is aligned and asking, “How do we win this?” instead of bickering about strategy.Data Centers in Space and the Physics of ComputeSwyx [00:23:31]: You had a tweet about data centers in space. Why no data centers in space?Jake [00:23:37]: It's not “no data centers in space.” My hot take is that I think it is solvable. I've just never seen anybody solve it.Swyx [00:23:49]: You said, “How are you going to dissipate that much heat in a vacuum?” You're making a physics claim.Jake [00:23:55]: I haven't seen anybody prove how you're going to dissipate that much heat in a vacuum. It doesn't mean it's not possible. It just means nobody has brought it up yet.Swyx [00:24:05]: Astrophage.Jake [00:24:06]: I don't know what that is.Swyx [00:24:07]: The Martian thing. Okay, you're very logical.Jake [00:24:09]: It could work. A lot of people are putting the cart before the horse. They say, “We're going to put data centers in space.” Okay, but how? “We have time to figure it out.” It's like in The Martian where they ask how they're going to intercept something and say, “We'll figure it out.”Swyx [00:24:36]: Making a bet on human invention is weird because you blind trust that it can be solved. But with physics, there are first-principles bounds you can put on it. Maybe not. Maybe you're asking to travel time or break a fundamental thermodynamic law.Jake [00:24:57]: I don't know how VCs do this either. How do you know what's not possible and a grift versus what's possible but sounds completely insane? “We're going to put data centers in space.” Coin flip as to which it is, and I guess you'll know in 10 years. That's one cycle.What Agents Need: Versioning, Observability, and 1,000x ScaleSwyx [00:25:23]: Moving back to agents. The branching, fast spin-up, and orchestration you do feels like pre-work that happened to be exactly what agents want. What do agents want differently than humans?Jake [00:25:37]: They want the ability to version things. It's not that different; it materializes slightly differently. Agents want a way to test changes incrementally. Engineers have feature flags. Is there a reason agents can't use feature flags? I don't think so.Jake [00:25:54]: They want version control. Can we use Git or not Git? That one is up in the air. I think something outside Git will emerge for how we version these things over time. They need observability. You need to query what happened, when it happened, which steps failed, traces, logs, metrics, and all the rest. They need network, compute, and storage. They need to write files, save files, iterate on files, and snapshot file systems.Jake [00:26:25]: A lot of what humans needed is in line with what agents need. Branching and forking are not different; we're just moving 1,000 times quicker. It can look like you need something massively different, but what you need is something massively better than what existed. You need orchestration massively better than Kubernetes. You need networking probably better than Envoy. It goes all the way down the stack.Jake [00:26:55]: If the workload profile doesn't change so much as it gets massively compressed because you need thousands of these things, what assumptions change? etcd is going to melt. You need to replace it with something. You can go all the way down the stack and say, “That part has to change, that part has to change, and that part has to change.”Jake [00:27:19]: The interesting thing about the super-exponential curve is that you have to build systems where you can rip out those parts at any time because a new bottleneck might emerge. You get good at parallel agents, and a different part of the system breaks. So it's similar to what humans needed, but at 1,000x scale.Jake [00:27:55]: How do you do code review in the age of agents?Swyx [00:28:00]: You throw more agents at it.Jake [00:28:01]: You don't. But then who reviews for CVEs and all these other things?Swyx [00:28:07]: More agents.Jake [00:28:08]: And that's how we hit the inference wall. You can continually throw agents at the problem, but I think there's a limit to the number of agents you can throw at a problem.CLI, Agent Handles, and Closing the LoopSwyx [00:28:24]: You already had a CLI before it was cool. How is the shape of what you're exposing changing, if at all?Jake [00:28:28]: CLIs have always been cool. The CLI changes because we think about how to give Claude, Codex, ChatGPT, or any model a handhold.Jake [00:28:50]: A CLI is a single command: deploy, get logs, and so on. Things that were prohibitively annoying to humans are not annoying to agents. They're nice. If I handed you a CLI with 40 arguments and 600 flags, you'd think, “I'm never going to use all of this.” But if you hand it to an agent, it says, “This is excellent. I have so many handles to work with.”Jake [00:29:24]: If you're going to expose things to agents that way, you want as many handles as possible where they can get information, query dynamic information, and close the loop quickly. Most problems right now are about how to close the loop as quickly as possible. Where does the agent get stuck, and how can you remove that?Jake [00:29:49]: Telemetry is important. If you can tell where the agent gets stuck from the CLI and say, “12% of people deviate from the happy path because of this, and now I add this argument and drive it down to 2%,” you massively increase the rate of loop closure.Jake [00:30:03]: That's how we think about not just the CLI, but every point in the dashboard. It's a user journey: I hear about Railway. I get something deployed. I get my first green build or aha moment. I see an endpoint, logs, whatever. Then I iterate. The iteration loop is indefinite. The user wants to deploy a new thing, a Postgres instance, change code, and keep iterating.Jake [00:30:36]: If you focus on the iteration loops and what's blocking them from closing quickly, one thing we say internally is: you never want to be waiting on compute anymore. You always want to be waiting on intelligence. If you're waiting on compute, there's a bottleneck that needs to be destroyed because eventually that bottleneck becomes so large that another workflow emerges to change it.Jake [00:31:04]: We've built a product where you push code, build it, and so on. But I fundamentally believe the push-pull loop is going away. We'll get to a point where you make a small change in production, that change is versioned across your infrastructure, you're working alongside copy-on-write versions of your database and infrastructure, and then you merge it in and it's instantaneously live. That's the holy grail of loops. The push-pull-rebuild thing is a point of friction that we're removing entirely.Canvas as Output: Dashboards, Context Anchors, and HyperstructuresSwyx [00:31:43]: It's incredibly fast. If anyone hasn't tried it, that fast feedback is great. My hot take is that Railway was famous for its canvas, which visualizes your infrastructure and lets you manipulate it visually. But that was for humans. For the next phase of growth, Railway CLI is more important than canvas.Jake [00:32:05]: The canvas is funny because it's a mechanism to show changes over time. You're right that previously we used it a lot as an input. Moving forward, its goal is more like an output. You would go to the canvas, make changes, see them, and watch your infrastructure evolve. Now agents have access to the CLI and can make those changes. So the canvas becomes an output: what information does the human need at this moment to make suitable decisions about control requests? Do I approve this or not?Jake [00:32:57]: It also has to be an anchor for your context, a port in the storm. Think of it like layers in a file system. You start with a project, then drill down into services, then into a function or code, because you want to represent the entire thing not just in your head, but in the canvas. Other people can share that representation, think on the same wavelength, and move quickly.Jake [00:33:33]: A lot of organizations get in trouble as they scale because all the context lives in someone's head. “How does this microservice work?” “I have no idea; go ask this person.” Then you have whole categories of products built around context discovery. A lot of that melts away if you have a solid hierarchy and can infinitely nest services, code, context, and everything else all the way down. That's what lets you build these structures over time.Jake [00:34:18]: It's also what lets us build what I've called hyperstructures: things that are way bigger. You look at the Golden Gate Bridge and ask, “How did we build that?” There's a meme that we lost the technology. To some extent, yes, because the coordination that built those things evolved and changed. We lost some of the art of building structure as we jammed everything into Slack.Swyx [00:34:52]: But you jam everything in Discord.Jake [00:34:53]: Same point. It doesn't matter. It's message passing and interrupts, message passing and interrupts.Swyx [00:35:00]: So you're arguing there should be something better and more structured than Slack?Jake [00:35:04]: Yeah. For sure. I think Slack is awful, and Discord is awful too.Central Station: Context Routing, Support, and Incident ClustersSwyx [00:35:09]: This is the equivalent of my mom test. What have you done that has your solution to this?Jake [00:35:15]: Internally, we've built a tool called Central Station that aggregates all the context from our users. Every piece of feedback, every customer support item, everything gets aggregated into clusters. If an incident is brewing, we can determine how many users are affected and break off a discussion based on that.Jake [00:35:40]: That is more helpful than long-running channels where you're trying to decide which channel to put something in. If you can dynamically aggregate information and dynamically route it to the right person based on context, it works better. We know internally that these four people are close to networking. If we see a networking thing, we can drill it down to those four people. If it's with this part, we can look at the commits. This is no longer a manual process internally.Jake [00:36:13]: If you go to station or help.railway.com, that's why we built it. We wanted to scale with a massive amount of leverage by aggregating feedback.Swyx [00:36:27]: This is built in-house?Jake [00:36:28]: Yep.Swyx [00:36:29]: I remember helping out on this one with Angelo in 2023. You scale a lot with a very small team.Jake [00:36:38]: Yeah. We're about 10 times bigger now.Swyx [00:36:40]: You have your full developer code here? Very cool.Jake [00:36:44]: If you go to railway.com/stats, we expose this as a pub-sub-able thing. It's all real-time metrics. There's a way to get it as JSON somewhere if you care.Jake [00:37:01]: We're big on trying to build everything in public and talk about what we're working on. We've had issues in the past, and we'll say, “Here's how we're fixing these things.” We've gotten compliments and flak for incident reports. We're always trying to make them better and talk with people.Incidents, Disclosure, and Progressive RolloutsSwyx [00:37:20]: You had a big one recently. I liked that it was scoped to 3,000. You presumably used Central Station. Talk through what happened and how you address it internally as a team.Jake [00:37:38]: Internally, this one really sucked. It had to do with an upstream provider that didn't do the behavior it said it documented, which is unfortunate given they wrote the RFC for how the behavior should work. We rolled those things out, and Central Station caught it initially when a couple users said caches weren't invalidating. We turned it off immediately.Jake [00:38:03]: When you roll out to a large user base of three million people, you get a lot of disparate behaviors. We tested in staging and had tests, but we hit an edge case. We've hardened those systems, and now we can make that better. But it was a tough one.Swyx [00:38:39]: I always wonder how private disclosure is supposed to work if people find an issue. Are they supposed to contact you first? When you run a platform, these things will happen. What channels should people pursue to quietly resolve it before it becomes a bigger incident?Jake [00:38:59]: There's responsible disclosure. We err on the side of over-disclosing and letting you know something is wrong versus having your provider gaslight you. We've erred on sharing those things more publicly, even if they impact a small subset of users. That's a decision we've made internally. We have four values. One is honor. The honorable thing is to notify people to the widest degree at which they may have been affected or there was an issue, and then confront it head-on: why did it happen, what can we do better?Swyx [00:39:45]: Not the whole user base. That's because of incremental rollouts and other things?Jake [00:39:50]: Yeah. Progressive rollouts.Swyx [00:39:54]: That should be the norm at all large platforms.Jake [00:39:58]: It should. A variety of companies do this. There's the quote that Meta runs 10,000 different versions of Meta. To our earlier point about agents, they need the same thing. They need shadow traffic and all these other things. We've built so much ceremony around production being sacred that we need to make it trivially easy to test different behaviors in a safe environment. Then you can make mistakes in a safe environment.Safe AI SRE: Customer Agents, Forked Environments, and Production ParityAlessio [00:40:30]: Do you see a world where these things get automatically caught, not necessarily by your agent, but by your customer's agent? The cache invalidation issue seems easy to check if you know to look for it.Jake [00:40:44]: It's hard because to determine it, we almost need to hook into your observability infrastructure. That's why we have the template loop on the platform: so you can roll things out progressively. You can roll out to Johnny Vibe Coder initially, or push a shard that someone consumes at their own leisure. Or you can roll it out over weeks: 0.1% of people, 1% of people, early adopters, then all the way up. That's the non-deterministic version control we talked about earlier.Jake [00:41:30]: I believe that's where most things should go, because most companies end up building staged rollout systems in-house. It's the same thing built again and again at every company. There's a massive opportunity to consolidate developer debt.Alessio [00:41:45]: You should have a free tier. Model providers give free tokens if you let them use the data. You could give free compute if someone is the number-one shard that goes out and lets you plug into their observability.Jake [00:41:55]: We do that. That's why we talked about the impact on 3,000 people. We start with lower-impact people. Larger companies on the platform are last to receive those rollouts so they have a version of the platform that's deeply stable.Alessio [00:42:16]: I have three services, so I'm sure I get the first rollout. You can nuke my thing at any time. There are all these SRE agent companies. Observability people also want agents that fix upstream problems. You have your own agent in the canvas now. How do you see that playing out?Jake [00:42:39]: It's the stacking entropy problem. If you don't have primitives to make iteration in production safe, it becomes difficult. If you're an observability provider saying, “Here's the fix to this error,” assume 80% are good and make sense. But in the last 20% long tail of complex issues, if you let somebody stamp it, you create an opportunity for an incident.Jake [00:43:08]: That's why forked environments are important. People have staging, but it always drifts from production. You need primitives, workflows, and experience built first-party on the platform so you can fork any service at any point in time.Jake [00:43:33]: I think of the canvas as a sheet of transparency paper. The agent is a little guy you push up into the canvas. It should say, “I need to copy that service and that service so I can test these two things.” It gets a read-only copy of production. Anything that's PII gets marked as a transform when we clone the database, create a copy-on-write version, or read from it. Then the agent makes changes and asks, “Does this actually work?” as close to production as possible.Jake [00:44:22]: That's how close you have to be, or you get massive drift. The system becomes unstable. You see this with massive systems built on Docker for local, Kubernetes for production, and a specific thing for something else. That complexity slows developers and becomes unstable at scale, making it hard to iterate. We want to compress that way down and say, “As close to prod as possible is where we want to be.”From AISRE Skeptic to Agent BelieverSwyx [00:45:00]: I was texting Erica for questions, and she says you were originally not a believer in AISRE. Have you come around on it?Jake [00:45:10]: I flipped, but I'm still not a believer in AISRE if you don't have the primitives to make it safe. If you unleash AISRE on production infrastructure without safe primitives for copying volumes and making sure things are fine, it's going to nuke your production database. It's not a matter of if, but when. I'm a big believer in making those loops safe.Jake [00:45:33]: I was a deep AI skeptic until 2023. In 2024, I thought, “Maybe I can roughly make this thing do it.” In 2025, I thought, “Now I can hold this.” Over winter break, everybody came back saying, “It's almost impossible to hold this.”Swyx [00:46:01]: Did you see this on the Claude docs? CloudBot? OpenCloud?Jake [00:46:06]: It's gotten to a point where it's harder to hold it wrong than to hold it right. There's a scene in Avengers where Vision picks up Thor's hammer and says it's terribly well-balanced. It self-balances and works well. I'm a deep believer at this point that this will be the dominant species: assembly, C, C++, JavaScript, words.Swyx [00:46:35]: It feels like a big jump.Jake [00:46:37]: It is. But it's not like you abandon CPU-based discrete logic and move straight to fuzzy logic. You need both. Your skills should call code or applications or some static structure. You can use skills to distill what the procedure should be or how the code should act.Jake [00:47:02]: I'm coming to a thesis: you need three points. You need a clear spec defining the system, the code, and the tests. When you say it out loud, if you've been in engineering long enough, you're like, “Of course. That's an RFC, tests, and code.” But they all matter. Having them together lets them reinforce each other: the spec and tests match, but the code doesn't, so reconcile it. Or the tests and code match but the spec doesn't, so reconcile that. That's the iteration loop.Jake [00:47:41]: That's why you're seeing people talk about software factories, docs, and reconciliation. Some of that is architectural astronomy if you don't implement it, but that loop is where most things will end up.Swyx [00:48:07]: For listeners, we've been talking about this on the pod for three years: the holy trinity of specs and tests. Itamar Friedman from Qodo is the reference if people want to look it up.Self-Modifying Infrastructure and the End of Push-Pull-RebuildSwyx [00:48:18]: One thing I want to mention on the OpenCloud idea is self-modification. I don't know how Railway would support it, but I have my OpenClaw, and I just tell it it has the Railway CLI and can do whatever. In theory, whatever capabilities or new infra it needs, it can call the Railway CLI, provision it, and add it to itself. The agent can modify its own infra.Jake [00:48:45]: It's nuts. I have a loop set up where you put the Railway CLI on top of something that runs on Railway. You're authenticated as whatever the current box is, and you can make any changes to it. Then you call Railway deploy, and it deploys itself.Jake [00:49:04]: It's like: “I need to spin up this instance of this environment. I already exist in this environment. Excellent, I have access to a Postgres instance now.” That's where we want to go with agentic, self-replicating infrastructure. That's your loop: iterate in production. You continue making changes. If it works, merge it upstream. If it doesn't, throw it away.Jake [00:49:37]: How do you make throwaway copies trivial to spin up and super cheap? The era of “I have an AWS instance with four vCPU and 16 gigs of RAM” is going to get destroyed. If you do that for agents, you need a thousand of those machines. It's prohibitively expensive compared with what we've spent a ton of time figuring out: the atomic unit of deploy, whether you call it isolates, sandboxes, or something else. Only pay for what you use, spin up instantaneously, and close the loop as quickly as possible.Jake [00:50:15]: If the system can self-replicate safely and say, “This is my environment, I'm making these changes,” it can come back with, “Does this look good? This is a new state of infrastructure given this prompt. I think I've solved it.” Then you go back and say, “Actually, it looks different.” It does the loop again. Then you say, “Cool. Apply.”Swyx [00:50:38]: That's retroactively obvious, which is the most useful kind. Any other comments on agent deployment on Railway?Jake [00:50:51]: It's getting better every day. I'm on X or Twitter. You can always yell at me about the parts not working as well as they should, because plenty of things should work way better.The New Serverless: Stateful, Long-Running, Pay-for-What-You-Use LinuxSwyx [00:51:04]: At this stage, when people want massively or embarrassingly parallel compute, they usually talk serverless. I feel like there's a new serverless compared to the previous five years of serverless. You're in that new bucket. Do you have comparisons or philosophical differences you want to call out?Jake [00:51:31]: It's somewhere in between. It's the ability to run stateful, long-running workflows or executions.Swyx [00:51:42]: Vercel has Fluid Compute, Cloudflare has some container thing, Google has App Runner and others.Jake [00:51:55]: That's where everything is roughly going, and it's why we've been working on this for six years. We believe users need access to a computer: a box that speaks Linux. They need to deploy what they want. Other systems change the surface area of what you can build. For us, users need a computer and need to deploy anything they truly want. That's why we've focused on the primitives: network, compute, storage. If we give you those and expose them so you can run things indefinitely, that's where we believe it's going.Jake [00:52:43]: Twitter has no nuance, so everyone says “servers” or “serverless.” It's always somewhere in the middle: I want to run it for a long time, but I don't want to provision the resource statically or pay for things I'm not using. That's been our thesis from day one: pay only for what you use, run it indefinitely, and it is full Linux.Swyx [00:53:12]: That's why I like the naming of Fluid. It's fluid. Flexible.Heroku, Focus, and Carrying the Torch Without Becoming the PastSwyx [00:53:18]: Another milestone is the Heroku official deprecation. You're one of the presumptive new Herokus. “New Heroku” has been a category for as long as I've been in developer tooling. It's finally happening. What was that like? Any behind-the-scenes of, “This is the moment”?Jake [00:53:42]: You have people where you're like, “You were running stuff on here? You, as this company?” It's crazy that names you would know are running on it and now coming to us saying, “We want to move a lot of this off.”Swyx [00:54:00]: Any behind-the-scenes on why Salesforce let Heroku stagnate?Jake [00:54:05]: I can only guess. It's hard when it's not your business. Salesforce's business is to build a great CRM. That's their focus. Then you acquire a compute business as an offshoot. A lot of early Meta people talk about focus. Boz has a write-up about how in the early days of Meta they had no money, so they were forced to focus. Then they turned on the money tree and had no reason not to split their focus.Jake [00:54:52]: But that dilutes your product. You get offshoots where you ask, “Is this the focus of the business?” If it's not core, it languishes. A lot of companies get in trouble when they split focus because they're fighting a multi-front war, not just externally but internally for alignment. Where are we going? What are we doing? What is our purpose?Jake [00:55:24]: If you're Salesforce-built and mission-driven, you want to work on Salesforce. Heroku is off to the side. It's not core to the business. Getting resources, budget, focus, and alignment internally becomes hard. It was a matter of time.Swyx [00:56:06]: Kudos for them to call it out instead of leaving it unknown.Jake [00:56:12]: Their release was a little odd. They called it out, but they didn't say they were shutting it down. Behind the scenes, I think they issued messages to people saying they should close accounts and that they were going to deprecate and remove things over time.Jake [00:56:30]: It's crazy because some of my first deployment experiences were on Heroku. You start with dragging things into an FTP server, then you try to get a deploy working, and then it's Heroku. It was the on-ramp for us. But the wheel turns. New things emerge. We're happy to carry the torch for a lot of that. But we don't want to be the new Heroku. We want to be the way people build and deploy software, and ultimately the way people monetize software over time.Swyx [00:57:19]: It's still a big crown to be the new Heroku. There are 50 companies that fought for that.Jake [00:57:23]: Everybody is holding some portion of it. We're happy to support people and companies. The platform works differently. The game loop is similar, but we've been dogmatic about where these things are going: primitives, agents, fan-out. Some things fit; some workflows need to change. We have an approximation of Heroku pipelines with the environment system. It's exciting. We've got a ton of people we can support, and it's growing a lot.Temporal, Workflow Engines, and State MachinesSwyx [00:58:12]: I have one more technical question about Temporal. I've sold my shares. You're a power user and one of our earliest customers. I met you through Temporal. You built on Temporal. You have complaints. This may be the most neutral and informed conversation anyone will hear about Temporal without someone working at the company.Jake [00:58:39]: That's fair. I've used Temporal for almost 10 years because of Cadence at Uber.Swyx [00:58:52]: Give people a sense of what Cadence was at Uber.Jake [00:58:57]: Cadence was the precursor to Temporal. It powers trip actions, rides, when you rent a Jump bike or scooter or car. You're running workflows for a period of time and saying, “This ride will run indefinitely until it finishes.” You attach information: you paused in this zone, so add this charge to the bill. When you end the trip, the workflow is done. That experience was powered by Cadence at the time.Swyx [00:59:34]: I used to say it's like programming the entire user journey top-down as one function.Jake [00:59:39]: It's a powerful idea and important. It's also important for the next phase of the agentic journey. You want an agent to do a specific task, be complete or incomplete on that task, and move on to the next thing. You need a way to manage workflows dynamically.Jake [00:59:59]: Temporal was always great in theory, and great when you got it working the way you wanted in production. But it required you to model the entire journey in your head. If you didn't, you could cause issues where replaying the state of the workflow causes non-determinism.Swyx [01:00:25]: Because it works on deterministic workflow history.Jake [01:00:28]: Exactly. I describe it as a jet engine. If you know how to operate it and run it, it's great. But you can't hand it to people trying to build complicated things if they don't have the whole state in their head.Jake [01:00:48]: We run our whole deployment pipeline on top of it. That's a reasonably complicated workflow: pre-commit hooks, signaling, queuing, and all the rest. We ran into the same thing at Uber. As you express a large workflow, it gets more complicated, with more states in the state machine that you have to map back to the workflow.Swyx [01:01:15]: It's a lot of ifs.Jake [01:01:16]: Exactly. At Uber, we built a system for doing the state machine and testing it. We've started to build some of those things here because it's grown heavily. It's not quite love-hate. When it works well, it works super well. But if someone who doesn't have full context puts something into the system that invalidates state or causes non-determinism, or spins off a ton of activities, you have to keep track of underlying SRE knobs like activity slots. Those should scale with memory, vCPU, and so on. It becomes a bear to scale.Swyx [01:02:10]: You need a capable sysadmin running things behind the scenes. If you moved off, what would you do?Jake [01:02:19]: We'd build our own workflow engine. We have a few internally that we've worked on.Swyx [01:02:27]: This is one of those classes of things you typically wouldn't vibe code, but I'm wondering if you can.Jake [01:02:33]: I still don't think you should vibe code it. You still want to run decent tests to make sure it works.Swyx [01:02:39]: Timo didn't invent that from scratch either. There are libraries you can run. On top of that, it's just a state machine that you have to map out. Ultimately, you define the instructions you want and run them through a state machine.Jake [01:03:00]: It's very doable. Workflow stuff is interesting. Restate is doing neat stuff here.Swyx [01:03:10]: You're tied into JavaScript. Are you a JavaScript maxi?Jake [01:03:13]: Internally, we have TypeScript, Rust, and Go. We don't add more languages. Actually, we have a little C because we write BPF code and hooks. But those are the languages.Swyx [01:03:28]: Is this for sidecars?Jake [01:03:32]: No. It's for the networking stack, volumes, and things like that. We use TypeScript a lot because it powers the dashboard, but we're moving a lot of workflow stuff off the dashboard stack and into the infrastructure stack.Railpack, Nixpacks, and Content-Addressable FilesystemsSwyx [01:04:00]: Cool. Any other technical infrastructure stuff? Railpacks?Jake [01:04:07]: We built an engine for determining dependencies based on source code. It's called Railpack. We built the first version, Nixpacks, on top of Nix, and then we moved.Swyx [01:04:17]: People have been trying to get me to adopt Nix and NixOS for four years. Is it ever going to be a thing?Jake [01:04:23]: I don't know. We're excited about it, but it has pain points. Think of it as a stack of versioned binaries at specific slices in time. If you want version X and version Y, you bloat the package space, which blows up image size and makes real-world workloads difficult.Swyx [01:04:53]: But you content-address it and cache it. In theory, there are optimizations.Jake [01:05:00]: In theory, yes. But with a large enough user base and disparate enough machines, you run into a problem Meta described in the XFAAS paper, their internal serverless system. It becomes difficult at scale unless you break out specific runtimes.Jake [01:05:24]: We didn't want to do that because we wanted to truly allow you to deploy anything. That was our initial thing with Nix. But we've moved toward interesting work around content-addressable file systems that can lazy-load anything from any point and page it into memory.Swyx [01:05:48]: Amazing.Jake [01:05:49]: The future is very bright. It's crazy, and it's going to be nuts.Coding Agent Spend, Roadmaps, and Token ROISwyx [01:05:54]: Founder journey stuff?Alessio [01:05:56]: Your cloud usage: you tweeted you're going to spend $300K this month?Jake [01:06:01]: I think we got to $200K.Alessio [01:06:02]: Coding agents?Jake [01:06:03]: Yeah.Swyx [01:06:04]: Across the company?Alessio [01:06:05]: You only have 35 people, so I'm sure they're not all spending $10K a month. What's the distribution?Jake [01:06:10]: I think I'm at about $25K. We have power users all the way down. We came back from winter break, and I basically said, “If you're writing code by hand, you're doing this wrong.” The tools are good enough now that you can move extremely quickly. There are issues and pain points, but you should be reviewing the code you are writing instead of writing it by hand.Jake [01:06:40]: Architectural patterns matter more now than ever, but you shouldn't spend your time generating code you would write. If you know how to write it, ask the agent to write it and reconcile it until it looks like you would have written it yourself.Jake [01:06:58]: People misconstrue my propensity to push people toward agents as connected to our growth and some reliability bumps. They're not necessarily related. The tools are good enough to move extremely quickly and build things way larger than you could before.Jake [01:07:19]: To the earlier point about cooling data centers in space: I don't know. But with software, you can ask, “How would I build block storage from scratch? How would I do these things?” I have ideas because I have history and have read papers. Let me work them out and build massive test benches with thousands of tests, because those are now free to author. If you're not using AI systems to speed-run your roadmap and reconcile your existing system onto the future, you're missing a large point of what's happening.Alessio [01:08:12]: What's the path to spending $3 million a month? Is it bound by ideas and things customers can absorb?Jake [01:08:19]: For most companies, it's bound by deployment at this point. That's why we've seen a massive boom in users and companies, from Fortune 50s down, asking how to get developers to move faster. You'll probably hit your CFO before any technical limits because they'll look at the eye-watering amount of money spent on tokens. Inference costs have to come down, but we're inference constrained now. There will be price discovery around what makes sense for an org to adopt.Jake [01:09:06]: I think you'll end up with the F1 driver concept. If someone is really adept at these things, it makes sense to put them in a $3 million car. If they're not, it probably doesn't make sense. You'll take a few people and say, “You can drive the F1 car. We need to go in this direction. Figure out if it works and prototype it.”Jake [01:09:33]: We've done some of that and vastly accelerated our roadmap. We thought we'd ship something in a few years; now we can probably ship it in a few months because we validated it and don't have to build it incrementally. We can skip steps and move toward our vision.Alessio [01:09:58]: A lot of people are realizing the roadmap doesn't always have a business impact, so they say tokens are too expensive. But if your roadmap were built to make more money by the time you built it, you'd have token pricing for it, the same way you do with sales. You'd spend a billion dollars on sales if you knew you would get $2 billion of revenue.Jake [01:10:19]: Exactly. A naive way to measure this is the percentage of tokens that end up in production. If you can measure impact because those tokens end up in production, that's awesome. But the burden of proof will rise. Internally, we have a growing number of pull requests that haven't merged. The question becomes: how do you get this into production? It's about how quickly you can build and deploy software, which is exciting because that's our whole thing.The SDLC Shift: Prompt Requests, Feature Flags, and Safe RolloutsSwyx [01:10:56]: The SDLC is changing. One thesis is that the pull request is dying. It's going to be the prompt request. Beyond that, code review is also kind of dying if you have all the other systems in place. What else is changing about the SDLC?Jake [01:11:19]: The AISRE and the tools to make it happen. AISRE is pie-in-the-sky aspirational. What does it take to get an AISRE? What tools do you need to build?Swyx [01:11:32]: You should expose your tooling to customers at some point. The Central Station command center.Jake [01:11:39]: We have it for template maintainers. Template maintainers can deploy and maintain templates, and they get feedback. We're going to expose those things incrementally.Swyx [01:11:51]: Clustering around incidents. Everyone has a version of that, but I don't think anyone has solved it.Jake [01:11:56]: I won't say we've solved it internally, but it's gotten so good that we can see incidents forming pretty quickly. At some point, those will be things either someone else builds or we build. We've always built things purpose-built for us. If it makes sense to make it useful for users, monetize it, or turn that loop into a profit center instead of a cost center, we want to do that.Jake [01:12:28]: Pull request is definitely dying.Swyx [01:12:29]: Do you do first-party feature flagging and incremental rollout stuff?Jake [01:12:34]: We have a feature-flagging engine we built internally and will eventually roll out.Swyx [01:12:38]: I don't see it as a user. How come you didn't give us what you have?Jake [01:12:43]: We have to beta test it. We care a lot about the quality of the things. There's plenty we've used internally that doesn't make it all the way through the journey because it fails. It works for one service but not multiple services. We'd have to build it for multiple services and know that if we released it, we'd rebuild it again and again. Some things are worth that, but many inform the roadmap.Jake [01:13:18]: We don't want to dilute the experience by saying, “This works, but only for this service,” unless it's a core initiative. Over the next few months, we'll roll out things that work for a single service, then multiple services, then multiple services across the environment. You have to be deliberate. Otherwise you create broken disparate experiences and support load because people ask how to use the feature.Jake [01:13:52]: It's the earlier expansion and compaction pattern. You expand the company to get features, then compact and smooth them out so the experience is stellar. You told me in the hallway, “It's gotten so much better.” Internally we're saying, “This part really sucks. We need to make it significantly better.”Swyx [01:14:11]: I can attest to that over the last three years watching you build Railway. For listeners, feature flagging is a huge part of Uber culture. So much so that they have too many feature flags and another thing to remove feature flags. Facebook has Gatekeeper. Agents are going to need this. It's fundamental to incremental rollouts. OpenAI acquired Statsig. GPT-5 is routing and flagging through different models.Jake [01:14:56]: It's super important. If the software development lifecycle is going to change because we're doing things 1,000 times faster and 1,000 times more concurrently, what becomes important at scale?Jake [01:15:16]: Before I started Railway, I built a feature-flagging product and tried to sell it. It was an easier version of LaunchDarkly. I ran into a problem: anyone small enough to adopt your technology doesn't care about feature flags, and anyone large enough to need feature flags needs so much scale that you have to build out all the infrastructure. I scrapped it.Jake [01:15:42]: But what is old is new again. Companies are trying to move quickly, but you can't YOLO a vibe-coded thing straight into production. You need to say, “Here's my blast radius, my impact, and I want to shadow it for these users.” Feature flags. You're going to need the tools larger companies built to maintain their structures. Everything gets compressed by 1,000x so everybody can build those structures quickly.Jake [01:16:07]: That's exactly where we are: compressing the software development lifecycle, then expanding it and adding more new things.Cattle, Pets, and Clonable InfrastructureSwyx [01:16:15]: Another term that comes to mind for newer developers is “cattle, not pets.” People treat production like a pet. It has a name. You baby it and keep it alive. With cattle, you can mass farm, roll out, portion parts out, and kill them.Jake [01:16:37]: I think that might change. You can move toward having pets as long as you have a cloning machine for your pets.Swyx [01:16:52]: Yeah.Jake [01:16:52]: If you can snapshot every single thing at every frame, it doesn't matter if something gets obliterated because you have a snapshot of it. The things we've built right now are designed to block changes from the hermetically sealed DevOps line. You have to write a Dockerfile because you nee

Just about every animal with a backbone yawns (maybe even dinosaurs), but why we do it is still something of a mystery. A SciFri listener from Texas recently spotted some research that suggests yawning could play a role in clearing waste products from the brain, and asked us to get to the bottom of it. Biomechanical engineer Lynne Bilston, an author on that study, joins Flora to discuss the findings and what they could mean for neurodegenerative diseases like Alzheimer's. Plus, about a third of Americans aren't getting the recommended seven hours of sleep per night, according to a new CDC report. We check in with sleep researcher Stuti Jaiswal to break down the report and find out how to get a better night's sleep. Check out an MRI video of what yawning looks like inside the body. Guests:  Dr. Lynne Bilston is a biomechanical engineer at UNSW Sydney in Australia. Dr. Stuti Jaiswal is a physician scientist and co-director, education at Scripps Research Translational Institute in San Diego, California. Other episodes you may enjoy: Does Taping Your Mouth Shut Help You Sleep? The Brain's Glial Cells Might Be As Important As Neurons Want SciFri gear? Check out our new shop! Transcripts for each episode are available within 1-3 days at sciencefriday.com. Subscribe to this podcast. Follow our show on Instagram, TikTok, Facebook, and Bluesky @scifri and sign up for our newsletters. Got a science question that's keeping you up at night? Call us: 877-4-SCIFRI Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Things Discussed: VALIANT! Craig shares the story of the nadir of Michigan basketball: Northwestern-Michigan. Combine: Michigan rosters do not lie: Bare feet measurements were the real measurements. Meanwhile Alabama is adding 4 inches. Brandon McCoy—needs to make free throws but he's going to lead the B10 in steals. Quinn Costello: remarkable shooter, is a true jumpshot. Does he have a left hand? Does he have any post-up game? Skinny right now. Jalen Reed is VERY interesting. Fluid at 6'10, can defend and shoot and should be healed after a year from an Achilles. Will Wade just invents new ways to be the villain of CBB. Football: Zack Marshall and four OCs in four years. Bryce in the offense: Going to use his legs more than his arm. Should create more explosives because you're taking away a free hitter from the defense. Will also feature the tackles in space more. To run this you have to beat what stops it, IE Don Brown man defense. JJ Buchanan could be a breakout guy. Is that the way to get 5-star QBs? No, but maybe you should be looking to the portal nowadays.

The situation in the Strait of Hormuz is fluid as Iran attempts to wait out the U.S. Gregory Copley argues the U.S. requires regime change to stop trans-Eurasian monopolies and restore regional stability. (10/16)JUNE 1964

Rigid org charts are quickly becoming a barrier to AI-fueled business impact. Microsoft's CVP of Workforce Transformation joins WorkLab host Molly Wood to share how the most forward-thinking companies are breaking down silos, building teams around skills, and embracing constant change. Discover why adaptability, curiosity, and a willingness to reinvent are the new must-haves for leaders and employees alike—and how your organization can unleash human capability for the AI era. Show Notes WorkLab Subscribe to the WorkLab newsletter

Rigid org charts are quickly becoming a barrier to AI-fueled business impact. Microsoft's CVP of Workforce Transformation joins WorkLab host Molly Wood to share how the most forward-thinking companies are breaking down silos, building teams around skills, and embracing constant change. Discover why adaptability, curiosity, and a willingness to reinvent are the new must-haves for leaders and employees alike—and how your organization can unleash human capability for the AI era. Show Notes WorkLab Subscribe to the WorkLab newsletter

Contributor: Aaron Lessen, MD Educational Pearls: There has long been many questions about which IV fluid is best for ED resuscitation Multiple adult studies have shown no clear benefit of balanced fluid vs normal saline A large pediatric randomized clinical trial published in April compared balanced fluid vs normal saline in children with septic shock  The study included about 9,000 patients from 47 emergency departments in five countries Patients with septic shock were randomized to receive either balanced fluid or normal saline The primary outcome was adverse kidney event (death, dialysis, or persistent kidney dysfunction) at 30 days or hospital discharge Results showed no difference in any safety outcomes and no adverse events occurred The key takeaway is that early fluid resuscitation matters more than which crystalloid you choose   References Balamuth F, Weiss SL, Long E, et al. Balanced Fluid or 0.9% Saline in Children Treated for Septic Shock. New England Journal of Medicine. Published online April 23, 2026. doi:https://doi.org/10.1056/nejmoa2601969   Summarized by Meg Joyce, MS3 | Edited by Meg Joyce & Ahmed Abdel-Hafiz, NREMT-P Donate: https://emergencymedicalminute.org/donate/  

Do you find yourself attracted to people who don't fit into your usual gender of choice? Or do you go back and forth? Mark Cusack, author of Fluid: A Guide for People with Flexible Sexuality explains how attraction works and how by expanding our understanding of sexuality we can find greater ease.In this episode:Author, coach, speaker Mark Cusack. On Instagram @notdefiningFluid: A Guide for People with Flexible Sexuality Host, sex educator, and energy worker Karen Yates Vote for Mark as LGBT Role Model in the UK's National Diversity Awards!Get Say It Better in Bed, Karen's free guide to upping your intimacy pleasure. Download here!Show your love for Wild & Sublime: Leave a tip!The Afterglow, our Patreon membership group, brings you regular bonus content, early alerts, and discounts to live shows! Be Wild & Sublime out in the world!  Check out our new tees and accessories for maximum visibility. Peep our Limited Collection and let your inner relationship anarchist run free… Support the showSupport the showFollow Wild & Sublime on Instagram and Facebook!

Are your feet and ankles swelling every evening? Discover why your ankles swell at night and how to relieve edema in the legs and feet naturally by addressing the root cause. 0:00 Introduction: Why feet swell in the evening0:50 Common swollen feet causes 2:04 The real reason why feet swell3:21 Potassium and swollen ankles and feet4:28 How to eliminate edema symptoms

If you have ever wondered why you are holding water despite doing everything right, this episode is for you. I dive into the complex physiological mechanisms behind water retention, moving beyond the simple vanity aspect to explore its real impact on health. By understanding these root causes, you can stop second-guessing your plan, avoid the "screw it" effect, and manage those normal fluctuations with an objective, informed perspective. Topics discussed: - The health implications of water retention- The three main hormones controlling water balance- The role of stress and high cortisol - The Minnesota Starvation Experiment- The impact of poor sleep and circadian rhythm- Sodium and potassium imbalances- The relationship between carbohydrate intake, glycogen storage, and water weight---------- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠My Live Program for Coaches: The Functional Nutrition and Metabolism Specialization ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠www.metabolismschool.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠---------- [Free] Metabolism School 101: The Video Series⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠http://www.metabolismschool.com/metabolism-101⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠----------Subscribe to My Youtube Channel: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://youtube.com/@sammillerscience?si=s1jcR6Im4GDHbw_1⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠----------⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Grab a Copy of My New Book - Metabolism Made Simple⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠---------- Stay Connected: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram: @sammillerscience⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Youtube: SamMillerScience⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Facebook: The Nutrition Coaching Collaborative Community⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠TikTok: @sammillerscience⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠----------“This Podcast is for general informational purposes only and does not constitute the practice of medicine, nursing or other professional health care services, including the giving of medical advice, and no doctor/patient relationship is formed. The use of information on this podcast and the show notes or the reliance on the information provided is to be done at the user's own risk. The content of this podcast is not intended to be a substitute for professional medical advice, diagnosis, or treatment and is for educational purposes only. Always consult your physician before beginning any exercise program and users should not disregard, or delay in obtaining, medical advice for any medical condition they may have and should seek the assistance of their health care professionals for any such conditions. By accessing this Podcast, the listener acknowledges that the entire contents and design of this Podcast, are the property of Oracle Athletic Science LLC, or used by Oracle Athletic Science LLC with permission, and are protected under U.S. and international copyright and trademark laws. Except as otherwise provided herein, users of this Podcast may save and use information contained in the Podcast only for personal or other non-commercial, educational purposes. No other use, including, without limitation, reproduction, retransmission or editing, of this Podcast may be made without the prior written permission of Oracle Athletic Science LLC, which may be requested by contacting the Oracle Athletic Science LLC by email at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠operations⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@sammillerscience.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠. By accessing this Podcast, the listener acknowledges that Oracle Athletic Science LLC makes no warranty, guarantee, or representation as to the accuracy or sufficiency of the information featured in this Podcast."