Because the downtown area is in the flight path to nearby Mineta San Jose International Airport, there is a height limit for buildings in the downtown area, which is under the final approach corridor to the airport. The height limit is dictated by local ordinances, driven by the distance from the runway and a slope defined by Federal Aviation Administration regulations. Core downtown buildings are limited to approximately 300 feet (91 m) but can get taller farther from the airport.[80]
The rest of the article did a good job of arguing that housing prices harm migration and contribute to income inequality. But twisting a fact like that makes me suspicious. Hopefully fault lies with Matt Yglesias, not the author.
Yglesias' style is generally this kind of slapdash big-claim making sensationalism. He's basically an opinion writer who cherry picks a few facts to try to support his hypotheses. For example, see the reviews of the book mentioned in the article on amazon: http://www.amazon.com/The-Rent-Too-Damn-High-ebook/dp/B0078X...
To be fair to him though, its a hard line to walk when you are discussing the kind of complex open-ended issues which he does. I think his writing has done good to stir up thinking and provoke responses on some of the issues he discusses.
> For example, see the reviews of the book mentioned in the article on amazon
He got lots of bad reviews because he pissed off some right-wing folks who showed up in droves to write bad reviews about the book out of spite, not because they'd actually read it or thought about it:
The subject of his competence came up (not by me) and as someone familiar with his writings I attempt to contribute both my own view (based on a good understanding of his work and not one sided) and a link to others views. I'm not sure what in this is wrong.... I can see you like the guy - perhaps you'd like to explain why?
I just pointed out that the bad reviews were not there because a lot of people disliked his book after reading it and considering what he had to say, but because a lot of people were angry at him and found that writing nasty reviews was a good way of venting their rage.
Can you explain how you think it is twisted? It doesn't seem to me that 'why' matters in this case - the article didn't seem to say 'San Jose has introduced zoning limits in an attempt to price out poor people', but 'San Jose has restrictive building limits that price out poor people because they are unable to meet demand'. You could perhaps add a little detail by changing it to say 'the city doesn't have any buildings with more than 27 stories' but that doesn't really feel like a big difference to me.
I have not read the Washington Monthly much in many years. When I did, it seemed to me that they had a bad habit of picking one one aspect of a situation, explaining everything by it, and wrapping it all up with a QED at the end of five pages. It made for very satisfying reading, but eventually doubts would set in.
I've worked remotely for big American companies like Motorola (I live in Sweden) and continue to work from home for local Swedish companies. Almost all the people I interface with are in various offices in various timezones around the world anyway.
I also do game programming jams e.g. Ludum Dare over a weekend occasionally, and these are also distributed remote efforts. Yet we manage to work at a furious pace with the same immediacy and accessibility as if we were sitting in the same room.
It works well. It works well for me, and I believe it can be made to work well in general.
This is not just about IT type jobs; most office-work can be done remotely. Only people actually manipulating machinery directly need to be in physical contact with their machine.
But there is a definite distrust and dislike of it, especially among management types.
The biggest problem is that there's no gradual migration process. The first remote worker on a team forces everyone to change how they work and communicate. Even with the whole team accommodating the remote person, they'll still miss out on a lot. It can be frustrating for both sides.
Also, the software for real-time collaboration sucks. Even if you constantly screen-share and video chat, it's not as good as working in the same room. Simple things like pointing at a section of code are difficult to do, and synchronizing files can be a pain.
I'm working on solving this (Floobits YC S13 yadda yadda), but there's still much to be done.
One small startup I helped out briefly many years ago was using Linux/KDE. They had it set up so that everyone's desktop was accessible from everyone else's desktop. In Linux you usually have several desktops which are easy to switch between, and they made it so that everyone else's desktops appeared in your desktop list. There are virtual desktop products for windows too.
I don't know if they used standard software for this, or whether it was their own cobbled-together scripts with normal screen-sharing apps like vnc. I was not involved in setting it up. But it worked very well.
I recall discussing using mosix (that's how old it was) too, so we were a big beowulf cluster for compiles etc. That appealed to them, but I don't know if it was acted on after I moved on.
In this particular case it wasn't about monitoring, this was about collaboration. But you can see how such a system would appeal to managers too.
This complete lack of privacy took some getting used to, but it was super focusing. It quickly sunk in that everything you did (on your screen) was visible to everyone else, and whilst there was toleration for reading the news and so on, everyone was self-censoring themselves to apply themselves.
This was in an open-plan office, but with modern bandwidth could work well remotely.
The biggest problem is that there's no gradual migration process
I'm not convinced this is true: the biggest problem seems to be the way knowledge spills over from person to person when they're in close proximity to each other, and the way new ideas often appear from serendipitous encounters. Popular books like Steven Berlin Johnson's Where Good Ideas Come From and Edward Glaeser's The Triumph of the City discuss the issue in greater detail and cite much of the original research on this phenomenon.
Some of that original research attempts to measure knowledge transfers by proxy, like the way patents tend to cite other patents whose authors live nearby. It's not perfect but it is pretty compelling. Other research relies on descriptions of famous people describing how chance encounters fertilized their ideas.
I'm working on solving this (Floobits YC S13 yadda yadda), but there's still much to be done.
Very cool. If you haven't read Johnson's book in particular you should!
There may not be a full migration path but I would say the first thing that needs to change (and still hasn't happened in many companies) is getting everyone:
* To use shared sources for things (company/department wide Wikis, bug-trackers etc) instead of c:/my_docs/spec.v1.docx being mailed about.
* Reduce the number of meetings (Which, in my experience, are usually unnecessary in a software-dev environment at least)
Obviously some roles are going to be less amenable to Remote working but without the above 2 (or even the first bit) done most companies couldn't even do it if they wanted.
> The biggest problem is that there's no gradual migration process.
Sure there is. The process is similar to all the WinXP to Linux migrations going on. The intermediary step to OS migration is cross-platform applications. The intermediary step to remoting is to phase out everything that is based on paper or face to face communication.
Based on my experiences with heavily collaborative remote work, the gains are tremendous. Local efforts do not scale when when you get an influx of people. Remote processes do. And even for locals, the remote tech works better and faster than the old methods. (Of course a group of locals still get a bonus to communication and are often more productive than a bunch of individual remotes.)
The answer is not screen-sharing, it's making everything an API. The remote worker is responsible for her API, and no one needs to know or care how it works as long as it does.
While I generally do favor service oriented architectures (and remote work), this is woefully short sighted.
Say the remote worker builds you a shaky RoR+MongoDB app, no scalability, no error handling, no tests, no comments. At least in the short run, it works - there are occasional outages, but the worker (remote or otherwise) does a great job keeping it going. Then the remote worker quits. What do you do?
Just because something is behind an API doesn't mean you don't have to worry about knowledge transfer, code quality, etc.
Okay, good points ;-) I may have overstated my case for emphasis; but I maintain that in general, an API is better than a library (there was an article saying just that some time ago on HN; can't seem to find it right now).
I wouldn't even go that far. "API" and "Library" are not distinct concepts. A library has an API - it's the set of public functions (ideally rarely changing) that you are supposed to call from external programs. It is beneficial if one developer can hide their work behind a simple interface with only a few access points (the API), but there is no compelling reason this should be json over http.
The real distinction between a network API and a library is that the network API allows users to avoid thinking about the hardware. The API provider is responsible for allocating hardware, the user need only send messages over the network to use it. I.e., buying hard drives is Amazon's problem, I just GET/PUT my files onto S3.
If the API isn't hardware intensive, this is pointless - you are adding network overhead (i.e., latency, network errors) for nothing.
That just opens another can of worms. Now every single application you either provide or use come with an integration issue attached.
I have read somewhere that was the Amazon way of doing thing but it was a costly investment. A costly technological investment. And even Amazon did it only at team level, not individual level.
I cannot imagine a 500 developers company being able to afford that without some serious competitive advantages down the line. If what I can see around here is any indication (medium size IT company in London), if you can afford not having people on site, there are better opportunities to take in Poland or even India than a small discount on a UK worker.
Unfortunately, a network API letting you mix and match languages still opens up risk from a rogue employee who uses something different than the status quo and then quits, leaving something unfamiliar that needs to be maintained.
What a demoralising (and grossly incorrect) way to look at work.
If your work can be reduced to such an API, then I'd argue that you can be replaced with a script. Most jobs, however, even today, are far more complex than that. As a very obvious example, culture is an extremely important aspect of building a successful business, and a person's contribution to culture is irreducibly complex and unmeasurable, and untameable to stating an API type contract.
I meant the remote worker builds and maintains an API, not that he himself is an API.
> culture is an extremely important aspect of building a successful business
Yes, maybe; but there are many businesses that are already built and that would benefit from treating some parts of their process as self-enclosed APIs.
I would go so far as saying many already do, without knowing it.
That only works if you can separate responsibility out to the extent that each person is responsible for a specific area of the code and works only on their designated area.
What happens in practise is that a feature or bugfix might require a large change to one part of the code and a much smaller change in another.
So the developer tasked with the small change will finish before the other. Now you have an idle developer and an overloaded developer holding the process up. If you have a process whereby the idle developer can't share some of the workload of the other you are going to have very inefficient development.
You also run into problems if one developer is on holiday , off sick or leaves the company since nobody else has ever looked at their code.
There's also a risk of bringing politics into re-factoring decisions. "This functionality should be part of your API".
I've just started using floobits, I work remotely with people all over the place(and they all use sublime) so it's a fantastic product for me. One thing I haven't got my head around is the workflow involving git. Have you guys put any thoughts down about this?
We use Floobits to develop Floobits, so we feel your pain.
If one person commits and pushes, others in the same workspace have to stash, pull, and stash pop. That doesn't always work, since people might edit files in the workspace during the stash/pull/pop. It also doesn't solve the problem of people being on different branches.
We're planning on making our plugins and tools more git-aware. Syncing much of .git would help things quite a bit. We're also toying with the idea of making each workspace a git repo, but that's farther off.
I see there's a git-core feature request open for multiple authors[1]. Would be awesome if floobits could include all of the workspace authors (gazing into the future here...).
It makes it easier for managers to work with people in open offices. They can keep a passive ear open for other people's status and possibly change design decisions as it happens.
Remotely, a lot of potential communication gets dropped and you have to do a lot of active effort to get status and so on. It's basically more work to manage remote workers. Just like its more work to have your team spread throughout a building or on another floor.
There is also the micro-management aspect of it, where they can shoulder surf and make sure people are only doing work activities. Some people probably get some sort of emotional satisfaction in telling people what to do in person too.
Timezones can be annoying for communication. Anybody who has to do 8pm india/china meetings can tell you that.
I have yet to crack the code in motivating myself in a remote-work setting, despite working as a programmer and despite my best intentions. For those whom it works, great, but that... let's call it skepticism instead of distrust -- that skepticism isn't wholly unfounded.
How is a construction worker or teacher supposed to remote work? The problem is not that people like us can't afford to move, but that the average employee in normal other work roles cant. Sweden is much better at this, but I think even there I didn't meet anyone who telecommuted who wasn't in the tech industry.
All over the world people really do do remote learning, even at primary school level.
Another fun thing you see in Sweden is prefabricated houses. In England, prefabs have a horrid reputation from the war years, but modern Swedish houses and flats are assembled from large prefabricated sections that arrive on a lorry and are assembled in just a day or two.
Remote learning for primary school requires a significant amount of time on the part of the parent, and lots of communal time for the children so that they develop adequate social skills.
Prefab has been a force particularly in commercial and industrial construction in the US for some time. My company has done a lot of work in the design and construction of standardized/commoditized hospital rooms, for example. It makes construction like an exercise in Legos :-)
If your healthcare is tied to your job in the USA, wouldn't that impede social mobility? If you can't change jobs because you would lose cover, how are you meant to move around?
Your new job usually offers healthcare to replace your old. True, the coverage can be different - sometimes greatly so. It’s one of the factors you take into account when deciding to change jobs.
But you still can't move without having a new job lined up in the new place then. As someone who has recently moved to a new place by getting a remote job offer first, I'll tell you that it's a heck of a lot harder than getting a job in person.
Not saying it's not possible to move somewhere sight unseen and without health insurance (since that's presumably what older generations did) but it's still much higher risk than staying put.
That's true, but isn't COBRA extremely expensive though? Of course there are ways to lower relocation risks, but many involve having a fair amount of money saved up. The people the article is talking about don't have money whatsoever (which is the point of moving to places with higher paying jobs and opportunities).
But if you have a preexisting condition, you could be denied you're new job because of it. This creates an environment where the best worker for the job isn't doing it, leading to market inefficiencies.
I've really struggled to understand why people will stay living in a certain area, unemployed, for years and years. Whether it's in a rustbelt city where the factories have shut down 20 years ago or a rural city where the only jobs are at Walmart or McDonalds, if you give people unemployment pay, they won't move.
I hear all the excuses for them not moving. It's too expensive, they'll uproot their families, etc. Do you think our grandparents didn't have those problems when they moved from the south to the rust belt to take those long-gone factory jobs?
It used to be people moved to where the jobs were. Now they are content to stay where the checks come.
Maybe now that the early phases of globalisation have settled down and all the frontiers have dried up, the global culture of movement has died down. It's a lot harder to think of moving as a possibility, let alone a good possibility, when it isn't part of the zeitgeist. People used to do it a lot in the 1800s especially, and it was something you could get swept along in - and there was an excitement of going to a fresh place where most people were new as well, economic opportunities and social relations were still up in the air.
Now you can trade a grind in one settled area for a slightly more profitable grind in another. With the tradeoff of losing contact with your whole social milieu and having to start a lot of things from scratch in the new place, while you're surrounded by people who have a lot more than you because they've been grinding in that place for years.
Not appealing, so it's no surprise that it's mainly the highly-educated who can a) seek high value economic opportunities and b) are guaranteed a welcoming social reception from university or work colleagues :)
People like us should be more generous about the incentives governing the lives of the new post-mobility local cultures.
My parents and I came to the US in 1981 and landed in Philadelphia. Over the next 32 years, my parents moved roughly every 9 years across state lines.
The mobility which my parents enjoyed was really tied to a reasonable cost of housing across the places they lived and a stable job market. My Dad generally could stay in one company for 9 years without moving. And he's never experienced a layoff. The one time he came close was due to an acquisition where the acquiring company offered every engineer a full relocation package to move to the midwest OR a 1 year severance to find a new job.
I look at the situation today, and I find the picture to be very different. Many housing markets are largely out of reach, many hiring companies are extremely volatile, and the salary differences across state lines are modest when compared to cost of living differences.
When things are like that, it's hard to justify moving and losing a social circle, uprooting kids, and being farther away from family members.
A construction worker can generally make more money in San Francisco than in suburban Fresno. But it won’t likely be enough more to make up the difference in the relative cost of living. Indeed, few working-class people earn enough money to live anywhere near San Francisco anymore, to the point that there is now a severe shortage of construction workers in the Bay Area.
The wages for construction workers will go up and the situation should correct itself automatically. Unfortunately, it will take some time for people to adjust their cultures so that construction workers are valued more socially - like people who write term sheets.
Isn't a lot of construction work done by poor migrant workers who live in dirty dorms provided by their contracting company? I've seen this in much of the rest of the world, even in places like Sweden where the workers are often from the other side of the Baltic. I'd be surprised if the US was very different in this regard.
Construction workers don't make a lot of money, but they aren't the poor migrant workers living in dirty dorms. They are the working class.
My uncle was doing construction, then just decided to start his own construction business rather than work for someone else, and makes very very good money doing that.
Every year the US Dept of Labor produces the Occupational Outlook Handbook which contains information about occupations in the US. Salaries, number employees, job outlook, etc. These are median salaries.
Then prepare to be surprised, it is nothing like that here in 99.999% of cases. The average american construction worker lives in a house or apartment comparable to any other working class / middle class person, owns a vehicle, etc.
In the American Southwest, much of the construction and landscaping work, especially odd jobs, is done by immigrants, usually from Latin America.
Historically, construction has been seen as a union job, and that's probably still true in certain parts of the U.S. and in certain specializations.
As far as housing arrangements, I'm not positive, but I do believe immigrants tend to pack in more people per square foot of an apartment. I have not heard of dorm-style arrangements run by employers.
People who write term sheets are using trust -- human capital -- accumulated over a 30-50 year career, to raise the funds to be able to deploy them in the first place.
For better or worse, the reason any random person off the street can't raise enough capital to start a bank, VC fund, or other capital-intensive project is lack of trust. Goldman Sachs, Sequoia Capital, etc. have trust; you don't.
I always wonder how its feasible for people in service industry roles to work in the bay area. (Something I think about a lot when I go to work at a cafe).
That being said, it would be interesting to see a graphic of commute time and wage/salary to see the tradeoffs people make.
Good question. The answer I think comes from the fact that "cost of living" is a blunt measure, however it's measured. Price differences vary between by good. Rent might be more expensive, but ipods and levis cost the same.
If you don't pay rent (eg you live with parents), its probably a net win. If you don't consume much housing (eg, 4 person house share), it might still be a net win. Also, some people are more flexible than other in their consumption which is influenced by relative price. So, they might consume less housing by house sharing but more iphones and clothes.
Try figure out if a 22 year old barista living in a trendy city centre with 3 housemates, but a nice nice budget for gadgets and clothes is better off then one in a small town with a completely different lifestyle. Its extremely subjective.
> If you don't pay rent (eg you live with parents), its probably a net win. If you don't consume much housing (eg, 4 person house share), it might still be a net win.
The typical person in the job market has a spouse or children. Having to have multiple roommates on top of that is generally considered a nonstarter.
When you say, "If you don't consume much housing...," you're saying, "If you're single and unattached..." And it's only a net win as long as you stay that way, which isn't usually the case.
To connect the dots the rest of the way, when housing prices shoot through the roof, people with families and special needs get pushed out. What is left are people with fixed housing costs and single people who don't see having many roommates as being a quality of life issue.
I don't think we disagree on much. A family of four that can't comfortably cut back on housing. Their cost of living is even higher in an expensive housing town than the measure suggests because the average also takes into account the single house share people.
Paul Krugman has commented about this phenomenon as well. Based on the literature he says it is due to lack of regional specialization. Interstate goods shipping has also declined. This is mentioned in the article but dismissed.
Personally, having recently conducted an interstate move, I think it is a combination of the lack of specialization (My career as a programmer was going fine elsewhere) and cost of living as mentioned in the article. Moving is expensive, especially when you have an underwater house, and it's hard to leave your social network behind. If you're moving for a raise from $18/hour in Ohio to $25/hour in San Francisco, that's not worth it.
"[W]ithin the United States, at least, people are moving less — a lot less. Greg Kaplan and Sam Schulhofer-Wohl (pdf) say that interstate mobility has been cut in half over the past 20 years. And interestingly, they suggest that this is in part because regions have become more similar: increasingly, different parts of the country are producing the same kinds of things and employing the same kind of people, so that there’s less reason to move.
This story actually matches up with what the new economic geography literature says, which is that regional specialization peaked around a century ago and has been declining since."
> We might similarly observe, “Nobody moves to that state anymore. It offers too much economic opportunity.”
This article rests on the premise that all you need for a higher salary is to live somewhere where salaries are higher. But that is highly questionable -- just because they're higher in general, doesn't mean they'll be higher for you. At no point does the author convincingly explain that American unemployment is a problem of geographical mismatch, instead of the far more likely case of skills mismatch.
> If labor markets were operating efficiently, construction workers, along with electricians, plumbers... would receive enough compensation to live near the places where their work is most needed. But our labor markets are not efficient; rather, they are rigged and skewed, offering too much compensation to people with some skill sets (merging companies and writing derivatives, for example) and not enough to others whose skills are often just as hard to learn (e.g., brick laying and teaching children to read) and often more vital to society.
What? How exactly does the author magically come to the conclusion? As far as I can tell, construction work and plumbing and electrical wiring is all getting done. (Never listen to businessmen complaining about a lack of workers, it's just a masked complaint that they're having to pay higher wages.) What evidence is there that our labor markets are "rigged and skewed"? By whom? It's like the author doesn't understand the basic concepts of supply and demand in a labor market.
It's extremely interesting that Americans are moving less. I'd love to know more of why. But tying it into arguments about career mobility seems highly dubious, at best. It's ridiculous, and almost patronizing, to suppose that people's careers nationwide are being held back by not being able to live in downtown metro areas. It's a big country out there.
> At no point does the author convincingly explain that American unemployment is a problem of geographical mismatch, instead of the far more likely case of skills mismatch.
If it were a case of either of those, it would be visible in the data. Which it isn't. American unemployment - and European unemployment, for that matter - is a result of the class warfare practiced by the rich against the poor in recent years. Paul Krugman suggests Republican policies are responsible for 2% extra unemployment, nationwide:
High unemployment is a result of policies that have artificially suppressed demand for goods and services by taking money out of the hands of people who will actually spend it, resulting in an overall excess supply of labor and low demand for labor and therefore, low wages.
Yeah I think housing markets are much more the problem. I just moved from a dead end place in upstate NY to Denver, CO, seeking the better job market for software developers. I'd have loved to have gone right to the main nerve in SV but the housing prices are just so insane it was beyond my budget.
> "Average earnings in the valley grew by nearly 40 percent between 1997 and 2000"
Taking wage data from the massive tech bubble is some serious cherry picking.
Earlier in the same paragraph:
> "in 2005 the [San Jose] metro area approved permits for only 5,700 new units"
Again, this also cherry picking, as the area was just coming out of one of its biggest busts-- the aftermath of the tech bubble (the number of tech jobs is still not as high as it was in 2000). Although one would never know it from reading the piece.
Ah, yes. Back around 1980, a piece in WM gave an number of hours flown for the USAF during the previous year or so, compared it with hours for some period about 10 years previous, and suggested that the decline was due to the Air Force's appetite for ever more complex and high maintenance airplanes. That the earlier period had been in the middle of the Vietnam War they did not mention.
I think major reason is housing price. If you want to leave local safety net of relatives and friends, you must be able to survive on your own. You must also have savings for first couple of months. Not possible if housing is too expensive compared to salary.
This article seemed strange to me. It started out talking about how mobile people in the U.S. were for moving to where jobs are and then moved to making a case that people don't move to places with high housing costs.
The U.S. is a big place and locations with crazy housing costs are not the norm. I would think that most people moving for a job would already have a job available. I suppose there are plenty of cases where people might move without a job offer in advance because anything would be an improvement.
Maybe today people don't move as often simply because EVERYTHING is getting more expensive while the jobs people could land are staying the same or getting worse. Moving is quite expensive, especially when you don't have a job and especially when you don't have a job lined up at the place you are moving to. Gas is expensive for moving long distances. Getting into a house or an apartment is expensive. How many jobless people have the savings to withstand all this?
It would also be interesting to see more statistics. For example, where were people moving to and from when the rates were the highest? What industries were supporting the places these people moved to? Maybe the decline of jobs that could take just about anyone, in large numbers and paid well (manufacturing) contributed to the decline in mobility. There really isn't anything which could take the place of engineering.
Though people may be less mobile today, the options for that mobility will always be great. The U.S. is a huge nation with a lot of diversity. You can't really compare mobility in a nation like the U.S. with 50 states to a small country like that of Denmark or Sweden.
But in a small country like Denmark or Sweden, citizens there are also citizens of the EU and so can freely live and work in 27 countries with minimal bureaucratic hassle. Language barriers notwithstanding, it makes the EU a lot more like the wide-open market of the USA.
I had an opportunity recently to move to the Bay for a contract position from a fulltime one in LA. Risk/benefit considerations aside, the cost of living, much of it rent, in the Bay stayed my hand from signing off and changing jobs, and I am someone who could afford to live there, I can easily see why anyone who made as much or less would never move from here to there either.
So Douglas county in Colorado grew the fastest, 3600% growth! Indeed, it had a population of about 8000 folks in 1969 & now averages about 300000 => thats your 3600%
Generally speaking, the South is a big winner - GA, TX, FL, AZ...
3139 counties ranked by population growth in my github repo here - http://bit.ly/16RsjWa
Cheap cost of living? I live in Chicago, but the rest of my extended family lives in Tampa, FL. I make $120K/year in Chicago, but due to lower costs of living, only need to make $90K/year in Tampa for the same lifestyle.
I moved from the Bay Area back to Portland to work remotely, so I fit in these statistics. I did it because Portland has a more laid-back focus on quality of life and I'm able to live without a car here.
I know a decent number of people (often with college degrees) who've moved to Arizona because they could afford to get by working at Best Buy or Target or similar, but couldn't at their previous locations in New York, California, and similar.
I think for the average person (who, let's remind, is probably part of a household making $50k or less per year) cost of living (and particularly housing) is what matters more than taxes or wages.
I'm sure that's true for people who for whom that's true, however, that 'study' is very anecdotal itself, and quite ridiculous. It doesn't address where people with low wages live, income distribution, and other complexities. The group I'm referring to is a group who will not have $35k+ left over for house no matter where they live, and is pretty much invisible in that study. If anything the article you linked is showing that higher incomes live in places with higher housing costs and make more after paying for housing also, which is a different conclusion than is claimed by the article.
This was really interesting as an economic look at migration. I moved from LA to Austin because I couldn't stand the city and have loved it here, but one of the things I've loved most is starting from scratch and being forced into meeting new people and doing new things. I've loved it so much that I can't see myself staying in one place for too long until I am ready to have a family.
I love a simple Gladwell-style opinion piece that actually makes me think with a few carefully revealed key facts.
My big takeaway here is that America is not and never has been one country. In Europe we are wringing our hands that the Southern states are too poor and being carried by the richer North, that migration must be controlled lest we depopulate a country and why can't we be more like America who just seems to go from strength to strength
yet, it's not true - all we fear in Europe apparently happens in the US anyway - different areas have different economic cycles, mass migration, vastly different state laws and yet it seems to balance out ...
Oddly I guess Anerica is a small working example of Keynes' International Monetary Fund - perhaps call the Fed a Continental Monetary Reserve.
It also suggests that acting more like a proper country might not be very good for you.
edit: The IMF was originally conceive as a way to balance out economic cycles - countries would pay in in good times, draw down in bad times. It seems however that politicans like the spend in bad times, but happily forget the pay in in good times part.
This article had potential, but its facts are questionable. For example, it claims that "California has been losing native-born residents for two decades."
I read that statement as almost guaranteed for every location on earth. The only way it is not true if no one born there leaves. For a location of any size that would be unexpected.
That's right. You shouldn't leave California just because there's no way to make a living anymore! Verily, if you just stay put, a way to pay taxes again shall be revealed!
Across the HC a couple days or maybe even a week ago. I saw a map posted here that predicted the odds over a colorful map across north america of exactly what you are looking for. just so you know.
I work remotely from Cambodia for companies mostly based in the UK (but also in the US and elsewhere). Lots of startups do not want to hire remotely. I have heard "no" more than once from companies in the Bay Area. However, it has become less of a problem over the last few years, because with every year that goes by, it gets easier to just do your own startup without ever setting foot in the Bay Area. For example, there are amazing opportunities in the Chinese market at the moment, while it does not give any advantage whatsoever to be located in the Bay Area for those.
The city’s tallest building, Yglesias notes, is a mere twenty-two stories high.
Anyone who lives in San Jose can tell you why this is the case. From http://en.wikipedia.org/wiki/San_Jose,_California#Arts_and_a...
Because the downtown area is in the flight path to nearby Mineta San Jose International Airport, there is a height limit for buildings in the downtown area, which is under the final approach corridor to the airport. The height limit is dictated by local ordinances, driven by the distance from the runway and a slope defined by Federal Aviation Administration regulations. Core downtown buildings are limited to approximately 300 feet (91 m) but can get taller farther from the airport.[80]
The rest of the article did a good job of arguing that housing prices harm migration and contribute to income inequality. But twisting a fact like that makes me suspicious. Hopefully fault lies with Matt Yglesias, not the author.