What’s the difference between legacy code and technical debt? Serious question. If you have one you always have the other?
16% Yeah they’re the same.
62% No (explain in replies)
5% WTF (complain in replies)
17% 🐧
173 votes • Final results
38
1
1
11
Or current code - i.e., the kind you write to meet the sprint deadline that just barely works, but Monday we're onto a different feature
2
3
How true! So it kind of means that legacy is actually up to last hour of committed code... Maybe it's our perception of time that's the problem.
2
1
3
Haha. It is definitely tricky to define "legacy" & I think it's often in the eye of the beholder. I don't think the age of the codebase is always a factor - really simple/stable code can live decades. I'd say maybe "code that we'd prefer to rewrite/refactor if we had the time"
1
3
Replying to @TroyWarr @mediajunkie @noahsussman
Would that everyone thought more carefully (or knew how to) about our code, potential longevity, of course the commenting and cleanup of hacks and old bugs as you mentioned and knew what risks legacy issues can cause! It's at subject for at least a book, a talk, and courseware!

Mar 17, 2022 · 9:49 PM UTC

1
2
Replying to @mholzschlag @mediajunkie @noahsussman
For sure! Not the sexiest subject, but I've worked at a couple of early-stage startups that would arguably still be here if only for better code maintenance habits. A team can get crushed under the weight of technical debt. Maybe I'll write the book, you write the foreword? 😉
1
2
Deal! 🤣
2