I'm gettin' older, I guess
I retired at the end of 2021 after a 45-year career as an application programmer. I only used two languages during those 45 years: PL/1, and COBOL. I don’t think anyone uses PL/1 anymore (which is a shame, as I understood it more than I understood instructions for making toast), but according to http://zdnet.com, there are still an estimated 800 billion lines of COBOL code being used every minute of every day.
So in reading an article about the SSA dashboard being less user-friendly than it used to be (due to some self-service things being removed), I saw this little gem:
“DOGE also has sought to upgrade and update SSA technology systems, including a coding regimen called "COBOL" that goes back to the 1950s.”
"Coding regimen"? They didn't even have the courtesy or respect to call it a programming language.
Makes me feel real old.
So in reading an article about the SSA dashboard being less user-friendly than it used to be (due to some self-service things being removed), I saw this little gem:
“DOGE also has sought to upgrade and update SSA technology systems, including a coding regimen called "COBOL" that goes back to the 1950s.”
"Coding regimen"? They didn't even have the courtesy or respect to call it a programming language.
Makes me feel real old.
Previous comments... You are currently on page 2.
I am confident NOBODY on the DOGE team that codes called COBOL a "Regimen". Having worked briefly with COBOL and PL/X (a custom variant of PL/1)... I have better names for cobol.
But good luck getting rid of it. (I remember opening a DB table, and seeing a group of 8 fields, repeated like 24 times in a row, numbered, and when I asked WTH? I was told. Oh, that's how COBOL stores an ARRAY of options. I said "Well it's ONE way to do it. And it's clearly wrong"... But the normal way takes too many I/O cycles, LOL).
So, the upside of the COBOL is that it is working.
After that. Ughh.
In my book, you add another language inside the cobol code, a more modern language, like Python.
Make them interoperate. And slowly rewrite the system into Pythonized COBOL. Until you have nothing but Python remaining. Then refactor it to normal.
Otherwise, having worked on huge code bases. Good luck. It aint moving unless you just write a new version and switch.
Meanwhile... CitiBank still using their COBOL screens! While you scan your card and type a pin into a machine.
Like yours, that computer also had 64k of memory (and required a full floor of the building.)
We had to re-code overlays (running out of memory) to add capabilities that the original
designer hadn't considered when he designed it with an old college drinking buddy providing
the design requirements. ;^)
Edit add: Oh wait! I took a 3 month DP course in high school in '69 and was introduced to JPL and COBOL! Had to take a bus to a downtown location to time share on an IBM 360. (I think it was a 360) Forgot about that!
And you're right; without us oldies, the newbies wouldn't exist. As exhibit A, I give you: Pong.