Return to Question

We've all done it, we've labelled some code (often stuff we've inherited) as "legacy"? But it's still used in the production systems - so is it really legacy? And what makes it legacy? Should we shy away from this unwarranted labelling of perfectly functioning code; where the labelling is a pure convinience which allows us to push through new stuff and keep upper management nice and happy?

###Summary of answers

Looking through the answers I see four general themes. Here is as I see the breakdown:

1. Any code that has been delivered: 6
2. Dead systems: 2.5
3. No unit tests: 2
4. Developers are not around: 1.5

We've all done it, we've labelled some code (often stuff we've inherited) as "legacy"? But it's still used in the production systems - so is it really legacy? And what makes it legacy? Should we shy away from this unwarranted labelling of perfectly functioning code; where the labelling is a pure convinience which allows us to push through new stuff and keep upper management nice and happy?

Summary of answers

Looking through the answers I see four general themes. Here is as I see the breakdown:

1. Any code that has been delivered: 6
2. Dead systems: 2.5
3. No unit tests: 2
4. Developers are not around: 1.5

We've all done it, we've labelled some code (often stuff we've inherited) as "legacy"? But it's still used in the production systems - so is it really legacy? And what makes it legacy? Should we shy away from this unwarranted labelling of perfectly functioning code; where the labelling is a pure convinience which allows us to push through new stuff and keep upper management nice and happy?

EDIT: So looking through the answers I see four general themes, here is as I see the breakdown:

1. Any code that has been delivered: 6
2. Dead systems: 2.5
3. No unit tests: 2
4. Devs not around: 1.5

I think I've distilled the answers correctly(?) (@satanicpuppy's answer is kind of straddling two themes)

EDIT 2: Lot's of interesting discussion here, and it's hard to select a "correct" answer - as I summarised above, there are several different themes. However, I've selected @Aaronaught's answer as I think it covers most of the points I've raised rather than just the title...

We've all done it, we've labelled some code (often stuff we've inherited) as "legacy"? But it's still used in the production systems - so is it really legacy? And what makes it legacy? Should we shy away from this unwarranted labelling of perfectly functioning code; where the labelling is a pure convinience which allows us to push through new stuff and keep upper management nice and happy?

###Summary of answers

Looking through the answers I see four general themes. Here is as I see the breakdown:

1. Any code that has been delivered: 6
2. Dead systems: 2.5
3. No unit tests: 2
4. Developers are not around: 1.5

We've all done it, we've labelled some code (often stuff we've inherited) as "legacy"? But it's still used in the production systems - so is it really legacy? And what makes it legacy? Should we shy away from this unwarranted labelling of perfectly functioning code; where the labelling is a pure convinience which allows us to push through new stuff and keep upper management nice and happy?

EDIT: So looking through the answers I see four general themes, here is as I see the breakdown:

1. Any code that has been delivered: 6
2. Dead systems: 2.5
3. No unit tests: 2
4. Devs not around: 1.5

I think I've distilled the answers correctly(?) (@satanicpuppy's answer is kind of straddling two themes)

We've all done it, we've labelled some code (often stuff we've inherited) as "legacy"? But it's still used in the production systems - so is it really legacy? And what makes it legacy? Should we shy away from this unwarranted labelling of perfectly functioning code; where the labelling is a pure convinience which allows us to push through new stuff and keep upper management nice and happy?

EDIT: So looking through the answers I see four general themes, here is as I see the breakdown:

1. Any code that has been delivered: 6
2. Dead systems: 2.5
3. No unit tests: 2
4. Devs not around: 1.5

I think I've distilled the answers correctly(?) (@satanicpuppy's answer is kind of straddling two themes)

EDIT 2: Lot's of interesting discussion here, and it's hard to select a "correct" answer - as I summarised above, there are several different themes. However, I've selected @Aaronaught's answer as I think it covers most of the points I've raised rather than just the title...