Engineers Want To Learn, Even If They’re Very Senior But /what/ do they want to learn? Something about this bit is rubbing me the wrong way: > "In 2002, a ver

Engineers Want To Learn, Even If They’re Very Senior But /what/ do they want to learn? Something about this bit is rubbing me the wrong way: > "In 2002, a very good COBOL or Fortran engineer was probably in a good place as far as their job search was concerned, but today they're unlikely to get much attention from companies that have moved on to more modern languages. Had that engineer focused on growth to keep up with changes in the industry, they might have learned Python or JavaScript and been able to keep up with the market." Is .. reinventing the wheel, or learning the same thing in a new language, really the same as "growth"? Is it even "learning" in any way more than "memorization"? Since when is "keeping up with the Joneses" the same as "(personal) growth"? Had that engineer focused on growth and learning, perhaps they'd now be a High Performance Computing specialist in Fortran, or a business analyst with an MBA overseeing a COBOL team's migration, or a founder of a COBOL codebase analysis tool company, or a bi-lingual contractor traveling to help foreign companies move away from COBOL, or .. anything, growing and changing instead of writing a database report in COBOL then in Java then C# then in JavaScript.