Contemporary COBOL: Developers' Perspectives on Defects and Defect Location

https://arxiv.org/abs/2105.01830

by Fragoel2 • 5 years ago

50 12 5 years ago

arxiv.org

xiaodai• 5 years ago

"Contemporary COBOL". At least they didn't say modern COBOL, or it will be an oxymoron.

skissane• 5 years ago

At least they didn't say modern COBOL, or it will be an oxymoron.

Is COBOL 2014 "modern COBOL"? https://www.iso.org/standard/51416.html

Or what about the in-progress COBOL 202X standard? https://isotc.iso.org/livelink/livelink?func=ll&objId=194689...

pjmlp• 5 years ago

Here is modern COBOL, https://www.microfocus.com/en-us/products/visual-cobol/overv...

p_l• 5 years ago

Having experienced, if peripherally, MicroFocus, I'd rather go with IBM COBOL on z/OS...

leoc• 5 years ago

Obligatory mention of J. Wayne Spence's COBOL for the 80's https://www.worldcat.org/title/cobol-for-the-80s/oclc/116217... (images of different covers: https://www.ebay.com/itm/223985240042 and https://www.ebay.com/itm/352577866145 ). That title hit its peak humour value about the mid-'90s (when I first heard of it) and has been becoming steadily more horrifying ever since.

NikolaNovak• 5 years ago

Note that COBOL does exist outside of mainframe systems. Peoplesoft is a fairly popular HR Payroll package and works on what they call distributed systems as well (windows Linux Unix rtc). I've worked on various peoplesoft systems over the years and they include a mixture of "modern" but proprietary languages (peoplecode, application engine) as well as legacy (Cobol, sqr). Currently on a project that implements them on Unix,serving 350k self service employees. Data issues are indeed our number one type of defect. I wonder how much that is language vs environment that language is typically deployed - I.e. Our own reasons for data being our number one issue seem external, but maybe there's data handling capabilities, or lack thereof, that we are blind to.

marktangotango• 5 years ago

Mainframe systems are facing a critical shortage of developer workforce as the current generation of COBOL developers retires. Furthermore, due to the limited availability of public COBOL resources, entry-level developers, who assume the mantle of legacy COBOL systems maintainers, face significant difficulties during routine maintenance tasks, such as code comprehension and defect location.

Old stuff is hard to maintain? Who would have thought!

This myth of a Cobol developer shortage really has a lot of legs. I personally know of hundreds of former Cobol developers who moved on after their jobs were offshored over the past 12 years. If Cobol paid current salaries, a lot of former Cobol developers would be back. But companies don't pay, and developers stay away.

AlbertCory• 5 years ago

I can't say about the ones you know, but I can guess that many Cobol programmers have simply forgotten most of what they knew, and would struggle to even write a Hello World on current hardware & software.

And also, they're tired of that shit.

danpalmer• 5 years ago

Doesn't look like it's mentioned here, but expense of the COBOL toolchain has got to be an issue for its uptake.

Paid toolchains have essentially failed in software engineering. There are some hybrid business models in game engine toolchains, but moving towards more free/open/flexible systems has resulted in huge growth. You can pay for support from certain companies, but that's not quite the same.

If you want to run COBOL, you typically need to buy a compiler, buy specialist hardware, and buy an IDE. There are open COBOL compilers but COBOL compilers have compatibility issues worse than browsers so particular compilers do matter.

The most modern and accessible COBOL development that I'm aware of is JVM/CLR COBOL developed in Visual Studio/Eclipse. You can even run it on Android! But you have to buy the whole toolchain, and it's very much "call us for pricing", not low prices and putting in a card number.

This ultimately prevents new people from joining the community as open/free compilers and toolchains are essentially table stakes at this point, and that means the community is only going to shrink.

maxharris• 5 years ago

If you're still working at a place that still maintains COBOL code, you should quit and come back as a much better paid contractor. Don't waste your retirement doing that for less than a few hundred bucks an hour.

And if you're a young person, don't waste your youth on the dead-ends of the past. You can make a million bucks in a year if you're really good at all that AI stuff!

vajrabum• 5 years ago

I just peeked at Linked-in and searched on COBOL. They have a thousand or so COBOL listings. The contract ones seem to run about $60/hr and the salaried at $60k-$80k. Not terrible for some locations but also not what I'd call a gold rush either.

France_is_bacon• 5 years ago

COBOL is an extremely easy language to learn.

Companies needing COBOL programmers find it easier to train up someone in COBOL, rather than finding a pre-existing COBOL programmer.

I learned COBOL in a month.

The only reason a company can't get COBOL programmers is because programmers want to work in Python or Java or anything that looks good on a resume for the next job. COBOL is pretty much a dead end, a hiring person is going to look at your last job and see COBOL and say no thanks. Not all companies, but why take the risk?

Contemporary COBOL: Developers' Perspectives on Defects and Defect Location

Related Stories