If I were a programmer, I’d probably prefer to be maintaining some ancient language that entire city is dependent on me maintaining. Those languages never die.
Coding sucks! Learn Physical Sciences.
I thought I was succeeding in moving away from COBOL programming at my old job. Then Y2K came around, and I was put on that team, and they didn’t know what to do with me after. The group I might have worked with had moved on without me.
COBOL and Fortran live on.
>>> If I were a programmer, I’d probably prefer to be maintaining some ancient language that entire city is dependent on me maintaining. Those languages never die.
I have 14 years in Sys370 mainframe assembler.
That was 20 years ago.... After Y2K, couldn’t find another job.
Been cleaning carpets since.
“”If I were a programmer, I’d probably prefer to be maintaining some ancient language that entire city is dependent on me maintaining. Those languages never die.””
RPGILE has been very good to me.
Dilbert cartoon strip used to have a story line about the “legacy” computer in the basement that no one knew anything about but was critical to everything else they ran. It was hysterical.
There are 80 year old COBOL guys still working, because they’ve pulled them out of retirement.
Still, I don’t think I’d recommend someone spend any time learning COBOL.
I made very good money doing COBOL Y2K code remediation in 1999. Haven’t touched a line of COBOL since.
Nonetheless, just last week I got a call out of the blue from a headhunter who was trying very hard to talk me into coming out of retirement to take a COBOL programming job. It seems that government agencies and financial institutions all over the country are just now realizing they’re dependent on millions of lines of decades-old COBOL code, and there’s a real shortage of people who can write or maintain it.
I’ll admit, for a few minutes, I was tempted.
Visual Fox Pro