Refactoring with Observability
summary
Two practices emerge from dojo experimentation: architecture mapping uses the C4 model on Miro/Lucid, mob-style drawing and story-map “red string” journeys to plan a large architectural refactor and align mental models; refactoring with telemetry uses static-analysis tools like NDepend (or JArchitect), cyclomatic complexity and maintainability indexes plus automated refactors and unit tests to pick targets and iterate. One team breaks an 8,000-line class into 100+ classes in two weeks; another built ~10,000 unit tests and drops bugs to about one per quarter.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 1:02Challenging best practices
- 3:07Context and complexity
- 7:00Architecture mapping practice
- 17:58Refactoring with telemetry
- 27:50Emergent practices and principles
- 30:19Q&A
related talks
40mTesting Software Architecture
40mArchitecture Modernization: Aligning Software, Strategy, and Structure
57mUnlocking The Awesome Power of Refactoring
41mInside Software Architecture - Where the Bodies are Buried
47mArchitecture as Code or How to Survive Legacy and Keep Your Sanity
45mConquering complexity: refactoring JavaScript projects
01h 00mVisualise, document and explore your software architecture
01h 04mRefactoring Is Not Just Clickbait