Use the Mikado Method When Every Change Breaks Something
Use a Mikado graph to sequence a tangled refactor safely.
Remove a circular dependency where orders imports billing, but direct removal breaks imports and tests. Mikado Method: try the direct goal, roll back on failure, record prerequisites, then implement leaf nodes first. Pushing through a broken refactor creates a half-migrated working tree where every failure has multiple possible causes. Write the goal Top node: orders no longer imports billing. A clear goal keeps discovery focused. Try the direct change Remove the import and run tests; imports fail on InvoiceSummary. The failure is information, not a reason to keep hacking. Rollback and record prerequisite Restore the tree; add node: move summary…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in