All Episodes
Maintainable — 234 episodes · page 2 of 3
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
EUrban Hafner - Management Isn't For Everyone
EAmy Isikoff Newell - Code Shouldn't Drive Us To Drink
Podcast Panel at RailsConf 2022
EChelsea Troy - All Code Has Maintenance Load
Paula Paul - Getting People To Understand Is a Challenge
EBen 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
EJean Yang - Not All Software is Meant to be Maintained
EShaundai Person: Work on Having a Short-term Memory
EChris Birchall: Re-Engineering Legacy Software
ESwizec Teller: What is a Senior (Engineer) Mindset?
EHeidi Waterhouse: Documentation: The Best Diff is a Red Diff
EDHH: Celebrating Legacy Software as a Victory and the Story of How Humans Can't Estimate
EMatt Wynne: Cucumber and Why Is TDD Such a Challenge?
ETom Granot: Finding Your Style When Explaining Things to Technical Audiences
EAndrew Watkins: How To Test What You're Trying to Build
ERodney Cobb: Repeatable. Testable. Scalable.
EDr. 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
EAmy Sorensen: Nail Baths vs Nail Soaks
ELogan Luke Tyler Tanner: Overcoming Nail Biting During a Pandemic
EErica Tafavoti: Adding Density to Extend Their Life
EDuncan Thorpe: Disrupting the Mammalian Industrial Nail Complex
EShannon 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
EMichael 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?
EGianluca Arbezzano: Technical Debt Beyond Code & Your First Contributions to Open Source
EAli Spittel: Junior Developers and Helping Unlock Their Potential
ERobby Russell: Turning the Mic Around with Kayla Reopelle
ERyan Cromwell: Is the Juice Worth the Squeeze?
ECamille Fournier: How Does a Developer Become a Manager?
EGonçalo Silva: How A Fully-Remote Team Builds and Maintains Software
Tudor Girba: Moldable Development and Software Environmentalism
EJeff Haynie: How Can We Make Software Development Better for Dev Teams?
EVladimir Khorikov: 100% Test Coverage is an Artificial Metric
EBryan Helmkamp: Don't Let Perfect Be The Enemy of Good
EDr. Aino Vonge Corry: Why Do We Have Retrospectives, Again?
Trisha Gee: Developers Should Invest More Time Into Learning Their Tools
ESandi Metz: Making is Easy, Mending is a Challenge
Clare Sudbery: Refactoring Should Be Part of Your Daily Work
EKelly Sutton: Custodians of the Monolith
EJonathan Abourbih: Creating a Culture Where It's Okay To Take Risks
EJessica Kerr: Software Is Not A Craft (or an Art)
EJon Thornton: Technical Debt is a Good Thing (Sometimes)
EBen 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?
EMike Perham: How Developers Underestimate Long-Term Costs of External Dependencies
EEv Haus: Good Code Can Be Easily Deleted
EAdam Tornhill: Prioritizing Technical Debt With Behavioral Code Analysis
EM. Scott Ford: Menders In Hiding and the Joy of Legacy Code
EGitte Klitgaard: Making Space For Psychological Safety in Software Teams
ENathaniel Bibler: Communication Strategies Between Developers and Clients
E