I took COBOL, Fortran, Assembler, and RPG II when I was in college working on my data processing degree. The first job I got in IT was to batch process COBOL-based databases and recompile them into a newer format. The program was already pre-written and debugged, all I had to do was use command lines at the prompt to execute whatever batches I wanted, then format and print them into a corresponding spreadsheet. I veered off into the desktop and network realm, but my brother-in-law had just finished his degree and got a job in ‘98 or’99 to pull old databases and programs, and update it into a newer programming language that wouldn’t cripple the old COBOL-based stuff in the process. (Y2K pearl-clutching and all that - I worked a contract for that, too.) I remember employers offering fat bucks to old retirees who were utilizing COBOL-driven mainframes back in the ‘60’s, then cashed out in the 80’s and 90’s, took their pensions and their Social Security, and were out on Caribbean cruises half the year. Some places were paying programmers by the line, not as salary. If you were fast, they’d load you up with as much work as you could handle, and my brother-in-law-had fingers that were greased lightning. For almost two years, he was pulling down a hard six figures because of that and his ability to focus. Afterwards, he said he was glad it was over. The money was stoopid good, but the job was so high-intensity and production driven, he was just frazzled to the core. By The Lords of COBOL, I can’t believe that language is still around. I don’t remember a single switch or command, but I can still see the textual formatting in my mind. *Brrrr*
“By The Lords of COBOL, I canâÂÂt believe that language is still around. I donâÂÂt remember a single switch or command, but I can still see the textual formatting in my mind. *Brrrr* “
LOL!
The “lords of COBOL” live forever.