7. • Estimates always wrong.
• New bugs.
• Secret knowledge in the code.
• Lengthy code freeze.
• Organisation needs to wait for new features.
Risks of Re-building
Friday, 26 April 13
8. But Renovating?
• The code is a mess.
• You don't know where to start.
• It has become poorly designed.
• It is typically untested.
Friday, 26 April 13
9. Botch it then?
• Just hack the change in.
• Code will be worse.
• Which leads to worse code.
Friday, 26 April 13
10. Right let's do it!
• Scratch refactor
• Tell the story of the system
• Sketches
• Characterization tests
• Golden Master technique
Friday, 26 April 13