Trick question, a televised urgent plea for COBOL developers could be any year between 1959 and 9999https://twitter.com/zarawesome/status/1246518788759134210 …
-
Show this thread
-
There's a joke whose punchline is "Well we're coming up to the Y10K problem and it said on your cryogenic unit that you know COBOL", I'll let you reverse-engineer how it goes
1 reply 7 retweets 42 likesShow this thread -
quarantine 'em Retweeted quarantine 'em
quarantine 'em added,
1 reply 2 retweets 21 likesShow this thread -
That troubling possibility that leaving your system to run unattended for years at a time, and placing an urgent public call for COBOL developers only when it breaks, may be more cost-effective than keeping a COBOL developer on staff or migrating to something modern
4 replies 6 retweets 29 likesShow this thread -
Six weeks later the emergency COBOL developer has saved your bacon and gone back into retirement. Thus solving the problem once and for all
1 reply 1 retweet 21 likesShow this thread -
To be clear, I don't want to disparage COBOL. I know barely anything about it as a language. It being old is not a problem. The problem is the diminishing number of available programmers
2 replies 0 retweets 11 likesShow this thread -
Replying to @qntm
I had this conversation with a friend yesterday. I really don't think we'd be in better shape if they had paid someone to rewrite it all in node.js at some point, they'd just have an easier time finding developers to fix it when it broke because it wasn't designed for this.
2 replies 0 retweets 0 likes
That's the crux of the matter. They have a critical system, but they didn't keep anybody around who could take care of it. Doesn't matter what the system is written in
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.