Carola Lilienthal: Tackling Technical Debt with Patterns and Domain Knowledge

Episode Summary

In this episode of Maintainable, Robby sits down with Carola Lilienthal, Software Architect and Managing Director at WPS. Together, they explore the intersection of cognitive science and software architecture, strategies for tackling technical debt, and why simplicity, modularity, and domain knowledge are crucial for maintainability.

Carola shares her approach to improving legacy systems, fostering domain-driven development, and introducing sustainable patterns into software design. She also discusses the Modularity Maturity Index (MMI), a tool her team has used to assess and improve over 300 systems.

Topics Covered

• [00:00:43] What makes software maintainable?
• [00:01:24] The importance of clear structure, modularity, and simplicity in software.
• [00:02:38] How patterns help reduce complexity and onboard developers faster.
• [00:04:42] Addressing the challenges of systems with mixed architectural patterns.
• [00:06:20] Strategies for fostering creativity while maintaining simplicity.
• [00:07:05] How to guide teams to balance technical experimentation and maintainability.
• [00:14:03] Practical techniques for documenting architecture and decisions.
• [00:16:17] What is the Modularity Maturity Index (MMI), and how does it measure system health?
• [00:18:02] Common mistakes in managing technical debt and how to avoid them.
• [00:21:20] Why domain knowledge is essential for innovation and problem-solving.
• [00:33:03] Evolving legacy systems with domain-driven design and transformation.

Key Takeaways

• Modularity matters: Simplified, modular systems with high cohesion and loose coupling reduce cognitive load and technical debt.
• Patterns as a shared language: Establishing a pattern language within your team creates consistency and eases onboarding.
• Cognitive science in software: Architecture aligned with how our brains process complexity results in more maintainable systems.
• Domain knowledge drives innovation: Teams should focus their creativity on solving domain-specific problems, not over-complicating the architecture.
• The value of architecture documentation: Keeping clear decision records helps teams navigate legacy code and onboard new developers.

Resources Mentioned

• Carola’s LinkedIn
• WPS Website

Carola’s books:

• Sustainable Software Architecture
• Domain-Driven Transformation (English version coming soon)
• Modularity Maturity Index Overview

Books Carola recommends:

• Reinventing Organizations by Frédéric Laloux
• Team Topologies by Matthew Skelton and Manuel Pais

Be sure to follow Carola on LinkedIn and X.

Thanks to Our Sponsor!

Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tr