@ben_a_adams and I had a discussion about a better name for "old code" that is still useful, I believe "Heritage" was the term we came to rather than legacy
-
-
-
Vintage
- 2 more replies
New conversation -
-
-
Btw, did you notice that “legacy” have a negative connotation only in software engineering? In all other fields “legacy” - is something good. Probably that’s bc most people inherit a house or money instead of debts and problems.
-
Code is liability. Functionality can be an asset.
- 2 more replies
New conversation -
-
-
I like
@david_whitney’s phrasing, not legacy code but legendary code - stuff that delivered the enterprise you now work for.https://youtu.be/Z2CZn966cUgThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It depends on the def. of the term "legacy code". I like the definition given by
@mfeathers in his book "Working Effectively with Legacy Code", which is: "Legacy code is code without tests". Very pragmatic, very useful, and giving hope: Maybe we can prevent it? I believe so. -
I like the definition "legacy code is code we are afraid to change". But more fluffy though

- 3 more replies
New conversation -
-
-
Is this today's gif shitposting thread?pic.twitter.com/sAMEgqXvay
- 1 more reply
New conversation -
-
How about the vestigial code that does nothing and simply wastes space but has been around so long nobody dares touch it just in case some other code that actually is “successful” mistakenly depends on it?
-
I think most of us mean vestigial when we say legacy. Legacy made it through spikes, hackathons, refactorings, acquisitions. It's as good as it serves a purpose.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.