Maintainable

Sally Lait, a fractional technology leader with 20+ years modernizing legacy systems and guiding teams. She reframes maintainability around documentation, onboarding speed, knowledge sharing, and especially team confidence. The conversation covers measuring qualitative health, communicating small wins, modernizing long-lived apps, and practical onboarding tips for older codebases.

Rein Henrichs, a principal software engineer focused on maintainability and resilience, shares why maintenance is about shared understanding. He explains the line of representation, common ground, weak signals of decaying understanding, incident coordination, partial failures, and how mentoring and observability build adaptive capacity.

Russ Olsen, independent consultant and author of Eloquent Ruby (Second Edition), shares why code gets costly when the original reasoning vanishes. He discusses documenting intent and trade-offs, spotting pinch points in legacy systems, when elegance becomes harmful, the value of fresh perspectives, and practical strategies for incremental rewrites and improving developer quality of life.

Joel Oliveira, engineering manager at ezCater with decades in software, focuses on maintainability and practical migrations. He talks about predictability in codebases, why test coverage can mislead, replacing a leaky image service with ImageProxy, finding a GraphQL seam for incremental migration, and using feature flags and small steps to safely modernize systems.

Lucas Roesler, Managing Partner and CTO at Contiamo, is a data engineering and DevOps leader focused on observability and modernizing legacy systems. He talks about designing for fast feedback through logs, metrics, and tracing. He tells a concrete decade-old Postgres modernization story. He explains treating SQL and infrastructure as code and running local observability to reduce guesswork.

Brittany Ellich, a Senior Software Engineer at GitHub, talks about the importance of maintaining existing software rather than opting for risky rewrites. She emphasizes that well-maintained software is readable and manageable for future developers. Brittany redefines technical debt, arguing it often includes bugs and reliability issues. The conversation highlights how AI, like coding agents, can assist in tackling small maintenance tasks incrementally while leaving complex problem-solving to humans. Her insights challenge conventional views on software evolution and ethical AI use.

Kent Beck, a pioneer in agile methods and author of Tidy First?, dives into the critical but often overlooked concept of optionality in software development. He discusses the tension between current features and maintaining future flexibility, highlighting how developers must balance these while navigating cost shifts from cheap labor to expensive compute. Beck advises on making hard changes easier, avoiding splitting teams, and emphasizes the ethical duty to enhance code clarity to benefit the entire team. His insights challenge traditional views on software maintainability.

Don MacKinnon, a software engineer and founder of Searchcraft, discusses the importance of simplicity in software design. He shares a story about how an unnecessary abstraction in a Node.js API complicated development. Don explains how his team’s structure evolved from consulting pain points and emphasizes the value of clear project structure and documentation. He also advises on evaluating third-party libraries and uses real-world examples to illustrate the transition from dynamic languages to TypeScript and Rust for improved maintainability.

In this conversation, Chris Zetter, a software engineer and author focused on architecture and maintainability, shares insights about building relational databases. He emphasizes that effective software should enhance value and adaptability, often prioritizing solid documentation over code comments. Chris challenges the typical notions of technical debt, advocating for transparency about its causes. He also discusses the benefits of pairing in coding, especially for junior developers, and the value of choosing stable technology to improve reliability.

Maintaining consistency across a sprawling codebase is one of the hardest challenges in software engineering. Denis Rechkunov, a Principal Software Engineer at Elastic, joins Robby to share how his team turned consistency into a cultural practice rather than a technical checklist. From managing open source projects with hundreds of contributors to experimenting safely with new patterns, Denis believes maintainability begins with shared ownership, not just clean code.He explains how Elastic introduced automation and linters to improve cohesion without discouraging creativity. Instead of enforcing perfection across the entire system, Denis’ team scopes their changes to manageable areas and rewards steady progress over sweeping rewrites. Their annual “On Week” tradition gives engineers space to fix what frustrates them most, showing how small, focused bursts of work can produce big leaps in stability and morale.The conversation also explores the human side of maintainability. Denis recalls early lessons about unclear expectations, the importance of documenting decisions in public pull requests, and how open feedback loops build trust across remote teams. Whether it’s stabilizing a flaky CI pipeline or mentoring new engineers, Denis argues that technical excellence thrives when consistency becomes a habit shared by everyone.Episode Highlights[00:01:02] Defining Well-Maintained SoftwareDenis identifies consistency, documentation, testability, and agility as the key ingredients of maintainable systems.[00:02:22] Balancing Standards and AutonomyHow automation and linters help preserve code cohesion while minimizing interpersonal friction.[00:04:08] Experimenting SafelyElastic scopes new patterns to low-risk modules before broader adoption, avoiding mass rewrites.[00:07:19] Incremental CleanupLinters only apply to changed files, helping the team fix issues gradually without overwhelming contributors.[00:08:02] Maintainability as a People ProblemDenis highlights that sustainable systems depend more on culture and mentorship than on architecture.[00:10:13] Lessons from MiscommunicationAn early experience showed the cost of undocumented conventions and unclear onboarding.[00:17:09] Making Space for Technical DebtElastic’s engineers dedicate part of each sprint and an annual “On Week” to tackle maintenance work.[00:23:05] Restoring CI ReliabilityDenis shares how the team revived a pipeline with only a 10% success rate by categorizing failures and focusing on data.[00:32:00] Practicing Software ArchaeologyHe stresses the value of documenting discussions in pull requests to avoid historical guesswork later.[00:36:09] Feedback and TrustOpen communication, humility, and mutual feedback loops form the backbone of a maintainable culture.[00:51:00] Embracing Chaos in Open SourceDenis encourages teams to accept a degree of entropy and focus their efforts on user-facing stability.[01:00:00] Security and PrivacyWhy maintainability, trust, and privacy are inseparable pillars of long-term sustainability.[01:01:06] Where to StartInstead of rewriting code, start by cultivating maintainability as a shared value across the team.Resources MentionedElasticgolangci-lintAppSignalThe Caves of Steel by Isaac Asimov — Denis’ recommendation inspired Robby to finally pick up a copy and start reading it himself.Denis’s Blog – rdner.deDenis on GitHubDenis on MastodonDenis on LinkedInThanks to Our Sponsor!Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks.It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.