Podcasts about prefer

I didn't learn until I was 40 years old that my body moves through four distinct phases every single month — and that each one of those phases affects my mood, my energy, my patience, and my ability to connect with the people I love. Which means that the version of me who felt so present and empathetic last Tuesday wasn't just "having a good day." And the version of me who snapped at everyone before dinner on Friday wasn't failing. Both of those women were showing up exactly on schedule — I just didn't have the language for it yet. This episode is about what becomes possible when we finally have that language, and how empowering it is to understand our bodies well enough to show up the way we actually want to — and to have real grace for ourselves when that's harder. This week's guest is Shara Jackson Harper, a licensed mental health therapist, hormone and cycle guide, and mother of five who helps women understand how their internal rhythms shape the way they show up for the people they love most. In this episode, you'll learn: ✨ The golden conversation Shara had with her 15-year-old son — and the specific reason she believes the timing made all the difference ✨ Why most women are often carrying a "basket of shame" about their hard days, and what Shara says we can do with it instead ✨ The simple three-part formula Shara uses to talk to her own family about where she is in her cycle — and why her kids actually know what "lower bandwidth week" means So here's to understanding ourselves a little better, giving ourselves a little more grace, and showing up for our people in the ways we actually want to.   For full show notes, including takeaways, click here. *** Announcements: Hormone Cycle Guide: Shara has created a free handout with an overview of all four phases of the menstrual cycle plus a printable tracker to help you start noticing your own patterns. Grab it at 3in30podcast.com/cycleconnection.   March 30th is 3 in 30 Day! This year I wanted to celebrate by highlighting YOU. I'm collecting voice messages from listeners sharing your favorite episode and what about it made an impact or stayed with you, and my podcast editor is going to weave them all together into one really special episode. Prefer to write it out instead? You can do that too. Just head to 3in30podcast.com/tellrachel before March 20th. It only takes a minute, and I really cannot wait to hear from you. Related Episodes: 410: Align Your Goal-Setting with Your Menstrual Cycle // April Davis of Haus of Vagina 314: How to Feel Like Yourself in Motherhood // Aleisha McKean 205: How to Coach Yourself Through Big Emotions // Georgia Anderson Episode Sponsors: Skylight: Skylight offers a 120-day guarantee—if you're not thrilled, full refund. Right now, get $30 off the 15-inch Calendar at MySkylight.com/TAKEAWAYS. That's M-Y-S-K-Y-L-I-G-H-T dot com slash TAKEAWAYS Let's Connect! Join me on Instagram! Get weekly-ish emails with BTS of my life Find Your Magic in Motherhood: Free 3-Day Email Course *** Learn more about your ad choices. Visit megaphone.fm/adchoices

Spring break is magical until Sunday night, when you realize you have no plan for Monday. In this episode, we share our “soft landing” strategy for the first day back, built around three simple phases: reunion, bridge, and re-anchor. You'll learn how to reconnect before academics, use low-stakes review to ease back in, and restore routines in a way that feels calm, flexible, and community-centered.Prefer to read? Grab the episode transcript and resources in the show notes here: https://www.secondstorywindow.net/podcast/first-day-back-after-spring-break/Resources:Flying Wish PaperDie with zeroJoin The Teacher Approved ClubConnect with us on Instagram @2ndstorywindowShop our teacher-approved resourcesJoin our Teacher Approved Facebook groupLeave a review on Apple Podcasts!Leave a comment or rating on SpotifyRelated Episodes to Enjoy:Episode 181. How To Get Ahead on Your Teacher Tasks For A Stress-Free Spring BreakEpisode 186. 5 Teacher Tasks You Need to Do Before Spring BreakEpisode 4. Bouncing Back After A BreakEpisode 237. Do These 3 Things Before Winter Break To Make January EasierMentioned in this episode:Try the Teacher Approved Club free for 10 days and get one perfectly timed, research-backed strategy each month—plus support from Heidi and Emily to help you actually use it when it matters most. Start your free trial at https://secondstorywindow.net/trial

Jon looks at recently announced "Trump Accounts" for newborns, questionable maps, and Jon has strong opinions on the MN Paid Family Leave. Sam records himself calling the Star Tribune. Jon has questions about a new proposal for obtaining a MN Driver's License.See omnystudio.com/listener for privacy information.

Are you exhausted by your child's public meltdowns, your teenager's attitude, or your partner's sudden bad moods? What if I told you that their behavior has absolutely nothing to do with you?In this episode of the PAWsitive Choices Podcast, we're exploring the brain science and psychology behind why we get so triggered by other people's overflow. We are learning how to Q-TIP (Quit Taking It Personally) so we can stop reacting to the person and start responding to the underlying need.

UK Dentists: Collect your verifiable CPD for this episode here >>> https://courses.dentistswhoinvest.com/smart-money-members-club———————————————————————The clock is ticking on Making Tax Digital, and we're cutting through the noise with a straight-talking guide tailored for UK dentists. If you earn self-employment income as an associate or rental income from buy‑to‑lets, this is the moment to get clear on thresholds, timelines, and the smartest way to stay compliant without drowning in admin.We unpack the real meaning of “relevant income” and why HMRC looks at gross receipts, not profits, when deciding who must file quarterly. You'll learn exactly who is in scope right now at £50,000, why PAYE and dividends don't count for MTD for income tax, and how planned drops to £30,000 and £20,000 will bring many more clinicians into the regime. We also cover the penalty system you need to avoid: an initial grace year for late submissions, points that stack to a £200 fine, and a 24‑month compliance runway to reset. Most crucially, we explain the three‑year lock-in once you're on the system and how that affects timing if you're considering incorporation.From there, we move to tools and tactics. Prefer minimal effort? Ask your accountant about bridging software so you can send simple spreadsheets or bank statements each quarter and let them handle the submission. Want more control and real-time insight? We compare software options like FreeAgent, Sage, Xero and QuickBooks, highlighting free tiers, bank feeds, common setup pitfalls, and how live data can help you steer clear of the 60 percent effective rate band with timely pension and expense planning. We set out the dates that matter: Q1 runs 6 April to 5 July, with the first update due 7 August, and why registering before 5 April buys breathing space and avoids easy points.We finish with a practical checklist you can act on today: register for MTD or ask your accountant to do it, choose between full bookkeeping or a bridging route, and schedule your July data handover so the first submission lands on time. It's a clear, calm path through a complex change, built for busy clinicians who value certainty and time.———————————————————————Disclaimer: All content on this channel is for education purposes only and does not constitute an investment recommendation or individual financial advice. For that, you should speak to a regulated, independent professional. The value of investments and the income from them can go down as well as up, so you may get back less than you invest. The views expressed on this channel may no longer be current. The information provided is not a personal recommendation for any particular investment. Tax treatment depends on individual circumstances and all tax rules may change in the future. If you are unsure about the suitability of an investment, you should speak to a regulated, independent professional. Investment figures quoted refer to simulated past performance and that past performance is not a reliable indicator of future results/performance.Send a text

In Episode 212 we answer our March Instagram questions across a full spectrum of training and nutrition topics. We cover how we'd approach movement assessments with in-person clients, managing a reverse diet after significant fat loss, and our takeaways from Scott Stevenson's discussion on mind-muscle connection versus training to failure. Same-muscle-group supersets, rep tempo and the fatigue cost of slow negatives, exercise selection consistency, and the hypertrophy merit of low-rep cluster sets with heavy loads.On the nutrition side, we address the macros versus calories debate for body recomposition, how we handle missed rep or RIR targets mid-session, and what it realistically takes to improve abdominal definition at low body fat.Enjoy!Timestamps:00:01:40 - Why did you hop on TRT? Were you experiencing signs of low test? 00:16:30 - If you train a client in person, what kind of movement screen or assessment would you do? 00:20:14 - Post long diet (down 8kg and ~10% bf so far). Fats are at .6 per kg. Prefer increase in carbs for reverse diet? 00:25:44 - You mentioned Scott Stevenson discussing MMC versus failure. Can you elaborate your takeaways? 00:31:32 - When doing same muscle group supersets (iso to compound), should you take the first movement to failure or stop at 1-3 RIR? 00:35:59 - What's your perspective on rep tempo? Specifically the negative. I feel like slow negatives are super fatiguing…00:40:42 - Keep exercises the same or change them frequently? Why? 00:45:20 - What do you think of taking a heavy weight (Like 5-6 RM), and doing a buncha sets of 2-3 reps? Good for hypertrophy? 00:48:43 - You're def looking bigger and more jacked since TRT. What do you think? 00:54:34 - Order these in terms of systemic stress: Upper body lift, lower body lift, Zone 2 cardio, HIIT cardio. 00:58:55 - If you miss a rep or RIR target, do you prefer to drop weight or rest longer for the next set?01:01:55 - What is more important for body recomp, Macros or calories?01:05:56 - How to tighten the abdominal area? 39 years old. Female. 5'2. 112 lbs. 13% body fat but soft abs/no definition. No kids. Lifts 5x week. Cardio 3-4x. Work 1:1 with Aaron ⬇️https://strakernutritionco.com/nutrition-coaching-apply-now/Done For You Client Check-In System for Coaches ⬇️https://strakernutritionco.com/macronutrient-reporting-check-in-template/Paragon Training Methods Programming ⬇️https://paragontrainingmethods.comFollow Bryan's Evolved Training Systems Programming ⬇️https://evolvedtrainingsystems.comFind Us on Social Media ⬇️IG | @Eat.Train.ProsperIG | @bryanboorsteinIG | @aaron_strakerYT | EAT TRAIN PROSPER PODCAST

The Inspiring Life School Podcast helps quietly ambitious women get unstuck, build momentum and take aligned action without the mind drama.No fluff. No endless motivation hype. Just honest conversations and practical mindset coaching to help you finally follow through on the things that matter.Hosted by Frances Vidakovic - mindset and action coach, life strategist, author and creator of Inspiring Life Academy - this podcast will help you rewire your thinking, break out of self-sabotage, and step into your full potential with clarity and courage.

🧭 REBEL Rundown 🔑Key Points Try the coffee nap! Where you combine caffeine and a 30-minute nap to then have that boost energy and alertness by the time it kicks in.💤 Sleep isn’t optional—it’s crucial for memory, mood regulation, and physical recovery. It is fundamentally different from rest❌ Replacing sleep with caffeine isn’t effective and can have negative health impacts. Make getting enough sleep a priority🌞 Sunlight exposure is important for maintaining circadian rhythms and sleep quality. This applies even if you work as a nocturnist💡 Creating a personalized sleep system enhances quality and consistency. It gives you back control of a schedule that you may feel like is out of your hands.🧩 If you’ve tried these strategies and you’re still struggling, consider true sleep pathology (insomnia, shift work disorder, sleep apnea) and get help—this is not a “be tougher” problem.🩺 Better sleep isn’t just about feeling good; it’s directly tied to error reduction, patient safety, and longevity in EM/ICU careers. Click here for Direct Download of the Podcast. 👀Previously Covered and Related Content: REBEL Core Cast: Sleep HygieneREBEL MIND: Rest Is Not Sleep: The Seven Dimensions of True RecoveryRebellion in EM: Care For Yourself – Sleep HygieneFirst10EM: Some Evidence For Working Night ShiftsREBEL MIND: Dunning Kruger Effect 📝 Introduction Welcome to this episode of REBEL MIND, where MIND stands for Mastering Internal Negativity during Difficulty. Here we sharpen the person behind the practitioner by focusing on things that improve our performance, optimizing team dynamics and the human behavior that embodies the hidden curriculum of medicine. Today we are exploring the imperative topic of rest and why it’s not just about sleeping. The second of a two part series, hosted by Dr. Mark Ramzy with guests Dr. Maureen Aiad and Dr. Amil Badoolah, continue our discussion but this time on the multifaceted nature of sleep, how it serves as medicine and how we can use our tools deliberately to get more of it! Cognitive Question How would your clinical performance, patience with families, and long-term career sustainability change if you treated sleep as a non-negotiable clinical intervention rather than a flexible “nice-to-have”? 💤How is Sleep Different From Rest? 1. Rest reduces load; sleep repairs systemsWe previously talked about the 7 types of rest and you can check that out hereExamples of physical rest include: pausing tasks, stepping away from the monitor, taking a walk, stretching, breathing, journaling, connecting with a colleague. This lightens your cognitive/emotional burden.Sleep is fundamentally different in that it’s an active biologic process that helps:Consolidates memory and learning (yes, including the tough cases from last night).Regulates mood, impulse control, and emotional reactivity.Supports immunity, metabolic health, and cardiovascular function.Repairs tissue, replenishes neurotransmitters, and fine-tunes neural networks.You can have “rested but underslept” days (you took breaks but got 4 hours in bed), and “slept but unrested” days (you got hours, but all junk sleep). Both matter, but they are not interchangeable.2. Sleep architecture vs. “knocking out”True restorative sleep cycles through NREM and REM in predictable patterns.Alcohol, late caffeine, and fragmented nights may help you fall asleep faster but:Suppress REM.Shorten deep sleep.Increase awakenings and light sleep.The result: you technically slept, but your brain didn’t get the “software updates” it needed.Biology isn’t built for your scheduleCircadian rhythms were designed for light-day / dark-night cycles, not:10 pm–7 am ED shifts.24-hour calls.6 nights in a row followed by days.Your body can adapt partially, but not instantly and not perfectly. That’s why:You can feel “jet-lagged” even when you haven’t traveled.Sleep before and after nights feels odd and fragile.Recognizing that “this is biologically unnatural” is key: you’re not weak; you’re fighting physiology. 🏥How This Applies to the Emergency Department or ICU? Performance & safetySleep deprivation:Slows reaction time and increases error rate.Impairs risk assessment and complex decision-making.Drops your frustration tolerance with consultants, families, and staff.In both emergency medicine and critical care, that translates into:Anchoring on the wrong diagnosis.Missing subtle clinical changes.Snapping at a tech, nurse or resident and damaging team culture. Chronic health for chronic shift workLong-term sleep disruption is associated with:Hypertension, diabetes, obesity.Depression, anxiety, burnout.Arrhythmias (e.g., AFib) and increased stroke risk.Possibly increased all-cause mortality.You’re already in a high-stress, high-exposure specialty. Chronically poor sleep amplifies that risk profile and can end a career early—or make you miserable while you’re still in it.Culture of “heroics” vs. healthSkipping sleep to pick up extra shifts, late meetings, or “just one more note” is often praised.We rarely celebrate:The attending who says “no” to a 2 pm meeting post-nights.The resident who defends their blackout-curtains-and-earplugs routine. 🛏️Different Ways to Improve Your Sleep Clarify your “sleep non-negotiables”Decide how many hours you realistically need to function (e.g., 7–9 on off days, realistic blocks on nights).Treat those hours as you would a procedure time—blocked, protected, and respected.Use caffeine like a drug, not a reflexAim for ≤ 2 cups equivalent on most days.Avoid caffeine within 4–6 hours of your planned sleep time (remember: it can hang around up to 12 hours).Consider scheduling caffeine for:Early in the shift for alertness.Strategic “coffee naps” (see below), not late-night chugging.Respect alcohol’s impact on sleepRecognize that even small to moderate doses degrade sleep architecture.Avoid using alcohol as a “sleep aid”—you’ll fall asleep faster but sleep worse.If you do drink, separate it from bedtime and keep it modest.Optimize food and fluid timingHydrate consistently on shift, but taper fluids ~4 hours before bed to reduce nocturnal bathroom trips.Avoid heavy, spicy, or large meals within 2–3 hours of sleep to decrease reflux and discomfort.Plan a light, balanced “pre-sleep” snack if going to bed hungry keeps you awake.Move your body (but not right before bed)Regular exercise improves sleep depth and latency.Try to avoid intense workouts within 2 hours of bedtime.On shift: micro-movement (stairs, brisk walks between pods, quick stretch sessions) can help alertness without wrecking sleep later.Control light exposureMaximize sunlight or bright light after waking (even if that’s 3–4 pm after a night).Minimize bright light and screens before sleep:Dim lights.Use night mode/blue-light filters if you must scroll.For daytime sleep:Use blackout curtains, tinfoil, cardboard, or sleep masks.Yes seriously use tinfoil if you have to, we talk about it on the podcast episode!Aim for “I might be blind” darkness—so dark you can’t see your hand in front of your face.Dial in your sleep environmentCool room temperature (fan or AC if possible).White noise or sound machine to mask household/traffic noise.Earplugs and eye masks as needed.Bed used primarily for sleep (and sex)—not for charting, doom scrolling, or email.Strategic power napsKeep naps ≤ 20–30 minutes to avoid sleep inertia.Prefer early-afternoon or pre-night-shift naps.Coffee nap strategy:Drink a small coffee.Immediately lie down for a 20–30 min nap.Wake up as the caffeine kicks in, combining nap benefit + stimulant.Thoughtful melatonin useRemember melatonin is a hormone, not a vitamin gummy.Lower doses often work as well as (or better than) large OTC doses.Use it intentionally and intermittently, not as a crutch every night.Over-reliance may reduce your own natural production and its effectiveness over time.Build pre-sleep ritualsRepeated, calming habits signal your body it’s time to downshift:Warm shower, gentle stretching, or yoga.Guided breathing or body scan.Brief journaling or “brain dump” of tasks to get them out of your head and onto paper.Protect from pathologic patternsIf despite consistent effort you:Snore heavily, stop breathing, or gasp in sleep.Feel excessively sleepy driving home or at work.Cannot fall asleep or stay asleep for weeks to months.Consider evaluation for sleep apnea, insomnia, or shift-work sleep disorder with your physician or sleep specialist. ⏩Immediate Action Steps for Before/During/After Your Next Shift 1. **Before the Shift**: Plan a 20–90 minute nap before your first night shift (many clinicians find 3–5 hours earlier in the day is ideal).I treat ED and ICU shifts very differently. I always sleep 3-5 hours before my night shifts aiming for the full 5 (sometimes 6 or more) hours for my ED shifts because you always have to be “on”. Depending on the ICU I’m working in, I may have a bit more downtime so 3 to 5 hours is plenty.Set a caffeine plan: decide in advance when your last dose will be (e.g., none after 2–3 am if sleeping at 8–9 am).Tell your household, “This is my sleep block” and agree on a plan for kids, pets, deliveries, etc.On my calendar, I completely block off time called “Pre-call sleep” so no meetings can be scheduled and then put my phone in airplane mode2. **During the Shift** Hydrate early; taper fluids in the last 3–4 hours of your shift Eat something light but adequate; avoid “last-minute” heavy meals right before sign-out.Build in micro-breaks and movement: one or two short walks, a few stretches, even a quick stair run if safe.Get outside or near a window for a few minutes of light exposure if possible.3. **After the Shift**On the way home:Use sunglasses to reduce bright morning light if you’re aiming for sleep soon.Avoid “just checking” email or messages; shift into wind-down mode.At home:Do a brief, calming decompression (shower, light snack, 10–15 minutes of low-stimulation TV or reading).Make your room cold, quiet, and dark (blackout curtains, tinfoil/cardboard, white noise, fan).Put your phone on Do Not Disturb and physically place it away from the bed.On my calendar, I completely block off time called “Post-call sleep” so again no meetings can be scheduled and then I personally don’t just put my phone on Do Not Disturb but rather in airplane mode and WIFI OFF If you can’t sleep after ~20–30 minutes:Get out of bed, do something calming in dim light (breathing, gentle stretching, journaling).Return to bed when sleepy—this trains your brain to associate bed with sleep, not frustration. Conclusion Rest and sleep are both critical—but they’re not interchangeable. Rest helps you step out of the constant “on” of our jobs, while sleep is the biological intervention that restores your ability to show up safely and sustainably. Rest ≠ sleep. Rest reduces load; sleep repairs your brain and body. You need both, on purpose.As EM and ICU clinicians, we’re trying to perform formula-one-level medicine with engines that often only see half their maintenance. You won’t fix shift work. You can build a sleep system that respects your biology, your schedule, and your life at home.That system starts with valuing sleep, then prioritizing it, personalizing it, trusting the process when it’s imperfect, and actively protecting both your routine and your mindset. 🚨 Clinical Bottom Line Sleep is medicine. Shift work is biologically unnatural. Struggling does not mean you’re weak; it means you’re human fighting physiology. Use your tools deliberately. Caffeine, naps, light, food, movement, melatonin, and environment can be leveraged—or can quietly sabotage you. Build and defend a personalized sleep routine. Communicate it, normalize it, and protect it from casual encroachment. You can’t control every trauma, code, or admission—but you can control how seriously you take your own recovery. Your patients, your team, and your future self all benefit when you do. Further Reading Espie CA. The ‘5 principles’ of good sleep health. J Sleep Res. 2022 Jun; PMID: 34676592Solodar, J“Sleep hygiene: Simple practices for better rest.” Harvard Health, 31 January 2025 Link is HereSuni, E.“Mastering Sleep Hygiene: Your Path to Quality Sleep.” Sleep Foundation, 7 July 2025, Link is Here Meet the Authors Mark Ramzy, DO Co-Editor-in-Chief Cardiothoracic Intensivist and EM Attending RWJBH / Rutgers Health, Newark, NJ Maureen Aiad, DO Assistant Professor of Emergency Medicine NYU Grossman Long Island School of Medicine, New York Amil Badoolah, DO Assistant Professor of Emergency Medicine NYU Grossman Long Island School of Medicine, New York REBEL Core Cast 119.0 – Sleep Hygiene REBEL Core Cast 119.0 – Sleep Hygiene Click here for Direct Download of ... Read More The post REBEL MIND – How to Sleep When the World Says You Can't appeared first on REBEL EM - Emergency Medicine Blog.

If your core feels tight all the time… that's not strength. If you're constantly sucking in your stomach, clenching your abs, gripping your glutes, or holding your pelvic floor “just in case” — this episode is for you. So many women have been taught that strength means tension. Brace harder. Squeeze more. Engage constantly. Never relax. But what if that gripping is actually the reason you still feel weak… leak when you run… or experience pelvic pain? In this episode, we're breaking down the difference between true core strength and chronic tension — and why tight does not equal strong. In This Episode, We Cover: Why women often confuse tension with strength The cultural conditioning behind “suck it in” fitness cues How over-bracing impacts the diaphragm and pelvic floor The connection between gripping, leaking, and prolapse symptoms Why a tight pelvic floor can still be dysfunctional What real, functional strength actually feels like How breath and pressure management build resilient core stability Simple ways to stop over-gripping and start building true strength The Truth About Pelvic Floor & Core Strength Your pelvic floor is not meant to be clenched all day. It should contract and relax. Lift and descend. Respond and adapt. When your body only knows how to grip, it loses its ability to coordinate under real-life load — like running, lifting, jumping, or even laughing. True strength is: Breathable Responsive Adaptive Coordinated Not rigid. Not braced at 100%. Not constantly “on.” If You've Experienced… Leaking during workouts Pelvic pressure or heaviness Pain with intimacy Constipation Low back tension A core that feels tight but unstable …this episode will help you understand what may actually be happening. Why This Matters You can't build power on top of dysfunction. Before adding more crunches, heavier weights, or more kegels — your body needs coordination. That's exactly what we focus on inside RESTORE, my 12-week pelvic floor and core rebuilding program inside the Pelvic Floor, Core & More app. We start with breath. Rebuild pressure management. Restore true core control. Then layer strength safely and progressively. Because strong women don't need to grip harder. They need to move smarter. If this episode resonated with you, share it with a friend who thinks tight = strong

What is Asturian cider? Asturian cider (sidra natural) is a traditionally fermented apple cider from Asturias, Spain, served through a high pour (escanciado) and shared socially in small servings called culines. This episode is part of the Cider Chat archive documenting global cider traditions and producers since 2015. In this epic replay from Season 2 of Cider Chat, Ria Windcaller traveled to Asturias, Spain, and sat down with Anzu Fernández, international delegate for La Sidra magazine and a lifelong ambassador of traditional Asturian cider culture.   Find the full show notes for this episode at CiderChat.com Episode 493: https://ciderchat.com/podcast/493-cider-as-a-sport-sidra-in-asturias/ Listen to Episode 493 of Cider Chat® wherever you get your podcasts and don't forget to subscribe so you never miss what's coming next in Ciderville. Prefer to watch? Find Cider Chat on YouTube for more cider stories, orchard adventures, and global cider culture.

Nick and Jonathan delve into the viability of Kyler Murray as a low-cost quarterback option for the Cleveland Browns while debating the organization's long-term strategy under Andrew Berry. They examine the pitfalls of transition years and the allure of unknown prospects compared to veteran continuity. The conversation includes a heated exchange with a caller regarding player value and the team's history of roster management. 01:00 - Kyler Murray Browns Fit 04:10 - Transition Year Frustrations 08:15 - Andrew Berry Roster Strategy

Ken Little: Bridging Engineering and BusinessToday, we're tackling one of the most expensive and underestimated problems in modern organizations: the communication gap between technical professionals and nontechnical leaders. I'm joined by Ken Little, SVP of Engineering, to explore where engineers most often struggle with nontechnical audiences, how to make complex ideas understandable to business-minded leaders so they can make better decisions, and what happens when that translation breaks down. We also dig into how organizations can build stronger communication muscles, and how engineers can move from explaining problems to making recommendations.To learn more about Ken, visit https://www.linkedin.com/in/kennethllittle/__TEACH THE GEEK (http://teachthegeek.com) Prefer video? Visit http://youtube.teachthegeek.comGet Public Speaking Tips for STEM Professionals at http://teachthegeek.com/tips

In this episode, Evan H. Hirsch, MD, and Larisa Sharipova, MD, explore how bioenergetics can support people with long COVID and chronic fatigue syndrome by identifying and correcting energetic imbalances before they become biochemical and physical disease. Larisa Sharipova is a Holistic Health Practitioner, Bioenergetic Specialist, and women's lifestyle doctor who helps women reclaim their health, balance their lives, and thrive naturally. A trained medical doctor and former OBGYN, she now blends Western medicine with holistic healing, bioenergetics, and lifestyle medicine to address the real root causes of hormonal imbalance, fatigue, and accelerated aging.  She is the Amazon bestselling author of ''Listen to Your Body and Regain Your Health'' and the founder of Holistic Expert. As co-host of the Harmonic Alignment Podcast, Larisa explores the new frontier of energy medicine, bridging Western medicine and quantum physics to offer grounded, practical tools women can use right away. In this episode, you'll learn: What bioenergetics actually means and how energy functions inside biological systems How heart rate variability, brain waves, MRI technology, and quantum biology demonstrate measurable energetic activity in the body How energetic incoherence can precede physical symptoms How voice scans and bioenergetic assessments detect organ and emotional imbalances How energetic correction may support detoxification, hormonal balance, and mitochondrial function When to combine bioenergetics with functional lab testing and conventional medicine Why some chronic fatigue cases may require energetic correction before physical healing can fully occur To learn more about Larisa Sharipova, MD, or work with her directly: Website: https://dr-larisa.com Schedule a call: https://harmonicalignment.co/larisa-calendar Book: ''Listen to Your Body and Regain Your Health'' https://a.co/d/0aCgLAUN . We help you resolve your Long Covid and Chronic Fatigue (ME/CFS) by finding and fixing the REAL root causes that 95% of providers miss. Learn about these causes and how we help people like you, Click Here. Do you have fatigue, brain fog, shortness of breath, muscle pain, or other strange symptoms? You might have Long Covid. Take our free quiz to find out if Long Covid is behind the mystery symptoms you're experiencing, Click Here. For more information about Evan and his program, Click Here.   Prefer to watch on Youtube? Click Here.   Please note that any information in this episode is for educational purposes only and does not constitute medical advice.  

Today's devotional is read by author and host of Eleven2one, Janice Wolfe. Taken from the heartfelt pages of her book, What Do I Have to Lose? Losing My Way and Finding God's, this transformative Bible study is rooted in the 100 occurrences of the Greek word for "lose" from Mark 8:35 and offers powerful insights to deepen your walk with the Lord.  To listen to the full audio book visit Audible.com. Prefer to read? Grab a printed copy at CausewayMediaGroup.com or the Kindle version on Amazon. Tune in to Faith Music Radio each Wednesday at 12:30 PM central time for this uplifting audio reading of What Do I Have to Lose? Losing My Way and Finding God's. You may also subscribe to Eleven2One on your favorite podcast platform for a weekly Wednesday download of the devotional.

On today's disturbingly dirty episode of Quick Charge, Elon Musk is undoing nearly two decades of decarbonization by pumping out massive amounts of pollution to keep his xAI and Grok slop-machines rolling – and hurting some of America's most vulnerable communities at the same time. Tesla's troubles with pollution and carbon don't end there, either – two of company's biggest buyers of carbon credits are taking their business elsewhere, and the damage to Tesla's bottom line could be in the billions. Plus: it's a record month for Hyundai IONIQ 5 sales, electric semi trucks really do save fleets money, and some cool pictures of Volvo heavy equipment assets getting topped off at the Circle K! And, before you ask: NO! The irony is not lost on me ... but I didn't waste any water making the image, I just copy/pasted it in (he said, defensively). Source Links Tesla loses Toyota and Stellantis from its EU CO2 pool, taking billions with them Elon Musk's xAI is undoing Tesla's climate work all in the name of AI slop Hyundai bucks the trend as IONIQ 5 EV sales surge 33% in record-setting February Real-world test: electric semi trucks can save fleets nearly $160,000 per truck Where do you charge your wheel loader? Try the Circle K! Prefer listening to your podcasts? Audio-only versions of Quick Charge are now available on Apple Podcasts, Spotify, TuneIn, and our RSS feed for Overcast and other podcast players. New episodes of Quick Charge are (allegedly) recorded several times per week, most weeks. We'll be posting bonus audio content from time to time as well, so be sure to follow and subscribe so you don't miss a minute of Electrek's high-voltage podcast series. Got news? Let us know!Drop us a line at tips@electrek.co. You can also rate us on Apple Podcasts and Spotify, or recommend us in Overcast to help more people discover the show. If you're considering going solar, it's always a good idea to get quotes from a few installers. To make sure you find a trusted, reliable solar installer near you that offers competitive pricing, check out EnergySage, a free service that makes it easy for you to go solar. It has hundreds of pre-vetted solar installers competing for your business, ensuring you get high-quality solutions and save 20-30% compared to going it alone. Plus, it's free to use, and you won't get sales calls until you select an installer and share your phone number with them.  Your personalized solar quotes are easy to compare online and you'll get access to unbiased Energy Advisors to help you every step of the way. Get started here.

The Dipsh*t Files #217 with the Script KeepersToday's Show:This week we get right back into the story of Kurt Cobain. Mrs. Script Keeper introduces a number of interesting characters in and around Kurt's life, and goes over some key details that paint a different story than the one we've grown to know over the last 30+ years.Thank you for listening! Have the best Wednesday possible!Visit us for more episodes of SKATCAST and other shows like SKATCAST presents The Dave & Angus Show plus BONUS material at https://www.skatcast.com Watch select shows and shorts on YouTube: bit.ly/34kxCneJoin the conversation on Discord! https://discord.gg/XKxhHYwu9zFor all show related questions: info@skatcast.comPlease rate and subscribe on iTunes and elsewhere and follow SKATCAST on social media!! Instagram: @theescriptkeeper Facebook: https://www.facebook.com/scriptkeepersATWanna become a Patron? Click here: https://www.patreon.com/SkatcastSign up through Patreon and you'll get Exclusive Content, Behind The Scenes video, special downloads and more! Prefer to make a donation instead? You can do that through our PayPal: https://paypal.me/skatcastpodcast Hosted on Acast. See acast.com/privacy for more information.

A question from the Lord with an interesting insight. (Fabulous, fabulous story.)

We sat down with Anthony Scavo over cocktails to break down his career trajectory and the strategy behind Basis Industrial's recent $84.75 million acquisition of a 42-building industrial portfolio in Hialeah.Anthony brings decades of institutional weight to the table. After growing up in Brooklyn and attending NYU, he spent 26 years alongside his father overseeing construction for the LeFrak Organization. Since joining Basis Industrial in 2021, he has helped pivot the firm toward a highly lucrative niche: small bay warehouses.In this episode, we cover:The transition from the LeFrak Organization to Basis Industrial.The specific economic tailwinds driving the small bay warehouse market.The thesis behind their massive $84.75 million Hialeah portfolio acquisition.How Basis scaled to over 77 properties and 12 million square feet of industrial space.Basis is actively looking for new opportunities, making this required listening for anyone operating in the South Florida industrial market.Connect with usWant to dive deeper into Miami's commercial real estate scene? It's our favorite topic and we're always up for a good conversation. Whether you're just exploring or already making big moves, feel free to reach out at info@builtworldadvisors.com or give us a call at 305.498.9410. Prefer to connect online? Find us on LinkedIn or Instagram - we're always open to expanding the conversation. Ben Hoffman: LinkedIn Felipe Azenha: LinkedIn We extend our sincere gratitude to Büro coworking space for generously granting us the opportunity to record all our podcasts at any of their 8 convenient locations across South Florida.

Journals play an important role for academics. They disseminate new knowledge and separate good from bad research. They also signal competencies, reputation, and standing. Publishing in certain journals often means your work is more rigorous. It may also mean your work is more visible and gets cited more often. Plus, having your work appear in certain journals can be an important prerequisite for career advancement and it can literally affect your salary. Yet of course, these different functions can be evaluated in different ways. Not all journals score equally high or low on all these different aspects. Determining which journal is "good" or "top" becomes a complicated multidimensional riddle. We decided to ask Jason Thatcher. He is one of the most prolific authors of journal papers our field has ever seen and he has served as reviewer or editors on most if not all of them. We try to develop a simple 2x2 decision tool that helps authors identify journals that are both rigorous and prestigious, that are good for the research we do and good for our careers as well. References AIS College of Senior Scholars. (2023). Senior Scholars' List of Premier Journals. Association for Information Systems, https://aisnet.org/page/SeniorScholarListofPremierJournals. Lowry, P. B., Moody, G. D., Gaskin, J., Galletta, D. F., Humpherys, S. L., Barlow, J. B., & Wilson, D. W. (2014). Evaluating Journal Quality and the Association for Information Systems Senior Scholars' Journal Basket Via Bibliometric Measures: Do Expert Journal Assessments Add Value? MIS Quarterly, 37(4), 993–1012. Dennis, A. R., Valacich, J. S., Fuller, M. A., & Schneider, C. (2006). Research Standards for Promotion and Tenure in Information Systems. MIS Quarterly, 30(1), 1–12. Abbasi, A., Parsons, J., Pant, G., Liu Sheng, O. R., & Sarker, S. (2024). Pathways for Design Research on Artificial Intelligence. Information Systems Research, 35(2), 441–459. Rai, A. (2017). Editor's Comments: Seeing the Forest for the Trees. MIS Quarterly, 41(4), iii–vii. Recker, J. (2020). Reflections of a Retiring Editor-in-Chief. Communications of the Association for Information Systems, 46(32), 751–761. Agarwal, R., & Lucas Jr., H. C. (2005). The Information Systems Identity Crisis: Focusing on High-Visibility and High-Impact Research. MIS Quarterly, 29(3), 381–398. Applegate, L., & King, J. L. (1999). Rigor and Relevance: Careers on the Line. MIS Quarterly, 23(1), 17–18. Rai, A. (2017). Editor's Comments: Avoiding Type III Errors: Formulating IS Research Problems that Matter. MIS Quarterly, 41(2), iii–vii.

The SKATCAST Show #216 with The Script KeeperToday's Skit-SKATs:[ Talking Pets | 1:41 ] - "The Bellzzz" - Drok and friends deal with a new problem Kitty has.[ Lilac City Nightmare Band | 7:17 ] - "DIY MFer" - The LCNB boys are busy recording their own album. It's also a nice night for acoustic.[ Lilac City Nightmare Band | 15:47 ] - "Selling Out?" - The LCNB is offered is a deal that is hard to refuse, but also stupid to take.[ Corporate C*nts | 24:14 ] - "Sweet Goop" - With powerful enough marketing (and a strong enough desire for a sweet beach house), one can sell anything, even glowing goop. I'd probably eat it.Thank you for listening!!! What a ride so far!!! Happy Tuesday!!!Visit us for more episodes of SKATCAST and other shows like SKATCAST presents The Dave & Angus Show plus BONUS material at https://www.skatcast.com Watch select shows and shorts on YouTube: bit.ly/34kxCneJoin the conversation on Discord! https://discord.gg/XKxhHYwu9zFor all show related questions: info@skatcast.comPlease rate and subscribe on iTunes and elsewhere and follow SKATCAST on social media!! Instagram: @theescriptkeeper Facebook: https://www.facebook.com/scriptkeepersATWanna become a Patron? Click here: https://www.patreon.com/SkatcastSign up through Patreon and you'll get Exclusive Content, Behind The Scenes video, special downloads and more! Prefer to make a donation instead? You can do that through our PayPal: https://paypal.me/skatcastpodcast Hosted on Acast. See acast.com/privacy for more information.

Hello, Protagonists!Welcome to another episode of the Creative, Inspired, ALIVE podcast—where we go behind the scenes with the storytellers shaping our culture.Our next guest, Cynthia D'Aprix Sweeney, is the author of the instant New York Times bestselling novels The Nest (named a best book of the year by People, the Washington Post, and NPR) and Good Company (a Read with Jenna selection). Her work has been translated into more than 28 languages, and The Nest is in development as a limited series with AMC Studios. Sweeney holds an MFA from the Bennington Writing Seminars.Today, we talk about:* writing distinct and integrated POVs,* finding the right pace of writing for yourself,* how we sometimes scare ourselves out of taking risks in writing,* the truth of having work developed into a TV series,* and so much more!xo,Joanna & Evelyn

Sem condenar diretamente o ataque a território iraniano, o MNE esclarece que preferia a via diplomática. Paulo Rangel garante que a oposição foi consultada pelo executivo sobre utilização das Lajes.See omnystudio.com/listener for privacy information.

March brings higher energy and lower stamina, and suddenly your classroom feels louder, messier, and harder to manage. In this episode, we explain why spring classroom management isn't about cracking down harder, but about rebuilding structure. We walk through four common spring trouble spots: transitions, messiness, chattiness, and behavior outside the classroom. We also share practical ways to reset expectations so the environment does more of the work for you. The goal is simple: create structure now so your day requires less of you tomorrow.Prefer to read? Grab the episode transcript and resources in the show notes here: https://www.secondstorywindow.net/podcast/spring-classroom-management-headaches/Resources:Pre-order Structure and SparkStain StrikerClay MooJoin The Teacher Approved ClubConnect with us on Instagram @2ndstorywindowShop our teacher-approved resourcesJoin our Teacher Approved Facebook groupLeave a review on Apple PodcastsLeave a comment or rating on SpotifyRelated Episodes to Enjoy:Episode 48. How to Make Classroom Transitions Simple With Clear Beginnings and EndingsEpisode 49. Rapid Classroom Transitions: How to Save 45 Hours a YearEpisode 50. 3 Guidelines to Make Classroom Transitions Work Smarter Not HarderEpisode 119. Chatty Class Management: 5 Ways to Handle a Talkative ClassMentioned in this episode:Try the Teacher Approved Club free for 10 days and get one perfectly timed, research-backed strategy each month—plus support from Heidi and Emily to help you actually use it when it matters most. Start your free trial at https://secondstorywindow.net/trial

Dust doesn't just cloud water; it wrecks schedules, clogs filters, and turns simple visits into expensive marathons. We break down three battle-tested ways to remove heavy dirt loads without touching the customer's equipment, so you protect pumps, save water, and finish faster. First, we put the Advantage Portivac 2.0 under the microscope. With a 1.5 HP pump and a 150 sq ft cartridge, this cart lets you vacuum to waste or safely recirculate back into the pool, keeping thousands of gallons on site across a season. It even doubles as temporary circulation when a pad is down. We outline real-world pros like strong, steady suction and huge dirt capacity, along with limits in leaf-heavy mixes and the light setup time you should plan for.Next, we turn a leaf-focused vacuum system into a dust killer. The Bottom Feeder or Shrimp now supports a cartridge assembly that filters down to 20 microns. Start at 50 sq ft for about two pounds of dirt, or stack to 100 sq ft to tackle dust-storm loads over four pounds. The threaded mount makes swapping from cartridge to bag fast, so crews can move from silt to leaves without breaking stride. American-made Unicel media brings durability and predictable performance shift after shift.Finally, meet the Vac Daddy with its vacuum-to-waste adapter, a compact setup that punches above its weight. Connect your discharge hose, set it on the deck, and move fine dirt out of the pool at remarkable speed without running through a filter. It runs corded or on a battery pack for tough access jobs, and while it's not built for huge leaf piles, it shines for dust with minimal gear and maximum agility.Choose Portivac for high-capacity recirculation and backup circulation, pick the Bottom Feeder cartridge kit to add true dust capture to your vacuum workflow, or deploy the Vac Daddy adapter when fast vac-to-waste is your edge. Prefer a discount? Call Advantage Manufacturing and mention David Van Brunt. If you want more practical tactics and support, subscribe, share the show with a fellow pro, and leave a review to help others fSend a textSupport the Pool Guy Podcast Show Sponsors! HASA https://bit.ly/HASAThe Bottom Feeder. Save $100 with Code: DVB100https://store.thebottomfeeder.com/Try Skimmer FREE for 30 days:https://getskimmer.com/poolguy Get UPA Liability Insurance $64 a month! https://forms.gle/F9YoTWNQ8WnvT4QBAPool Guy Coaching: https://bit.ly/40wFE6y

The Inspiring Life School Podcast helps quietly ambitious women get unstuck, build momentum and take aligned action without the mind drama.No fluff. No endless motivation hype. Just honest conversations and practical mindset coaching to help you finally follow through on the things that matter.Hosted by Frances Vidakovic - mindset and action coach, life strategist, author and creator of Inspiring Life Academy - this podcast will help you rewire your thinking, break out of self-sabotage, and step into your full potential with clarity and courage.

On The Pilates Lounge Podcast, Katie Crane speaks with Lourdes, a Pilates teacher living with fibromyalgia, sharing her lived experience of chronic pain, fatigue, depression, and the long, often confusing road to understanding her body. Speaking from El Salvador, Lourdes brings honesty, humility, and deep compassion to this conversation — weaving together motherhood, injury, nervous system awareness, and the power of Pilates as a practice of reconnection rather than performance. This episode is part of Katie's ongoing fibromyalgia series, created to help Pilates professionals better understand the realities of this condition — so we can teach with more intelligence, empathy, and respect. We Explore: What fibromyalgia can feel like before diagnosis — and why it's often mistaken for depression or "just ageing" The overlap between chronic pain, fatigue, and emotional health Why pain often comes first — and depression follows Living, parenting, and teaching Pilates while managing fibromyalgia Why reconnection, not intensity, is the foundation of sustainable movement How mat work, breath, and props support safety and self-trust Why listening to the body matters more than loading it The role of self-love, gentleness, and pacing in long-term health This Episode Is For: Pilates teachers working with clients living with fibromyalgia or chronic pain Movement professionals supporting fatigue-prone, nervous-system-sensitive bodies Teachers navigating pain, injury, motherhood, and long-term practice Practitioners ready to prioritise awareness, regulation, and connection over intensity A Moment That Landed: "When we're in pain, we disconnect. My first goal is always to reconnect — through breath, awareness, and listening." Fibromyalgia cannot be understood through muscles, joints, or exercise prescription alone. Lourdes' story reminds us that pain, fatigue, and depression are not failures of motivation or discipline — they are signals from a nervous system under load. This conversation reinforces why Pilates teachers must expand their lens to include nervous system regulation, emotional safety, fatigue management, and lived experience. When movement is rushed or driven by aesthetics, we reinforce harm. When it's paced, intelligent, and compassionate, Pilates becomes a lifelong ally.

The SKATCAST Network presents:Truck Driver Theater #80 by the Script KeeperToday's Skit-SKATs:This week it's almost an hour pure Marnia dumb! Comprised of six episodes from the "Monsters of Marnia" arc (starting at episode 129 of the SKATCAST Show thru episode 135).Thank you for listening!!! Be safe out there!!!Visit us for more episodes of SKATCAST and other shows like SKATCAST presents The Dave & Angus Show plus BONUS material at https://www.skatcast.com Watch select shows and shorts on YouTube: bit.ly/34kxCneJoin the conversation on Discord! https://discord.gg/XKxhHYwu9zFor all show related questions: info@skatcast.comPlease rate and subscribe on iTunes and elsewhere and follow SKATCAST on social media!! Instagram: @theescriptkeeper Facebook: https://www.facebook.com/scriptkeepersATWanna become a Patron? Click here: https://www.patreon.com/SkatcastSign up through Patreon and you'll get Exclusive Content, Behind The Scenes video, special downloads and more! Prefer to make a donation instead? You can do that through our PayPal: https://paypal.me/skatcastpodcast Hosted on Acast. See acast.com/privacy for more information.

"You have to get beyond the 'it's all about me' and get over that 'non-profit mindset' to realize you have a skillset worth an investment. Don't compromise on your value." - Catherine Angus We sit down with Catherine Angus, founder of the Hear You Go podcast, to talk about self-worth, education businesses, and standing firm on value.  In addition to the Hear You Go podcast, Catherine is an English language mentor, specializing in helping advanced speakers and teachers maintain fluency while silencing their inner critics. Through her 1:1 coaching and WILDE: The Listening Festival, she uses authentic global conversations to help learners build confidence and rediscover their love for the language.   In this episode, we chat about:  starting a podcast: confidence, doubt, and the unknown overcoming the 7-episode dropoff [where most podcasters quit] what perfectionism actually means why you want to be the tortoise, not the hare  social media toxicity and discovering what clients really want why passive income is like buying a lottery ticket using podcasts as a lead magnet, not a product how to pivot without abandoning your mission   *Prefer video? Watch the episode on YouTube.   FOR MORE FROM CATHERINE ANGUS: 1. Follow on Instagram 2. Her website 3. Her podcast, Hear You Go    SUPPORT US:

If you've been following this series on pain with intimacy, you now understand: ✔️ What might be causing your pain ✔️ How mental load and nervous system stress impact arousal ✔️ Why pushing through makes things worse ✔️ Practical rehab strategies to reduce tension Now let's talk about something we don't normalize enough: Supportive tools. Because using tools does not mean you're broken. It means you're intentional. In this final episode of the series, we're discussing the different tools and toys that can reduce pain, improve blood flow, calm guarding, and help you rebuild positive experiences in your body — safely and confidently. In This Episode, We Cover: Why tools can help retrain pain pathways The connection between blood flow, arousal, and pelvic floor relaxation How graded exposure reduces guarding Why friction (not failure) is often the problem The role of pleasure in nervous system regulation If pain continues, worsens, or feels deeply triggering, it's time to see a pelvic floor PT. The Bigger Reframe Tools are not a crutch. They are bridges. Bridges between pain and safety. Between guarding and openness. Between survival and pleasure. Pleasure is not indulgent. It is nervous system medicine. Want Structured Guidance? Inside the Pelvic Floor, Core & More App, there is a FREE Masterclass: From Pain to Pleasure that you can access inside the app here: https://pelvic-floor-core-more.passion.io/  Or if you want more guidance join my 12 wk RESTORE program, where we combine: Breathwork Nervous system regulation Mobility and downtraining Core and pelvic floor coordination Progressive strengthening So you're not guessing which tools to use — or when. (More on what this is and how to join below) And if your pain is complex, trauma-related, or persistent, 1:1 pelvic floor PT may be your best next step. You don't have to navigate this alone. This wraps our Pain with Intimacy series — but healing doesn't end here. Your body is not broken. It is layered. And layered healing is possible. ~ XO Dr. Des

The SKATCAST Network presents:The Just A Ride Podcast #175 with the Four BahsToday's Ride:Bear-Bah in the JAR! We warned you! The Getch returns to the SKATCAST Network and sits at the JAR table to discuss his upcoming podcast "It's A Getch Thing!" coming to the SKATCAST Network. We also discuss people eating, AI's first attempt and doxing/destroying a human it doesn't like, life after policing and Shaiden teaches us about fairies or something. It's fun! This is the Script Keeper by the way, I write these and I just noticed I often write them like someone else is writing them. That's kind of weird. Like I would let Tim write this shit or something. I've also written over 1,000 of these description and I guess I felt like typing a bunch of shit that makes no sense here for reasons that I can't explain. Anyway, that was weird.Here is that link to the weird AI story Mrs. Script Keeper brings up.https://www.youtube.com/watch?v=BHol8DA2dJ0And here's a link to some sweet Getch merch!https://getch-things.myshopify.com/Thank you for listening! Happy Friday!Visit us for more episodes of SKATCAST and other shows like SKATCAST presents The Dave & Angus Show plus BONUS material at https://www.skatcast.com Watch select shows and shorts on YouTube: bit.ly/34kxCneJoin the conversation on Discord! https://discord.gg/XKxhHYwu9zFor all show related questions: info@skatcast.comPlease rate and subscribe on iTunes and elsewhere and follow SKATCAST on social media!! Instagram: @theescriptkeeper Facebook: https://www.facebook.com/scriptkeepersATWanna become a Patron? Click here: https://www.patreon.com/SkatcastSign up through Patreon and you'll get Exclusive Content, Behind The Scenes video, special downloads and more! Prefer to make a donation instead? You can do that through our PayPal: https://paypal.me/skatcastpodcast Hosted on Acast. See acast.com/privacy for more information.

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

Sign up for Practi, a new platform that helps law firms use subscription billing.Here are the top 5 takeaways from this episode:1. Fractional GC Model Fills a Critical Gap. Rachel discovered the fractional general counsel model while working at PEAK6, where the legal department provided services to multiple operating businesses that couldn't afford or didn't need full-time counsel. This experience showed her how valuable legal services can be when delivered in a flexible, accessible way - a model she now offers through Saturday Legal with flat monthly fees.2. Subscription Billing Aligns Incentives Better Than Hourly. The billable hour creates friction - clients withhold information to avoid running up the meter, and lawyers lack context on the business. With flat monthly fees, clients get unlimited access for strategic advice and routine legal work, eliminating the anxiety of watching the clock and enabling lawyers to add value beyond just legal tasks.3. The Billable Hour Wasn't Always the Standard. Before the billable hour became prevalent in the early 1900s, lawyers commonly used annual retainers - essentially the original subscription model. The shift back to flat fees and subscriptions isn't revolutionary; it's returning to a model that better serves both clients and lawyers.4. Subscription Practice Enables Work-Life Integration. Rachel can operate at a sophisticated level while maintaining autonomy - chaperoning her son's field trip, working out, having dinner with her kids, then logging back on after bedtime. The predictable revenue from subscriptions also allowed her to hire two employees and avoid the feast-or-famine cycle that plagues many solo practitioners billing hourly.5. Specialization Makes Subscriptions Even More Viable. While Rachel offers broad corporate counsel services, the subscription model also works for specialists (IP, tax, employment law, etc.) because it's easier to productize services and create efficiencies when you're deeply focused on a specific niche rather than being a generalist.__________________________Want your question to be answered on a future show? Fill out this short survey.Check out Saturday Legal.Sign up for Paxton, my all-in-one AI legal assistant, helping me with legal research, analysis, drafting, and enhancing existing legal work product.Get Connected with SixFifty⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, a business and employment legal document automation tool.Sign up for ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Gavel⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, an automation platform for law firms.Visit ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Law Subscribed⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ to subscribe to the weekly newsletter to listen from your web browser.Prefer monthly updates? Sign up for the Law Subscribed Monthly Digest on LinkedIn.Check out ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Mathew Kerbis'⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ law firm ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Subscription Attorney LLC⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠.Want to use the subscription model for your law firm? Click here to sign up for a new platform that helps law firms use subscription billing. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.lawsubscribed.com/subscribe

In Compassionate Kindness, we begin where all healing begins, in the quiet sanctuary of the heart. Gently arriving there, we soften and remember the steady pulse of love that lives within us. From this tender space, you are invited to bring to mind an “other” — a beloved friend, a colleague, a circle of people — and to surround them with compassionate love and luminous light. No fixing. No striving. Simply blessing. Then, in a sacred turning, that same compassion is offered inward. The love you so freely extend becomes the love that restores you. And finally, the boundaries dissolve. From me and you… to we… to One. Resting in the awareness of a single divine essence that knows only life, only love. Together, we bow inwardly to that holy presence and offer our blessing to all of life. Want more meditations and early access? Join me on Patreon for exclusive content and bonuses: patreon.com/theoptimisticmeditator. Prefer a one-time way to support? Visit buymeacoffee.com/tammylorraine. Your support means the world!

If you have a freebie, a ManyChat automation, and an email list that's slowly growing, but still isn't driving any sales, this episode walks you through the EXACT (simple!!!) email sequence you need to be sending to every person joining your list.I'm breaking down how to create a simple email funnel that turns new subscribers into buyers without emailing every day. You'll learn what to send immediately after someone downloads your freebie, how to clearly deliver and direct them for quick wins, and how to build belief through strategic emails that address objections and reframe common misconceptions about funnels and automation.Then I'll walk you through how to make a clear, calm sales invitation that feels aligned and effective.Prefer a more done-for-you option? Grab my plug-and-play email sequence templates & write all of your emails in just ONE day

The SKATCAST Network presents:The Dave and Angus Show #213This week's crap:[ Creepiest Sh*t | :40 ] - "Volume 12" - Dave and Angus once again star in Creepiest Sh*t, and as the season winds up, questions are answered (maybe), and things are given closure (possibly) and monsters and what not. It's another week of Dave and Angus in a super-sized Skit-SKAT!Thank you for listening! Happy Wednesday!Visit us for more episodes of SKATCAST and other shows like SKATCAST presents The Dave & Angus Show plus BONUS material at https://www.skatcast.com Watch select shows and shorts on YouTube: bit.ly/34kxCneJoin the conversation on Discord! https://discord.gg/XKxhHYwu9zFor all show related questions: info@skatcast.comPlease rate and subscribe on iTunes and elsewhere and follow SKATCAST on social media!! Instagram: @theescriptkeeper Facebook: https://www.facebook.com/scriptkeepersATWanna become a Patron? Click here: https://www.patreon.com/SkatcastSign up through Patreon and you'll get Exclusive Content, Behind The Scenes video, special downloads and more! Prefer to make a donation instead? You can do that through our PayPal: https://paypal.me/skatcastpodcast Hosted on Acast. See acast.com/privacy for more information.

This wasn't just any state of the union speech. It was a generational reveal that ripped off the Democrats' mask. A shockingly good economic trend that shatters previous records. Government should take your child by force and transition them? And more. (Please subscribe & share.)

In this episode of Real Life Conversations for Christian Coaches, I sit down with Erica Vinson for a real, honest conversation about how technology has changed coaching—and how it hasn't.We've both been coaching long enough to remember dial-in phone lines, paper notes, and simple scheduling. Now we're navigating Zoom calls, AI tools, automated systems, and more options than ever before.But here's what I keep coming back to:Technology has changed how we coach. It has not changed why we coach.In this conversation, we talk through what we're seeing in the coaching space right now, including the shift from phone to video, how we think about scheduling and rhythms, and the growing presence of AI in coaching businesses.We're not offering a step-by-step guide or telling you what tools to use.We're inviting you into discernment.We talk about:How coaching platforms have evolved over timeWhy phone coaching still holds valueHow to use scheduling tools without losing marginWhat role AI can (and cannot) play in coachingCreating guardrails for your digital presenceWhy coaching remains an inside-out practiceIf you're feeling overwhelmed by all the tools available—or unsure how to move forward with clarity—this conversation is meant to steady you.You don't need every new tool.You don't need to panic about AI.You do need to stay present, grounded, and aligned with your calling.FREE RESOURCES:Listen to our sister podcast the REALIFE Practice Podcast on your Favorite Podcast AppTake the FREE Intro to Needs & Values AssessmentReady to discover what uniquely matters to YOU? CLICK HERE to take our FREE Intro to the Needs & Values Assessment.FREE Download: 4 Steps to Simplify Your CalendarReady to uncover more time on your calendar? This FREE download will help you remove what doesn't matter, so you have space for what does. Click here to get this FREE resource!OTHER RESOURCES:Check out our YouTube Channel!Prefer to watch AND listen? Check out our YouTube channel for the podcast episode on video! Make sure to subscribe so you get all the latest updates.My Book LinkTeresa's Book  Do What Matters, Live from Rest Not Rush is available. ! Banish busyness and discover a new way of being productive around what truly matters. Learn more at DoWhatMattersBook.com.LifeMapping ToolsWould you life to discover  Life Mapping tools to help you recognize and respond to God in your Story. Check out New Digital Downloads for personal or professional use  here https://www.onelifemaps.com/JOIN OUR COMMUNITY & CONNECT WITH ME:Become part of the FREE REALIFE Process® Community! Connect with Teresa and other podcast listeners, plus find additional content to help you discover your best REALIFE.Connect with your host, Teresa McCloy, on:Facebook - The REALIFE Process® with Teresa McCloyInstagram - teresa.mccloyLinkedIn - teresamccloyAbout Teresa McCloy:Teresa McCloy is the founder and creator of the REALIFE Process®, a framework designed to empower individuals and groups with the tools, training, and community needed for personal and professional growth. Through the REALIFE Process®, Teresa is on a mission to help others grow in self-awareness, establish sustainable rhythms, and enhance their influence and impact by integrating faith and work into their everyday lives. She lives with her husband of 42 years on their 5th generation family farm in central Illinois and enjoys great coffee, growing beautiful flower gardens and traveling as much as possible. About Erica Vinson:Erica Vinson helps clients walk through defining moments with confidence and courage enabling them to move forward in freedom and embrace fearless living. As an ACC Credentialed and Certified Professional Life & Leadership Coach, she uses wisdom from all 3 Centers of Intelligence to help clients gain deeper self-awareness and grow in relationships with others both personally and professionally. Erica is a certified REALIFE Process® Master Coach, an ©iEnneagram Motions of the Soul Practitioner, and has a certificate in Spiritual Transformation through the Transforming Center. She lives in the Metro East St. Louis area and enjoys spending quality time with friends and family, golfing, tennis, boating/water skiing, traveling, is a bit of a technology nerd and loves learning!

This episode of Cider Chat explores the growing Maine cider scene through Absolem Cider Company in Winthrop, a farm-based cidery helping shape New England's evolving cider identity. Located on a 60-acre farm in Winthrop, Maine, Absolem Cider Company is a cidery that expresses place, heritage apples, and hospitality. In this episode, Ria sits down with cider maker Zach Kaiser to explore how Absolem blends traditional inspiration with modern experimentation. From wild-foraged apples and native fermentations to wine-inspired co-ferments and Basque-style pours, Zach shares how Maine's apple history is shaping a new generation of New England cider. 00:00 Intro Cask Cider 00:06 Meet the Guest 01:27 How Cask Service Works 03:08 Why Absolem Uses It 04:07 Episode Roadmap 04:48 Ciderville News MOFGA Workshops 07:19 Listener Shoutout Chalkys Cider 08:29 Featured Chat Begins 09:23 Absolem Farm and Tasting Room 10:31 Where Winthrop Fits in Maine 12:42 Zachs Cider Origin Story 14:24 Founding Absolem Through COVID 16:34 Coferments and Wine Blends 18:13 Wend Wild Apple Cider 22:32 Fermentation Yeast and Malo 24:57 Beer Hybrids and Collabs 25:39 Flagship Ciders to Try 27:18 Sidra Style Foeder Program 28:40 Taproom Vibe and Winter Maine 29:21 Year Round Tasting Room 29:31 Local Bar Vibe 30:41 Lake Town Tourism 31:41 Cider As Experience 32:22 Ice Cider And Mistelle 32:47 Brandy Barrel Aging 34:36 Lodging And Visits 35:14 Signature Events Calendar 35:30 Bembel Fest Details 37:57 Anniversary And Collabs 39:30 Pressing And Production 41:36 Heating And Expansion 42:58 Five Year Vision 44:30 New England Cider Association 50:12 Wrap Up And Links Find the full show notes for this episode at CiderChat.com Episode 492: https://ciderchat.com/podcast/492-absolem-cider-company/ Listen to Episode 492 of Cider Chat® wherever you get your podcasts and don't forget to subscribe so you never miss what's coming next in Ciderville. Prefer to watch? Find Cider Chat on YouTube for more cider stories, orchard adventures, and global cider culture.

Kader Sakkaria on Translating Technical Complexity into Executive DecisionsKader Sakkaria is a senior technology and data executive who has led enterprise-scale transformation across financial services and complex global organizations. The work sits at the intersection of data, AI, and executive decision-making, helping organizations turn fragmented efforts into durable business value. In this episode, we focus on how technical leaders communicate with nontechnical audiences, how that skill evolves with seniority, and how to translate complexity into clear business decisions.To learn more about Kader, visit https://www.linkedin.com/in/ksakkaria/__TEACH THE GEEK (http://teachthegeek.com) Prefer audio? Visit http://podcast.teachthegeek.comGet Public Speaking Tips for STEM Professionals at http://teachthegeek.com/tips

In this episode, Evan H. Hirsch, MD, sits down with Gina Worful, MS, RD, to explore what your food cravings are really trying to tell you. Gina Worful, MS, RD, is the founder of the Mastering Mindfulness Institute. Originally trained as a registered dietitian, Gina saw that traditional diet approaches failed to create lasting change. She developed a mindfulness-based methodology that helps people build self-trust and transform their health from the inside out. Today, the Mastering Mindfulness Institute supports individuals, health professionals, and universities in applying this transformational approach. For many people navigating long COVID, chronic fatigue syndrome, and other chronic illnesses, food can feel like a battleground. You know what you "should" eat, but exhaustion, depletion, and overwhelm make it difficult to follow through. Gina explains why cravings are not a lack of willpower, but a signal from your nervous system that your body has shifted into protection mode. In this episode, you'll learn: Why cravings increase when your body feels depleted or unsafe   The difference between physical hunger and stress-driven urges   The 3 R method: Reconnect, Reset, Reflect   How early nervous system stress shows up in the body   Why food often becomes associated with safety, love, and comfort   How mindfulness builds self-trust instead of self-control   Why your relationship with food mirrors your relationship with life  Rather than fighting cravings or trying to overpower them, Gina shares how to approach them with curiosity and compassion. When you understand what your body is actually asking for, cravings can soften naturally and become a pathway toward deeper self-awareness and healing. To go deeper into Gina's work and learn her full method, access her free training and explore her programs here: Free Training: https://masteringmindfulness.institute/freetraining Website: https://www.masteringmindfulness.institute . We help you resolve your Long Covid and Chronic Fatigue (ME/CFS) by finding and fixing the REAL root causes that 95% of providers miss. Learn about these causes and how we help people like you, Click Here. Do you have fatigue, brain fog, shortness of breath, muscle pain, or other strange symptoms? You might have Long Covid. Take our free quiz to find out if Long Covid is behind the mystery symptoms you're experiencing, Click Here. For more information about Evan and his program, Click Here.   Prefer to watch on Youtube? Click Here.   Please note that any information in this episode is for educational purposes only and does not constitute medical advice.

Today's devotional is read by author and host of Eleven2one, Janice Wolfe. Taken from the heartfelt pages of her book, What Do I Have to Lose? Losing My Way and Finding God's, this transformative Bible study is rooted in the 100 occurrences of the Greek word for "lose" from Mark 8:35 and offers powerful insights to deepen your walk with the Lord.  To listen to the full audio book visit Audible.com. Prefer to read? Grab a printed copy at CausewayMediaGroup.com or the Kindle version on Amazon. Tune in to Faith Music Radio each Wednesday at 12:30 PM central time for this uplifting audio reading of What Do I Have to Lose? Losing My Way and Finding God's. You may also subscribe to Eleven2One on your favorite podcast platform for a weekly Wednesday download of the devotional.

On today's high-dollar episode of Quick Charge, Tesla is reeling from a $243 million judgement against it in a high-profile wrongful death case involving the company's Autopilot system, and has a hard time getting the relevant data to NHTSA. We've also got news that Waymo its expanding its L4 autonomous and driverless taxi operations into four new US cities across Florida and Texas, bringing its total to 10 compared to Tesla's 0 total cities with driverless electric vehicles in operation. Plus: the US Air Force has deployed the world's first portable 5MW nuclear reactor – which seems like the kind of thing we should all know about, you know? Source Links Tesla has to pay historic $243 million judgement over Autopilot crash, judge says Tesla avoids 30-day California sales suspension after dropping misleading ‘Autopilot' marketing Tesla sues California DMV to reverse ‘Full Self-Driving' false advertising ruling Tesla is having a hard time turning over its FSD traffic violation data Waymo adds 4 more cities to its robotaxi service, now 10 total (Tesla: still 0) Tesla admits it still needs drivers and remote operators — then argues that's better than Waymo Waymo founder trashes Tesla safety as Waymos illegally pass school buses World's first: US Air Force deploys portable nuclear power station Prefer listening to your podcasts? Audio-only versions of Quick Charge are now available on Apple Podcasts, Spotify, TuneIn, and our RSS feed for Overcast and other podcast players. New episodes of Quick Charge are (allegedly) recorded several times per week, most weeks. We'll be posting bonus audio content from time to time as well, so be sure to follow and subscribe so you don't miss a minute of Electrek's high-voltage podcast series. Got news? Let us know!Drop us a line at tips@electrek.co. You can also rate us on Apple Podcasts and Spotify, or recommend us in Overcast to help more people discover the show. If you're considering going solar, it's always a good idea to get quotes from a few installers. To make sure you find a trusted, reliable solar installer near you that offers competitive pricing, check out EnergySage, a free service that makes it easy for you to go solar. It has hundreds of pre-vetted solar installers competing for your business, ensuring you get high-quality solutions and save 20-30% compared to going it alone. Plus, it's free to use, and you won't get sales calls until you select an installer and share your phone number with them.  Your personalized solar quotes are easy to compare online and you'll get access to unbiased Energy Advisors to help you every step of the way. Get started here.

The SKATCAST Network presents:The Dipsh*t Files #175 with the Script KeepersToday's Show:This week Mrs. Script Keeper gives us the first of two episodes on the life and death of Nirvana's Kurt Cobain. The commonly known story about the circumstances around Kurt's death doesn't add up, and with a recently published book on the subject, there are apparently new dipsh*ts to uncover.Thank you for listening! Have a happy Wednesday!!!Visit us for more episodes of SKATCAST and other shows like SKATCAST presents The Dave & Angus Show plus BONUS material at https://www.skatcast.com Watch select shows and shorts on YouTube: bit.ly/34kxCneJoin the conversation on Discord! https://discord.gg/XKxhHYwu9zFor all show related questions: info@skatcast.comPlease rate and subscribe on iTunes and elsewhere and follow SKATCAST on social media!! Instagram: @theescriptkeeper Facebook: https://www.facebook.com/scriptkeepersATWanna become a Patron? Click here: https://www.patreon.com/SkatcastSign up through Patreon and you'll get Exclusive Content, Behind The Scenes video, special downloads and more! Prefer to make a donation instead? You can do that through our PayPal: https://paypal.me/skatcastpodcast Hosted on Acast. See acast.com/privacy for more information.

Hey Girl, How many times have you ignored your body because you felt guilty? Guilty for not working out. Guilty for wanting alone time. Guilty for not being in the mood. Guilty for resting. Guilty for saying no. Guilty for going to girls' night. Guilty for spending money on yourself. In this episode, we're unpacking something that quietly sabotages women's health more than almost anything else: guilt. Because guilt doesn't just live in your mind. It lives in your nervous system. It lives in your breath. It lives in your pelvic floor. And every time you override your truth to keep the peace, avoid discomfort, or prove your worth — your body absorbs it. In This Episode, We Explore: Why guilt is often conditioning — not intuition How guilt shows up in movement, intimacy, rest, and relationships The connection between guilt, stress, and pelvic floor tension Why pushing through pain (in workouts or intercourse) creates more dysfunction How guilt keeps women stuck in all-or-nothing cycles The physiological impact of chronic guilt on cortisol, breath, and muscle tone The difference between guilt and integrity Practical ways to stop betraying your body in small, daily moments Every time you override your truth, your body adapts to that pattern. And over time, that pattern becomes pain. Or leaking. Or pressure. Or disconnection. Small moments of honesty create safety in your body. And safety is where healing begins. How This Connects to RESTORE Inside RESTORE, we don't just strengthen your core and pelvic floor. We: Retrain your breath Regulate your nervous system Address tension patterns Teach you how to move without overriding your body Help you rebuild strength from safety — not guilt Because true strength is not forcing your body to comply. It's learning how to listen to it. If you're ready to stop betraying your body and start healing from integrity, you can learn more about RESTORE inside the Pelvic Floor, Core & More App. And if you need deeper, individualized support, 1:1 coaching or pelvic floor PT may be your next step. Guilt is loud. Truth is quiet. Healing happens when you learn to hear the quiet voice. ~ XO Dr. Des

Test prep doesn't have to mean packets or pressure. In this episode, we redefine test prep as helping students remember what they've already learned through simple, low-stakes retrieval practice and reflection. We share why traditional review often falls short, how strategies like brain dumps and quick recall prompts strengthen learning, and how starting small right now leads to calmer, more effective test prep later.Prefer to read? Grab the episode transcript and resources in the show notes here: https://www.secondstorywindow.net/podcast/test-prep-strategies-for-elementary-teachers/Resources:Powerful Teaching bookBulb subscriptionGrow lightJoin The Teacher Approved Club (power questions included!)Connect with us on Instagram @2ndstorywindowShop our teacher-approved resourcesJoin our Teacher Approved Facebook groupLeave a review on Apple Podcasts!Leave a comment or rating on SpotifyRelated Episodes to Enjoy:Episode 185. 6 Easy Tips for Simplifying Your Test Prep SeasonEpisode 183. 2 Smart Test Prep Strategies You Need to Use with Your StudentsEpisode 182. Boost Your Test Prep with These 3 Retrieval Practice ActivitiesEpisode 121. How to...

How'd you say in German: “I prefer to work in Germany.”?

Whether you need a wedding ring, anniversary ring, or you just want a ring that looks awesome, head over to https://www.thorum.com and code WAN to get 20% off a truly unique ring Get a Circuit Board skin for your device so dbrand can keep messing with Linus at https://dbrand.com/pcb Check out the Razer Blade series of laptops; perfect for work or pleasure: https://lmg.gg/wanrazerblade Game or work in comfort on a Razer Iskur V2: https://lmg.gg/wanrazeriskur Get a special deal on Private Internet Access VPN today at https://www.piavpn.com/LinusWan Purchases made through some store links may provide some compensation to Linus Media Group. Learn more about your ad choices. Visit megaphone.fm/adchoices

Resilience is not grinding harder. Resilience is staying. And most entrepreneurs don't fail because they're incapable. They fail because they leave too early. Emotionally. Mentally. Sometimes physically. So today we're talking about the two traits nobody brags about on Instagram: Resilience and patience. If you're in a slower season right now, or you feel like things are not moving as fast as you want… this episode is for you.   Time Stamps:   (0:15) A Talk You Need At Any Stage of Business (2:17) What Resiliency Really Is (4:08) Patience Is Trust Compounding Over Time (6:00) Fear Is A Compass (8:20) Clarifying Massive Action (9:52) Protect Your Mental Inbox (11:13) Your Top 3 Priorities ----------