Maintainable · 2026-03-31 · 55 min
Software doesn’t become hard to maintain only because the code is messy. It often becomes hard to maintain because the reasoning behind it disappears. In this episode of Maintainable , Robby Russell talks with Russ Olsen about trade-offs, legacy systems, and why maintainability depends on context more than dogma. Russ brings decades of experience across very different kinds of systems, each with its own definition of what “maintainable” actually means. A central theme is that software must be understandable to the people maintaining it. Teams tend to document implementation details well, but often fail to capture system-level intent and the trade-offs behind major decisions. Russ makes the case for preserving that thinking, including the alternatives that were rejected, so future maintainers don’t have to rediscover it the hard way. The conversation also touches on Russ’s book Eloquent Ruby, Second Edition . Rather than teaching syntax, the book focuses on how Ruby is actually used in practice and why common patterns exist. That leads into a discussion about where elegance improves maintainability, and where it turns into unnecessary cleverness.
Chris Coyier: The Long Game of Maintaining CodePen75 / 100
Sally Lait: Confidence Is the Real Metric
Rein Henrichs: The Real Work of Maintenance Happens Before You Touch the Code
Joel Oliveira: Predictability Is a Maintainability Feature
Lucas Roesler: The Fast Feedback Loop Advantage