News for hackers. Stuff that matters.
Re:Banks should let COBOL die by marktangotango on Wednesday April 26, 2017 @09:48AM (#14202869)
I get tired of seeing these same sensationalist falsehoods propagated without challenge. So I shall challenge.

>> We did a piece the other day about how learning the ancient programming language COBOL could make you bank.

>> Which can only maintained by small group of veterans, that grows thinner every day.

>>There are almost no new COBOL programmers available so as retirees start passing away, then so does the maintenance for software written in the ancient programming language.

This is false because there is in fact tons of COBOL talent around (in the US). The waves of offshoring in the '00s left many thousands of unemployed COBOL developers. I personally know of 100's in the local market. A prominent financial services and BPO firm off shored mainframe development, and laid off many 100's here. Most got out of software development all together. This skills shortage simply doesn't exist.

Re:Banks should let COBOL die by krylon on Wednesday April 26, 2017 @10:06AM (#14203040)
I kind of suspect that when companies complain about lack of talent, what they really mean is a lack of people with the required skill set (God forbid they should pay for training their own employees!) willing to do senior-level work at entry-level wages.
Re:Banks should let COBOL die by potato_mOWX2EVX on Wednesday April 26, 2017 @10:15AM (#14203125)
Yeap, it's true.

Me, COBOL in LinkedIn... Inflated offers via LinkedIn, Zero.

Re:Banks should let COBOL die by rihegher on Wednesday April 26, 2017 @02:43PM (#14205798)
Same for Perl
Re:Banks should let COBOL die by samBergeron on Wednesday April 26, 2017 @09:57AM (#14202957)
>> The waves of offshoring in the '00s left many thousands of unemployed COBOL developers

If you were a developer affected by stuff in the '00s, you're probably nearing the end of your career (unless you'd just started) The problem here is the lack of a NEW talent pool.

Re:Banks should let COBOL die by le-mark on Wednesday April 26, 2017 @10:04AM (#14203016)
Why do you think this would be true? For example, I went through a mega corps cobol bootcamp in 2003 with 30 other people. They ran two courses a year up until 2008 or so. It's not as if all cobol training stopped in the 60's.
Re:Banks should let COBOL die by DanBC on Wednesday April 26, 2017 @10:25AM (#14203220)
Age 30 in 2000 is 47 today.

Is 47 really "near the end of your career"?

Re:Banks should let COBOL die by washadjeffmad on Wednesday April 26, 2017 @11:22AM (#14203707)
Nearer to the end than the beginning, perhaps.

I always get a chuckle when some hopeful naif writes like they're going to retire at 50 and be done. Most everyone I know who's tried that "gets bored" and goes back to work or starts consulting after a half year trying to find their feet. Those are also the ones who when asked what happened tell you they've got plenty of good years left and are now planning on retiring at 70.

47 is still building steam in my experience.

Re:Banks should let COBOL die by nickpsecurity on Wednesday April 26, 2017 @11:28AM (#14203773)
Our company has high turnover on the bottom. A steady percentage of new hires are bored, retired people. :)
Re:Banks should let COBOL die by pjmlp on Wednesday April 26, 2017 @11:09AM (#14203589)
I guess if one lives in SV, it might be.
Re:Banks should let COBOL die by dragonwriter on Wednesday April 26, 2017 @03:52PM (#14206367)
> Is 47 really "near the end of your career"?

As a non-lead, non-management code slinger? It's usually well past it.