Episode 209 · Maintainable
Joel Chippindale: Why High-Quality Software Isn’t About Developer Skill Alone
1 Jul 2025 · 56 min
Episode notes
Is high-quality code really just about developer skill? According to CTO coach Joel Chippindale, the key to maintainable software often lies in the conversations you have before writing a single line of code. In this episode, we explore how to reframe technical debt, build cross-team trust, and make legacy systems easier to change.
Podcast
Maintainable
Robby Russell · Tech & Science · English
Do you feel like you're hitting a wall with your existing software projects? Are you curious to hear how other people are navigating this? You're not alone. On the Maintainable Software Podcast, Robby speaks with seasoned practitioners who have overcome the technical and cultural problems often…
More from Maintainable All episodes →
-
E214 · 18 Nov 2025 · 50 min
Chris Zetter: Building a Database to Better Understand Maintainability
Software engineer and author Chris Zetter joins Robby to explore how pairing, documentation, and boring technology help teams build software that lasts. They unpack the real meaning of technical debt, how to guide junior engineers with confidence, and what building a database from scratch can teach us about architecture.
-
E213 · 28 Oct 2025 · 1 hr 7 min
Denis Rechkunov: When Consistency Becomes a Culture
At Elastic, Denis Rechkunov believes code consistency is more than a style guide — it’s a cultural practice. Robby and Denis explore how automation, empathy, and small rituals help teams write code that stays cohesive long after its authors move on.
-
E212 · 14 Oct 2025 · 55 min
Nathan Ladd: Relentless Improvement and the Cost of Neglect
In this conversation, Robby and Nathan Ladd, Principal at Brightworks Digital, explore what makes software sustainable in practice. Nathan argues that perfectly maintained software may be a myth, but that doesn’t stop teams from pursuing habits that reduce the burden of maintenance. He shares why keeping dependencies fresh, aligning around living standards, and fixing defects as they appear are all crucial to staying ahead.
-
E211 · 26 Aug 2025 · 56 min
Taylor Otwell: What 14 Years of Laravel Taught Me About Maintainability
Taylor Otwell looks back on 14 years of building and maintaining Laravel. From four stars on GitHub to a full-fledged ecosystem, he shares what it takes to design software that lasts—and why simple often wins.
-
E210 · 22 Jul 2025 · 53 min
Sara Jackson: Why Resilience Is a Team Sport
What happens when you treat resilience as a shared responsibility across your team, not just an infrastructure concern? Sara Jackson unpacks the value of documentation, application-layer chaos experiments, and test suites you can actually trust.
-
E208 · 10 Jun 2025 · 50 min
Melanie Sumner: Why Continuous Accessibility Is a Strategic Advantage
What if accessibility wasn’t a checklist—but an integrated part of your development workflow? Melanie Sumner shares how her team at HashiCorp is building with purpose and why continuous accessibility gives them a lasting edge.
-
E207 · 20 May 2025 · 56 min
Joe Masilotti: Simplify Your Stack, Ship Mobile Sooner
Consultant Joe Masilotti shares why most mobile apps don’t need to be fully native, how he helps Rails developers simplify their stack, and what it means to be a respectful guest in someone else’s codebase.
-
E206 · 22 Apr 2025 · 1 hr 3 min
Freedom Dumlao: What 70 Java Services Taught Me About Focus
Freedom Dumlao made the rare decision to rebuild a microservices platform as a monolith. In this episode, he shares why—and how it made his team more effective. Plus, we talk Java, Rails, AI, and how not to drown in decision-making.
-
E205 · 8 Apr 2025 · 49 min
Mercedes Bernard: Friendly Code Welcomes Everyone In
Mercedes Bernard believes that friendly code is the truest measure of maintainability. She shares how teams can reduce friction, make small architectural wins, and advocate for technical debt investment without sounding the alarm.
-
E204 · 1 Apr 2025 · 1 hr 9 min
Evan Phoenix: The Why of the One Line
What if trying to “future-proof” your code is actually making it harder to maintain? Evan Phoenix shares how a well-intentioned monolith split went sideways—and why clarity and confidence matter more than cleverness.
