COBOL joke from 1999:
A COBOL programmer, tired of all the extra work and chaos caused by the impending Y2K bug, decides to have himself cryogenically frozen for a year so he can skip all of it.
He gets himself frozen, and eventually is woken up when several scientists open his cryo-pod.
"Did I sleep through Y2K? Is it the year 2000?", he asks.
The scientists nervously look at each other. Finally, one of them says "Actually, it's the year 9999. We hear you know COBOL."
Y10K will be a serious issue when it eventually comes around.
year 9999. We hear you know COBOL.
slams cryo-pod door shut
I had a job that used COBOL and programmed in it. Its not terrible. It even works with sql.
The issue is the decades of code with little to o documentation, the fixes for issues like y2k that wirked at the time but now have problems, and greedy companies that want you to pay per processor. All the while you yourself are one of three people in the city that are looking to slowly pull everything out of COBOL, making it just a bit harder to get a job next time.
I've been programming in various languages for about 15 years. I'm stuck working on software automation.
how do I transition to COBOL development?
programming languages pre 2000: have heart and soul
programming languages post 2000: ai and javascript slop that take 80 chromium processes to run and 64gb of memory.
Duplicate post pls ddelete
For real, I should just teach myself cobol and have a guaranteed sequence of jobs for life
If you ever plan to kidnap a COBOL developer, make sure to offer their employer a "double-rate same day delivery option" in the ransom.
I feel like I have seen multiple such fight memes from this restaurant. What is going on there? Are they ok?
Our COBOL based system has MAXDATE = 31 Dec 9999
I tried to set a reference year to 9999 to temporarily disable a thing, but a mid-range system couldn't handle it, we had to use 2099
Now I'm almost considering learning the language
all 20 comments