Chad Fowler 4.35
"Legacy software". These two words evoke many feelings among developers, system administrators, and business people who rely on IT. Most of these feelings are negative. "Legacy" implies toil, trouble, expense, problems, burnout.
Is "legacy" a bad word? What does it mean to leave a legacy? Why don't we hope to do that in software development as we do in other fields? How might we work differently if we did?