Where the Good Jobs Are
nytimes.com
nytimes.com
This is a crazy sentence if you think about it. For a significant part of society wages did not only stagnate, they dropped. I don't think the trend will reverse any time soon. If the wages of another profecion rose 10 percent and were equal before, we would see a 22 percent difference (which is a lot!).
Since this is the trend for all workers with some college education but without a four year degree, i think it's a dire situation for those people. There's no easy way out (the article suggesst moving!).
The suggestion in the article may be smart on an individual level, but it could lead to a further segregation between sucessfull and not sucessfull regions.
What actually happened is that more people from less wealthy backgrounds went to college.
According to statistics, 30% of new immigrants have no high school diploma, so while the average wage is low, it's probably much higher than they would be getting in their native country (otherwise, presumably, many woudn't have left in the first place.)
This may be putting pressure on wage growth for native-born Americans but overall growth as a whole may be stronger than it looks.
You forget about cost of living here.
But I'm willing to bet globalization (wages in China) have a much larger effect on wages for average US jobs than immigrants coming to the US do.
There's a lot more competition to do almost anything in China or India than there is from (potentially) lower paid immigrants in the US.
Sure, not everything can be outsourced. But for everything else...
https://www.nytimes.com/2018/09/25/us/politics/wage-growth-b...
I'm confused by this argument. Has the value provided by health insurance gotten better to make up for the additional cost? If you're paying those 10% into health insurance and the benefit hasn't increased with that increase in cost, I'd say you're moving backwards.
That stuff doesn't come free. It would be kind of neat to offer the option of a 1950s level of care, only modernizing things if cost would be reduced by newer technology. Lots of people survived the 1950s just fine. Even just going back to 1995 would be a huge difference, avoiding all currently active patents.
https://www.managedcaremag.com/archives/2015/9/cost-differen...
ALWAYS remember: All benefits are paid for by reducing wages one way or another.
The effect of benefits on minimum wage is actually BIGGER than the current hourly minimum wage. Consider health insurance. Employers are required to pay for insurance for their employees working more than 30 hours. They cannot force the employee to pay more than around 10% of the cost AND the insurance must cover at least 60% of the costs. Average health insurance costs are (according to a quick google) $440 per month which leaves the employer paying $400 each month for health insurance per full-time employee (that's a $2.50/hr minimum wage increase for all full-time employees).
This leaves four options. The first is to raise prices across the board (hardly feasible). The second is to hire a ton of 29 hour "part-time" employees, but there are still hidden per-employee costs like extra unemployment, worker's comp, training, scheduling issues, etc. The third is to work employees 45-50 hours per week because the overtime cost in that range is still less than the cost of 1.5 time is still cheaper than all the fixed costs for bringing in another employee.
The final option (probably what we see here) is to use the other options until inflation allows you to recover from the pay issue, but with cash benefits not recovering in order to pay for all the other benefits the employee is buying.
These same things apply to all the other benefits ranging from vacation to 401k.
This also ties into 1099 negotiation. DO NOT negotiate with the cost of employment salary in mind. Instead, negotiate with the total cost of benefits in mind. Ask what the total cost of ownership for an employee would be. You need to be compensated for that $400 per month health insurance. You need to be compensated for that 3-4 weeks of vacation you can't take. You need to be compensated for losing 1 year of unemployment benefits if your job disappears. You need to be compensated for that 401k match. Especially don't forget that extra 7.5% you need for the other half of social security.
I worked for a company a few years ago for a while before finding out their cost to hire me as a contractor was around 100k per year while an employee with the same position would be paid 90k in cash and another 80k in benefits. That made a huge difference the next time I sat down at the negotiation table.
This growing gap shows how we value people, many in roles that our society requires.
On top of that, there are a lot of college education programs that have close to no market value (i.e. leading to no actual jobs or already in saturated job markets) so you should expect this to impact the median earnings, and lead to adjustments to take place over time (instead of seeing a linear growth).
I imagine the net result of globalization will be to make the two converge. (hopefully human rights will be converging too EDIT: I mean rise)
In other words, in 2000, the 25th percentile worker by education level had no college education, and in 2019 the 25th percentile worker by education level does have some college education (but no degree). The 25th percentile worker by education level makes more money in 2019 than they did in 2000, even when adjusting for inflation, but which category they are counted in has changed as the population becomes more educated.
(more can be said, and has been said elsewhere, about how much of the purpose of higher education is to develop one's skills and how much is to serve as an IQ / conscientiousness test that employers can't be sued for using)
That's probably my own experience and it involves a low sample size, but as a small business owner, Id argue that you can really benefit by dropping the degree barrier and looking for other indicators of maturity and reliability.
I've always been very grateful and always been willing to do any work I can or go out of my way when I can to get the job done. This stems from the fact that I am grateful for my boss for "taking a chance on me". I know hiring doesn't always work out and I do what I can to be the shining star of people they look for, in the future to hire.
It was very rewarding when in fact my direct manager said to me in conversation " How do we find more people like you?"
Probably the best compliment I could have received.
Before anyone else chimes in, I am not underpaid. I work for a great company and am probably paid above market average.
I've hired dozens of Software Engineers and could only tell you the degrees and/or schools of a couple of them. I don't even look at that. Can you demonstrates proficiency in what I'm asking you to do? Do you seem intelligent and willing & able to learn? Do you fill a gap on the team? Those are the things I want to know.
Software engineering is a trade skill, after all.
A well-intentioned intern can make a programming decision in an afternoon that might take a team of senior SWEs months or more to clean up later once the code or data is being used for something important.
We brush the bad engineering decisions under the rug by calling them "tech debt", but the truth is that if we invested more up front in hiring people with big picture skills and experience we'd probably save significantly more money in the long run, despite their higher salaries.
And a new maintenance tech with the wrong grease gun can cause millions of dollars of downtime. This kind of risk exists in all industries.
You don't need a degree for plumbing. It comes in damn handy when you're doing things like flow dynamics or combustion simulations
Just like aeronautical and construction engineering, surgery, dentistry...
I usually tell people "I program computers" when they ask what I do. I used to say "I do computers" but people are more used to computers and software now so fewer people ask, "so, you do computers?" so I had to change it up a bit.
They tend to just get things done, without spinning themselves in circles building unhelpful mountains of abstractions or searching high and low for a place that they can apply their algorithms coursework.
Though the flipside is that they make lateral transfers very easy, so those that are the most motivated by more challenging or even just more CS-oriented work find themselves drifting towards it.
On the other hand, even after you've performed the "real work" of thinking things through, the fact that your code works isn't the "real product". The real product is the degree to which the code can be understood, maintained, and extended.
I think that the idea that software engineering is a trade skill produces two problems:
It encourages management to discount software engineers' expertise and view the planning that comes before writing code as a waste of time.
I think when people today say "trade skill" they think of things like factory work and relatively routine construction. However, a programmer is more like a traditional artisan who must always be honing their craft and learning new techniques.
In my opinion, a better way of looking at it is that companies should start actually treating software engineers like engineers. I.e. by viewing them as professionals with the expertise to inform project planning and a professional obligation to follow best practices and design.
Much like being a software engineer the real product of a carpenter is how what the build withstands the elements, can be repaired, maintained, and extended, and that is only achieved after putting in the thought and design that comes before construction. Much like a software engineer, a carpenter must keep up to date on building codes and regulations, different materials and how they are used safely, and collecting, maintaining, and extending their tools.
Software engineers often talk about "sharpening the saw". That's literally something a carpenter would do.
It really depends. I don't think you can compare writing a CRUD to writing a hardware controller, for example.
I think HN tends to be in a bit of a web bubble. There's plenty of software engineering that has nothing to do with the web.
But seeing how I taught myself assembly language in the 80s and learned how to optimized programs to run on 65C02 1Mhz computers with 128KB of RAM in middle school, I don’t see why teaching yourself how to do low level hardware programming is any different than learning anything else.
Yes and I spent 12 years doing C bit twiddling.
Most of these programmers have moved on to Java, Javascript, and Python.
Those doing "C bit twiddling" are the other C programmers. Most commonly I hear the phrase from people who are capable of this low-level programming but never liked it. People using the phrase seem to be mostly people who have moved on to languages like C++, C#, and Go. People actually doing the "C bit twiddling" seem to just say "C programming" as you have suspected.
So I guess it is a way of saying "C, including the parts I don't miss" for people who could do it but never liked it.
Some would call it „willing”, some „more desperate”.
I wouldn’t have called Feynman desperate. http://longnow.org/essays/richard-feynman-connection-machine...
Some things just need doing, like buying pencils.
Being willing to take on tasks as menial as picking up some pencils for the team might be a symptom of desperation. It equally might be a symptom of a lack of egotistical arrogance [that one is above such tasks].
Also called into question is the definition of a lesser task. You see, in the Feynman scenario they could not have got much work done in a short time without more pencils—no matter who was fetching them.
Added: It really was quite like this Dilbert comic https://dilbert.com/strip/2019-01-21
Later on I did some framing work on my own. Ran into several cases where the designer completely ignored the dimensional instability of wood due to changes in humidity. Often that was really hard for the "no education" guys to fix.
Some contracts (mostly government) have a strict definition of what an FTE is/can be. Because it's the government, instead of having a nuanced understanding of the field, they treat everything as a series of buckets - "you have a college degree? You're Engineer II. No degree? Clearly Engineer I." There's some wiggle room with technical experience and whatnot, but it's tricky to do.
So, when the government customer puts out a request for bids, they'll say something like "we want a system that does X, Y, Z, and we expect this to require 3 FTE 2s and a part time PM for 6 months" - generally establishing the upper limit of what they'll pay/how many hours should be billed to the project. (This gets interesting when you realize that the customer doesn't really know how the sausage is made, so they talk informally with contractors to get a feel for what's possible/go to a team they've worked with before, get a feeler for what the requirements should be for a project/what to expect cost wise, and only then put out the formal request. 9/10 this means that the government PM has a team they want in mind, and basically has the team write their own requirements sheet).
Any way, long story short the credentialed designers look good on a contract, and produce valuable designs that can get approved/validated by the Powers That Be, while the mechanics who implement things come up with the product. Both are providing value, just in different ways.
Also, sometimes you need to start with a lovely design, even if you know it will never survive production.
Yes, it is technically possible to become one without a bachelor's degree, but it does require a minimum of three-quarters of a bachelor's degree and it is becoming more and more common for new RNs to be required to go ahead and get a bachelor's.
There is a kind of snobbery to working jobs which I think is wrong. My pal who is now a leccie (Electrician) can charge crazy money and is laughing all the way to the bank. Maybe I will quit my dev job and become his apprentice :)
Can he scale his business to more than a single employee? Does he get many connections that allow him to move on - e.g. become a senior engineer at a nuclear facility? What happens to him when we move on to some other "smart" electricity scheme which outdates all of his practical skills?
Also, does every business need to scale more than 1 employee? Even if it's 2, 3 people max, that level of "freedom from worry" would make that duo/trio very happy indeed.
AFAIK smart electricity for scheme for even a block level is notoriously hard with today's tech, the number of edge cases must be enormous.
The practical skills are unlikely to become outdated quickly, since they are mainly about standards compliance and electrical safety. Even if something as large as the shift from gas lighting to electricity >100 years ago happened today, there would probably still be need for electricians, just as we still have gas engineers now.
Most can take on other workers or young apprentices quite easily. The two i know that have done it now only work their trade 2-3 days a week and spend most their time doing the admin / business side.
Not sure how piratical skills in electricity can become outdated? New legislation can be released around safety i guess...?
> What happens to him when we move on to some other "smart" electricity scheme which outdates all of his practical skills?
Maxwell's equations aren't going out of fashion. Some regulatory updates are necessary, though. Cost of doing business.
Note that back in the day the entry requirements for advanced apprenticeships where quite high - higher than for entry level jobs in Banks or Nursing
You usually need 4+ years of experience as a licensed journeyman. That requires 4-5 years of apprenticeship school and usually 2-3 years as a helper before you will be able to get in. No chance at that "startup" until you're in your 30s usually.
Next, you need a few hundred for the exam. You need thousands in "working capital". Then you need tens of thousands for a bond. Not many people have that kind of money lying around.
Finally, as a final dose of nepotism, you have to be "pre-approved" to take the exam. That means that a few people who already have master's licenses must approve you to become their competitor.
I've met numerous people in my 10+ years of software development without a degree. I don't have one either.
As I heard from one candidate in an interview, “software development is one of very few career paths left to have a middle class lifestyle without a degree.“
My biased opinion is that devs without a degree hustle a little more and are more willing to tackle brownfield projects and nasty refactoring/conversion efforts.
That's very true, and it's because technology is more of a meritocracy than most other professions. Your compiler doesn't care about your credentials, or who your family is, emotional pleas, or any of the other myriad factors that get people into jobs they're not capable of. The culture of meritocracy is pretty heavily under assault, but I'm confident it will survive for a while yet.
As a dropout who learns faster on youtube than in a classroom, and making more than my state senator's entire family, let me give everyone reading this advice: Don't be scared away by elites protecting their jobs in large cities. Come in at 70% of the price, excellent work ethic, and give them a run for their money. Most Americans live in a country that values cost efficiency over credentials. We hold meritocracy above bureaucracy, and it should be celebrated not discouraged.
I promise you, unless these prestigious schools are able to vastly change their business model, they are going to decline heavily.
No, absolutely not.
Also, my Dad grew up on a shit farm, forced to work for free until he escaped as a teenager. I wasn't born with a silver spoon in my mouth. Work hard, get smart, get rich, in that order.
This isn't a 'meritocracy'. This is exploitative behavior disguised as being beneficial mixed in with a bit of survivorship bias. I've had friends of mine take software jobs paying well the average (as in, 50k and below in an expensive city) thinking that by just working extra hard the company will reward those efforts.
You're not the arbiter of cost efficiency. The company looking to hire you is. When you presume you're worth less than what you actually are, you're opening yourself up to abuse.
What you're describing is in essence the various entertainment industries which take advantage of fresh grads, forcing them into long overtime and for less pay.
College isnt for everyone, but parents push super hard to get their kids there and I dont know why. I went to a 2 year trade school for diesel engine repair. It was affordable and I could pay my way through with a job at a local pizza chain. Try finding a 4 year college you can afford with that pay-grade.
living in a big city isnt for everyone. I did a stint in Brooklyn once, learning to service buses and garbage trucks. The pay is good but the pace is sometimes insane because thats the pace of the city you live in. Theres a lot of pressure to deliver it right the first time, and i dont regret learning that work ethic, but I didnt find home in that city.
What i can say for the trade i have is that its rewarding and sometimes pays close to cut-rate lawyer money. I dont worry about bills and ive got plenty of cash to hit the pub once a week to see the game. The world needs electricians, plumbers, and even mechanics to keep running. Check out the hourly base pay of most of these trades and try to imagine pulling a little overtime, which is usually part of the trade in salary jobs as well im told. HVAC is also a great trade with endless advancement and opportunity.
Implying that the ordinary person has the opportunity to make more than another person's entire family is -- by it's nature -- a joke. You can't be anywhere near average and make more earn more than 3+ average people. Using a normal distribution, that puts you a MINIMUM of 3 standard deviations above average -- literally the 0.1%. Using the actual income distribution (since it's distinctively NOT normal) -- it puts you in the top 2%. But if you actually work for a living (as opposed to collect returns on investments), it's likely in the top 0.1%.
A state senator is likely to be above average -- as are family members. In general, we don't strive to elect average. We strive to elect excellence.
Maybe it was meant to be a pep-talk. But just because one person dropped out of school and did well, doesn't mean that everyone can do the same. Maybe the OP is a genius. If not, he got lucky. And not everyone can be a genius or lucky.
I would be interested to know what percentage of these jobs are actually filled by people without degrees. It could be that these markets have less degree holders so they change the requirements to increase applications. What matters is who ultimately gets hired.
I don't see how any of this relates to "opportunity," in the sense that they're going for in this article. These jobs aren't any more accessible than college-required jobs.
I'd guess there's a similar situation in most of towns on this list, which would mean living there is a huge risk unless you plan on working at the one or two companies in town for life.
If you calculate totals, the "superstar" cities do better, thanks to their larger overall populations.
For example: The lowest scoring city, Washington, has 452,600 good jobs. The highest scoring city, Toledo, has only 100,980 such jobs.
You're not going to live comfortably in San Jose on 47k a year.
[1]: https://www.deptofnumbers.com/rent/us
[2]: https://www.rentcafe.com/average-rent-market-trends/us/ca/sa...
I'm not usually one to be pedantic, but it seems like there's many MANY "terrible jobs" that pay $37k or more. I assume they had to keep it simple for their definition, and much of what makes a job actually good is subjective, but I was hoping this would have a little more nuance. It seems obvious to say pay is only part of what makes a good job good.
The interesting thing about this definition, to me, is the Lake Wobegon-esque effect that statistically half of all jobs are "good" because they're above the median. A poverty level or inflation-adjusted absolute metric might be more useful; you could measure the effect of policies based on the reduction of or increase in the number of good jobs.
"The last Cruze remained inside the plant, awaiting a final inspection. By then, it had already come to be much more than a car. It was a token of the most coveted working-class possession: a secure, well-paying job with health insurance and a pension."
I mean, guys, it's not much folks are asking for here.
For a counter example, you can look at Tokyo as a place that's more of a free for all, and indeed while it's still fairly expensive, it's much less so than the bay area or NYC.
https://www.numbeo.com/cost-of-living/compare_cities.jsp?cou...
You can't, but there are things that can be done to compensate or mitigate:
- Anti-union regulations like "right to work" laws are an anti-market intrusion that weakens the power of labor. Vote against them.
- Support works councils (they've worked well in Germany) for more democratic governance, which right now I believe are illegal in the US (read this in a Bloomberg article earlier, though haven't verified).
- Support things that make bad jobs less bad. For example, there are benefits offered by 'better' companies, like good health insurance or paid parental leave, that could be provided by the state or mandated by the state.
- Support land use and transportation changes that would allow more people to participate in the economies of 'superstar' cities without ruinous housing costs.
Note that two of these things are even market-oriented, not all the positive changes have to be about more/bigger government.
How is forcing me to join a particular union pro-market?
Also, how am I supposed to vote on this or any of the other things you mentioned? I get one vote per legislative body every 2 || 6 years and that one vote has to cover dozens of issues like this that come up in the interim.
A contract stipulating joining a union for a job is no more anti-market than a contract specifying work hours or clothing requirements or how much vacation you get. If that's how the business has decided to run, the free market perspective is that they should be allowed to. It's market forces that can compel a company to agree to such a setup, after all.
However, a regulation saying that this type of contractual obligations is illegal is very obviously an intrusion on the market. Not that I think all intrusions are bad, but I don't see a compelling reason to support this one, given that corporations already tend to have the advantage over workers and this reduces workers' collective leverage.
Agreed that it's hard to vote narrowly on this topic. But no different from any other political subject, really.
But businesses cannot mandate union membership for employees in right to work states. That's what "right to work" means.
> However, it is actually anti free market to stipulate thar businesses must do this.
Not sure what 'this' you're referring to here, could you clarify please?
Yes they can.. That is what 'right to work' means. If a company mandates union membership and you do not want to join the union, or decide to leave the union, a company in a right to work state will fire you. This is like a union in a non-right-to-work state, where, if there is a union, and you refuse to join it, you can no longer work at the company. This is how it works for teachers unions too (in California at least) -- if you leave or refuse to pay dues, you are automatically let go.
> Not sure what 'this' you're referring to here, could you clarify please?
If you tell all businesses in your state that you must have a union (or accept a union if your employees vote for one), then that is mandating that the company mandate union membership from their employees by a mechanism other than the company's directors' own will. This is an infringement on their liberty (justified or not).
No, it does not.
> According to the Legal Defense Foundation, right-to-work laws prohibit union security agreements, or agreements between employers and labor unions, that govern the extent to which an established union can require employees' membership, payment of union dues, or fees as a condition of employment, either before or after hiring.
https://en.wikipedia.org/wiki/Right-to-work_law
> If you tell all businesses in your state that you must have a union (or accept a union if your employees vote for one)
Nobody was talking about this?
Umm, From your own wikipedia article:
> "right-to-work laws" refers to state laws that prohibit union security agreements between companies and labor unions
You cited one particular definition by one particular foundation that marginally fit your purposes better. I don't see why I shouldn't do the same.
Right to work usually means the company can fire you for any reason, and you can leave the company for any reason.
While true that a company cannot expect an agreement with a union to be legally enforced, they can certainly decide to mandate membership in a union of their own accord. For example, it is reasonable for a company to specify in its job description that it only wants to hire certified Realtors or members of the ACM or whatever other group the company deems necessary.
> Nobody was talking about this?
This is what 'unionization' means in the context of a 'union shop'.
Oh, so this is actually pretty common: you're confusing "right to work" with "at will employment". They're not the same thing.
> At-will employment is a term used in U.S. labor law for contractual relationships in which an employee can be dismissed by an employer for any reason (that is, without having to establish "just cause" for termination), and without warning,[1] as long as the reason is not illegal (e.g. firing because of the employee's race or religion). When an employee is acknowledged as being hired "at will," courts deny the employee any claim for loss resulting from the dismissal. The rule is justified by its proponents on the basis that an employee may be similarly entitled to leave his or her job without reason or warning.[2] The practice is seen as unjust by those who view the employment relationship as characterized by inequality of bargaining power.[3]
https://en.wikipedia.org/wiki/At-will_employment
> You cited one particular definition by one particular foundation that marginally fit your purposes better. I don't see why I shouldn't do the same.
I could cite endless definitions from various sources. Here we go, since apparently you want this:
> The Right To Work principle–the guiding concept of the National Right To Work Committee (NRTWC.org) and the National Right To Work Legal Defense Foundation (NRTW.org) –affirms the right of every American to work for a living without being compelled to belong to a union. Compulsory unionism in any form–“union shop,” “closed shop,” or “agency shop” –is a contradiction of the Right To Work principle and the fundamental human right of freedom that the principle represents.
> The National Right To Work Committee advocates that every individual must have the right, but must not be compelled, to join a labor union.
https://nrtwc.org/facts/right-work-mean/
> Specifically, the right-to-work means that employees are entitled to work in unionized workplaces without actually joining the union or paying regular union dues.
https://www.thebalancecareers.com/right-to-work-2071691
> There’s some confusion surrounding "right to work laws"—perhaps due to the somewhat misleading title. While the "right to work" logically sounds like the right to have a job, or to keep a job once you have it, the term is related to membership in a labor union. More than half of U.S. states have enacted so-called "right to work" laws that guarantee no person can be compelled to join a union or pay union dues, as a condition of employment.
https://employment.findlaw.com/wages-and-benefits/what-are-r...
> I’ve heard that my state has a ‘Right-to-Work’ law. What does that mean?
> In the public-sector union context, right-to-work laws mean that union members do not have to pay union dues to be members of the union.
> In states that have enacted right-to-work laws that apply to private employers, although they vary based on state law, most Right-to-Work laws prohibit labor unions and employers from entering into contracts that only employ unionized workers for the jobs in the contract.
https://www.workplacefairness.org/unions-right-to-work-laws
> This is what 'unionization' means in the context of a 'union shop'.
No, it doesn't. This
> Under this, the employer agrees to either only hire labor union members or to require that any new employees who are not already union members become members within a certain amount of time.
is not the same thing as
> If you tell all businesses in your state that you must have a union
The former is about a particular business decided to only hire people who will join a union, likely because of market pressure from the union/its members. The latter would be a a state mandating that union membership is required by law. Those are not the same thing. The former may happen because of market forces, the latter is obviously because of government force.
It should be obvious given that a person has one vote.
Basically just live below your means.
But that is going to be hard for most people in tech to do because most people in tech were raised upper middle class and they simply don't know how to live below that and a lot of the rest are not from the US and they're mostly just going to do whatever makes them fit in.
And unless you can get everyone with money to live like they don't (which you can't) that's not actually going to solve anything. Telling everybody to just change their lifestyle is not a real solution to anything anyway.
It solves the problem of contributing to it.
Ultimately, there is nothing an individual can do to help housing affordability. That is a societal problem.
If you really want to help housing equality, buy ana apartment building, not a house, and add more units
And driving demand for luxury condos (or whatever) is better? Then you're giving an incentive for some developer to bulldoze the cheap "blighted" homes and apartments to make more luxury condos or overpriced new townhouses, or whatever.
There's no winning here.
No you're not. If you buy a luxury condo, you have reduced demand for luxury condos, since there's one less individual who both wants and can afford a luxury condo. If they build enough luxury condos as people who can afford them, then eventually it's no longer profitable to build luxury condos, and they'll have to concentrate elsewhere. However, the false restriction of the market enabled by policies such as 'neighborhood preservation' and lack of funding for rapid public transit means that development companies can basically make their entire year's profit only meeting the demand of the rich.
(Also, every new development is going to be branded as a 'luxury condo'. No one sells a 'boring old condo', ever).
> There's no winning here.
Yup. If you define 'winning' as 'I don't want my purchase of something to affect the price of similar things', then certainly, you cannot win.
This is true everywhere. Builders are not going to build cheap houses. My wife and I were looking for a house three years ago. At the time, it was only three of us - including my 15 year old step son. We were looking at buying in a county in the Atlanta burbs. We had two choices - old small houses being sold by the relatively few people who lived their or buy in one of the many neighborhoods where builders were building new houses. We purposefully chose the cheapest, smallest floor plan offered by the builder - and even that was over 3000 square feet, five bedroom. I’m not trying to humble brag. It was less than 330K all in and we only needed 5% down. Any software developer with 5-7 years of experience could easily afford it - especially a dual income couple.
You could just... decide not be in the market, despite being able to afford it. Market price is defined by what people are willing to pay for and sell for. If you are not willing to pay anything for a luxury condo, that reduces the price for everyone by making it less scarce.
You don't have to buy all the luxury condos in existence to eliminate the market. If people decide not to buy them, there is no demand, by definition.
Luxury condos lose their luster, and then become just regular condos. Regulars become cheap. It's effectively entropy. Also, people that can afford to live in a luxury home, don't want to live in a meh, or even crappy home. Yet, if they can't get a luxury home, they settle the meh one. Since they can pay luxury prices, the meh one becomes more expensive, and the less well off get frozen out, because they can't compete.
If you build at the high end, or more accurately "market rate", not only can developers recoup the cost of construction, but you're also taking pressure off the meh and crappy houses, because the people that can afford luxury prices, take the nice home. Also, those currently live in what was considered "nice", upgrade to the new luxury home, because they're now in downscale, thus freeing that house and and lower the prices.
https://ggwash.org/view/68496/why-are-developers-only-buildi...
Before jumping into the tech industry, I worked in the automotive industry and spent a lot of time around engineers. They were mostly all over 40 and they mostly all fit the stereotype of the frugal engineer. I don't see too many of those engineers in the Bay Area.
The URL has 5/2 in it which appears to be a date.