Some "sponsored pieces" are not worth reading but this is not one of them!
I have a reasonable understanding of Cobol but didn't know anything about Clear Street.
I now have huge admiration for what they are achieving, the timeline is going to be long but this is going to be so worth it. Thank you for putting in the time to create this profile. Really appreciated.
Hey, at least the IBM mainframe was/is a fairly simple structure. It's just one big blue box really with terminals. It was in many ways a much simpler era. The present era of information systems is a ghastly swamp of complexity. I refer you to the last chapter of Ledgard et al "Programming Language Landscape."
I subscribe to Not Boring to learn about things I don't really have a background in, so really enjoyed this one that us old(er) finance nerds can appreciate. You know, I remember when...!!!
As someone that has had to work with mainframes and cobol in GS, Chase, etc. I feel the pain. At Chase, they created a school just to take in new grads to teach them Cobol and mainframe jcl, zUniversity I think it was called, to address this. While I agree on the premise of that there has been a lot of knowledge loss, that's endemic of companies shortsighted decisions in many systems. Cobol had been kept modernized thru vendors efforts, like objective cobol, and allowing other languages to interface, like Java. My own first focus when detangling this mess, is documentation and ongoing work but any coders to update and add. But, before you throw it all out, remember that "if it ain't broke" attitude as well as fear of the risk are tough to overcome. E.g. Building the dictionary of the multiple possibilities of intake values of the various proprietary systems for mapping... Ugh!
Some "sponsored pieces" are not worth reading but this is not one of them!
I have a reasonable understanding of Cobol but didn't know anything about Clear Street.
I now have huge admiration for what they are achieving, the timeline is going to be long but this is going to be so worth it. Thank you for putting in the time to create this profile. Really appreciated.
Now when I'm using our enterprise software I feel like I'm going over a 60's era bridge. Thanks, I think?
Hey, at least the IBM mainframe was/is a fairly simple structure. It's just one big blue box really with terminals. It was in many ways a much simpler era. The present era of information systems is a ghastly swamp of complexity. I refer you to the last chapter of Ledgard et al "Programming Language Landscape."
I subscribe to Not Boring to learn about things I don't really have a background in, so really enjoyed this one that us old(er) finance nerds can appreciate. You know, I remember when...!!!
As someone that has had to work with mainframes and cobol in GS, Chase, etc. I feel the pain. At Chase, they created a school just to take in new grads to teach them Cobol and mainframe jcl, zUniversity I think it was called, to address this. While I agree on the premise of that there has been a lot of knowledge loss, that's endemic of companies shortsighted decisions in many systems. Cobol had been kept modernized thru vendors efforts, like objective cobol, and allowing other languages to interface, like Java. My own first focus when detangling this mess, is documentation and ongoing work but any coders to update and add. But, before you throw it all out, remember that "if it ain't broke" attitude as well as fear of the risk are tough to overcome. E.g. Building the dictionary of the multiple possibilities of intake values of the various proprietary systems for mapping... Ugh!