2 ms·
Think legacy. But not too legacy. A friend of the family got his first programming gig (in the early 80s) working on some old in house main frame system at a f
by dagw 4y ago
Think legacy.
But not too legacy. A friend of the family got his first programming gig (in the early 80s) working on some old in house main frame system at a fortune50 company and spent the next 20 years doing that. When they retired that system in the early 2000s they fired him and he ended up having to take a job at a gas station, since no one was interested in hiring someone who had spent their entire career working on some main frame system that no one had ever heard of.
- mikerg87 4y agoI'm not talking about a first gig, I'm talking about skills and skillsets where you aren't competing with new devs and the .js flavour of the month. Sorry to hear about your friend, but my friends in the mainframe priesthood tell me - "it's not about knowing COBOL so much as it is the CICS/JCL and other legacy stuff that keeps that COBOL alive they are really paying for". The kind of things that unless you lived it you can't possibly know because it never made it into google.