Podcasts about EMC

In this month's EM Quick Hits Podcast, Amna Karabegovic joins us for an EMC² case of pediatric altered LOA and neurocritical care, Anand Swaminathan simplifies the high-risk management of pulmonary hypertension and right ventricular failure, and Brit Long reviews how to recognize and treat Cytokine Release Syndrome. Plus, Andrew Tagg on whether uncomplicated pediatric distal radius fractures need reduction, Jesse McLaren on a systematic approach to ECG interpretation in the bradycardic patient, and Sara Gray and Katie Lin return for Part 2 of “Coaching the EM Mind,” with practical strategies for managing stress and optimizing psychological safety on shift… Please consider a donation to ensure EM Cases continues to be high quality Free Open Access Medical Education here: https://emergencymedicinecases.com/donation/

Today I'm sharing why your future isn't created by one big moment, but by the ordinary patterns you repeat every single day.The way you think, the emotions you practice, the conversations you have with yourself, and the habits you keep returning to are quietly shaping your tomorrow. I talk about subconscious patterns, identity, emotional habits, and why lasting change begins from within, not by forcing the outside, but by changing the root that creates it.► ⁠⁠⁠⁠⁠⁠⁠⁠GET MY DIGITAL "SHIFT YOUR IDENTITY FROM THE INSIDE OUT" WORKBOOK US$37⁠⁠⁠⁠⁠⁠⁠⁠► ⁠TAKE YOUR INNER IDENTITY REFLECTION ASSESSMENT (FREE)⁠► ⁠⁠⁠⁠⁠⁠⁠⁠CONNECT WITH ME ON INSTAGRAM⁠⁠⁠⁠⁠⁠⁠⁠► ⁠⁠⁠⁠⁠⁠⁠⁠SUBSCRIBE TO MY YOUTUBE⁠⁠⁠⁠⁠⁠⁠⁠►⁠⁠⁠⁠⁠⁠ ⁠⁠APPLY TO WORK WITH ME 1:1⁠⁠⁠⁠⁠⁠⁠⁠► ABOUT ME:Welcome home everyone, I'm Connie. Many people spend years chasing the next goal, the next relationship, the next level of success, believing it will finally bring them the joy and fulfillment they've been searching for.From the outside, everything looks fine. But inside, something still feels missing. And my channel is here to help you reconnect the missing piece.For years, my work through You Can Be Healed has helped people heal emotional wounds and past trauma. Today that journey naturally evolved into EMC, my unique coaching method for helping people recognize and shift the subconscious identity patterns that quietly shape their emotions, relationships, success, finances, and everyday reality.Because the outer world is the reflection of your inner world. When your inner world shifts, your outer world must follow.Take this free EMC Inner Identity Reflection and discover the identity pattern you may be living from: https://emcglobalacademy.comLove,Connie►

GB2RS News Sunday the 12th of July 2026 The news headlines: Upcoming IARU Region 1 Conference WRTC 2026 is supported by the RSGB Have you enabled RSGB app notifications on your mobile device? The IARU Region 1 Conference is held every three years. The next one will be in September 2026 and will be hosted by the Austrian member society ÖVSV, which is also celebrating its centenary. Reports and proposals on a wide range of amateur radio topics are available from the conference website at conf.iaru-r1.org/documents  The scope includes the more regular topics such as band plans, spectrum matters, EMC and youth. This particular event will also consider updates for amateur radio development, operating and organisational matters. The RSGB has contributed several inputs. More about the event will be shared via the Society's comms channels and a future edition of RadCom. This year's World Radiosport Team Championship is taking place in East Anglia in the UK between the 8th and 13th of July. The RSGB is an official partner to the event and representatives from the Society have been on site throughout the week. The team has been supporting various activities including media liaison to raise awareness for WRTC 2026, the RSGB and amateur radio as a whole. You can see coverage of the event in a range of radio and online outlets including BBC Radio Shropshire, BBC News Online, Shropshire Live and the East Anglia Gazette. Links to the coverage are available on the RSGB website. Volunteers at the RSGB National Radio Centre have been busy welcoming competitors, referees, and supporters of WRTC to the Centre, with some enjoying time operating the GB3RS station. Keep up to date with more WRTC news, including the winners of the Championship, by visiting  wrtc2026.org Remember to enable RSGB app notifications on your mobile device to be the first to hear when the Society releases the latest edition of RadCom and its sister publications. You'll also be notified when new editions are added to the collection of back issues. For iOS devices, go to Settings then tap Apps. Locate the RSGB app in the list, and toggle to allow notifications. For Android devices, go to Settings, navigate to Notifications and then tap on App notifications. Locate the RSGB app in the list and toggle to allow notifications. If you haven't yet downloaded the RSGB app, get the links by going to rsgb.org/radcom RSGB General Manager Steve Thomas, M1ACB visited the RSGB National Radio Centre earlier this month. Steve was on site to deliver two awards to volunteers including the Norman Keith Adams prize and another for outstanding services to the Centre. The RSGB National Radio Centre Coordinator Martyn Baker, G0GMB is currently looking for friendly and enthusiastic radio amateurs to join this successful team. If you are able to volunteer a minimum of one, or preferably two, days per month, find out more about the role by visiting rsgb.org/volunteers  Don't forget to listen out for all of the stations that will be on the air today, the 12th, during the 145 Alive event. From 1100 to 1400UTC, many hundreds of operators will be on the air using 145MHz FM and 144MHz SSB. For more information, go to the 145 Alive Facebook page or email 145aliveuk@gmail.com Please send details of all your news and events to radcom@rsgb.org.uk  The deadline for submissions is 10am on Thursdays before the Sunday broadcast each week.    And now for details of rallies and events Today, the 12th, McMichael Radio and Electronics Rally is taking place at White Waltham Airfield, Maidenhead, SL6 3LW. The doors are open from 8am for traders and to the public from 9am. The entry fee for visitors is £4 per person. More details are available at mcmichaelrally.org.uk On Sunday the 19th, Lincoln Short Wave Club Summer Radio Rally will take place at The Festival Hall, Caistor Road, Market Rasen, LN8 3HT. The doors open at 10am and admission costs £3. This in an indoor event and ample free car parking will be available. For more information email m5zzz@outlook.com Amateur radio will feature at the Electromagnetic Field EMF 2026 event taking place from the 16th to the 19th of July at Eastnor Castle Deer Park, Eastnor, Ledbury, Herefordshire, HR8 1EN. AMSAT-UK, the British Amateur Television Club and the UK Microwave Group are teaming up to showcase satellite communications, amateur television and microwave radio experimentation. Throughout the weekend, they plan to demonstrate how radio amateurs communicate via satellites in both low-earth orbit and geostationary orbit, including contacts and digital amateur television via the QO-100 satellite. They also hope to demonstrate microwave operating techniques and experimental radio systems used on the higher amateur bands. Visitors can see live satellite ground-station setups, microwave equipment, an amateur television demonstration and learn how hobbyists build and operate space-related radio technology. Special event callsign GB26EMF will also be active on site. If you are attending the event, drop by to explore satellites, video over radio and the microwave spectrum. More details are available at amsat-uk.org Now the Special Event news To mark the centenary of the New Zealand Association of Radio Transmitters, special callsign ZL100C is on the air until Thursday the 6th of August. QSL via the Bureau and Logbook of the World. Special callsign DL0SOP is active until the 31st of July for the 68th edition of the Sea of Peace Award. QSL via Club Log's OQRS, Logbook of the World and eQSL. More information, including the rules and how to apply for an award, is available at dl0sop.darc.de Now the DX news Emil, DL8JJ is active as OX/DL8JJ/P from Greenland until Tuesday the 14th of July. He is operating CW from the main island, NA-018, as well as from Tasiilaq, NA-151. Aldir, PY1SAD is active as 8R1TM from Guyana until Sunday the 26th of July. He operates using CW, digital modes and SSB on the 160 to 6m bands as well as via satellite. QSL via Logbook of the World, eQSL, QRZ.com  or directly to Aldir's home call. Now the contest news Today, the 12th, the UK Microwave Group 24, 47 and 76GHz Contest runs from 0800 to 1700UTC. Using all modes on 24 to 76GHz frequencies, the exchange is signal report, serial number and locator. The GR2HQ Challenge and IARU HF Championship started at 1200UTC yesterday, the 11th, and ends at 1200UTC today, Sunday the 12th of July. Using CW and SSB on the 160 to 10m bands, where contests are permitted, the exchange is signal report and ITU Zone. The UK is in Zone 27. On Tuesday the 14th of July, the RSGB 432MHz FM Activity Contest runs from 1800 to 1855UTC. Using FM on the 70cm band, the exchange is signal report, serial number and locator. Also, on Tuesday the 14th of July, the RSGB 432MHz UK Activity Contest runs from 1900 to 2130UTC. Using all modes on the 70cm band, the exchange is signal report, serial number and locator. On Wednesday the 15th of July, the RSGB 80m Club Championship runs from 1900 to 2030UTC. Using SSB on the 80m band, the exchange is signal report and serial number. On Thursday the 16th of July, the RSGB 70MHz UK Activity Contest runs from 1900 to 2130UTC. Using all modes on the 4m band, the exchange is signal report, serial number and locator. On Saturday the 18th of July, the RSGB 70MHz Trophy Contest runs from 1400 to 2000UTC. Using all modes on the 4m band, the exchange is signal report, serial number, locator and your two-letter postcode. On Sunday the 19th, the RSGB International Low Power Contest runs from 0900 to 1600UTC. Using CW on the 80, 40 and 20m bands, the exchange is signal report, serial number and transmitter power. Now the radio propagation report, compiled by G0KYA, G3YLA and G4BAO on Thursday the 9th of July 2026. We have had another week of mixed HF propagation. We started with a Kp index of 6.33 on Saturday the 4th of July which was caused by a coronal mass ejection, or CME. This caused a strong G3 geomagnetic storm and auroral conditions. A check on the bands on the 4th of July showed poor HF propagation with lower maximum useable frequencies, or MUFs, and weak and watery signals from the NCDXF beacons on 14.100MHz. But conditions have since improved and we had a Kp index of less than 3 over the past few days which means the ionosphere has returned to normal. Meanwhile, the solar flux index declined from a high of 203 on Thursday the 2nd of July to a low of 116 on Wednesday the 8th of July. That's quite a change and means that HF propagation has declined somewhat. An Earth-facing coronal hole has now passed with few effects and currently there is nothing of significance rotating into view. Solar flare activity has also declined with only two M-class flares over the past three days. So, the big question is: what happens next? Active region 4482 on the Sun continues to be a major threat. A solar flare and accompanying CME could soon ruin our chances of good HF conditions. The declining solar flux index hasn't helped either. Again, NOAA predicts the solar flux index will be in the 120 to 145 range over the coming week with a Kp index of 2 to 3. So, good news overall. DX to be worked this week includes D73G on Ch'ongsan Island; T22TT from Tuvalu; TY5FR in Benin; RT9K, the Arctic Legends IOTA DXpedition; JK1HFB/JD1 in Ogasawara, OX3LX from Greenland; and VP5G operating from Turks and Caicos. And now the VHF and up propagation news from G3YLA and G4BAO The weather is becoming a talking point in terms of the heatwave developing over much of the country, but especially in the south. This has propagation implications too. It's all being driven by a large area of high pressure, which for much of the coming week resides to the north and west of the British Isles. This will give a north-easterly breeze over the south-eastern half of the UK which means it will be blowing in from the North Sea, possibly with areas of low cloud at times. The propagation implication is that this represents almost ideal tropo potential. This is especially the case when the low cloud moves inland and we find a marked contrast between the hot dry air above the inversion and the cool, moist and shallow cloud layer below. However, in high summer the daytime heating over the land degrades the lift during the morning as the temperature inversion gets broken down by the strong sunshine. Northern areas will see the occasional weakening front clip the northwestern fringes of the UK to offer up the only rain scatter prospects available at first. However, some models are starting to suggest a breakdown by the end of the week, so more rain scatter and an end to the tropo. The prospects for aurora depend upon the Kp index, which at the moment is mostly cycling between 1 and 3. This is not anything to generate radio interest, for which a Kp index of 7 is nearer the mark. Meteor showers are still in the random state with the next shower, the Delta Aquarids, coming late in the month. The Sporadic-E season is doing well this year, particularly for digital modes. There have also been events for CW and SSB up to 2m at times. However, not all parts of the country experience an opening, so watch the clusters for early notice of workable paths. EME now, and declination reaches maximum today, the 12th, so Moon window lengths will peak along with maximum Moon elevation. Path losses are still falling, until perigee tomorrow, the 13th. 144MHz sky noise is moderate until Tuesday the 14th when the Sun and Moon are close in the sky, then low for the rest of the week. And that's all from the propagation team this week.

A reporter calls Jason Bates every week looking for the big layoff story. The five-hundred-people-let-go story. Jason keeps telling him the truth: layoffs are happening, in small numbers. So is hiring. But the catastrophe the headlines want isn't what he sees across hundreds of Ontario plants every day. Trevor sits down with Jason, Manufacturing Consortium Manager at EMC, Canada's largest manufacturing consortium, to unpack what's really going on, the plants that are quietly adjusting and diversifying, and the peer community most owners haven't tapped into. Growth doesn't sell papers. Manufacturing team leadership doesn't happen inside your four walls. The vast majority of plants are doing just fine. Most owners don't know that. Connect with Jason: LinkedIn

Host Eric Lanke interviews Barun Acharya, system engineering manager for electrification at Parker Hannifin, about energy efficiency gains from electrified hydraulics and insights tied to NFPA's white paper and a CONEXPO technology conference. Acharya describes how emissions rules, noise limits, and ESG mandates are driving electrification, and outlines key challenges including unclear duty cycles (addressed via energy mapping), power-density mismatch between hydraulic and electric actuators, complex system integration (CAN, software, EMC, operator feel), and revealed hydraulic noise once diesel is removed.   He explains that traditional inefficiency is largely the engine–pump coupling, while smart hybrid architectures use batteries to buffer transients and run engines near optimal BSFC. He details a hybrid backhoe case with engine downsizing and indoor electric operation, enabled by sensors, data, and machine-learning use for duty-cycle classification, predictive maintenance, and operator coaching. Subscribe to the Fluid Power Forum today to never miss an episode. The podcast is available on all of your favorite podcast platforms, including YouTube, Apple Podcasts, Spotify, and iHeart Radio.   Connect with our host, Eric Lanke, at elanke@nfpa.com.   Connect with our guest, Barun Acharya, at bacharya@parker.com.   Learn more about the company at www.parker.com.   Find and share more interesting fluid power technologies and unique applications using #onlyfluidpowercan and follow podcast and other fluid power industry-related updates at @TheNFPA.   #FluidPowerForum #EnergyEfficiency #HybridArchitecture #Electrification

New episode! This week we head to Brooklyn to talk about one of the greatest storytellers Hip-Hop has ever seen. Starting out being a member of the Juice Crew, to reinventing himself multiple times, he continued to release classic albums. This week, Top 10 Masta Ace songs. As always you can find the audio version on all major podcast platforms and the video version on YouTube.Follow the podcast on Instagram, X & Tik Tok: @b_boypodcastFind us online: www.riplak.comFollow Raven Hunter on Instagram & X: @ravenhunteryps

EMC testing is one of the toughest hurdles in PCB design, with industry pass rates often falling below 50% and every failure triggering expensive respins. In this OnTrack Podcast episode, host Zach Peterson sits down with Andy Eadie—owner of EMC FastPass and founder of Engentica—to unpack why so many products fail electromagnetic compatibility testing on the first attempt, and what designers can do to get it right up front instead of budgeting for inevitable rework. The conversation digs into the growing role of AI in hardware design: where machine learning genuinely accelerates simulation, signal integrity, and power integrity work, and why a fully generative "design my circuit board" tool is still a long way off. Andy also demos Engentica, an AI-powered design co-pilot that runs compliance-focused checks on schematics and layout, lets engineers investigate EMC risks in natural language, and scales hardware design expertise across an organization. Whether you're a hardware engineer, EMC consultant, or software founder building your first custom PCB, this episode is packed with practical insight on respins, pre-compliance testing, and the future of electronics design.

Altium Develop unites your design, sourcing, and manufacturing teams in one cloud platform so EMC and layout problems get caught long before your board ever reaches the test house: https://www.altium.com/develop?utm_source=youtube&utm_medium=video&utm_campaign=ontrack-podcast&utm_content=70-of-pcbs-fail-emc-testing-and-ai-is-making-it-worse EMC testing failure rates are climbing toward 70%, and on this episode of the OnTrack Podcast, host Zach Peterson sits down with EMC expert Dr. Anton Tishchenko to unpack why — and what role AI is really playing in modern PCB design. They cut through the AI hype, explaining why large language models will confidently hand you a bad PCB layout, why setting up constraints is "garbage in, garbage out," and why hardware is heading for the same reckoning software already faced. If your boards keep failing radiated emissions, this conversation explains where the real problems start. Anton also demos his web-based EMC analysis tool (pcb4emc.com), an EMC design rule check that works directly from Gerber files — no schematics, no NDAs, no sensitive data required. You'll see how it evaluates ground plane quality, differential and single-ended impedance, return paths, and crosstalk risk using the 3W rule, plus a frank discussion of coplanar waveguides, stackup awareness, and where AI genuinely helps engineers (datasheet summaries, literature reviews, and simulation enhancement) versus where it falls flat. Essential viewing for any PCB designer serious about EMC compliance.

In this episode of The Eureka Rewatch, Cory and Tom are stupid and invisible as they discuss season 2 episodes 8 & 9, E=MC...? and Sight Unseen. Blog Post

For high‑growth B2B tech brands, the next funding round or IPO is no longer just a financial milestone – it is a communications stress test. Investors are bringing AI‑driven tools, sharper scrutiny and higher expectations into every decision. The companies that win are those that can match strong numbers with a compelling, consistent story.In this episode of the FINITE Podcast, Jodi Norris sits down with Liam McLaughlin, Managing Partner at Clarity Europe, to unpack how CMOs and marketing leaders can actively prepare for their next raise or listing through comms and marketing. They explore where tech investment is flowing today, why AI is fueling a renewed funding boom, and what it really takes to move from “interesting startup” to “serious international player” in the eyes of investors.Liam breaks investor attraction down into three pillars: authenticity, narrative and AI visibility. He shares practical examples from an EV charging infrastructure client on the road to IPO, and a fintech brand using AI visibility programmes to show up consistently across search, executives, media and analysts – and, crucially, inside LLMs.Liam has almost 20 years of integrated communications experience, working with global technology brands including Oracle, NetApp and EMC, as well as consumer names such as Canva, Clearscore and eBay. As Managing Partner of Clarity Europe, he has led communications strategies for brands navigating major funding rounds and public offerings across the UK and Europe.Inside you'll find…How to build an authentic, investor‑ready brand story that goes beyond “AI‑washing”A practical framework for aligning spokespeople, channels and proof points over a multi‑year funding journeyWhy AI visibility is now a core stakeholder in investor relations – and how to measure and optimise it

우주만물상 2026년 6월호! E=MC² 은 틀렸다! 그리고 화성에 가는 가장 빠른 길은 직선이 아니다!? - 뉴스 앤 올디스 공개방송 신청신청링크 : https://forms.gle/HbYBq6f9BpsmQeh86출연: 파토, 전혜정 교수, 송민령 박사일시: 2026년 6월 21일 일요일 오후3시 (2시 45분까지 입장 완료)장소: 캠퍼스디 서울(9호선 선유도역 7번 출구 도보 2분)신청 기간: 2026년 6월 6일(토) ~ 6월 11일(목) 자정까지당첨자 발표: 2026년 6월 12일(금) (당첨자 개별 문자 연락)- 세상에서 제일 다정한 양자 책 - 구매 링크교보문고: https://product.kyobobook.co.kr/detail/S000220036172예스24: https://www.yes24.com/product/goods/189660610알라딘: https://www.aladin.co.kr/shop/wproduct.aspx?ItemId=393544146- 오프닝미국 정부 UFO 자료 대거 공개 중!화성에서 발견된 등산로 돌탑!?가스행성 뒤에 암석행성이?- 홍승수 박사화성 가는 길은 직선이 아니다! 호만 전이의 세계.- 김현철 교수질량에 대한 심오한 고찰 2E=MC² 은 잘못됐다!정지 질량과 상대론적 질량의 세계전체자료https://www.slideshare.net/slideshow/2026-6-pdf/287899975과학과사람들 제공

Message #5 of the 2026 EMC spring revival sermon series. Series: 2026 Revival: Open Our Eyes Speaker: Dr. Steve McGuire Scripture: Galatians 4:18-19; 2 Corinthians 3:12-18

Dan Ciruli is VP and General Manager of Cloud Native at Nutanix. A computer science graduate of UC Berkeley, Dan spent a decade in engineering before pivoting to product management in 2003, a role that barely had a name when he started. Since then he has held product leadership positions at EMC and Google, where he was part of the team that helped create Kubernetes and open source Google's cloud infrastructure.He was a founding member of the OpenAPI Initiative and a steering committee member for the Istio service mesh project, and has spent the last two decades with one foot in commercial product development and one in the open source community.In this episode, Dan explains why open source is not a charity exercise, how companies actually make money from code they give away for free, and what product managers get wrong when they tell their engineers to avoid it.Key takeaways— Open source is not crowdsourcing from individuals — much of the contribution comes from companies investing on the clock, because broad adoption benefits everyone more than proprietary lock-in.— The CNCF succeeded because it created a neutral space where the largest and smallest organisations felt equally safe contributing and consuming. That structure — not the code itself — is what made cloud native computing universal.— Being a product manager in open source requires the same core instinct as any other PM role: understanding the why. The difference is that your engineers may work for a competitor, and your roadmap is not entirely yours to control.— AI is multiplying the capability of both good actors and bad actors in open source security. The answer is not to slow adoption but to keep a credible human in the loop — someone with accumulated trust, judgement and accountability.— Before open sourcing your own work, be clear on how your company will make money, articulate it concisely for leadership, and then find at least one other organisation — even a competitor — willing to join you. A consortium signals a standard. A solo release signals a gamble.Chapters1:16 — From engineering to product management3:11 — Bridging open source and commercial work5:05 — The origin of Kubernetes at Google6:35 — How Nutanix embraces open source7:16 — The crowdsourcing misconception8:51 — Why the CNCF changed everything11:25 — Building a defensible moat in open source12:13 — The business models behind free code14:18 — Managing roadmaps you don't fully control15:04 — When your competitor writes your code16:04 — The CEO who wore his secrets around his neck18:13 — Developing an open source strategy19:37 — The one question every PM must ask22:44 — What is the CNCF?23:34 — AI, open source and the security arms race29:45 — Chop wood, carry water: the human in the loop31:48 — Advice for PMs running open source products33:15 — Harnessing a community you don't manage34:38 — Should you open source your own work?36:35 — How messy does it really get?39:33 — Linux is an anti-patternOur HostsLily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She's currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. She's worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Lily also founded ProductTank Bristol and runs ProductCamp in Bristol and Bath.Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury's. He participated in Silicon Valley Product Group's Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He's the author of What Do We Do Now? A Product Manager's Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon's music stores in the US & UK.

Message #4 of the 2026 EMC spring revival sermon series. Series: 2026 Revival: Open Our Eyes Speaker: Dr. Steve McGuire Scripture: Ephesians 1:3-14

Message #3 of the 2026 EMC spring revival sermon series. Series: 2026 Revival: Open Our Eyes Speaker: Dr. Steve McGuire Scripture: John 12:12-26; 20:24-31

Message #2 of the 2026 EMC spring revival sermon series. Series: 2026 Revival: Open Our Eyes Speaker: Dr. Steve McGuire Scripture: John 1:35-51

Message #1 of the 2026 EMC spring revival sermon series. Series: 2026 Revival: Open Our Eyes Speaker: Dr. Steve McGuire Scripture: Isaiah 6:1-8

Dell's CTO built a 4-category agent framework from real production deployments. Most enterprises are ignoring two of the categories that matter most.Full Show NotesEnterprise leaders are mapping AI agents to org charts — building digital employees, agentic teams, AI workers — and then wondering why the results fall short. Dell's Global CTO John Roese has been running agents in production long enough to know exactly why that framing fails, and what to do instead.In this episode, Roese shares a framework Dell developed from actual production deployments, not pilots. It identifies four categories of AI agents defined by two dimensions: how much autonomy you grant the agent, and how complex the underlying process is. Most enterprises are focused on one category. Two of the four are widely overlooked — and they may represent the fastest path to measurable ROI.This is a practical, grounded conversation about where agents are actually delivering value today, how to think about infrastructure cost in the context of agent economics, and why the sequence in which you deploy agents matters as much as which agents you build. If your organization is trying to move from AI experimentation to production, this episode is required listening.3. Chapter titles:[00:00] — Introduction: Dell's dual role as tech vendor and enterprise AI user[01:38] — Why the org chart model for agents fails[03:12] — Decoupling human capacity from work capacity for the first time[04:23] — The two-by-two framework: autonomy vs. process complexity[06:14] — Productivity agents: what most enterprises already have[07:00] — Hygiene agents: the overlooked category that fixes foundational data problems[08:01] — The CRM data example: why every CRM is inaccurate and how agents fix it[10:05] — Latent infrastructure capacity: running agents in GPU white space to cut costs to cents[13:53] — Facilitation agents: removing entropy from complex cross-functional workflows[17:30] — The sequencing insight: hygiene and facilitation as the path to expert agents[19:24] — Why coordination agents aren't agentic bosses — and where human control actually lives[22:21] — Roese's closing advice: become literate, pick a few, get them into production4. Guest BioJohn Roese is the Global Chief Technology Officer and Chief AI Officer at Dell Technologies, where he is responsible for technology strategy, AI deployment, and research and development across the company. He has held senior technology leadership roles at Nortel, Enterasys Networks, Broadcom, and EMC. At Dell, he operates at a rare intersection: leading AI strategy for a major technology vendor while also deploying AI internally at enterprise scale — which means his frameworks are tested against real production constraints, not just market positioning.LinkedIn: linkedin.com/in/johnroeseDell Technologies: dell.comAbout This PodcastAI with Maribel Lopez is a podcast for enterprise technology leaders navigating AI adoption, agentic systems, AI infrastructure, and AI governance. Host Maribel Lopez covers enterprise technology and advises CIOs, CDOs, CMOs, and technology vendors on how to move from AI experimentation to measurable business outcomes. New episodes published bi-weekly.Subscribe on your platform of choice: buzzsprout.com/1947446

In Episode 103, Brennan is joined by NYC actor, Cambria Klein, as they mourn the soon to be death of the EMC program and try to figure out what the heck they're gonna do now! The decision is a very complex one to make and there are 1 million factors to take into consideration. However at the end of the day, it's a decision only you can make for yourself, so you gotta trust your heart!Support the showHost/ Production/ Editing: Brennan StefanikMusic: Dylan KaufmanGraphic Design: Jordan Vongsithi@batobroadway on Instagram, Threads, and TikTokPatreon.com/batobroadway

This week, we interviewed Rod Mathews. Rod is the CEO of TeamDynamix and a member of the board of directors. Most recently, he was President and CEO at Axcient, a business continuity and disaster recovery software company, where he focused on innovation and market acceleration, leading to its acquisition by ConnectWise late last year. During his tenure, Axcient's growth rate tripled, driven by the expansion of the market-leading x360 platform focused on the MSP market.  As a 34-year tech industry veteran, he has held leadership positions across R&D, marketing, corporate development, and general management with Barracuda Networks, EMC, Data Domain, and NetApp.  Rod is also executive chair of the board at Spin.AI, a SaaS security company with a mission to secure SaaS data against ransomware attacks, insider threats, data loss, data leaks, and non-compliance.

Preparation does not become less important as sellers gain experience. It becomes more visible as a differentiator. In this replay segment with John Rowell, he breaks down of how disciplined pre-call preparation sharpens positioning, turns cold outreach into meaningful engagement, and allows reps to stay fully present in the moment. The conversation highlights why preparation is not just about information gathering, but about earning credibility, accelerating sales cycles, and creating the conditions for authentic customer conversations. John Rowell is the Co-Founder of Pinned Golf and a former enterprise sales leader with experience at EMC and Lacework. He brings a practitioner's perspective on applying enterprise sales discipline to startup growth. Connect with John: LinkedIn Pinned Golf Website Resources mentioned: Pin Golf's Caddie GPS Tablet Catch the full conversation, here:  Pinned Golf: Making the Shift from Sales to Entrepreneurship Hosted by five-time CRO John McMahon and Force Management Co-Founder John Kaplan, the Revenue Builders podcast goes behind the scenes with the sales leaders who have been there, done that, and seen the results. This show is brought to you by Force Management. We help companies improve sales performance, executing their growth strategy at the point of sale. Connect with Us: LinkedInYouTubeForce Management

What does it take to become a “rockstar” CFO in the age of AI? Today, Zane Rowe, CFO of Workday, shares lessons from a career spanning global airlines, Apple, EMC, and VMware—to leading finance at one of the world's most influential enterprise software companies. From navigating generative AI in the finance function to building a true CEO–CFO partnership, Rowe breaks down how modern financial leadership is evolving. He reveals why today's CFO must think beyond accounting, how AI is reshaping decision-making, and what the next generation of finance leaders must do to stay ahead. If you want insight into the future of financial strategy, enterprise AI, and what separates good CFOs from great ones, this is a conversation you won't want to miss.

Roger Harrison VK2ZRH, Editor-in-Chief of Amateur Radio magazine . - Alan VK2COD, YOTA news and his reminder of the VKSUMMIT . - New downloadable EMC leaflet available, Jason VK2LAW tells how . - EI 0 WAAAW for Autism Awareness and VK4FUQ Felix gives us the when and where . - ARISS Outlines Opportunities for Space Station Contacts in 2027 during Operational news this week with Bruce VK3FFF.

In this episode of China Manufacturing Decoded (Ep. 322), host Adrian is joined by Renaud to take a high-level, practical look at product compliance. Many hardware teams think about compliance too late. By the time testing starts, the damage is already done: failed certifications, redesigns, delays, and unexpected costs. In this episode, we break down what product compliance really means and why it needs to be considered from the very beginning of product development. You'll learn: What “compliance” actually covers (it's more than just CE or FCC labels) Why designing without compliance in mind leads to expensive rework The key compliance areas: safety, chemicals, EMC, and more How requirements change depending on your target market (EU, US, etc.) Real ways companies get caught out, and how to avoid it   Episode Sections: 00:00:03 – Introduction & why compliance timing matters 00:01:23 – What product compliance actually means 00:02:24 – Why compliance must be built into design & sourcing 00:04:48 – What happens when products fail compliance testing 00:06:06 – The cost of redesign loops after failed tests 00:08:30 – Compliance explained: beyond CE & FCC labels 00:11:10 – How requirements vary by market (EU, US, global) 00:13:30 – Key compliance categories (chemicals, safety, EMC) 00:16:00 – CE marking, EU rules & US differences (UL, FCC) 00:18:52 – Additional requirements: toys, packaging, batteries 00:21:28 – Common compliance mistakes & supplier pitfalls 00:26:00 – Final takeaway: think about compliance early   Related content… CE Compliance for Manufacturing in Asia: A Beginner's Guide 11 Common Electronic Product Certification And Compliance Requirements Why Smart Devices Fail CE RED or FCC Testing & How to Prevent It Common Compliance & Recall Risks for IoT Devices Sold in the EU & UK US Consumer Electronics Compliance Basics Your Product is NOT Compliant in the EU or UK if You Don't Have All of its Technical Files Reliability vs. Compliance: Both Matter Equally for Your New Product Launch   This episode is brought to you by The Sofeast Group and includes links in the show notes to our blog posts and resources, and recommended books. For help with manufacturing in Asia, inspections, auditing, new product development, contract manufacturing, 3PL warehousing and fulfillment, visit sofeast.com.  Get in touch with us Connect with us on LinkedIn Contact us via Sofeast's contact page Subscribe to our YouTube channel Prefer Facebook? Check us out on FB

Pat Hindle talks with Jürgen Meyer, Vice President of the Automotive Market Segment at Rohde & Schwarz, about their new, larger office in Osaki, Japan, with increased capabilities, including some interesting demos covering EMC and automotive applications.

Raiders of the Lost Ark turns 45 this year and, for Earth's Mightiest Critics, Steven Spielberg's globe-spanning archeological adventure is a foundational part of their love of movies! But after nearly half a century and countless viewings, there's still a lot to discover about Harrison Ford's fascist-fighting scoundrel--and his intriguing relationship with faith.Tonight, the EMC will pay tribute to a great film and dig into the character's decades-long struggle with various aspects of belief, non-belief, and everything in between.Join us as we unearth the secrets of Raiders's enduring legacy and the Indy franchise's spiritual thematic resonance! We also take your questions, comments, and SuperChats!Support Kicking the Seat on Patreon, subscribe to us on YouTube, and follow us at:XLetterboxdInstagramFacebookShow Links:Watch the Raiders of the Lost Ark (1981) trailer.As mentioned in the show, Ian recently saw Raiders of the Lost Ark at Chicago's Auditorium Theatre, as part of the "Auditorium Philms" series--in which attendees watch classic movies projected on the big screen, with live orchestral accompaniment! Check out the full 2026 lineup here!Also mentioned in the show was Ian's recent appearance on The Spoiler Room Podcast, discussing Wall-E. Give a listen!Support all of Earth's Mightiest Critics at their various outlets:Keep up with Jeff York's criticism and caricatures at The Establishing Shot and Pipeline Artists.Check out Mark "The Movie Man" Krawczyk's The Spoiler Room Podcast.Get seated with The Blonde in Front!Follow David Fowlie's film criticism at Keeping It Reel.Get educated with Don Shanahan at Every Movie Has a Lesson…...And Film Obsessive...and the Cinephile Hissy Fit Podcast.Keep up with Annie Banks at The Mary Sue....and We Got This Covered.Make Nice with Mike Crowley of You'll Probably Agree.And save your celluloid soul with Dave Canfield's Substack, "Creature Feature Preacher".-------------------------------------------------------------------------------------------------------------------------------------------- Subscribe, like, and comment on Kicking the Seat here on YouTube, and check us out at: -------------------------------------------------------------------------------------------------------------------------------------------- kickseat.com: https://kickseat.com/ Patreon: patreon.com/u35249528 X: https://x.com/KICKSEAT Instagram: https://www.instagram.com/kickseat/ Facebook: https://www.facebook.com/kickseat/ -------------------------------------------------------------------------------------------------------------------------------------------- Show Links -------------------------------------------------------------------------------------------------------------------------------------------- Support ALL of Earth's Mightiest Critics at our various outlets: Get educated with Don Shanahan at Every Movie Has a Lesson: http://www.everymoviehasalesson.com/ ...And Film Obsessive: https://filmobsessive.com/ ...AND the Cinephile Hissy Fit Podcast: https://open.spotify.com/show/6G0dYEHovZsjHd2ItOuRL2 Check out Mark "The Movie Man" Krawczyk's The Spoiler Room Podcast: https://www.specialmarkproductions.com/spoilerroompdcs.html Get seated with Cati Glidewell, The Blonde in Front! https://www.youtube.com/@theblondeinfront Follow David Fowlie's film criticism at Keeping It Reel: https://keeping-it-reel.com/ Keep up with Jeff York's criticism and caricatures at The Establishing Shot! https://theestablishingshot.org/ Keep up with Annie Banks at Comic Book Resources: https://www.cbr.com/author/annie-banks AND We Got This Covered: https://wegotthiscovered.com/ Make Nice with Mike Crowley of You'll Probably Agree: https://www.ypareviews.com/ And save your celluloid soul with Dave Canfield's Substack, "Creature Feature Preacher"! https://creaturefeaturepreacher.substack.com/ Ep1220: Raiders of the Lost Ark (1981) - Live 45th Anniversary Roundtable Review Kicking the Seat

Karen Burnham feels your pain - the pain of EMC, that is. Karen is an EMC engineer, instructor, and founder of EMC United, a consulting company that aims to make EMC less painful for the rest of the PCB design engineering community. Karen joins Andy Shaughnessy to discuss some of the most common EMC challenges facing our industry today, a variety of solutions for these challenges, and design practices that can help you avoid EMC problems the first place. Karen also explains why EMC needs to become part of every high-speed PCB design cycle, and not an afterthought that's only addressed when a board fails FCC. Karen will be speaking at PCB East 2026, and she offers a preview of what attendees can expect to learn in her class, "EMC 101 - Fundamentals," which takes place April 30 at the DCU Convention Center in Worcester, MA. 

In this special episode recorded live on site at SXSW EDU, Dustin chats with Greg Smith from Britebound about their recent rebrand and their expanding work helping young learners explore potential careers and the ways to navigate the postsecondary landscape. He highlights how his team's work impacts higher ed during a time of increased scrutiny about value and relevance. Guest Name: Greg Smith, Vice President of Marketing, Britebound Guest Social: LinkedIn Guest Bio: As Vice President of Marketing at Britebound, Greg Smith is responsible for translating annual business objectives into strategic marketing plans and leading the marketing team to concept, create and execute the digital campaigns that impact millions of students each year. Greg brings over 25 years of corporate strategy, brand development and global marketing experience with a career that has spanned the technology, banking and financial services industries. In prior agency and client roles, Greg partnered with executives at companies such as American Express, EMC and Citizens Commercial Bank to envision how their marketing organizations must evolve to embrace the digital world and to transform their go-to-market strategies as the power shifted from companies to consumers. - - - -Connect With Our Host:Dustin Ramsdellhttps://www.linkedin.com/in/dustinramsdell/About The Enrollify Podcast Network:The Higher Ed Geek is a part of the Enrollify Podcast Network. If you like this podcast, chances are you'll like other Enrollify shows too!Enrollify is made possible by Element451 — The AI Workforce Platform for Higher Ed. Learn more at element451.com. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

⬥EPISODE NOTES⬥ The conversation that led to this episode started with a LinkedIn post -- and it quickly surfaced a challenge that security leaders across industries are wrestling with but rarely talk about openly: who is actually responsible for protecting the people inside an organization, not just the systems they use? Roland Cloutier has sat in some of the most demanding security leadership seats in the world -- Global CSO at TikTok/ByteDance, a decade as Global CSO at ADP, and VP and CSO at EMC -- and he now advises CISOs and CSOs through The Business Protection Group. His lens is converged security: the deliberate integration of cyber, physical, privacy, and people-risk under a unified program and leadership model. Roland identifies three patterns that typically bring organizations to him. First, an emergent crisis -- a threat against an executive, a workplace violence incident, a travel security failure -- that suddenly exposes the absence of a coherent protection program. Second, a cost and structure conversation where the CEO is tired of receiving two different risk pictures from two different security leaders and wants a single accountable voice. Third, a board-driven inquiry where general counsel or the CEO is being asked questions about executive resilience and duty of care that nobody inside the organization can confidently answer. What makes this conversation particularly sharp is Roland's framing of convergence not as an org chart exercise, but as a force multiplier. A unified threat intelligence picture -- one that covers cyber, physical, executive, brand, and customer risk simultaneously -- enables cleaner prioritization, better resource allocation, and a fundamentally stronger conversation with the CEO. The alternative, which he has seen firsthand, is four separate threat management platforms reporting independently with no team working across all of them. The episode also pushes into territory that most security programs have not yet mapped: employee protection at scale. Not bodyguards for everyone, but the organizational consciousness to monitor for geographic threats, proactively check in with distributed employees during major events, and build a duty-of-care posture that extends beyond the office walls into people's home lives and total risk environment. For high-risk employees -- those with keys to the kingdom, not just C-suite titles -- that responsibility extends further still. For CISOs and CSOs wondering where to start, Roland offers a practical crawl-walk-run framework: start with shared services rather than full convergence, open the conversation with leadership, surface the gaps the business already knows exist, and build a financial and risk model that makes sense for your specific organization. The goal is a converged security program that treats people -- not just infrastructure -- as an asset worth protecting. ⬥GUEST⬥ Roland Cloutier, Principal at The Business Protection Group | On LinkedIn: https://www.linkedin.com/in/rolandcloutier/ ⬥HOST⬥ Sean Martin, Co-Founder at ITSPmagazine, Studio C60, and Host of Redefining CyberSecurity Podcast & Music Evolves Podcast | Website: https://www.seanmartin.com/ ⬥RESOURCES⬥ The Future of Cybersecurity Newsletter | https://www.linkedin.com/newsletters/7108625890296614912/ More Redefining CyberSecurity Podcast episodes | https://www.seanmartin.com/redefining-cybersecurity-podcast Redefining CyberSecurity Podcast on YouTube | https://www.youtube.com/playlist?list=PLnYu0psdcllS9aVGdiakVss9u7xgYDKYq ⬥ADDITIONAL INFORMATION⬥ On ITSPmagazine: https://www.itspmagazine.com/ On YouTube: https://www.youtube.com/@itspmagazine On LinkedIn Newsletter: https://itspm.ag/future-of-cybersecurity Sean Martin's Contact Page: https://www.seanmartin.com/ ⬥KEYWORDS⬥ roland cloutier, the business protection group, sean martin, executive protection, employee protection, converged security, physical security, ciso, cso, duty of care, threat intelligence, workplace violence, security convergence, business resilience, redefining cybersecurity, cybersecurity podcast, redefining cybersecurity podcast Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

⬥EPISODE NOTES⬥ The conversation that led to this episode started with a LinkedIn post -- and it quickly surfaced a challenge that security leaders across industries are wrestling with but rarely talk about openly: who is actually responsible for protecting the people inside an organization, not just the systems they use? Roland Cloutier has sat in some of the most demanding security leadership seats in the world -- Global CSO at TikTok/ByteDance, a decade as Global CSO at ADP, and VP and CSO at EMC -- and he now advises CISOs and CSOs through The Business Protection Group. His lens is converged security: the deliberate integration of cyber, physical, privacy, and people-risk under a unified program and leadership model. Roland identifies three patterns that typically bring organizations to him. First, an emergent crisis -- a threat against an executive, a workplace violence incident, a travel security failure -- that suddenly exposes the absence of a coherent protection program. Second, a cost and structure conversation where the CEO is tired of receiving two different risk pictures from two different security leaders and wants a single accountable voice. Third, a board-driven inquiry where general counsel or the CEO is being asked questions about executive resilience and duty of care that nobody inside the organization can confidently answer. What makes this conversation particularly sharp is Roland's framing of convergence not as an org chart exercise, but as a force multiplier. A unified threat intelligence picture -- one that covers cyber, physical, executive, brand, and customer risk simultaneously -- enables cleaner prioritization, better resource allocation, and a fundamentally stronger conversation with the CEO. The alternative, which he has seen firsthand, is four separate threat management platforms reporting independently with no team working across all of them. The episode also pushes into territory that most security programs have not yet mapped: employee protection at scale. Not bodyguards for everyone, but the organizational consciousness to monitor for geographic threats, proactively check in with distributed employees during major events, and build a duty-of-care posture that extends beyond the office walls into people's home lives and total risk environment. For high-risk employees -- those with keys to the kingdom, not just C-suite titles -- that responsibility extends further still. For CISOs and CSOs wondering where to start, Roland offers a practical crawl-walk-run framework: start with shared services rather than full convergence, open the conversation with leadership, surface the gaps the business already knows exist, and build a financial and risk model that makes sense for your specific organization. The goal is a converged security program that treats people -- not just infrastructure -- as an asset worth protecting. ⬥GUEST⬥ Roland Cloutier, Principal at The Business Protection Group | On LinkedIn: https://www.linkedin.com/in/rolandcloutier/ ⬥HOST⬥ Sean Martin, Co-Founder at ITSPmagazine, Studio C60, and Host of Redefining CyberSecurity Podcast & Music Evolves Podcast | Website: https://www.seanmartin.com/ ⬥RESOURCES⬥ The Future of Cybersecurity Newsletter | https://www.linkedin.com/newsletters/7108625890296614912/ More Redefining CyberSecurity Podcast episodes | https://www.seanmartin.com/redefining-cybersecurity-podcast Redefining CyberSecurity Podcast on YouTube | https://www.youtube.com/playlist?list=PLnYu0psdcllS9aVGdiakVss9u7xgYDKYq ⬥ADDITIONAL INFORMATION⬥ On ITSPmagazine: https://www.itspmagazine.com/ On YouTube: https://www.youtube.com/@itspmagazine On LinkedIn Newsletter: https://itspm.ag/future-of-cybersecurity Sean Martin's Contact Page: https://www.seanmartin.com/ ⬥KEYWORDS⬥ roland cloutier, the business protection group, sean martin, executive protection, employee protection, converged security, physical security, ciso, cso, duty of care, threat intelligence, workplace violence, security convergence, business resilience, redefining cybersecurity, cybersecurity podcast, redefining cybersecurity podcast Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

  If you run a business with a sales team, this episode will make you uncomfortable. That's the point. Marcus Cauchi and Andy Hough have a no-holds-barred conversation about why sales has become distrusted, what's causing it, and what founders and CEOs can actually do to fix it. Andy has spent decades in the field, from Lloyds and Barclays to 16 years at EMC (now Dell), and has since sat through hundreds of hours of sales meetings as a researcher. He knows where the bodies are buried. What we cover in this episode: Why sales has shifted from a relationship-driven profession to a numbers and technology treadmill, and what that's costing you in customer trust, revenue quality, and staff retention. How shareholder pressure flows down through leadership, management, and sellers, and arrives in front of your buyers as inauthenticity, shallow discovery, and unwanted pressure. Why the best sales interactions are built on understanding how your customer makes money, protects margin, and carries risk, and why most sales teams have lost this entirely. The 90-day productivity myth. Research puts it at 3.2 years for a salesperson to hit full stride. Most organisations churn people before they ever get there. Why activity metrics destroy quality, and what the alternative actually looks like in practice. The player-manager trap and why it almost always ends badly for the team, the manager, and ultimately the customer. What sales coaching actually is, and why the gap between what managers think they're doing and what salespeople are experiencing is wider than most leaders realise. Why seller psychological safety is as important as buyer trust, and how the wrong people keep getting promoted. Why your CRM is aligned to your sales process and not your buyer's journey,  and why that single misalignment is costing you deals you didn't even know you lost. The case for sustainable sales: focusing on the 6-to-36 month pipeline where there's no competition, time to build real relationships, and room to become a trusted adviser rather than another vendor chasing a quarterly number. The question this episode leaves every founder and CEO with: Are the systems you've built designed to create trust with customers, or are they quietly destroying it in order to hit this quarter's number? And critically, does anyone in your organisation feel safe enough to tell you? About Andy Hough Andy Hough is co-founder of the Institute of Sales Professionals, a tireless advocate for sales as a profession, and a doctoral researcher studying the adaptability of salespeople and its impact on performance. He lectures at Cranfield University and is part of the Global Sales Science Institute. He has carried a target, led teams, and spent his career trying to return sales to what it was in its best form. A genuinely human, outcome-focused profession. Connect with Andy on LinkedIn or visit the ISP at www.isp.uk.com About Marcus Cauchi Marcus Cauchi is the host of the Inquisitor Podcast and works with founders, CEOs, and sales leaders on decision safety, go-to-market alignment, and building sales organisations that create long-term customer value. He is currently completing a manuscript on the systemic compromises that accumulate inside sales cultures and the cost they carry. Connect with Marcus on LinkedIn If this episode resonated, share it with your CRO, your Head of Sales, or any founder who's wondering why pipeline feels harder than it used to. The answer is probably in this conversation.

In this month's EM Quick Hits Podcast we introduce not one, but two new series! First, "EMC²" - EM Cases Cases (we know, horrible name ;) where Anton or Katie discuss a knowledge building case with a special guest. And second, "Coaching the EM Mind" with Dr. Sara Gray a professional coach for EM providers, where Katie discusses with her the science and best expert advice on how to perform your best in the ED. Plus, a withdrawal syndrome that is new EDs, life-threatening and requires specific treatment - metetomadine withdrawal, EMS handover done right, why community ED docs should not use the PECARN C-spine Rule and Part 2 of Petro's tips on management of traumatic pneumothorax... Please consider a donation to ensure EM Cases continues to be Free Open Access here: https://emergencymedicinecases.com/donation/

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

IEC 60601 has been central to medical electrical equipment safety for decades. From the prescriptive approach of the 2nd edition to the risk-based philosophy introduced in the 3rd edition, the standard has continuously evolved to address technological and regulatory complexity.Now, the upcoming 4th edition represents more than an amendment — it signals a structural transformation.This article explores:The Evolution of IEC 60601• Key shifts from the 2nd to the 3rd edition• Why risk management became central• What lessons shaped today's safety philosophyWhat the 4th Edition Brings• A major rewrite rather than incremental updates• The introduction of “atomic requirements”• Structural clarity for manufacturers, test labs, and regulators• Emerging technical considerations (digitalization, AI, cybersecurity, home use)Impact on Existing Devices• Will re-testing be required?• How to assess validity of existing test reports• Transition strategies with notified bodiesIntegration into Design & Documentation• Embedding IEC 60601 into risk management from day one• Required updates in risk files, EMC documentation, labeling, and usability engineering• Practical advice for SMEs with limited resourcesThe Future of IEC 60601• Greater harmonization with ISO 14971 and IEC 62304• Alignment with digital and AI regulatory frameworks• The long-term outlook for medical electrical safetyFor manufacturers, the message is clear:IEC 60601 is not just a testing standard — it is a design and risk management framework that must be integrated early and strategically.Who is Monir El Azzouzi? Monir El Azzouzi is the founder and CEO of Easy Medical Device a Consulting firm that is supporting Medical Device manufacturers for any Quality and Regulatory affairs activities all over the world. Monir can help you to create your Quality Management System, Technical Documentation or he can also take care of your Clinical Evaluation, Clinical Investigation through his team or partners. Easy Medical Device can also become your Authorized Representative and Independent Importer Service provider for EU, UK and Switzerland. Monir has around 16 years of experience within the Medical Device industry working for small businesses and also big corporate companies. He has now supported around 100 clients to remain compliant on the market. His passion to the Medical Device filed pushed him to create educative contents like, blog, podcast, YouTube videos, LinkedIn Lives where he invites guests who are sharing educative information to his audience. Visit easymedicaldevice.com to know more.  If you need help implementing QMSR or preparing your teams for FDA inspections, contact: info@easymedicaldevice.com If you are located outside the EU/UK/Switzerland and need an Authorized Representative (and possibly an Importer), we can support you as well.LinkLeo Linkedin: https://www.linkedin.com/in/leoeisnersafetyconsultants/Social Media to followMonir El Azzouzi Linkedin: https://linkedin.com/in/melazzouziTwitter: https://twitter.com/elazzouzimPinterest: https://www.pinterest.com/easymedicaldeviceInstagram: https://www.instagram.com/easymedicaldeviceThis podcast is powered by Podcastics, the easiest platform to create and publish your podcast.

מגיל 13 היא פרצה למחשבים, בגיל 36 היא מנכ"לית חברה בשווי 300 מיליון דולר - טל קולנדר מחברת רמידיו חושפת איך בנתה עסק של 10+ מיליון דולר בהכנסות ללא גיוס כסף חיצוני במשך שנים, עד שאמזון הפכה ללקוחה וקרנות ההשקעות המובילות הציעו לה "הצעה שאי-אפשר לסרב לה".פתיחה וגיוס הכסף - 0:00הרקע האישי של טל ותחילת הדרך בסייבר - 4:03השירות הצבאי ביחידות מיוחדות - 8:43המעבר לעולם האזרחי ועבודה בדל EMC - 11:02הקמת החברה עם השותפים - 13:35המוצר הראשון ולקוחות ראשונים - 15:13הצמיחה ללא משקיעים חיצוניים - 17:17הגדלת הצוות והכנסות מעל 10 מיליון דולר - 18:53המוצר הנוכחי ופתרון בעיות קונפיגורציה - 22:28הרחבה לעולם הקומפליינס - 26:00הפיבוט למוצר חדש ופלטפורמה רחבה יותר - 27:27החיים עם משקיעים לעומת בלעדיהם - 29:13הצמיחה הבינלאומית ולקוחות גדולים - 32:24אסטרטגיית השיווק והאירועים - 35:36הסיבות לגיוס הכסף בשלב זה - 37:38התרבות הארגונית ואיזון חיים ועבודה - 39:20התוכניות לשנה הקרובה - 43:18החזון לטווח הארוך ו-2026-2027 - 45:34

How do strong relationships within underwriting teams and between underwriters and producers shape the surety business? In this episode, we sit down with Bob Bowman of Holmes Murphy, Justin Tomlin of FNIC Group, and Rocky Pofahl and Cory Hamling of EMC to explore the vital collaboration between home office, field underwriters, and producers — and why trust, clarity, and communication drive success. Don't miss this look at the people and relationships inside the business of surety! With special guests: Bob Bowman, Surety Underwriting Manager, Holmes Murphy Justin Tomlin, Senior Vice President – Surety Manager, FNIC Group Rocky Pofahl, Assistant Vice President-Bond Underwriting Superintendent, EMC Cory Hamling, Bond Director, EMC Hosted by: Kat Shamapande, Director, Professional Development, NASBP

In today's episode we speak to the 2026 EMC keynote speaker Dave Weber

This episode covers the next part of chapter 30 from: “The frank realization that physical science is concerned with...” to “...this conception brings us to the law of miracles. " Summary: In this episode we focus on the concept of "mind stuff" and scientific breakthroughs, particularly the development of the electron microscope. Paramahansa Yogananda explains how electrons exhibit both wave and particle properties, and how this dual nature challenges traditional scientific understanding of reality. We also cover Sir James Jeans' concept of the universe as a "great thought" rather than a mechanical structure, and Einstein's famous equation E=MC^2.  0:00 Prior Episode; 10:10 Electron Microscope; 22:30 There is no material universe; 32:05 The Law of Miracles; 40:00 Looking Ahead. Links discussed in this episode:  Tungsten crystals https://www.microscopy.ethz.ch/nbwo.htm https://www.yogananda.com.au/gurus/yoganandaquotes12.html  Homework for next episode— Read, absorb and make notes on the next part of chapter 30 from: “Masters who are able to materialise and dematerialise their bodies...” to “...rise up as master of maya, knowing his dominion over the cosmos." #autobiographyofayogi  #autobiographylinebyline  #paramahansayogananda Autobiography of a Yogi awake.minute Self-Realization Fellowship Yogoda Satsanga Society of India #SRF #YSS

In this episode of the Altium OnTrack podcast, host Zach Peterson sits down with Karen Burnham, chief engineer and founder of EMC United, to explore why electromagnetic compatibility remains one of the most challenging aspects of product development. Karen shares her journey from physics to NASA Johnson Space Center and eventually into EMC consulting, offering invaluable insights into why so many engineers struggle with compliance testing and what they can do about it.   Whether you're a new designer facing your first EMC test or a seasoned engineer looking to refine your approach, this conversation covers critical topics including common misconceptions about ground plane splits, the dangers of blindly following data sheet recommendations, requirements management pitfalls, and cost-effective pre-compliance strategies. Karen also discusses the evolving role of simulation and AI in EMC design review, upcoming changes to CISPR standards, and her practical seminars designed to help engineers avoid costly failures.  

In this episode, Adam Torres ⁠interviews Alex Kangoun, CEO of Athena Solutions, Inc., about why data readiness—not AI models—is the real driver of success in the AI era. Alex shares how companies can overcome data management debt, build trust through incremental wins, and turn data into a competitive advantage. About ⁠Alex Kangoun Alex has over 20 years of data warehousing and business intelligence consulting experience across multiple industries. His experience includes solution delivery for BI and data quality initiatives. His core strengths include managing global projects involving teams across multiple locations. Prior to Athena Solutions Alex was responsible for BI solutions at Pitney Bowes and was Director of Business Intelligence and Data Quality at Monster.com. His other clients included Price Waterhouse Coopers, PTC, Fidelity, Teradyne, EMC, Citizens Bank, and others. Alex has MBA from Boston College and MS from Kiev National University of Construction and Architecture. Alex is certified Project Manager Professional (PMP) from PMI. About Athena Solutions Athena Solutions offers strategic data management and business intelligence consulting that empowers businesses to access and use their data to make better business decisions. The experts at Athena Solutions have over twenty years of business intelligence experience, having worked on over 100 successful projects in various industries such as financial services, healthcare, consumer product goods, retail, telecom and high tech. Watch Full Episode on ⁠Youtube⁠. --- Follow Adam on Instagram at ⁠https://www.instagram.com/askadamtorres/⁠ for up to date information on book releases and tour schedule. Apply to be a guest on our podcast: ⁠https://missionmatters.lpages.co/podcastguest/⁠ Visit our website: ⁠https://missionmatters.com/⁠ More FREE content from Mission Matters here: ⁠https://linktr.ee/missionmattersmedia Learn more about your ad choices. Visit podcastchoices.com/adchoices

In this episode, ⁠Adam Torres ⁠⁠interviews ⁠Alex Kangoun⁠, CEO of Athena Solutions, Inc., about why data readiness—not AI models—is the real driver of success in the AI era. Alex shares how companies can overcome data management debt, build trust through incremental wins, and turn data into a competitive advantage. About⁠ ⁠⁠Alex Kangoun Alex has over 20 years of data warehousing and business intelligence consulting experience across multiple industries. His experience includes solution delivery for BI and data quality initiatives. His core strengths include managing global projects involving teams across multiple locations. Prior to Athena Solutions Alex was responsible for BI solutions at Pitney Bowes and was Director of Business Intelligence and Data Quality at Monster.com. His other clients included Price Waterhouse Coopers, PTC, Fidelity, Teradyne, EMC, Citizens Bank, and others. Alex has MBA from Boston College and MS from Kiev National University of Construction and Architecture. Alex is certified Project Manager Professional (PMP) from PMI. About⁠ ⁠⁠Athena Solutions⁠ Athena Solutions offers strategic data management and business intelligence consulting that empowers businesses to access and use their data to make better business decisions. The experts at Athena Solutions have over twenty years of business intelligence experience, having worked on over 100 successful projects in various industries such as financial services, healthcare, consumer product goods, retail, telecom and high tech. Watch Full Episode on⁠ ⁠Youtube⁠⁠. --- Follow Adam on Instagram at⁠ ⁠https://www.instagram.com/askadamtorres/⁠⁠ for up to date information on book releases and tour schedule. Apply to be a guest on our podcast: ⁠⁠https://missionmatters.lpages.co/podcastguest/⁠⁠ Visit our website: ⁠⁠https://missionmatters.com/⁠⁠ More FREE content from Mission Matters here:⁠ ⁠https://linktr.ee/missionmattersmedia⁠ Learn more about your ad choices. Visit podcastchoices.com/adchoices

The return-to-office debate has been hijacked by the wrong conversation. In this episode, Josh and Bob cut through the noise to reveal what's really driving RTO mandates—and it's not what most leaders will admit.There are two clouds hovering over every in-office decision: the Control Cloud and the Innovation Cloud. The Control Cloud is about distrust, micromanagement, and leaders who feel uneasy when they can't physically see butts in seats. The Innovation Cloud is about something entirely different—creating the conditions where teams can do their absolute best work together.Drawing from decades of experience building high-performing teams at companies like iContact, Teradata, and EMC, Josh and Bob make the case that co-located teams aren't just a preference—they're an innovation multiplier. They share stories of conference rooms turned into collaboration bootcamps, cube walls torn down with power drills, and the simple magic of a room erupting in applause when someone moves a sticky note to "Done."But this isn't about forcing people back to the office for control. It's about understanding what gets lost when we optimize purely for individual convenience over team collaboration. The watercooler conversations. The yelps from a frustrated tester that bring immediate help. The face-to-face tension that drives real innovation.Josh, who has debated this question with himself for fifteen years, finally lands on an answer: if he were building a team from scratch today, he'd build a co-located team of collaborative problem solvers. Not because remote can't work, but because the magic of true team collaboration is worth the commute.The question isn't whether you should return to office. The question is: which cloud is driving your decision? Stay Connected and Informed with Our NewslettersJosh Anderson's "Leadership Lighthouse"Dive deeper into the world of Agile leadership and management with Josh Anderson's "Leadership Lighthouse." This bi-weekly newsletter offers insights, tips, and personal stories to help you navigate the complexities of leadership in today's fast-paced tech environment. Whether you're a new manager or a seasoned leader, you'll find valuable guidance and practical advice to enhance your leadership skills. Subscribe to "Leadership Lighthouse" for the latest articles and exclusive content right to your inbox.Subscribe hereBob Galen's "Agile Moose"Bob Galen's "Agile Moose" is a must-read for anyone interested in Agile practices, team dynamics, and personal growth within the tech industry. The newsletter features in-depth analysis, case studies, and actionable tips to help you excel in your Agile journey. Bob brings his extensive experience and thoughtful perspectives directly to you, covering everything from foundational Agile concepts to advanced techniques. Join a community of Agile enthusiasts and practitioners by subscribing to "Agile Moose."Subscribe hereDo More Than Listen:We publish video versions of every episode and post them on our YouTube page.Help Us Spread The Word: Love our content? Help us out by sharing on social media, rating our podcast/episodes on iTunes, or by giving to our Patreon campaign. Every time you give,...

In this episode, we sit down with Adam Zimman, author and VC advisor, to explore the world of progressive delivery and why shipping software is only the beginning. Adam shares his fascinating journey through tech—from his early days as a fire juggler to leadership roles at EMC, VMware, GitHub, and LaunchDarkly – and how those... Read more »

In this episode, we sit down with Adam Zimman, author and VC advisor, to explore the world of progressive delivery and why shipping software is only the beginning. Adam shares his fascinating journey through tech—from his early days as a fire juggler to leadership roles at EMC, VMware, GitHub, and LaunchDarkly – and how those... Read more »

Earth's Mightiest Critics ring in the New Year with the escapism of economic uncertainty!Park Chan-wook's latest film, No Other Choice centers on Man-su (Lee Byung-hun) who has been out of work for several years. In a desperate attempt to eliminate job market competition, he concocts a darkly brilliant plan. It's no secret that Ian is not the biggest Park fan (who else on planet Earth thinks the remake of Oldboy is better than the original?!).The question, then, is can this critically acclaimed new slice of dramatic social commentary--and the rest of the EMC's very best arguments--turn things around?Join us as we seek truth, gainful employment, and airtight alibis. We'll also take your questions, comments, and SuperChats!Support Kicking the Seat on Patreon, subscribe to us on YouTube, and follow us at:XLetterboxdInstagramFacebookShow LinksWatch the No Other Choice (2025) trailer.Support all of Earth's Mightiest Critics at their various outlets:Keep up with Jeff York's criticism and caricatures at The Establishing Shot and Pipeline Artists.Check out Mark "The Movie Man" Krawczyk's The Spoiler Room Podcast.Get seated with The Blonde in Front!Follow David Fowlie's film criticism at Keeping It Reel.Get educated with Don Shanahan at Every Movie Has a Lesson…...And Film Obsessive...and the Cinephile Hissy Fit Podcast.Keep up with Annie Banks at The Mary Sue....and We Got This Covered.Make Nice with Mike Crowley of You'll Probably Agree.And save your celluloid soul with Dave Canfield's Substack, "Creature Feature Preacher".

Lights! Camera! Diggler!Earth's Mightiest Critics close out 2025 with a look at Paul Thomas Anderson's classic 1997 drama, Boogie Nights! Mark Wahlberg stars as Eddie Adams, a young California dishwasher who gets lured into the glamorous, sinister world of 1970s adult entertainment. His found family includes legendary mogul Jack Horner (Burt Reynolds), Jack's matronly muse, Amber Waves (Julianne Moore), and fellow performer Reed Rothchild (John C. Reilly).Together, they build a new hard-core franchise while struggling against the unrelenting winds of drugs, video tape, and societal backlash.It's also a (really messed up) New Year's movie! AND a reminder of PTA's roots, as we prepare for the likely Awards sweep of his latest film, One Battle After Another.Join us for a free-wheeling Pre-NYE party, where we'll also take your questions, comments, and SuperChats!Support Kicking the Seat on Patreon, subscribe to us on YouTube, and follow us at:XLetterboxdInstagramFacebookShow LinksWatch the Boogie Nights (1997) trailer.As mentioned in the show, Ian had a couple of run-ins with Boogie Nights star Thomas Jane at the 2009 San Diego Comic-Con. Presented here is the two-part "The Thomas Jane Affair":Part OnePart TwoPick up Warner Bros' recently released 4K UHD of Boogie Nights.In case you missed it: check out EMC's roundtable review of One Battle After Another from earlier this year.Support all of Earth's Mightiest Critics at their various outlets:Keep up with Jeff York's criticism and caricatures at The Establishing Shot and Pipeline Artists.Check out Mark "The Movie Man" Krawczyk's The Spoiler Room Podcast.Get seated with The Blonde in Front!Follow David Fowlie's film criticism at Keeping It Reel.Get educated with Don Shanahan at Every Movie Has a Lesson…...And Film Obsessive...and the Cinephile Hissy Fit Podcast.Keep up with Annie Banks at The Mary Sue....and We Got This Covered.Make Nice with Mike Crowley of You'll Probably Agree.And save your celluloid soul with Dave Canfield's Substack, "Creature Feature Preacher".

The Cognitive Crucible is a forum that presents different perspectives and emerging thought leadership related to the information environment. The opinions expressed by guests are their own, and do not necessarily reflect the views of or endorsement by the Information Professionals Association. During this episode, Bill Wall discusses Accrete AI's comprehensive AI platform. The conversation explores the necessity for the U.S. to balance military focus with information strategies, diplomacy, and a deeper understanding of the populace to achieve success in modern conflicts. Recording Date: 9 Dec 2025 Resources: Cognitive Crucible Podcast Episodes Mentioned #56 Bob Jones on Governance Accrete AI Seven Pillars of Wisdom: A Triumph by T.E. Lawrence The Tipping Point: How Little Things Can Make a Big Difference by Malcolm Gladwell LikeWar: The Weaponization of Social Media by P. W. Singer and Emerson T. Brooking Contagious: Why Things Catch On by Jonah Berger Link to full show notes and resources Guest Bio:  Bill Wall is the CEO and Co-Founder of Accrete AI Government, an enterprise AI company helping government entities rapidly capture and analyze massive amounts of siloed data, providing analysts with deep insights that enable faster decision-making. Bill has a unique background, combining elite military service and deep experience in the sales and implementation of innovative solutions that drive business transformation. In the private sector, Bill has built technology teams across various industries. His professional experience includes leadership roles at companies like EMC, Praescient Analytics, Boundless Geospatial, and Flywheel Data, where he focused on IT solutions, big data analytics, and geospatial software. Before entering the corporate world, Bill retired from the Army as a Special Forces Lieutenant Colonel after twenty-two years in service. During his military career, he founded a computer network operations organization within the Joint Special Operations Command (JSOC) and deployed multiple times to Afghanistan, Iraq, and Yemen where he worked closely with the national intelligence community to transform the way intelligence was developed and shared. Academically trained in international relations, Bill holds a Bachelor of Science from Georgetown University's School of Foreign Service and a Master of Arts in International Relations and Latin American Studies from the University of Miami. Beyond his professional achievements, he has been married to Francesca for 30 years and is a father to two sons, sharing his home with two dogs and a cat. About: The Information Professionals Association (IPA) is a non-profit organization dedicated to exploring the role of information activities, such as influence and cognitive security, within the national security sector and helping to bridge the divide between operations and research. Its goal is to increase interdisciplinary collaboration between scholars and practitioners and policymakers with an interest in this domain. For more information, please contact us at communications@information-professionals.org. Or, connect directly with The Cognitive Crucible podcast host, John Bicknell, on LinkedIn. Disclosure: As an Amazon Associate, 1) IPA earns from qualifying purchases, 2) IPA gets commissions for purchases made through links in this post.

At first, we wondered why Zane Rowe was once again leading us back to Continental Airlines. With notable CFO tenures at VMware and EMC—chapters rich with transformation—surely there were fresh stories to surface.But as Rowe began tracing the logic behind flight profitability, route modeling, and data-rich decision making, the relevance snapped into focus. His Continental experience isn't just a recurring anecdote; it's the lens through which he still interprets complex systems today. That early foundation made this discussion every bit as insightful as our last—especially as he connected those lessons to Workday's AI trajectory and the accelerating pace of strategic decision making.“I spent a lot of time in the airlines in what we called flight profitability,” Rowe tells us. At Continental, he helped build systems to understand which routes truly created value when full planes were still losing money, he tells us. That work, grounded in heavy telemetry and EMC technology, showed him how finance could move from reporting results to reshaping the route portfolio, he tells us.In his first conversation with CFO Thought Leader, Rowe walked through those early chapters—from revenue management at a post-bankruptcy airline to a bold sales pivot at Apple and multiple CFO roles in technology, he tells us. In this second interview, he returns to the same storyline but takes it one step further, drawing a direct line from that profitability model to today's AI-driven world, he tells us.Now, as Workday's CFO, he describes AI as an equalizer that lets small teams run multiple forecasting models and ingest far more variables in cash projections than before, he tells us. He points to “Everyday AI,” a company-wide initiative, and a cross-functional AI leadership group that pushes common tools, responsible use, and regular check-ins on what is changing in the work itself, he tells us.Rowe's finance strategic moment this year is “recognizing the importance of investing more into AI”—organically and inorganically—because peers are not standing still and customers want those capabilities, he tells us. With a total addressable market “in the hundreds of billions of dollars” and revenue “much less than that,” he frames leadership now as deciding where to lean in hardest, he tells us.

This Week's Callers Caller 1: Backdoor Clint says everyone likes SnailMail Caller 2: Jeff from OR talks about the budget 9" Caller 3: Nathan from Pittsburgh says he is excited for Trail Hero Caller 4: Beer Craig has a podcast suggestion for caring for your winch. Factor55 Winch Line Video: https://www.instagram.com/reel/DQCXD62DQYP/?utm_source=ig_web_copy_link&igsh=MzRlODBiNWFlZA== Caller 5: Trevor talks about 1-15 Trail Ratings Caller 6: Chris Rea clarifies what EMC stands for Caller 7/8 Alex from Botches Off-road says congrats on getting married CALL US AND LEAVE US A VOICEMAIL!!!! We want to hear from you even more!!! You can call and say whatever you like! Ask a question, leave feedback, correct some information about welding, say how much you hate your Jeep, and wish you had a Toyota! We will air them all, live, on the podcast! +01-916-345-4744. An alternative method would be sending us an email at Jimmy@snailtrail4x4.com or at Tyler@snailtrail4x4.com. You can also find us on Instagram at SnailTrail4x4 or 4x4ToyotaTyler Listener Discount Codes: SnailTrail4x4 -SnailTrail15 for 15% off SnailTrail4x4 MerchMORRFlate - snailtraill4x4 to get 10% off MORRFlate Multi Tire Inflation Deflation™ Kits4WheelUnderground - snailtrail for 10% offIronman 4x4 - snailtrail20 to get 20% off all Ironman 4x4 branded equipment!Sidetracked Offroad - snailtrail4x4 (lowercase) to get 15% off lights and recovery gearSpartan Rope - snailtrail4x4 to get 10% off sitewideShock Surplus - SNAILTRAIL4x4 to get $25 off any order!Mob Armor - SNAILTRAIL4X4 for 15% offSummerShine Supply - ST4x4 for 10% offBackpacker's Pantry - Affiliate