4 ms·
I 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
by exabrial 8y ago
I 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 jump.
* Outdated development methodologies. My experience with COBOL so far is a lot of entrenched practices that we later learned are inefficient. Both tools and management have been extraordinarily reluctant to improvement and change. I'm not willing to undertake the additional stress to deal with PITA, so until the management over these ares is forced into retirement, companies will endure a shortage of fresh talent.
- yashap 8y agoAnd really, it’ll probably pay A LOT less than you make using a JVM language, not more.
- jeremy_wiebe 8y agoI 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.