Old code should be laid to rest, not refactored to death

(Lightning talk, 10 min)

Author(s): Ole-Marius Moe-Helgesen (Itverket)
Session: Refactoring
Session chair: Johannes Brodwall (Steria)
Date: Thursday, 3 June 2010: Main Conference
Time: 10:30-12:00
In our world of agile development, continuous improvement and refactoring we've been taught how to deal with legacy code: Refactor to support testing, write a test suite and THEN start to change it. The other option is what we did before: throw away the old and start again. The problem is that we can't release it until we've completed all the features of the old system. There is a third option though, and that is to combine agile practices with a strategy of replacing all the old code. I'll share some experiences doing both and explain why I think we should let old code die a peaceful death.

<< Back to the program