When a codebase is large and complex, it's risky to big changes. Here's a structured way to approach

Hacker News is a community-driven platform for sharing and discussing technology news, startups, and programming-related topics. Through user submissions and comments, Hacker News offers insights into emerging technology trends, industry developments, and entrepreneurial ventures. Readers can participate in discussions, share their insights, and stay informed about the latest advancements in technology and innovation.

Hacker News

The Mikado Method is a structured technique for making safe, incremental changes in large, complex codebases. Instead of diving into a big change and getting stuck when problems cascade, you set a goal, attempt it within a short timebox (e.g., 10 minutes), and if you fail, revert all changes, identify what prerequisite work is needed, write it as a subgoal, and repeat. This builds a dependency graph of small tasks. You tackle leaf tasks first—those with no blockers—commit each success, and progressively work toward the main goal. Key practices include keeping timeboxes short to avoid sunk-cost fallacy, always reverting on failure, and committing each completed subgoal so the codebase stays shippable throughout. The method is named after the pick-up sticks game, where you remove the easiest sticks first to untangle the one you actually want.

Use the Mikado Method to do safe changes in a complex codebase

A structured way to make valuable changes