11 comments

[ 3.2 ms ] story [ 30.0 ms ] thread
Interestingly that would put some UK banks as running code that was written when the currency was still Pounds, Shillings and Pence.

In the past I've heard that some banks put a decimalisation layer on top of their existing business logic, that would translate between the old Pounds, Shillings and Pence currency, and the new decimal currency. I wonder if there are any banks out there which still have Pounds, Shillings and Pence at the heart of the computer systems.

I have a '60s book on PL/1 which mentions a specific data type for storing the pre-1971 currency. It was a syntactic structure around storing the amount as a quantity of pence.

I'd expect there was still ugliness as the conversion ratio was 2.4 to 1, not making for an elegant quick shift.

For the basic processes, why wouldn’t they? It’s not like adding an amount of money to an account while simultaneously subtracting the same amount from another account has gotten out of vogue or that the algorithms to do so have changed.

FTA: “the reason it lasted is because it was very simple and it worked properly and it was high volume, simple transactions,” he added. “The banks are moving away from these systems because the people who understand them are leaving, and no young professionals want to learn languages like Cobol.””

I guess young professionals do not want to write software that is very simple and works properly (/s, but only partially)

Seems like a band of highly experienced COBOL programmers could organise/unionise and drive up their rates and even demand equity.
> It found that 50% of banks admitted to relying on software that only one or two staff members, who are at or near retirement age, understand.

This is an organizational problem or just plain neglect. I learned cobol back in the seventies in one day. I used it for 40 years and I never had any problems understanding programs written by others.

I wonder if the use of LLMs will extend the lifespan of this software. Instead of hiring a niche programmer, they can now offload the syntax and nuances of COBOL to the AI while being supervised by experienced developers.

Granted, perhaps banking isn’t the ideal place to experiment with this type of technology, but it does seem like a promising use case.

oh no it does not, it runs sixty year old code, beside 50 year old code, alongside 45 year old code,with 40 year old hardware,plugged into 30 year old modem that connects to 17 min old web site
I wonder if any of them have the original source, or could even compile a list of all the "Business Rules" needed to create a new version of their software, with all the need one off. Even then the "It works" mentality might not allow the risk of missing a "One off business rule", if they don't have a copy of there original source anymore... I mean maybe there a still using copies of a compiled program, that they don't know what's fully in it.. </I-Hope_NOt>.. Imagine if the same is true for pharmacy, big chemical manufacturer, then imagine finding a decent cobol programmer now a days to help smooth the conversion.. </TooMuchImaginationHopefully></StuffOfNightmares>
I mean that isn't necessarily a bad thing. I trust battle tested code more than brand new hyped code.
Lot of people are living in buildings more than 100 years old. Why it should be a problem?