Software maintenance without the folklore.
Maintainable treats software maintenance as both a technical and human practice. Robbie Russell talks with practitioners about codebases that carry history, pressure, tradeoffs, and the people responsible for keeping them understandable.
PRESS PLAY
Maintainable is a software engineering interview show about the work that begins after a system has users, history, deadlines, and baggage. Robbie Russell talks with seasoned practitioners about keeping software understandable and useful when easy answers have run out. The recurring focus is maintenance, but the show treats that word broadly. Code matters. So do team memory, communication, feedback loops, product pressure, management skill, and the ability to revisit old decisions without contempt. Recent conversations range from technical debt and legacy systems to AI coding agents, optionality, boring technology, database work, and the cost of running teams at full utilization. The guests tend to resist tidy slogans. Rein Henrichs frames maintenance around whether software makes sense to the people responsible for it. Russ Olsen pushes on the hidden assumptions that stick to old systems. Joel Oliveira talks about predictability, incremental migration, and compassion for past decisions. Lucas Roesler emphasizes readability and fast feedback in systems shaped by client work and complex database projects. Brittany Ellich considers AI as a tool for structured maintenance rather than wholesale replacement. Kent Beck brings the discussion back to options, capacity, and the value of making future change cheaper. Chris Zetter favors technology choices that reduce future traps. Nathan Ladd connects standards, validation, and cross-functional barriers to the daily health of a codebase. Across episodes, Maintainable feels less like a lecture series and more like a careful engineering debrief. The pacing allows nuance. The host asks practical follow-ups, especially when a concept needs to be grounded in team reality. The show is strongest when it sits with tension: measuring progress without flattening weak signals, modernizing without erasing history, and improving software without pretending every mess was avoidable. It is for engineers and technical leaders who have inherited systems, maintained systems, or wondered why a clean rewrite so rarely solves the deeper problem.
Made for: Maintainable is for software engineers, engineering managers, consultants, and technical leads working with long-lived systems. It especially suits listeners who care about legacy code, team habits, and practical architecture tradeoffs.
What sets it apart: The show treats maintainability as a lived operating condition, not a checklist. Its interviews connect code quality with team capacity, historical context, feedback, and the human judgment required to improve systems gradually.
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 associated with software development.Our guests will share stories in each episode and outline tangible, real-world approaches to software challenges. In turn, you'll uncover new ways of thinking about how to improve your software project's maintainability.
Based on 6 episodes we listened to · August 2026
Interview by interview, Maintainable turns the unglamorous work of keeping old software alive into specific, practitioner-level testimony for engineering leads.
Maintainable sits in the unglamorous, load-bearing corner of Technology: not the next launch, but what happens to software after it ships and keeps running for years.
You want the legacy-system therapy session before anyone says, 'Let's rewrite it.'
Press play if you want
Short reviews from the PlayNext desk, based on the episodes we processed.
A thoughtful look at the human judgment behind maintainable software.
Maintainable frames maintenance as a matter of shared understanding. Well-maintained software is not just code that runs, but software that makes sense to the people responsible for writing, changing, and operating it.
A thoughtful reminder that maintainability depends on who has to live with the code.
Maintainability lands as something more conditional than absolute: it depends on who has to keep a system alive, how long they are stuck with it, what they need from it, and what kind of software they are dealing with.
A humane, practical case for making legacy software manageable enough to improve.
Maintainable frames legacy software as the result of accumulated decisions, not a fixed mess waiting to be condemned. Joel Oliveira, an engineering manager at EasyCater with more than two decades in software, walks through a stubborn modernization effort that moved forward…
A practical episode on readable software, fast feedback, and the work of modernizing systems that have grown hard to understand.
Maintainable's conversation with Lucas Reisler, head of engineering at Contiamo, frames simplicity as something a team can work with day to day.
A practical discussion of using coding agents to chip away at technical debt without discarding software that already works.
Maintainable argues for treating working software as something worth caring for, especially once it is already in production and serving real users.
Kent Beck makes spare capacity sound like a design tool for the software that comes next.
Maintainable frames software upkeep as a bet on what a team may need next. Kent Beck describes development value as a balance between visible features and the options that make later work possible, then puts much of that tension in the hands of senior developers who have felt…
Power Platform news with practical static.
Rain Heinrichs, a principal software engineer at Procore, says maintainable software is software that makes sense to the people who keep it running.
Russ Olson tells Robbie Russell that maintainability depends on who is maintaining the code, what the software is for, and how long it has to last, then uses databases, device drivers, and landmine-tracking software as different examples.
Joel Oliveira, an engineering manager at EasyCater, tells Robbie Russell that maintainability starts with predictability in Rails, where models, controllers, views, helpers, and command objects give engineers a map.
Maintainable brings Robbie Russell together with Lucas Reisler, head of engineering at Contiamo in Berlin, Germany, for a conversation about software that is readable, observable, and easier to change.
Maintainable opens with Brittany Ellick of GitHub arguing that readable code is the first sign of well-maintained software, not a shiny rewrite.
Maintainable host Robbie Russell interviews Kent Beck, Agile Manifesto signatory and author of 'Tidy First?', about the tension between shipping features and preserving future options.
Maintainable host Robbie Russell interviews Chris Zetter, a London-based engineer and author of "Build a Database Server," about what actually keeps software maintainable over time.
Maintainable host Robbie Russell talks with Nathan Ladd, principal at Brightworks Digital, about what actually keeps software maintainable as teams and codebases grow.
Carola Lilienthal discusses characteristics of well-maintained software, emphasizing clear structure, patterns, automated tests, and simplicity.
Justine Gehring discusses common characteristics of well-maintained software, emphasizing documentation, reusable code, and testability, drawing from her experience in AI research.
April Wenzel discusses the importance of positive emotions and curiosity in well-maintained software, contrasting it with fear and avoidance in legacy code.
Lutz Hühnken discusses characteristics of well-maintained software, emphasizing breaking down complex systems into small, bounded contexts and avoiding magic in code.
Paola Ducolin discusses the characteristics of maintainable software and why teams struggle to achieve it due to business pressures.