If your code has lasted long enough to be considered “old”, but is still so useful that it can’t just be deleted without a dedicated replacement effort… it’s doing something right.

[–] spongebue@lemmy.world 7 points 4 months ago

I work with a different kind of legacy system. It was retrofitted to work with SOAP, OOP, and some other modern stuff, but none of the old farts bothered to learn it. When I inherited a SOAP service that system used, I had to learn a lot about it to get what I needed.

And honestly? It's been a lot of fun. It's a unique kind of challenge, I've practically gained celebrity status at work, and even if it's nothing I'll be doing long-term it shows how I can pick up weird systems and work with others to make some miracles happen.

[–] regdog@lemmy.world 6 points 4 months ago (2 children)

Instead of "legacy code" they should call it "veteran code", because it has seen some shit.

[–] silasmariner@programming.dev 5 points 4 months ago

Brb updating my personal lexicon

[–] AnarchistArtificer@slrpnk.net 2 points 4 months ago

That is a much better name for it, especially because some of the ways in which veteran code gets creaky does feel analogous to age