What if under the hood of your vintage Datsun 1200, you actually had a Rolls Royce engine that needs sprucing up? Quite often, the purpose of a piece of legacy software within a business has not gone away. Instead, what is needed is an update to its functionality to do more or do it better. Or it could be that the program is not performing at its optimal level because you haven’t maintained and updated
It’s not always about the new ‘technology’ I’ve had quite a few conversations in the last month with companies that are dealing with legacy inhouse software which is critical to keeping things moving on the factory floor. The conversation starts out with a ‘what to do with this piece of outdated programming’. It then evolves into a fresher perspective driven by a needs-must approach. Afterall ‘necessity is the mother of all invention right, particularly during a pandemic?
Years ago, you had a need to automate a business process, make production systems talk to each other, glue disparate systems together, so you bought in a contractor to develop a solution. Does this sound familiar? The software solution is now critical to operations, and the developer can’t be contacted or does not want to be involved anymore. Luckily you were able to salvage the source code, and you hope it was the latest version.