| ▲ | iefbr14 9 hours ago |
| > 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. |
|
| ▲ | CoastalCoder 8 hours ago | parent | next [-] |
| Maybe "COBOL" here is a misleading shorthand for mainframe banking programming? |
| |
| ▲ | WJW 6 hours ago | parent [-] | | The original quote doesn't say anything about COBOL, or about mainframes for that matter. It speaks about "systems only one or two people understand", which seems normal enough. You can write incomprehensible software in any language if the specs are convoluted enough, and a bank that has existed for over half a century will almost inevitably be a mishmash of poorly integrated systems written over multiple decades. Sometimes at different banks which were subsequently merged with, sometimes by a consultancy which has long since gone bankrupt, sometimes with a compiler that is no longer available. It's a miracle the system works at all. |
|
|
| ▲ | netdevphoenix 4 hours ago | parent | prev [-] |
| > I used it for 40 years and I never had any problems understanding programs written by others That's quite exceptional. Have you never worked on legacy code or with below average devs? |
| |
| ▲ | iefbr14 2 hours ago | parent [-] | | I've been a consultant for a long time and in that role you were hired only to fix old systems that the resident staff refused to maintain, because not sexy. I didn't mind, it paid good money and I have seen a lot of companies from the inside which is also a plus. The dev were not below average, they just weren't interested. |
|