I recently listened to an IT manager talk about how many Novell Netware servers the organization still used. I could hear the pain in his voice.
I’m planning to write a blog post about the old software that IT folks and developers have to support. I’m thinking it might be entertaining… in a schadenfreude way. And perhaps the “why” answers can give us all insight into what makes organizations hold onto legacy applications, for good or ill.
I’m not looking for answers about custom applications or in-house software. The reasons to hold onto old custom code are relatively well-known, and a different discussion. But software you acquired from a vendor…?
But… what’s the oldest software your shop still uses? Why is it still in place?
Send me a note privately if you like, but I'm not planning to quote anyone by name. It does help to have a context (e.g. "says a sysadmin at a midwest insurance company") but it’s the experience that matters, not the company or source’s name.
--Esther
_______________________________________________ Discuss mailing list Discuss@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
