They usually do as they please, and assign extras or not, and ultimately learn in the long run.
This isn’t to say that extra staff on a project can’t be helpful. But more often than not, management miss-estimates how the extra staff will impact the project.
In my experience what instead happens is that companies are ok with bugs so long as you communicate why it happened and how you are going to fix it. So the tradeoff is clear, spend a lot of time managing and let bugs happen so long as they are being managed properly. This is what I think causes fragile software at scale. People with high level technical knowledge should be hands on, and any bugs should be unacceptable.
The shits that I give wax and wane on a quarterly basis, but the average pattern is me being largely disengaged, disincentivized to well, and burnt out. I’ve basically told my company they can’t really count on me for anything.
Maybe they’re trying to get me to quit or waiting for the contract company to hire me direct.
can you imagine if the IEEE had formed a union, way back in the 40's or so...???
The Seattle area is full of tech employees who are millionaires and some even up to 9 figures.
SV is also not the whole industry so looking outside of that, I see exactly what OP is saying. Technical staff are usually required to split their time across numerous project management tasks that are mostly to support the project management team's communication of goals to the client up the ladder. I am not purporting to have a solution to the problem mind you, it's more complex than just "let em code man!"