I don't believe the market actually is bad for people with a modern systems programming skillset (not least because we have trouble hiring those people), but I don't doubt that there are systems jobs that used to be common that no longer are.
Nobody has a license not to adapt. If you're stuck in a crappy job working overtime solely because you're stuck maintaining AIX database applications, it's hard to blame the structure of the job market on that. Get thee to Github.
One, I wasn't referring specifically to myself.
Two, I wasn't referring to someone who never learns new things. What company do you work for? We may have spoken before on this subject...
Three, not everyone is in Silicon Valley.
And the attitude displayed in this argument, is part of the problem, IMHO. Because it translates to only "rock-star" (as denoted by the "qualified") programmers/employees getting to benefit from such an environment. It's as if, if some person isn't a top-notch in his field, it's ok to suffer that kind of abuse from his employer.
Yet, companies don't run only with "qualified" guys that can easily shop around for new jobs, they also use lots of run-of-the-mill programmers, sometimes even purposefully ("we get a few greats to design the program architecture, and dozens of monkeys to code the parts"). They also should not have to work for unpaid overtime.
(I'm not talking as a sprint to finish before some deadline once in a while, I'm talking as a regular occurrence).
Huh?
You specifically said in your comment that: "a qualified employee will simply quit an abusive job and sell their skills to a more reasonable employer".
This is exactly what I addressed.
You might not have meant that "thus average guys are ok to suffer unpaid overtime", but I didn't argue against what you "actually said" or "meant to say", I argued about what the above stance implies.
And, yes, for a lot of people, it implies "and screw the average guy".