All Episodes

Gabriela Moreira: When 800 Tests Aren’t Enough

Matija Šošić: Abstractions Aren’t Going Anywhere

José Valim: Designing a Language You Can Maintain for Decades

John Athayde: Maintaining the User Side of Software

Kristin Isaac: The Customer Doesn’t Care About Your Technical Debt

David Hayes: Boring Software, Clear Incentives, and Better Checklists

Diana Pfeil: Building Confidence in Probabilistic Systems

Chris Coyier: The Long Game of Maintaining CodePen

Sally Lait: Confidence Is the Real Metric

Rein Henrichs: The Real Work of Maintenance Happens Before You Touch the Code

Russ Olsen: The Hidden Cost of Forgetting Why the Code Looks Like That

Joel Oliveira: Predictability Is a Maintainability Feature

Lucas Roesler: The Fast Feedback Loop Advantage

Brittany Ellich: Using AI to Maintain Software, Not Rewrite It

Kent L Beck: You’re Ignoring Optionality… and Paying for It

Don MacKinnon: Why Simplicity Beats Cleverness in Software Design

Chris Zetter: Building a Database to Better Understand Maintainability

Denis Rechkunov: When Consistency Becomes a Culture

Nathan Ladd: Relentless Improvement and the Cost of Neglect

Taylor Otwell: What 14 Years of Laravel Taught Me About Maintainability

Sara Jackson: Why Resilience Is a Team Sport

Joel Chippindale: Why High-Quality Software Isn’t About Developer Skill Alone

Melanie Sumner: Why Continuous Accessibility Is a Strategic Advantage

Joe Masilotti: Simplify Your Stack, Ship Mobile Sooner

Freedom Dumlao: What 70 Java Services Taught Me About Focus

Mercedes Bernard: Friendly Code Welcomes Everyone In

Evan Phoenix: The Why of the One Line

Chris Salvato: Building Developer Paradise by Sitting in the Problem Space

Heimir Thor Sverrisson: Architecture First, Tech Debt Second

Noémi Ványi: Only Fix Problems That Are Actually Problems

Julia López: Code Tells a Story—Even the White Spaces

Marty Haught: Rethinking Technical Debt—Is It Really Just Drift?

Mike Bowers - From ISAM to JSON—Navigating 40+ Years of Database Evolution

Lorna Mitchell: Writing Documentation Engineers Will Actually Read

Carola Lilienthal: Tackling Technical Debt with Patterns and Domain Knowledge

Joel Hawksley: The Hidden Costs of Frontend Complexity

Austin Story: Making Software Easier to Change, Remove, and Evolve

Dan Moore: Building Developer-Friendly Authentication Solutions

Tom Johnson: From Auto-Documentation to Better Collaboration

Gulcin Yildirim Jelinek: Maintaining Postgres for Modern Workloads

Justine Gehring: Refactoring Software at Scale with AI

Katerina Skroumpelou: Bridging Engineering and Advocacy for Scalable Software

Moriel Schottlender: The Challenges of Modernizing MediaWiki's Monolith

Kate Holterhoff: From Front-End Engineering to Developer Advocacy

Alan Ridlehoover: Building Robust Systems Through Behavior-Centric Testing

April Wensel: Navigating Legacy Code with Compassion

Saron Yitbarek: The Balance Between Maintainable Code and Multiple Streams of Income

Lutz Hühnken: Crafting Resilient Systems with Event-Driven Design

Noel Rappin: Reviving the Pickaxe— A Journey through Ruby's Legacy

Cassidy Williams: Navigating the Career Jungle Gym in Tech

Obie Fernandez: Pioneering AI in Ruby on Rails Development

Tekin Süleyman: Balancing Complexity and Team Size

Ryosuke Iwanaga: The Benefits of Cell-Based Architecture

Julia Ferraioli - Capturing Untold Open Source Stories

Tanmai Gopal: Unlocking the Potential of Unified APIs

James Socol: Building Social Capital in Engineering Teams

Paola Ducolin: Building Trust and Communication in Engineering Teams

Robin Heinze - React Native and the Art of Flexibility

Scott Hanselman - The Fear Factor in Maintainable Software

Stig Brautaset: Understanding Alien Artifacts in Legacy Code

Brit Myers - Decoding Product vs. Technical Risk

Andrea Guarino - Leveraging Static Analysis for Better Code

Staffan Nöteberg - On the Power of Monotasking in Software Development

Martin Emde - Ruby Central and the Art of Being Tolerant to Change

Esther Olatunde - AI's Role in Evolving Software Engineering Practices

Robbie Wagner - Whiskey, Front-End, and Whatnot

Irina Nazarova - Investing in Innovation: The Consultancy's Guide to Growth

Kyle Daigle - Scaling Up with AI: A New Era of Code Maintenance

Jon Moniaci - Can We Draw A Boundary?

Chad Fowler - How Small Can We Make This Problem

John Nunemaker - How Scary Is This Change?

Jemma Issroff - Running the Parser in the Rain

Jeanine Soterwood - Helping Clients Understand Maintenance Work

Andrew Atkinson - Maintainable... Databases?

Jimmy Koppel - Aspects of Good Code

Hila Fish - Maintainable Infrastructure Code, Culture, and Documentation

Jacob Aronoff - At Least One Person Who Cares To See It Through

Oliver Drotbohm - Modulithic Applications

Colin Campbell - The Daily Habits of Effective Engineers

Dave Bryant Copeland - Quantifying the Carrying Cost

Cameron Jacoby - Am I Learning From This?

Adriana Villela - On Being a Serial Refactorer

Ahmed Wasfy - Thriving as an Engineering Manager

Naomi Ceder - People-Centric Community Building

Nadia Odunayo - Don't Try to Solve a Pain Point For a Problem You Aren't Experiencing

Daniela Baron - About Those Docs

Cory House - Finding Opportunities for Improvement

Avery Quinn - Can You Quantify the Impact?

Carlos Blé - Código Sostenible

Lena Reinhard - How Will People Get Stuff Done?

Eric Normand - Grokking Simplicity

Henrik Warne - There is No Software Maintenance

Andy Croll - Keep the Weird Stuff Weird

Marianne Bellotti - Building Empathy by Asking, "How Would You Write This in 2007?"

Arpit Mohan - Aspiring To Be Boring As Possible

Noah Clark - Maintainable Software is a Team Sport

Ben Parisot - Documentation Just Needs To Be Used Once

Stefanni Brasil - When Is Tackling Tech Debt Possible?

Andrea Goulet - Empathy-Driven Software Development

John Ousterhout - It's Not You, It's the Codebase