Live data from Hacker News

New Jersey needs COBOL programmers for their unemployment claims system

twitter.com

81–90 of 309 posts

Re: New Jersey needs COBOL programmers for their unemployment claims system

#81
post #65

Earlier quoted context omitted.

Do they mean that SDLC? Or do they mean "synchronous data link control"?

Nope - http://www.ambysoft.com/essays/agileLifecycle.html Though I would of prefered your flavour as way more fun and less admin work overheads.

And the very fact that you refer to "admin work overheads" in something claiming to be "agile" indicates that it's Agile(TM), not actual agile. (Though I got that idea very quickly from your link, as well...)

Re: New Jersey needs COBOL programmers for their unemployment claims system

#83
post #4

How hard is cobol to pick up and learn at the level needed to contribute? I'm sure there are many no longer employed programmers in the tri state area that might be able to help

Here's a taste: https://qntm.org/zomg >System z is a living fossil; it is computing archaeology; computing palaeontology. System z is an example of the principle "If it ain't broke, don't fix it" carried to its logical extreme. System z and its predecessors haven't broken for forty-five years: the "z" stands for "zero downtime" and some of these machines have been running continuously for decades without a reboot. No…

"AS YOU KNOW, "Return" and "Enter" are separate keys on your keyboard"

Just FYI, my laptop has "Enter" clearly printed on both keys.

Re: New Jersey needs COBOL programmers for their unemployment claims system

#84

I was sort of tempted to pursue this. I did a few years in the salty COBOL mines back when I was a PFY about 20...plus years ago. This niche probably hasn't moved very much since then and I could probably recall most of it after a few hours. I'm freelancing right now anyway and some other projects just vaporized. But. A quick skim of the postings is finding that what they're really screaming for is somebody who's bee…

Don’t be surprised if this position then goes to an H1B contractor though. If enough anericans who have this knowledge do not apply because they - Hate the tech - Can’t provide their feedback to improve the system - Don’t like the salary offered even if’s greater than their current unemployment income, then is it for an offshore company to come in and fill that gap.

Re: New Jersey needs COBOL programmers for their unemployment claims system

#85
post #15

The point at which the government should have rewritten their COBOL systems into a language that would have a talent pool to draw from was at least 30 years ago.

In SF permitting/entitlement system is being rewritten for already 5 (8?) years. Funding is only ~1M, while this is an easy task such small budget for for 5 years of work does not worth it even if you can build this by a single developer.

And this is a department that have billions.

Re: New Jersey needs COBOL programmers for their unemployment claims system

#86

Techies: What can we do to help? 3D print ventilators? Process terabytes of data in seconds? AI?! Govt: We need COBOL programmers. Techies: I am powerless to help. But seriously some of the brightest techies I know quit their jobs to do a stint of government work which included slinging VBA and ASP Classic to remove SQL injections from VA websites and other similarly unglamorous tasks with huge impact. If you want to…

I could help rewrite in some other language.

Re: New Jersey needs COBOL programmers for their unemployment claims system

#88
post #74

Earlier quoted context omitted.

> Instead of hiring three mediocre or less than mediocre engineers at $60k, why not hire an amazing $150k - $180k engineer? In many cases, it's literally not legal for them to do so. For example, at the Federal level: https://en.wikipedia.org/wiki/General_Schedule_(US_civil_ser... (These restrictions don't tend to apply to hiring one via a contractor at $250-500k/year, though. Sigh.)

> These restrictions don't tend to apply to hiring one via a contractor at $250-500k/year, though. They very well may have to go that route, i.e. some greybeard independent contractor that can name their price. It's a very limited skillset and God knows this ain't the kind of work that gets the super talented motivated.

Dad started out as a COBOL programmer before he got distracted by management and decided being a PM was a better path. This was his explainer to me once:

To hire someone who can do the job reasonably quick and well is really expensive no matter how you slice it. Consider it a 'job well done' if you can persuade them to:

a) Un-retire

and

b) Come out of said retirement to do actual work in the trenches again - as opposed to management.

In the private sector, these people have probably made the equivalent of GS-15 Step 10 for years if not decades. Good luck trying to convince them to jump back in for what is essentially a pay cut.

Re: New Jersey needs COBOL programmers for their unemployment claims system

#89

Techies: What can we do to help? 3D print ventilators? Process terabytes of data in seconds? AI?! Govt: We need COBOL programmers. Techies: I am powerless to help. But seriously some of the brightest techies I know quit their jobs to do a stint of government work which included slinging VBA and ASP Classic to remove SQL injections from VA websites and other similarly unglamorous tasks with huge impact. If you want to…

Imagine making even a minor change to the COBOL code. It's not likely to be very well structured or comprehensible. I'm guessing there would be a lot of global variables and strange database / file system interfaces. Very hard to do it without breaking something somewhere.

Edit: per the thread starting with vaidhy's comment.

Re: New Jersey needs COBOL programmers for their unemployment claims system

#90
post #65

Earlier quoted context omitted.

Nope - http://www.ambysoft.com/essays/agileLifecycle.html Though I would of prefered your flavour as way more fun and less admin work overheads.

And the very fact that you refer to "admin work overheads" in something claiming to be "agile" indicates that it's Agile(TM), not actual agile. (Though I got that idea very quickly from your link, as well...)

Yes, naming of projects was one of the most fun aspects in projects. Seen that play out in many ways, often case of thinking of what you wanted and working out some acronym or reason to go with that. One team the project manger was a fan of the TV show BILKO, so the new invoiceing system became called that once a passable acronym was worked out. Was something like Billing and Invoicing ...was so long ago but was clever and worked. Then their was the buzzword period and marketing departments, so would get whole rafts of things with Rapid as a prefix and the irony played out.

Still, maintenance is the biggest cost of any code that has lived so long, so with that such systems overall may well be agile, you just smooth out the pain over time in a more manageable way.

Post reply on HN