DEV Community

Discussion on: How do you deal with legacy projects?

Collapse
 
aminmansuri profile image
hidden_dude

You say "legacy" as if it was a bad thing. It CAN be a bad thing.

But it can also mean that the project has been a success for years or decades even.

If you're working on the Windows OS, or Office, or Linux, or GMail those are all "legacy" codebases. They're also some of the most successful software projects of history.

I've dealt with new projects and "legacy" projects. I tend to look at them much the same way. Often I'm more concerned with ADDING VALUE TO THE BUSINESS than worrying if they are "still" using this or that.

A "legacy" system is often a PROVEN system. And many times has a lot of value, an rewriting it is going to be extremely costly or impossible.

Old projects can involve innovation as well.

I'm surprised by how many people commenting here mention rewriting or replacing. Maybe they are confusing "legacy" with "failed".

But in general you want to find a way to ADD VALUE to END USERS and avoid rewriting code that has worked for years or decades.