... if you can't learn COBOL in a week. It's all about syntax, and it's really not that difficult.
I've jumped from language to language my entire career, the first one was only the most difficult because I had to learn constructs like 'if
If someone can't translate their current skills into COBOL, they have no business being in computers at all. Languages change all the time, and if you can't learn a new one quickly, you have no future in the business at all. Hell, I once modified a program written in a language I had never seen before and had no manuals for.
A developer's goal should be to become proficient in many language, and at least knowledgeable in many more. Just last month, I had to read COBOL code in order to write a Java program because the files were created by a COBOL program and I had to know figure out to process EBCDIC files with COMP data into a class and what each field was for. No one on the team had a clue
But I'm old and have skills because I've never said that I don't know how or can't do something. Instead of whining like a little baby when given a small challenge.