Organization ROI: Reduce story cost in code that has a large number of independent parts.
Engineer ROI: Gain insights about related code chunks that are scattered across the old system.
This change series will guide undoing various architecture choices that turned out to be bad ideas but are universal in the old system. This allows re-using code into a new system with a different architecture.
Habit: Read Fragmented Code
Habit: Undo Layers
Organization ROI: Teams code and ship more independently.
Engineer ROI: Reduce the number of different parts of the system you have to update for each story.
Habit: Stop Inheriting
Organization ROI: Reduce cost for unexpected features.
Engineer ROI: Code is more re-usable and easier to extend in novel ways.
