When do you say code is legacy code?

Question

Any useful indicators will be good.

Answer 1

One of the things I'm looking for in code is unit test. This will give freedom to reorganize it. Therefore, if the code does not have tests, I consider it to be obsolete code.

Answer 2

If the code:

• has been replaced by new code that implements the same or functionality or better
• not used by current systems
• will soon be replaced by something else altogether
• was archived for historical reasons.
• when suppliers stop supporting it

Answer 3

"" , , , .

, , .

Answer 4

Micheal Feathers, " ", , .

Answer 5

, , , .

. , "" , .

, , - .

- , , - legacy, , .

Answer 6

, , , , , , , , .

Answer 7

" " , , . , - , .

Answer 8

-, - . , , , , , . , ?

, , , , , . , . , - . , . , , .

Answer 9

" ". , , , , - , , .

. " "

Answer 10

, , , .

, 5-6 (, ). , , .

Answer 11

.:)

...

, ,

MIA

... .

Answer 12

• , , .
• .

Answer 13

- , , , .

, , , "".

Answer 14

, , . , , , , , . , , .

, .

Answer 15

I do not know any real indicators that can be used to determine whether something is "obsolete code" or not, but something older than just written can be considered a legacy. Outdated code means different things to different people / organizations, so it really is somewhat subjective.