Richard Gross Head of Software Archeology, MaibornWolff
summary
Compares renovating a house with modernizing a legacy app and shows concrete outcomes: codebase maps produced with CodeCharta reveal a lower-tier code area owned by a departed author, two branches a year apart block releases, and an Ionic 3→5 migration causes 30-minute outages; tooling stack includes Quality Views, ArcUnit, dependency‑cruiser, SonarQube, ESLint and Renovate Bot; team adopts trunk‑based development plus branch‑by‑abstraction and 10–20 feature toggles, achieves regular secure releases within a year and sharply reduces security findings while changing team habits via the four laws of behavior change.
AI-written summary · about
chapters (8)
- 0:00Introduction to renovation analogy
- 1:29Assessing inherited codebases
- 5:01Modernizing legacy systems
- 8:34Planning and prioritizing work
- 11:47Adapting plans to feedback
- 16:04Learning and collaboration
- 19:34Sustaining improvements long-term
- 22:04Outcomes and key takeaways
related talks
51mSoftware Archeology and The Code Of Doom
43mCode quality as an engine of your IT business
31mStrengthen Our Developer eXperience to Face Obsolescence and View...
26mLegacy Codebases are a DevOps Issue
18mAgile leadership and technical mastery, a harmonious alliance
47mTales from the Dev Side: What Went Wrong, What We Fixe & What You Can Steal
42marchitect's Guide to Managing a Code Base
48mLegacy, for lack of a better word, is good