Dealing with Medusas in your Codebase.
summary
Claim: the Mikado Method makes large refactors tractable by breaking a goal into a directed dependency graph of small, verifiable experiments. Tools actually used: Visual Studio, XUnit, mind‑map/draw or big paper for the Mikado graph, git with frequent reset hard undoing, and small commits. The demo builds a new console UI/common assembly around an existing encryption library, keeps tests passing with 15–20 minute experiments, and aims to CI/CD unlock large changes.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:40Omnia Retail
- 3:40Warmup
- 4:22New Zealand flag
- 4:59New Zealand
- 5:44Dwarf
- 12:52The Mikado Method
- 16:01Cognitive Limits
- 16:39Medusa Goal
- 17:35Experiment
- 18:54Visualise
- 22:20Advantages
- 23:11Faster progress
- 23:46Getting in the zone
- 24:39Intentional programming
- 25:11Collaborative refactoring
- 25:57Visibility for large changes
- 26:48Refactoring
- 27:20Example
- 28:29Code Example
- 29:18Magic
- 31:36Goal
- 31:50Testdriven development
- 38:24Visual Studio smarter
- 41:16Ship to production
- 48:53Summary
- 50:38Questions
related talks
30mThe Limits of Mikado Method
28mI've Fallen Into a Large Codebase and I Can't Get Up!
46mThe Surprising Effectiveness of Small Steps
47mLiving Domain Model
55mDigging into the Matrix: Practicing Code Archaeology
49mTreat Your Code as a Crime Scene
53mTools and practices to help you deal with legacy code
43mOvercoming Broken Window Syndrome Code Verification Techniques for NET Develop