Tech News
← Back to articles

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

read original related products more articles

Struggling with Legacy Code and not enough time to clean it up?

can help you rescue any codebase quickly and safely !

You’ve inherited a 300k lines of spaghetti code. What do you do now?

Large, untested, poorly documented codebases are tricky to work with. They’re very hard to reason about.

You can’t move fast in a complex codebase.

Stuck in the quicksand of Legacy Code

The thing is, they called you to change that codebase! You need to meet new functional requirements. Or fix some bugs.

Maybe you decided that you’ll address the technical debt and refactor that legacy code. Maybe you want to improve the architecture of this system while it’s serving customers in prod.

But any valuable change takes you down to a path of failures 😩

Say you want to upgrade your ORM dependency. You start doing so, but you quickly realize that there are some breaking changes. So you need to change some function calls across the codebase. To make it easier, you decide to refactor and extract them somewhere, so you only have one place to change. But to do so, you need to adapt each call first…

... continue reading