Life-Saving Networks

Send a textWhat does “mission-critical networking” really mean?At St. Jude Children’s Research Hospital, it’s not about uptime SLAs or dashboard metrics; it’s about supporting the research and care that helps save children’s lives.In this episode, we sit down with Remington Loose and Josh Morris to explore the architecture, scale, and responsibility behind one of the most meaningful networks in the world.We dig into:How research networking differs from traditional enterprise ITThe massive data demands behind pediatric cancer researchDesigning networks where downtime isn’t just inconvenient, it’s unacceptableSupporting clinicians, researchers, and life-saving applications simultaneouslyLessons enterprise engineers can learn from healthcare environmentsFrom high-performance data movement to reliability strategies that operate without margin for error, this conversation reframes what networking looks like when human outcomes are on the line.Because in environments like St. Jude…The network isn’t just infrastructure; it’s part of the care team.This episode has been sponsored by Meter. Go to meter.com/aone to book a demo now! Support the showFind everything AONE right here: https://linktr.ee/artofneteng

Send a textErika Dietrick (aka “Erika the Dev”) is back on the show, and she’s days away from a major life change (welcome, Baby Dev). In this follow-up conversation, we dig into the thing that keeps coming up in network engineering careers: programming is no longer a “nice-to-have.”Erika breaks down her free YouTube course designed specifically for network engineers: Level 1 is “programmatic thinking” (the mindset + foundations), Level 2 is where AI becomes your learning accelerator, and Level 3 is about generating code responsibly, without falling into the “vibe coding” trap.We also talk about why coding feels so foreign to CLI lifers, why so many “slick” courses lose beginners, and how to use AI like Google-on-steroids. If you’ve ever thought, “I’m not smart enough for this” or “I don’t have time,” this one’s for you.What we cover:- Why network engineers struggle with coding (and it’s not your fault)- The difference between using AI while coding vs vibe coding- How to build foundations that make AI actually useful- Why libraries matter, and how Level 2 focuses on network automation libraries- Career reality: why Python shows up in job descriptions everywhereFind Erika:YouTube: https://www.youtube.com/@UCkWURMuDQZox53bskCFS6vw LinkedIn: https://www.linkedin.com/in/erikadietrick/This episode has been sponsored by Meter. Go to meter.com/aone to book a demo now! Support the showFind everything AONE right here: https://linktr.ee/artofneteng

Send a textWe've all worked on those technical projects that felt doomed from the start. In this episode, we're joined by Eyvonne Sharp and Mike Bushong to dig into what actually derails technical projects, and why the root cause is usually people, not packets.We unpack:- Why 80–90% of project failures aren’t technical- What “executive sponsorship” is supposed to mean (and why most teams never use it)- The real reason timelines feel arbitrary: information asymmetry- What “healthy escalation” looks like (and how to avoid the courtroom vibe)- How to deliver bad news to leaders: few words, calm tone, clear next step, clear ask- The leadership move that instantly lowers the temperature: removing blame- Why informal networks matter, including a legendary security-incident save powered by… cheesecakeIf you’ve ever felt stuck in status-call theater, pressured to keep the project's status green, or unsure how to talk to leadership when reality hits, this episode is your playbook.This episode has been sponsored by Meter. Go to meter.com/aone to book a demo now! Support the showFind everything AONE right here: https://linktr.ee/artofneteng

Send a textRecorded on-site in Austin, Texas, at AutoCon 4 (Network Automation Forum), Andy sits down with Colin Doyle to talk about the human side of technical communication and why it matters more than ever in technical careers.They dig into practical speaking advice for engineers: how to slow down without losing authority, why “dead air” feels scarier than it is, how to stop relying on scripts, and how to structure a talk so your audience can repeat your message when you leave the room. Colin shares the “audience-first” mindset shift: don’t tell your story, tell the audience’s story with you in it.Then the conversation widens into the network automation adoption problem: why network automation still lags behind other IT domains, why tooling fragmentation creates anxiety (“what if I learn the wrong thing?”), and why starting with Python is often the safest first step. Colin also reframes overlays (EVPN/VXLAN) as a fundamental shift: abstraction changes operations, pushes configuration to the edge, and makes intent-based operations and assurance the real job.If you’re a CLI lifer preparing to level up, or you’re giving your first big talk, this episode is a practical, grounding guide.In this episode: communication fundamentals, talk prep, booth culture at AutoCon, automation adoption barriers, overlays → intent → assurance, and why you don’t need to be a “kung fu wizard” to start automating.This episode has been sponsored by Meter. Go to meter.com/aone to book a demo now! Support the showFind everything AONE right here: https://linktr.ee/artofneteng

Send a textMost network engineers know BGP, OSPF, and maybe EIGRP, but far fewer have hands-on experience with ISIS. In this episode of The Art of Network Engineering, Andy Lapteff sits down with Russ White and Mike Bushong for a deep, opinionated, and refreshingly honest discussion about routing protocol design in modern data centers.We explore why BGP has become the default hammer for every networking nail, what we lose when we blend underlay and overlay into a single protocol, and why some of the largest networks in the world still rely on IS-IS for simplicity, scale, and resilience.This isn’t a “which protocol is best” argument, it’s a design conversation. One about failure domains, operational reality, education gaps, and why many engineers never learn the protocols that quietly power hyperscale networks.In this episode:Why BGP is policy-rich but intentionally slowThe architectural value of separating underlay and overlayHow ISIS works and why it’s simpler than you thinkTLVs, scalability, and protocol evolutionWhy familiarity often beats good design (for better or worse)Where RIFT fits and where it doesn’tThe cost of losing deep protocol knowledge as engineers retireIf you’ve ever wondered why networks are designed the way they are, or if you’ve felt uneasy about “just using BGP everywhere,” this conversation is for you.Subscribe for more conversations where technology meets the human side of IT.This episode has been sponsored by Meter. Go to meter.com/aone to book a demo now! Support the showFind everything AONE right here: https://linktr.ee/artofneteng

Send a textIn this special on-location episode of The Art of Network Engineering, Andy Lapteff sits down in person with Kevin Myers for a conversation that pulls no punches.Kevin brings decades of service provider and whitebox experience to the table as the two dive deep into one of networking’s most complex decisions: how to choose the right vendor to build your network.From Cisco to whitebox, from enterprise carpeted IT to hyperscale data centers, this episode is all about designing networks that align with business needs, not just personal bias or legacy choices.Topics include:Why vendor selection should come after requirements gathering.How multi-vendor environments can create both resilience and complexity.When whitebox networking makes sense—and what kind of teams can support it.The hidden "operational tax" of expanding your vendor portfolio.Why understanding the business is the most critical skill for modern engineers.Whether you're a design engineer, network architect, or just trying to future-proof your ops, this episode is packed with insights that will change how you think about gear, vendors, and the networks we build.This episode has been sponsored by Meter. Go to meter.com/aone to book a demo now! Support the showFind everything AONE right here: https://linktr.ee/artofneteng

Send a textAndy sits down with longtime friend William Collins to unpack three big themes shaping modern NetOps. First: the AWS US-East-1 outage and the myth that “cloud = resiliency by default.” They explore blast radius, hidden regional dependencies, cost trade-offs (active/active vs. DR), and why resiliency is engineered, not purchased. Next: how public speaking accelerates a technical career (without live-demo heartbreak). William shares practical tactics to craft a memorable talk, lean on story, and handle Q&A. Finally: a plain-English walkthrough of Model Context Protocol (MCP), why it exists, how it standardizes tool access for LLMs, and what that means for real NetOps workflows. If you design for failure, want to level up your communication skills, or keep hearing “MCP” and wonder what it actually does, this one’s for you.This episode has been sponsored by Meter. Go to meter.com/aone to book a demo now! Support the showFind everything AONE right here: https://linktr.ee/artofneteng

Send a textNetwork engineers don’t tune into corporate all-hands because they’re “lazy,” they tune out because the message often isn’t for them. In this episode of The Art of Network Engineering, Andy Lapteff sits down with longtime industry leaders Scott Robohn and Mike Bushong to unpack the disconnect between engineering teams and executive communications, and how to fix it.They talk about:Why engineers roll their eyes at town halls, earnings calls, and “four pillars of excellence”How leadership actually thinks about growth, stock price, cost centers, and enablementThe two jobs every company really has: build stuff or sell stuff, and where networking fitsHow to pitch your ideas in business terms so they get fundedWhy AI networking and data center infrastructure are the next durable growth areas for network prosThe difference between being part of the product vs. enabling the product,  and why it matters for your careerIf you’ve ever thought, “Just let me do my job,” this one’s for you. You’ll walk away knowing how to connect your automation, operations, or data center work to the outcomes your company actually cares about: revenue, speed, customer experience, and risk.Listen in, take notes, and then go advocate for your work like it matters, because it does.This episode has been sponsored by Meter. Go to meter.com/aone to book a demo now! Support the showFind everything AONE right here: https://linktr.ee/artofneteng

Send a textBlue Origin’s Lexie Cooper is back! We riff on New Glenn’s first launch and what “vehicle #2” means for launch cadence, where to watch from Florida without getting arrested, and why streaming your learning, even when it’s awkward, is a cheat code for growth. Andy shares his live Python study saga (and a friendly dust-up with Jeff about “just code it”), while Lexie takes us down to Layer 1: PHYs, link pulses, why “turning off auto-negotiation” isn’t always what you think, and why messy home labs beat pretty cable porn. We also get real about authenticity at vendors, the pressure to be “polished,” and whether networking is still a great career in an automation-heavy market.If you need a nudge to build, break, and learn in public, this one’s it.In this episode:New Glenn’s growing fleet & why multiple boosters matterHow/where to catch a Florida launch (scrubs happen)Learning in public: textbooks on stream, tension on mic, real takeawaysPHY vs. ASIC, MAC sublayers, and auto-neg gotchas (with an oscilloscope!)Home labs: why “spaghetti” > showroom racks for actual learningCareers: automation pressure, Git for config history, staying authenticStreaming nuts & bolts: TikTok vs. Twitch vs. YouTube, OBS scenes 101Women in networking and inviting more people into the fieldThis episode has been sponsored by Meter. Go to meter.com/aone to book a demo now! Support the showFind everything AONE right here: https://linktr.ee/artofneteng

Send a textLearning Python as a network engineer can feel confusing, frustrating, and let’s be honest, pretty dry at times. But Andy and Jeff are diving in together to make it real, relatable, and (hopefully) a little more fun.In this episode, they pick up where the last Python Party left off: exploring variables, strings, methods like .title() and .strip(), and why whitespace can break your scripts. Along the way, they share honest struggles, “aha!” moments, and practical applications for automation in the networking world.If you’ve ever looked at Python code and thought, “this isn’t for me,” this episode will make you feel seen. Join Andy and Jeff as they lab, laugh, and learn the building blocks that every network engineer needs to stay relevant in an automated future.This episode has been sponsored by Meter. Go to meter.com/aone to book a demo now! Support the showFind everything AONE right here: https://linktr.ee/artofneteng