The majority of tech companies and tech employment in the US exists outside of San Francisco, New York, Los Angeles, Boston and Seattle.
There are 6.9 million technology jobs in the US currently. There are about 1.2 million technology jobs in all of California. Just Texas + Florida = 900,000. New York has close to 400,000.
So CA + NY = 1.6 million out of 6.9 million US technology jobs. Not all of those are located in SF, LA, NYC. Also of importance: a very large percentage of that tech workforce in California, consists of a small number of huge tech companies.
The slim minority of tech companies are located in locations with such extreme living expenses. They do represent the extreme outlier outcomes when it comes to producing iconic mega corporations (high value market capitalizations).
It turns out there is an extremely large economy outside of Silicon Valley. See:
Cyberstates 2017 Study
"The definitive state-by-state analysis of the U.S. tech industry"
http://www.cyberstates.org/pdf/CompTIA%20Cyberstates%202017....
I see this a lot; techies are paid well compared to a lot of other industries, and yeah, no argument there.
My question becomes: how much better paid should they be, looking up the company hierarchy, looking at owners/investors/etc?
The question of "what's fair" shouldn't be restrained just to us workers, the comparison should really map out in along a different spectrum.
Actually maybe only 80. Foundin is hard.
Back when I was making 35k/yr in Seattle I did the math and could have doubled my take-home working a min-wage job at the hours I was putting in.
The last game studio I worked at measured actual work hours and noted a significant discrepancy between what people thought they worked and what they actually worked. A lot of people over-estimate their load during crunch. Maybe they factor in commutes, maybe they just over-estimate, but a lot of people that though they worked 80 were only in the building for ~60-65. Some people who thought (or at least said) they were pulling 45-50 were actually working 35. Maybe the mental stress of crunch adds phantom hours.
People overestimate their hours when they work places that treat long hours as a sign of commitment or productivity. When the culture expects long hours, people fake long hours.
Either way crunch has no place but that industry has so many wide-eyed people clamoring to get in that I don't see it ever changing.
Who about on call? You can be called repeatedly in the middle of the night, every night.
I've seen people being abused to work on days, nights and week end. It's doable.
Got a ton of shit for it too because everyone else usually rolled in at 12-2pm and stayed till 2-3am so the time I worked from 8-12 wasn't noticed and I got called out for leaving "early" at 11pm.
Got into a huge fight with one of our content guys over it which was one of the catalysts for leaving that industry. That along with blowing a red light next to my place 2 times when I realized that job was literally going to kill me.
FWIW the previous gig was pretty similar.
That's not even half of the crazy war stories I have from that industry. I'm always happy to talk to engineers who are interested so I can tell them to stay the fuck away(or learn how to put proper boundaries on working hours, which will get you passed over on career progression).
Once I started managing, I found it extremely difficult to avoid discounting the people "only" working 55 hours rather than the guys who pulled 65. People with kids on my team putting in an extra 3 hours each and every weekday for years, and the company/environment/industry made it seem like slacking.
I more or less missed the first year of one of my kids over a long crunch. Here's to the wives we didn't deserve to keep!
As a younger person I routinely put in 36h of continuous work. Can’t do that no more.
Some of us actually prefer to sprint then rest.
I laughed.