Is it not enough to just say that we should pay people market rates? If the true cost of a firefighter in California is indeed 190k then thats what they should be paid. If its lower then they are overpaid and if its higher than they are underpaid.

This is not to say that firefighters are not essential workers, of course they are. We can make an argument that every firefighter should be paid 500k or 1 million. Heck, they save lives, so why not 10 million?

Ultimately, the vast majority of people not in public sector work doesn't get to make these kinds of arguments, and are simply forced to take market rates.

These markets are monopsonies. The market rate is much lower than the actual value these jobs are worth. Even so, we do not have enough firefighters and teachers. This is a price signal that the current compensation is insufficient.

Not enough firefighters in that there are open positions and no one is interested? Or open positions only for the already trained/experienced?

If it’s the latter then that’s an argument that compensation is too high if anything. It should be rebalanced such that some of it is used for training.

If the former then that’s just alien to me. Here in Australia firefighting is a prestigious job with a lot of competition. People volunteer to do it for free or do it part time while working another primary job, for years, in the hopes of being able to become a full time firey.

In California, people aren't volunteering enough, they have to resort to prisoners. As far as teachers at least, there are open positions, that require training of course, hence the need for a higher salary.

Kind of? Do you think the market for firefighters is a monopsony and if so, how does that shape the firefighter labor market?

Maybe so, but this is always going to be a problem with unionized government work. We can try to approximate a free market by reducing the power of public-sector unions. Ultimately it has to come down to tax payers to hold government accountable. More transparency is a step in that direction.

Is this the bureaucracy defense? I need to be certified, have 30 years experience, and do a 10,000 page analysis before I can have a "legitimate" opinion.

No, but you presented a false dichotomy.

They are saying my process isn't "rigorous" enough and needs to follow their complicated rules and ways of doing things, I don't think calling that bureaucratic is a false dichotomy.

No, they're saying you're making purely gut judgements that are rash.

For any employer, private or public, slashing salaries and benefits is a great way to start trending towards 100% turnover, which is a pretty negative outcome if you want to maintain any semblance of operation.

All I said is that it might be excessive to pay 40% of public employee's individually [1] 40k more a year than the median household income [2] in the area.

Don't equate that with arguing for Austerity.

https://www.openthebooks.com/forbes-why-san-francisco-is-in-... [1] https://www.census.gov/quickfacts/sanfranciscocitycalifornia [2]

Are you not arguing that public sector employees in San Francisco should get a pay cut?

Not really, all I did was question the OP scoffing that an 150k salary is not a lot of money. My mother is a public school teacher.

It's not a lot of money in San Francisco, where you're fighting with every tech company employee for housing

Do you have a quantitive way of making the distinction of what "a lot" is? 150k is substantially more than the average SF household, and is about 83 percentile for individuals.

https://dqydj.com/income-by-city/

Average home prices in SF is 1.3M, so a household of two teachers would give them a P/E ratio of 5. The P/E ratio for the average US home is 4.4.

Are teachers overpaid, or are people in SF underpaid relative to the value of a house?

a P/E ratio of 4.4 is nuts. The fact that we normalized that is wild. Same for committing 30% of net income to housing.

That's right. I enjoy phrasing social problems in the language of software engineering so I'll do that here. The structures which enable these salaries are a Chesteron's Fence[1]. Shooting from the hip ignores second-order effects[2] and is a thought terminating rhetorical pattern. It's the equivalent of trying random code to fix a bug without doing root-cause analysis. If I tried to do any of these on a development team I'd expect someone to take me aside and kindly explain the consequences. For some reason (which I'd be happy to understand) all of these valuable mental tools are left on the bench when we move out of development and into other realms. They are powerful techniques to understand systems of all types -- we should aspire to use them whenever we can.

1. https://fs.blog/chestertons-fence/

2. https://personalmba.com/second-order-effects/

Agreed that it is important to understand things on a systems level, but at what point are we not talking about Chesterton's Fence but The Divine Right of Kings/Mandate of Heaven.

This feels risky, like a reply to a rhetorical question. For me the difference between the two is the acknowledgement of human authorship. Chesterton's Fence assumes human authorship leaving open the possibility for change, while the The Divine Right of Kings/Mandate of Heaven explicitly buries its authorship in an attempt to crystalize it as immutable. Feel free to disagree, but it feels like we're drifting away from the plot.

My thought is that your claim that setting salaries is a complicated process and we shouldn't rashly come to judgement, while not untrue, is also in effect saying "ours is not to wonder why" and that because high salaries exists therefore they are legitimate a la Divine Right of Kings.