How and where to learn COBOL?
Do You Know Cobol? If So, There Might Be a Job for You
51–54 of 54 posts
Re: Do You Know Cobol? If So, There Might Be a Job for You
#52I could learn COBOL; I've had to take classes in my undergrad and one of my careers involved it. There's a couple of reasons why I dont: * Putting my career on a trajectory where I am using a dying technology. Unless it paid 3x-5x what I could make using a JVM language (my current career path), the risk/reward isn't there. So market forces will need to drive the cost of salaries up even farther before I consider a ju…
I made the explicit choice to avoid the COBOL trajectory in 2001 when I graduated from college. At the time the place I graduated from was working hard to graduate people with skills for the local industry (which was cobol, jcl, rpgIII, etc)
I don’t blame the college. But it was a choice and for me it was a good one.
Re: Do You Know Cobol? If So, There Might Be a Job for You
#53I'm glad to hear about the freelance gigs for COBOL coders.
I started with COBOL. If the freelance gigs continue on, maybe I'll wind down my career with a little part-time, once-in-a-while COBOL work.
It might just be nostalgia, but I miss that environment a little bit.
Re: Do You Know Cobol? If So, There Might Be a Job for You
#54Replying to the title here, but from my experience knowing how to program COBOL was only one small part of the problem at my previous employer. Knowing what the programs where doing and what other programs the output affected mattered much more. Such knowledge was not set in documentation but rather in people's heads, more often than not that knowledge disappeared as soon as the person that had been working in that p…
Yes, I agree.
It's the business knowledge that really matters. I think this is true no matter what languages and toolsets are used-- in the end, it turns out to be the surrounding information that's of value.