5 ms·

Your big problem with COBOL will be staffing - everyone knows that scarcity plus demand means that COBOL programmers routinely command 7-figure salaries, and ev

Your big problem with COBOL will be staffing - everyone knows that scarcity plus demand means that COBOL programmers routinely command 7-figure salaries, and even if your funders can pony up the required cash, getting those guys away from their private islands that they purchased with their Y2K booty is going to be tough.

wheels 6y ago
I placed second in a statewide (Texas) COBOL programming contest in high school. This was the late 90s. While in college (which I started early), I kept having people track me down to offer mid-six-figure salaries. It was very tempting. It was pretty surreal (again, this was pre-web boom, and starting tech salaries were mid-5-figures) as an 18 year old having people offer me $400k/year.
- gghggfd 6y ago
  I call bullshit.
  - deleted 6y ago
    [deleted]
  - mullen 6y ago
    Being offered $400K a year is a whole lot different than actually getting $400K a year.
  - wheels 6y ago
    Just saw this now. Not sure you caught the context, which was implied by the poster above. This was 1998, when loads of major corporations were terrified of "the Y2k bug" which was talked about in very apocalyptic terms. There was a scramble to find COBOL programmers, because it was feared that the majority of the bugs were in long-running COBOL systems, but most competent COBOL developers at that point had retired. It's true that I didn't follow up with those folks (other than to say, "no thanks"), but being contacted by multiple recruiters promising six-figure salaries was very much a thing.
somedude895 6y ago
That was always my impression. But some thread on HN from yesterday a lot of people were saying COBOL salaries were very low, so which is it?
- Intermernet 6y ago
  I know a guy who used to write COBOL at IBM. He was apparently quite good. He now drives trucks for a landscape supply company. I told him that he should look into COBOL jobs again so he did some research. It seems that the actual number of available jobs is a lot lower than the hype would suggest.
  - wiz21c 6y ago
    my understanding is that companies with COBOL are big instituions with people not much interested in "career" but in "stability". So those old programmers stay there until they retire (nothing wrong with that). So they keep up the COBOL system. Once they get older management thinks about replacing the COBOL system with something new. If it's really expensive, a new system is built around the COBOL system with new technologies : report by report, DB by DB, etc. until then old system can be unplugged. It takes 10 to 20 years to do so. Nothing unbearable for a big corp.
- johannes1234321 6y ago
  What is high paid is not the ability to write COBOL, what is being highly paid is understanding the 40 year old application building the foundation of the insurance or bank. If you understand all the implications of code changes there, you are worth a lot. If you need oversight to not break anything (hardly any tests etc.) you a worth a lot less.
  - jmt_ 6y ago
    Spot on. I see people talking about learning COBOL or not, but as you say that's not so much the point. You really need to know how ancient mainframes work. A programmer can pick up the basics of COBOL soon enough, but understanding the ins and outs of zOS and the likes? Much harder, especially the more recent your tech knowledge is. Approaches to software and systems design has changed dramatically since the IBM mainframe days. If you want to make money working on old software just learn Java EE or .NET Framework or something!

wheels 6y ago

I placed second in a statewide (Texas) COBOL programming contest in high school. This was the late 90s. While in college (which I started early), I kept having people track me down to offer mid-six-figure salaries. It was very tempting. It was pretty surreal (again, this was pre-web boom, and starting tech salaries were mid-5-figures) as an 18 year old having people offer me $400k/year.

gghggfd 6y ago
I call bullshit.
- deleted 6y ago
  [deleted]
- mullen 6y ago
  Being offered $400K a year is a whole lot different than actually getting $400K a year.
- wheels 6y ago
  Just saw this now. Not sure you caught the context, which was implied by the poster above. This was 1998, when loads of major corporations were terrified of "the Y2k bug" which was talked about in very apocalyptic terms. There was a scramble to find COBOL programmers, because it was feared that the majority of the bugs were in long-running COBOL systems, but most competent COBOL developers at that point had retired. It's true that I didn't follow up with those folks (other than to say, "no thanks"), but being contacted by multiple recruiters promising six-figure salaries was very much a thing.

somedude895 6y ago

That was always my impression. But some thread on HN from yesterday a lot of people were saying COBOL salaries were very low, so which is it?

Intermernet 6y ago
I know a guy who used to write COBOL at IBM. He was apparently quite good. He now drives trucks for a landscape supply company. I told him that he should look into COBOL jobs again so he did some research. It seems that the actual number of available jobs is a lot lower than the hype would suggest.
- wiz21c 6y ago
  my understanding is that companies with COBOL are big instituions with people not much interested in "career" but in "stability". So those old programmers stay there until they retire (nothing wrong with that). So they keep up the COBOL system. Once they get older management thinks about replacing the COBOL system with something new. If it's really expensive, a new system is built around the COBOL system with new technologies : report by report, DB by DB, etc. until then old system can be unplugged. It takes 10 to 20 years to do so. Nothing unbearable for a big corp.
johannes1234321 6y ago
What is high paid is not the ability to write COBOL, what is being highly paid is understanding the 40 year old application building the foundation of the insurance or bank. If you understand all the implications of code changes there, you are worth a lot. If you need oversight to not break anything (hardly any tests etc.) you a worth a lot less.
- jmt_ 6y ago
  Spot on. I see people talking about learning COBOL or not, but as you say that's not so much the point. You really need to know how ancient mainframes work. A programmer can pick up the basics of COBOL soon enough, but understanding the ins and outs of zOS and the likes? Much harder, especially the more recent your tech knowledge is. Approaches to software and systems design has changed dramatically since the IBM mainframe days. If you want to make money working on old software just learn Java EE or .NET Framework or something!