Los sistemas heredados son incómodos pero a menudo valiosos, impulsan el negocio. La decisión de refactorizar, reemplazar o retirar debe ser impulsada por costo y valor, no por aversión al código antiguo. "Es viejo y feo" no es una razón; "nos cuesta" es.
Por qué es importante
REFACTOR (improve in place) when:
- Core logic is sound; it's holding business value
- Problems are localized; you can improve incrementally
REPLACE (rewrite/migrate) when:
- It blocks important work and can't be incrementally fixed
- Maintenance cost > rebuild cost over a sensible horizon
- It's a growing security or reliability liability
RETIRE (remove entirely) when:
- Its value no longer justifies any maintenance cost
- Usage has dwindled; a simpler path exists
