In the loosest sense this is old, bad code that no one wants to touch out of fear of breaking it. I guess "bad" might be a harsh description. It works right? I guess it's bad in that you can't change it. Two more finite descriptions that could tell you when an app goes from healthy to legacy that I've heard are:
- This guy suggested that Michael C. Feathers' book "Working Effectively with Legacy Code" has the standard! Any code not under test is legacy code.
- This guy suggested that code becomes legacy code when it is easier to just build what you need around an application in lieu of trying to change the application.
No comments:
Post a Comment