3 ms·
I used to work for a financial services company. Their main product was a 30 year old cobol program used by many large banks. Some of them would use our softwa
by imron 8y ago
I used to work for a financial services company. Their main product was a 30 year old cobol program used by many large banks.
Some of them would use our software to print various reports and then manually enter those printed values in to excel.
Even worse, the software could export to a format excel could process so it wasn't necessary in the first place.
Don't expect to be disrupting banking anytime soon though. Banks are incredibly risk averse, especially when it comes to messing with expensive legacy software that has been working for decades.
At one point, one of the company's customers did an investigation to see how much it would cost to replace the software, and it was close to 9 figures, and so they decided it was more cost effective just to continue paying the multi-million dollar yearly licenses.
- badpun 8y ago> At one point, one of the company's customers did an investigation to see how much it would cost to replace the software, and it was close to 9 figures, and so they decided it was more cost effective just to continue paying the multi-million dollar yearly licenses. A bank I've worked at had a project to replace lots of bank's legacy (Mainframes and Cobol) with Java on Linux. The project's budget was over 1 billion dollars and it was estimated to take 5 years.
- imron 8y agoThe company I worked for tried to rewrite everything in Java twice. Both attempts cost millions, both were abandoned. The lessons (and pain) from the first attempt were ignored because not enough of the upper management were still around, and the only people who remembered the pain were the rank and file, who were ignored by the new upper management types looking to leave their mark on the product.