Almost nothing about the climate (I like winter) or culture appeals to me, yet I'm pulled towards there to succeed in a tech career. This is simply network effects in action, except that unfortunately this network has been built in one of the locales in the US with some of the most aggressively anti-growth policies possible. Things would be much better if tech was centered around somewhere like Chicago or even New York.
That is, would a guy like me (or you) be able to pull in multi-six-figures a year to telecommute to the Bay Area from out in the sticks if there weren't so many poor souls physically there keeping rates up for the rest of us?
What would things look like if the tech hub were in Ft. Worth TX instead (or Scott's Bluff, Nebraska), with hundreds of miles of flat empty cheap land in all directions to keep housing prices down near zero.
Even the tech hub was not on a peninsula, you'd still have an expensive center and poor people would have to suffer a long commute like East Bay people do in the Bay Area.
Just look at London or Paris: it's not cheap despite not having the same geographical problem. It's not as expensive as the Bay Area because there are many people with various jobs, not just highly paid tech workers.
Good governance matters. It makes a huge difference in cost-of-living. The way SF is run, it's almost as though people want the cost-of-living to be as high as possible.
Surely you're joking? Of course that's what they want. SF people, home owners, are voting on SF policy. Do you want to lose half the value of your house?
Its more complex than that, as SF people voting on policy also include renters, and even if rent control insulates them from directly paying for price increases, market price declines save them money (and both increases and declines affect local costs of other goods, so they affect CoL even if they don't directly affect existing renters rent payments.) But, renters are largely people who have decided the trade-off of quality for cost at the current price does make sense, so they are less likely than outsiders who might want to move to SF if it was more affordable to make trade-offs that impact the qualities that they prefer in SF for lower prices, even if it would reduce their cost of living.
For example, you can get to midtown manhattan in half an hour on NJTransit from East Orange, NJ, a very cheap place to live. The NYC metro area is chock full of affordable neighborhoods where the tradeoff is merely having a commute, not a LOOONG commute.
Ideally, you have your infrastructure scale as the city grows, to maintain constant commute times for workers even as they move further out.
In most other developed countries, developer salaries are about the same as physical engineering salaries and other highly skilled jobs.
Hasn't helped Austin
I can assure you that housing prices in that area are not near zero, even with all that land that is not necessarily available for development.
Salaries are a function of supply and demand. In that way, it wouldn't matter if the companies are in SV or in Kansas: they're still shooting themselves in the foot. Every company wants to hire the best, the top 10% of developers, when in actuality they probably only need to avoid the bottom 25% (assuming tech talent follows a bell curve). By setting up the ridiculous filters to hiring, they're artificially limiting the supply of developers on the market by 65%. In doing so, they keep the salaries of developers artificially high.
> As a west coaster, I can't stand Chicago or New York. The weather sucks, the topology is boring, the people are either boring Midwesterners, or crass north easterners. I'm happy the west coast gets more play, though I would probably not want to live in SF.
While the stereotypes exist for a reason (and anybody who's lived in NYC or Chi-town testify to these particular ones), have to disagree with you on the being able to put up with "those" people. It's the west coast that is the outlier here as a (stereotypical) bunch of pansies who can't (again stereotypically) deal with rawness of reality.
There is nothing wrong with the other areas of the US, and Americans are mostly the same, but I find the laid back style of the left west coast just to be the most suited. Well, Californians can take that a bit too far...
My problem is that a lot of people seem to be pretending that the only reason there's so much demand for housing in California is due to the favorable weather/people, when in reality a huge proportion of the people there wouldn't be there if it weren't economically beneficial.
It is nice that the economics and the nice weather coincide. It probably isn't a coincidence either, as tech is primarily limited by human resources.
I promise it is very possible to have a successful career in technology without being anywhere close to California.
That's neither pedantic, nor a correction. That's exactly what I've been saying all along. Career success isn't a 0/1 boolean, and no matter how successful someone currently is, there's always the potential for even greater career success. Optimizing for career success includes optimizing your chances for career progression.
Semantics aside, I think we're in agreement.
At least it keeps the area where I live free of that sort of toxic culture!
In particular, outside of SV it's substantially harder to:
1) Break into the top ranks of tech compensation. The companies and roles paying >200k/yr are heavily concentrated in SV.
2) Found a successful startup. The concentration of capital and connections in SV remains unparalleled elsewhere.
I don't think it's really that different from finance. You can have find finance jobs throughout the country and you can even build a successful career in most places. But if you want to succeed at the highest level, you'd be well-advised to move to NYC.
> 2) Found a successful startup. The concentration of capital and connections in SV remains unparalleled elsewhere.
From my perspective, your definition of a "successful software career" is rather narrow. Where else can you make 6-figures your whole life and be considered a failure?
Like I said, it's perfectly possible to have a nominally successful career in software elsewhere. It's just that if you want to reach even higher levels of success in software, you're encouraged to move to SV.
I'll take the 130k.
Do you have receipts for this claim?
I suspect the vast majority of cleaning ladies in SF don't make $70k either.
The absence of a table makes it hard to tell what the absolute order is, but Missouri, Iowa, Oklahoma, South Carolina, and Ohio also come out ahead of Nebraska, putting it at least at 11th.
So this economics that balances out the part of life you mention, is reduced since people are less mobile due to medical insurance.
If medical insurance was provided by the state (like in most other countries), you would see more people moving where it would be more efficient for them (and the economy) to work.
In any case, I'm not sure the conclusion follows. We see exactly the same pattern in the UK, where healthcare is almost entirely public. What the calculation fails to take into account, IMO, are other factors – someone who has lived in a location for a long time may be skeptical of moving, simply because they have roots (homes, friends, family, social groups etc.) and disrupting that is hard.
Not only that, if you move in the states you will want a job already lined up. If you build up a bunch of savings and then move to find a new job you won't be covered and so it's more of a risk.
Most other countries, it's not even considered a factor.
And so what if it is on my list? Taking it off removes so little friction that it is effectively irrelevant.
It's pretty expensive though, I'm not sure a lot of people would leave a job that included healthcare as a benefit to move to another area and look for a job.
Yes, this is still an example of economics explaining stuff.
A flat annual fee, as suggested by Proudhon, would be much more fair. I do not mean a "flat tax", which actually scales linearly with income, but a flat dollar amount.
The federal government could replace all of its taxes, all of them (income, corporate, capital gain, etc) with a simple $500 a month per person payment.
This would also make a lot of people reconsider their voting priorities. Let's see how likely they'd be to support trillion dollar wars.
Also, things like property tax have the same effect -- can't get away from taxes even if you have no other expenses. Property tax can be jettisoned by selling your property, but then where are you going to live? You'd need to generate taxable income to rent someone else's property.
Or is a head tax meant to apply to "households" (in the census sense) rather than to individuals? Or, alternately, is the breadwinner of a household meant to pay the head-tax for all their dependents?
It requires no more bookkeeping or accounting beyond that which is already required by the census.
It would apportion federal taxes to the states in proportion to their populations, as required in the Constitution prior to the income tax amendment. This could potentially reduce the number of taxing authorities any given individual would be exposed to. Your state might pay the federal capitation, but might raise the funds for it via other methods of taxation rather than its own head tax.
It reinforces the idea of equality before the law.
It encourages pursuit of additional income. You are more likely to do additional work for an extra $500 if you then get to spend all $500 of it, rather than just 75% of that.
The government is encouraged to promote increased birth rates and immigration as a means of increasing its revenue.
But the number one argument both for and against against head taxes, depending on who you are, is that it creates an inherent de facto limit on government spending, based on what the lower class can afford to pay. If there are people who simply cannot pay more than $500 a month, you cannot raise more than $500 x population via the capitation. So you can't spend more than that without resorting to other sources of revenue.
* It requires no more bookkeeping or accounting beyond that which is already required by the census.
That bookkeeping while annoying is extremely profitable, every additional dollar added to the IRS budget results in 4 dollars of revenue[0]. Simply put from a governmental perspective it's highly cost effective. While a head tax might be cheaper directly to implement, it has other costs that aren't considered that I will get into below.
* It would apportion federal taxes to the states in proportion to their populations, as required in the Constitution prior to the income tax amendment. This could potentially reduce the number of taxing authorities any given individual would be exposed to. Your state might pay the federal capitation, but might raise the funds for it via other methods of taxation rather than its own head tax.
I concede this point, but this more of a solution looking for a problem than anything. Moving money into different accounts is pretty much a solved problem.
* It reinforces the idea of equality before the law.
A flat percentage after a single deduction related to the cost of living would be equality (a man should not be taxed before he feeds himself in my opinion), the myth that the CEO and board actually created the billions of dollars that his corporation captured (because he worked a few hundred times harder then the guy pulling 12 hour shifts on the factory floor) is old and tired. It was his employees that did so as well, and taxing them at a far greater percentage (79.58% on minimum wage to be exact) than him is not equality. It's theft.
* It encourages pursuit of additional income. You are more likely to do additional work for an extra $500 if you then get to spend all $500 of it, rather than just 75% of that.
Firstly, Where is this a problem? On the one side of the spectrum we have the poor working 3 jobs to pay rent (whom you propose to more than quadruple the tax burden on, thus all but stopping the velocity of capitol and probably destroying the economy[1]) whom need to earn as much as they possibly can just to get by. On the other side the wealthy/upper middle class is generally obsessed with status symbols. That won't change if you tax them at 4,40, or 91% (see 1953 - 1961). They will still want to buy the newest Tesla, send their kids to whatever expensive school and go on exotic vacations as long as their neighbors do. Hell, in bad times many of them finance it up until bankruptcy to keep up appearances (see 2008 - 2010). The data is clear, they will continue to work and spend as they always have.
Secondly, Not once has someone gone, "Yeah I'd take that 10 million, but I'd have to pay 2.5 in taxes, so burdensome, forget it" and even if they did, someone else will step up and fill the void if a market exists. On the other hand if you tax a minimum wage employee at 80% why the hell would you even bother going to work? You are homeless and hungry either way, what will the few dollars you earn for 8 hours of work get you? Might as well sit in the park and panhandle, it's more profitable.
* The government is encouraged to promote increased birth rates and immigration as a means of increasing its revenue.
They aren't now? I see plenty of tax benefits for having children. More people, more consumption, more incomes, more revenue. The only difference here is the government has no incentive to raise the average rate of pay of Americans. Why educate them so they can get better jobs? Why worry about the state of the economy? They pay $1000/month anyway. A percentage doesn't have this problem.
* But the number one argument both for and against against head taxes, depending on who you are, is that it creates an inherent de facto limit on government spending, based on what the lower class can afford to pay. If there are people who simply cannot pay more than $500 a month, you cannot raise more than $500 x population via the capitation. So you can't spend more than that without resorting to other sources of revenue.
Firstly, why can't the government just take out debt like it does currently. This plan does nothing to prevent that and a proposal to do so can be applied to any tax plan (IE, constitutionally prohibit the government from taking new debt).
Secondly, I'd argue that the working poor can't afford the current levels of taxation. Raising it to above 60% for the working poor and below 1% for the wealthy is not a solution to that problem. In fact, the entire reason for the 2nd amendment is to prevent something like that from happening. If anyone seriously purposed this change there would be riots in the streets. If it passed, many would die before it was repealed or the government overthrown entirely. This is the nation that started a war with the greatest military power on earth at the time over a 3% tax on a single non-essential good, you'd be wise to not forget that. The rural poor certainly haven't.
So in conclusion, the people advocating this wish to lower their taxes at the expense of others and use justifications that make little sense in order to attempt to do so.
[0]http://www.cbpp.org/research/federal-tax/irs-funding-cuts-co... [1]https://www.imf.org/external/pubs/cat/longres.aspx?sk=42986....
I would assume (and always question assumptions) that tax revenues would be nonzero if IRS funding were zero. Some people will just voluntarily pay their taxes out of a sense of civic duty. Then, for the first dollar spent on the IRS, that will return some multiple of that dollar. I assume there are diminishing returns:
Revenue = integral( f(IRS_budget), 0, IRS_budget ) + C
f(1) > 4
f(current_IRS_budget + 1) = 4
f(current_IRS_budget + 2) < 4
That means that Congress decided to just stop funding the IRS at some point. In a sane business, this might be because all other projects return more than $4 for each additional dollar spent, and the revenues cannot immediately be used for additional spending. If there were no such restriction, all projects could be brainlessly funded to the point where only $0.99 in revenue is realized from an additional $1 in budget.The head tax simply has a different function: Revenue = integral( g(IRS_budget), 0, IRS_budget ) + D
We don't know what the shape of that function might be, only that there is a hard upper limit on revenue equal to the capitation * population.
--
You're confusing equality with fairness. A capitation would be equal. A fixed percentage after deduction would be fairer. I might argue that a different tax equation would be even fairer than that. But government is not, and never will be, fair. The minimum amount of fairness we should tolerate is equality.
--
You are missing the point about incentives for extra work. An extra $10M is so far beyond the scenario I had in mind that you might as well be talking about trade routes in the Tau Ceti system.
In the real world, at the very bottom, payroll taxes are very significant, as they are a regressive tax. Means testing on subsidy programs also play a role. So some people face a choice such that if they work harder, they actually get less disposable income. If you get $200 (gross) a week from working 20-30 hours part time at the supermarket, and you get WIC and/or SNAP benefits, due to your poverty, you are still paying $12.40 plus unemployment tax, even with no income tax withholding, for $187.60 net. If you become full time, working 40 h/wk at $7.35/h, you lose your SNAP benefit. And you are now paying $18.20 in payroll taxes per week. You now have $275.45/wk to spend. If your SNAP benefit was more than $87.85, you are doing more work for less disposable income. The average SNAP benefit is $127/person.
Accounting wise, the loss of subsidy is roughly equivalent to an additional tax on the extra earned income. If the only tax/subsidy were a capitation, no one would ever refuse promotion from part time to full time and a raise from $7.25/hr to $7.35/hr out of fear that they would end up with less to spend. (Again, not necessarily a fair way to encourage additional work.)
--
The government's ability to borrow and run the money-printing presses is orthogonal to discussion on forms of taxation.
--
I am not advocating a head tax. I am simply stating possible arguments in its favor, playing the devil's advocate. It is pretty much the exact opposite of guaranteed basic income, which I think would be more favorable. But a capitation is not an unmitigated negative. It does have its good points, which have to be compared with other systems. You said you couldn't think of any positives about it, so I gave you some to consider. I am not extremely motivated to defend any of those points, but I hope you will concede that they do exist.
Even back in eras when slavery and serfdom weren't widely seen as immoral, attempts at universal head taxes tended to cause riots.