All Episodes
Maintainable — 229 episodes
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
Courtney Wilburn - Maintainable Software Has Good Community Around It
Nelida Velazquez - We Have to Express Our Opinions
Casey Watts! - Culturesmithing
Marc Cornellà - Maintaining Open Source Projects
Shanea Leven - How To Bring Visibility To Your Codebase
Greg Foster - A Pattern for Smaller, Faster, and Frequent Code Reviews
Urban Hafner - Management Isn't For Everyone
Amy Isikoff Newell - Code Shouldn't Drive Us To Drink
Podcast Panel at RailsConf 2022
Chelsea Troy - All Code Has Maintenance Load
Paula Paul - Getting People To Understand Is a Challenge
Ben Halpern - Adventures In Open Sourcing Your Existing Application
Avdi Grimm - Don't Be Too Clingy To Your Tests
Aran Khanna - De-risk Your Cloud Resources
Jerod Santo - Having to Maintain Your Own Cleverness
Idit Levine - Production is the Real Test
Emily Giurleo - Maintaining Open Source vs Proprietary Software
Jean Yang - Not All Software is Meant to be Maintained
Shaundai Person: Work on Having a Short-term Memory
Chris Birchall: Re-Engineering Legacy Software
Swizec Teller: What is a Senior (Engineer) Mindset?
Heidi Waterhouse: Documentation: The Best Diff is a Red Diff
DHH: Celebrating Legacy Software as a Victory and the Story of How Humans Can't Estimate
Matt Wynne: Cucumber and Why Is TDD Such a Challenge?
Tom Granot: Finding Your Style When Explaining Things to Technical Audiences
Andrew Watkins: How To Test What You're Trying to Build
Rodney Cobb: Repeatable. Testable. Scalable.
Dr. Michaela Greiler: Getting Awesome at Code Reviews
Mark Kilby: Overcoming Challenges that Remote Technical Teams Experience
Kevin Stewart: Short-term Decisions That Need To Be Revisited
Ken Fogel: What Are You Leaving Behind?
Murray Steele: Maintainable Code Is Easy to Turn Off and Delete
Dr. Felienne Hermans: Looking Inside The Programmer's Brain
Bertold Kolics: Are You Carrying the Weight of Dead Code?
Kent C. Dodds: AHA Programming and Testing JavaScript
Mark Adams: HOWTO Prepare (Your Nails) for Burning Man
Amy Sorensen: Nail Baths vs Nail Soaks
Logan Luke Tyler Tanner: Overcoming Nail Biting During a Pandemic
Erica Tafavoti: Adding Density to Extend Their Life
Duncan Thorpe: Disrupting the Mammalian Industrial Nail Complex
Shannon Jackson: Oh, Wait, Nope...Those Aren't My Gutter Nails
Brian Scanlan: Improving Oncall Support with Meaningful Alarms
Alexandre Omeyer: Removing the Barriers to Track Technical Debt
Roopak Venkatakrishnan: The Importance of Optimizing For Local Development and Build Systems
Benjamin Wood: Rescuing Ruby on Rails Projects
Johanna Rothman: No, Great Developers Aren't Destined to Be Great Managers
Helen Scott: Strategies For Measuring Developer Experience (DX)
Robert Kaufman: Running a Consultancy and a Coding School
Heidi Helfand: The Art and Wisdom of Changing Teams
Jutta Eckstein: How Software Impacts Our Planet
John Cech: How To Mentor Interns On Software Projects
Theresa Neate: Testing != Quality
Michael Springer: Vetting External Dependencies
Jason Swett: Refactoring Is Necessary to Keep Your Blade Sharp
Sudhir Reddy: Don't Be Afraid to Slash and Burn
Monica Lent: Progress Is More Important Than Perfection
Trae Robrock: Understanding Your Risk Tolerance As An Engineer
Mark Erikson: Accidentally Becoming an Open Source Maintainer
Bonnie Brennan: Building Community
Khaled Souf: Track Down Dead Code and Delete it
Adrianna Chang: Using the Strangler Fig Pattern at Shopify
Mark Downie: Balancing The Promises That Open Source Projects Make
Glenn Vanderburg: Don't Ask For Small Things
Suzan Bond: Embracing Discomfort and Navigating Transitions
Nicolas Carlo: Changing Messy Software Without Breaking It
Brittany Martin: How to Quit Your Job and Leave Your Code in Good Hands
Luke Redpath: User Stories Should Prompt Conversations
Hampton Lintorn Catlin: Only Add Complexity When Necessary
Pat Kua: The Challenges that Come with Becoming a Tech Lead
Aaron Blohowiak: The Myth of the Sufficiently Smart Engineer
Magda Miu: Building a Technical Leadership Career Around Teaching
Gant Laborde: Technical Debt — Trading Risk for an Advantage
Karen Lee Rigg: Where Are the Bad Habits Coming From?
Gianluca Arbezzano: Technical Debt Beyond Code & Your First Contributions to Open Source
Ali Spittel: Junior Developers and Helping Unlock Their Potential
Robby Russell: Turning the Mic Around with Kayla Reopelle
Ryan Cromwell: Is the Juice Worth the Squeeze?
Camille Fournier: How Does a Developer Become a Manager?
Gonçalo Silva: How A Fully-Remote Team Builds and Maintains Software
Tudor Girba: Moldable Development and Software Environmentalism
Jeff Haynie: How Can We Make Software Development Better for Dev Teams?
Vladimir Khorikov: 100% Test Coverage is an Artificial Metric
Bryan Helmkamp: Don't Let Perfect Be The Enemy of Good
Dr. Aino Vonge Corry: Why Do We Have Retrospectives, Again?
Trisha Gee: Developers Should Invest More Time Into Learning Their Tools
Sandi Metz: Making is Easy, Mending is a Challenge
Clare Sudbery: Refactoring Should Be Part of Your Daily Work
Kelly Sutton: Custodians of the Monolith
Jonathan Abourbih: Creating a Culture Where It's Okay To Take Risks
Jessica Kerr: Software Is Not A Craft (or an Art)
Jon Thornton: Technical Debt is a Good Thing (Sometimes)
Ben Orenstein: "Someday We'll Go Clean That Up" Doesn't Work
Ernesto Tagwerker: Tracking Technical Debt With Metrics (aka Stink Score)
Marit van Dijk: How Are We Going to Test This?
Mike Perham: How Developers Underestimate Long-Term Costs of External Dependencies
Ev Haus: Good Code Can Be Easily Deleted
Adam Tornhill: Prioritizing Technical Debt With Behavioral Code Analysis
M. Scott Ford: Menders In Hiding and the Joy of Legacy Code
Gitte Klitgaard: Making Space For Psychological Safety in Software Teams
Nathaniel Bibler: Communication Strategies Between Developers and Clients
Abby Bangser: Building Trust In Your Deployment Pipeline
Viktor Klang: Condensing The Codebase Over Time
Beth Long: Maintainable Code Prioritizes How Humans Interact With It
Emily Bache: It's Always More Fun to Code with Others
Zee Spencer: How Can We Reduce Carrying Costs?
Ana Nelson: Writing Maintainable Code Documentation with Automated Tools and Transclusion
Dave Aronson: Putting the M in ACRUMEN
Michael Feathers: Be Curious & Chase The Rabbit Holes
Justin Searls: Learn To Understand The Runtime
Patricia Aas: Intersection of Programming & Security
Nate Berkopec: Why You Should Treat Performance Problems as Bugs
Victor Rentea: Never Separate The Refactoring From The Deliverable
Sandro Mancuso: Technical Debt is Anything Preventing You From Developing Fast
Bryan Liles: Create an Issue for Everything
Liz Keogh: The Power of Asking, "Can You Give Me An Example?"
Colin Jones: Software Consulting: Being a Good Guest
Jonathan Cutrell: Healthy Teams Know How to Eradicate Fear
Karolina Szczur: The Importance of Documentation for Remote Developers
Liran Haimovitch: The Benefits of Observability
Robert Meaney: Building Software That is Easy to Test
Melissa Eaden: It's Never a One Person Job
Steve Poling: The Real Enemy is Murphy
Matt Weagle: What Will It Enable Us to Do in the Future?
Mariah Howard: How To Discuss Technical Debt With Product Managers
Anne Marie Kirby: Selling the Upside of Improving your Codebase to Management
Marco "Ocramius" Pivetta: What Senior Devs Should Spend More Time On (It's Not Writing Code)
Lisa Crispin: Agile Testing & Technical Debt
Pim Elshoff: Refactoring How Engineers Communicate With Management
Morgan Senkal: Using Epics to Improve Code Quality Within Sprints
Eileen M. Uchitelle: Upgrading Ruby on Rails At Github And How To Stay Updated
Charity Majors: Deploys Are Just The Beginning
Sahil Lavingia: Pushing Forward Through Technical Debt After a Massive Layoff
Coraline Ada Ehmke: The Role Of Empathy In Engineering Teams
James Smith: What if We Measured Software with a Stability Score?
Anna Filina: How Every Decision Introduces Technical Debt