How do you convince management to invest time and money into refactoring your legacy monolith? Convincing management of refactoring can be a stopping point for many. It’s your job to provide a cost-benefit analysis of refactoring your legacy monolith and convince your team that this makes sense.
Btw, this is a sequel to my previous post on this topic where I discussed a starting point when facing this topic:
- Code that can be tested (at all!)
- And… have tests
- Business logic separated from your presentational logic
- Stop wasting time building code that is already available in stable/tested 3rd party libraries
Let’s look at overcoming the next hurdle in this process.