• @[email protected]
        link
        fedilink
        101 year ago

        Absolutely not. I left that job not long after. It officially became someone else’s problem.

        I assume they’re not using it anymore. The company was purchased last year so I have to think that they have problems with other code that makes no sense.

        • @AngryCommieKender
          link
          41 year ago

          Legacy spaghetti code gets used for too often in my experience.

          • @[email protected]
            link
            fedilink
            41 year ago

            Agreed.

            Theoretically they could still be using it, but it’s pretty doubtful. It was just a GUI to run a set of scripts for an old set of programs that should have been retired before XP came out.

            I was at an MSP at the time. One of our customers had stuff that wouldn’t install on anything after Win98, was looking for a bunch of hardware that no longer exists, and all the associated DLLs had to be registered manually. I created it because I was tired of doing it all by hand.

            My assumption would be the guys who were there at the same time as me used it (I know they did actually), but a year after I left the whole bullpen turned over and I doubt they used it after that. They lost a pile of clients. Even if that hadn’t happened, if they’re still supporting 25 year old software with 15 year old scripts run by a 12 year old and poorly hacked together front end by a guy who was definitely not a programmer at the time (and barely is now) then they get whatever they deserve.