Maintainable · 2026-02-03 · 54 min
Maintaining software over time rarely fails because of one bad decision. It fails because teams stop getting clear signals… and start guessing. In this episode, Robby talks with Lucas Roesler , Managing Partner and CTO at Contiamo . Lucas joins from Berlin to unpack what maintainability looks like in practice when you are dealing with real constraints… limited context, missing documentation, and systems that resist understanding. A big through-line is feedback . Lucas argues that long-lived systems become easier to change when they provide fast, trustworthy signals about what they are doing. That can look like tests that validate assumptions, tooling that makes runtime behavior visible, and a habit of designing for observability instead of treating it as a bolt-on. The conversation also gets concrete. Lucas shares a modernization effort built on a decade-old tangle of database logic… views, triggers, stored procedures, and materializations… created by a single engineer who was no longer around. With little documentation to lean on, the team had to build their own approach to “reading” the system and mapping dependencies before they could safely change anything.
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
Russ Olsen: The Hidden Cost of Forgetting Why the Code Looks Like That
Joel Oliveira: Predictability Is a Maintainability Feature