3 ms·
In 'Working with Legacy Code', Michael Feathers defines legacy code as code without sufficient tests. The great thing about this definition is that it doesn't
by willthames 13y ago
In 'Working with Legacy Code', Michael Feathers defines legacy code as code without sufficient tests.
The great thing about this definition is that it doesn't matter how old the code is - if it can be changed without worry about introducing unwanted behaviour because of test coverage, then it's not legacy.
It also means that you can write new legacy code right now!
- MartinCron 13y agoIt also means that you can write new legacy code right now! I once made the argument that a team within my organization was actively producing new legacy code. It wasn't my most diplomatic moment.