This change series will ensure that the new system gets the behavior of the complex method in a tidy readable way.

Habit: Names Expose Duplication

Organization ROI: Find opportunities to reduce duplication without introducing coupling bugs.

Engineer ROI: Honest names distinguish intentional from accidental near-duplication.

Habit: Make Methods Simple

Organization ROI: Reuse code more.

Engineer ROI: Separate parts of a method, unwinding their dependencies and testing each part separately.

Habit: Names Guide Design

Organization ROI: Prevent bugs that arise from differences between CS concepts and domain concepts.

Engineer ROI: Use your honest names to guide design for your system.

Habit: Power Combos

Organization ROI: Reduce risk in changing designs.

Engineer ROI: Complete extensive design changes as a series of small steps.