And I suspect one reason why we don't want to tackle climate change (or even generally take more advantage of technological progress) is that it requires a different skill set, the one that is lot more blue collar, and to make that transformation we would have to upset the existing social order.
In other words, I generally don't believe there is only one solution to the "market equations". Remuneration, price of different types of labor, also depends on cultural factors.
And because there is not always unique solution, you might end up in a local maximum of productivity. One way around it is what Doctorow suggests, we all gather around a table (well, metaphorically, with a government as our proxy) and decide, well, we have to do these things, and here are the jobs to be filled (and he further argues that we are in such local maximum regarding the climate change, and we can get out of it).
Sadly, it's been really difficult historically to get out of such local maxima without profound rifts in the society, civilizations often chose death rather than do this. And that's what I worry about, and I think we need to come to terms with.
Most of the people who go into management seem to do it reflexively. They see the word promotion and go for it. As you can imagine, they don't even get a respect upgrade, because everyone knows the cards.
Of course, the Post Office has a relatively strong union - particularly by US standards. That's the major hurdle for most blue-collar jobs. They don't even have a seat at the negotiating table. Without a coordinated voice and some power, workers take first offers. Companies can afford to pay shit wages the same way that factories during the Industrial Revolution could afford to work people to death.
It's hard and expensive to turn somebody into a programmer, and you can't scale it up as you wish. It's easy in comparison to have more people who can do dangerous jobs: you just need more children and wait 20 years.
For management and similar roles, I agree somewhat (it's much harder to pinpoint the skills required, and they often have less direct influence in the success of the company/project), but for the actual jobs, like software development and engineering? Yeah, they are high skill.
> Remuneration, price of different types of labor, also depends on cultural factors.
I don't think so. Unless you include religion and royalty where you can't just get into some career, the ones that are easy, low-risk and high-pay/high-power will always be attractive and you will be able to predict movements pretty well with market models.
Is it? We work in one of the few industries where self-taught may actually be the norm (or at least, a significant minority).
I am an autodidact, and I'm clearly worse than actual CS people in the CS stuff, but that's not a problem for me, because we're in an industry where we lump together people who work on hard problems and people who basically translate requirements into business logic code. The CS people could do my job, I couldn't do theirs (there are some autodidacts that could, but they are a tiny minority imho), and for most intents and purposes, it doesn't matter, because most requirements don't require high level computer science, they require python, php, javascript and css etc.
A good comparison is quality comments and coding standards. Consider if there was an enforceable standard for code structure, comments, documentation, etc like most decent github repos with developers striving to reach Linux kernel level overall quality. This would include a standard training/education process, collective bargaining and action for pay/benefits and standard to changes. It is a field where not every ISO standard needs to be applied in full, but there could still be some base enforcement.
Like, what if every code base was commented, well structured, and followed general best practices like to-code electrical or plumbing work? What if code review or inspections against a standard were enforced time set aside and sign off required before wrapping a project? What if the lowest bidder on a coding job had a floor due to set benefits and standing agreement on rates and max hours per week/day? These are practices the best employers may strive for and are able to apply but are required in most trades.
I appreciate a line comparing how artists are payed compared to trades: If a band is asked to do a show for the 'exposure' they should ask the planner to call the local plumbers union and ask their going rate for 4 plumbers for a 4 hour job. Home advisor has a few estimates but project data puts an average at $317/hour. Maybe a random band isn't worth $1200/hour or $5k a gig but some definitely can command that price. If most bands stuck to a standard rate range the planner will expect and budget for proper pay.
Isn't that exactly what we do though? Doesn't pay (very approximately) correlate with required skill? For example, compare the salary of a skilled carpenter with some of the lower skilled "tech" jobs. All of your examples (manager, scum master, programmer) are decidedly high skill jobs when compared to the economy as a whole.
(As far as software goes, consider that demand for laborers currently outstrips supply. Prices adjust to reflect that.)
What you're really describing (IMO) is that everyone is competing with each other and we all want to be above average. Going back to your tech industry examples, I've heard it said that the majority of programmers think they're above average.