Author left the organization, no document, obselete technology leads to one fact: it’s a nightmare for us to have to deal with this system.

The lowest common denomination of all the factors seem to be: it all depends on whether a piece of code can still be maintained, patched and extend in a confident manner.

Since, most factors are out of our control (you can’t force someone to stick to one job….or can you??), the ‘Tested code’ definition seem to be a reasonable proposition to maintain the integrity of a piece of code.

As long as Darwinism allow it to linger of course (-:

1) In the case where there isn’t much documentation, it becomes legacy when it’s authors leave the project.

2) When you start using different technologies that may not be compatible.

It is impossible to say not to write legacy code, even with a multitude of tests around it. Technology advances at a furious pace, so languages and methodologies fall out of use. One day were going to look back and think “hey, i remember writing OO code”, but everything will be different.

Eventually everything we write – unless we consistently update it – will become legacy.