Definitely got something here - legacy code becomes that way by mostly working, not by being constantly changed or rewritten. Though constant changes may also b

Definitely got something here - legacy code becomes that way by mostly working, not by being constantly changed or rewritten. Though constant changes may also be applied to legacy code. >> One common developer bias is that old code is bad. You've never heard anyone say the phrase "legacy code" without contempt in their tone >> As for the 'code age' point, I'd think it is more related to recency of the requirements, when was that problem domain last worked on and understood. So maybe the issue points to clarity of requirements capture, and perhaps the coding/design corresponding to the requirements. Another commenter referred to automated testing, which hits on having test cases to match the requirements. With that level of functional documentation, the code is likely to be easier to understand.