Inheriting legacy projects: continue to build or BURN IT WITH FIRE
Inheriting a legacy code base can be a smooth hand off, or like kicking a hornet’s nest. What is the best route forward in these situations? Do you continue to development on an aging code base, absent of any requirements, or do you burn it all to the ground to start over fresh free of all technical debt? Which option is best for the health of the project? What are the consequences of the choices? Is it an all or nothing nuclear option?
We’ll share past experiences with both approaches, how to handle some of the pain points that will arise from inheriting a legacy projects, as well as indicators to key off of in order to find the best path forward.