If the Programmer Won't Go To Silicon Valley, Should SV Go To the Programmer?

theodp writes: "If 95% of great programmers aren't in the U.S.," Matt Mullenweg advises in How Paul Graham Is Wrong (a rejoinder to Graham's Let the Other 95% of Great Programmers In), "and an even higher percentage not in the Bay Area, set up your company to take advantage of that fact as a strength, not a weakness. Use WordPress and P2, use Slack, use G+ Hangouts, use Skype, use any of the amazing technology that allows us to collaborate as effectively online as previous generations of company did offline. Let people live someplace remarkable instead of paying $2,800 a month for a mediocre one bedroom rental in San Francisco. Or don't, and let companies like Automattic and Github hire the best and brightest and let them live and work wherever they like." Microsoft and Google — which hawk the very tools to facilitate remote work that Mullenweg cites — have shuttered remote offices filled with top talent even as they cry the talent sky is falling. So, is "being stubborn on keeping a company culture that requires people to be physically co-located," as Mullenweg puts it, a big part of tech's 'talent shortage' problem?" Chris Pepper also recently posted another reasoned rebuttal to Graham's post.

Comments

Exactly this.

[fyngyrz]

Also, stop being anal about degrees, credit scores, old convictions, age, and health.

There's no programmer shortage. That's utter BS.

There's just a hiring pathology.

Re: Exactly this.

[Anonymous Coward]

If these companies were hiring a cook they would require 3 years experience working on an Ace cooktop, 5-years experience with Acme Food Supply, and be able to demonstrate the restaurant's recipe for their signature meat dish before being considered.

Companies didn't come into existence with their particular toolsets: they learned them, and quickly. Then they refuse to consider hiring anyone who doesn't already know them in depth.

Re: Exactly this.

[m00sh]

If these companies were hiring a cook they would require 3 years experience working on an Ace cooktop, 5-years experience with Acme Food Supply, and be able to demonstrate the restaurant's recipe for their signature meat dish before being considered.

Companies didn't come into existence with their particular toolsets: they learned them, and quickly. Then they refuse to consider hiring anyone who doesn't already know them in depth.

I've seen certain fortune 500 companies advertise software engineering job positions that do not require any experience, do not list any requirements (except high school) and job description is as vague and all-encompassing as desire and ability to write software. That does not make getting that position easier to get.

The biggest unwritten requirement is if you'd want to spend and interact 40+ hours a week with that person. That is why most women programmers no matter how inexperienced will always get hired very easily. Programming ability matters very little when the guy is a weirdo and awkward to deal with.

Not that I'm implying you're a weird or anything, but when a guy walks in the door, people fear for the worst. Until you get to know someone, guys think other guys are creepy or bad. Thus, it is very easy to get a friend hired in your company but if a friend doesn't want to give you the recommendation in his company, that probably means your friend doesn't like you and wouldn't care to work with you.

Despite what Slashdot and their parent Dice would like you to believe, job hunting is largely done through connections. If you are reading job requirements and fuming over not enough experience and what not, you're probably exhausted your contacts. Employers also fear the worst of the applicants coming through random job searchers and will scrutinize them more than if they came through connections.

It is blatantly false that companies will not consider hiring anyone who already doesn't know the tool in depth. The biggest tool to learn is the company software repo, the business and culture of the company which is the least documented. Any commercial tool can be learned in weeks or months since there are thousands of resources on it. Learning the company source code base and all the ways the company works is the hardest part.

My psychology book said that in most cases people make up their minds unconsciously and then go find reasons to justify it. I read somewhere (and it could be completely false) that an interviewer decides to offer a job or not very quickly and spends the rest of the time confirming it. I have found that it's the weird things that get people hired. If they were in the same fraternity, attended the same university or some other commonality. I hate to say it but if a team leader is Chinese, you will find that a lot of junior Chinese developers and this is because ethnicity is a super-obvious observation. Sometimes, entire teams have hidden commonality like an fraternity, an ex-employer or a university.

Anyway, I've been turned away from many jobs that I was qualified for and had the technical skills for. But, if I want to land that job right after an interview, I have to have connections or be a super-charming person. Everyone thinks they are geniuses in their own right but others think differently. The most qualified candidate isn't the one who always gets hired. In the end, in software development, it is the team effort than the individual that matters.

Physical security as information security layer

[tepples]

I can think of a few reasons why some software development companies oppose telecommuting.

Sometimes, an air gap can be the most effective form of information security. By 1985, Atari was already adding electronically locked doors; see posts about "building access" in Jed Margolin's inter-office memos from 1985. And for years, Nintendo required that authorized game developers operate out of a "secure office facility", explicitly excluding a home office. (Source: WarioWorld.com, the home of Nintendo's software development support group) This caused a bit of drama when Nintendo refused to sell a DS devkit to Robert Pelloni's home-based studio and Pelloni ran to the news media. (Nintendo relaxed this a bit in 2011, possibly to meet a threat of competition from iOS, Android, and OUYA.)

In addition, a lot of people still live in areas where affordable, reliable, high-speed, low-latency Internet access needed for telecommuting is unavailable.

Finally, the dynamics of interrupting another team member for a quick answer to a quick question differ between working in person and working remotely.

Re:They want you there...

[BarbaraHudson]

No, they want you there because they are incompetent at managing, so they've got to have endless meetings and interrupt you all the time to justify their existence. The whole "management is giving people a task, the tools they need to solve it, and making sure nobody else gets in the way" mentality is GONE.

We complain about "hover parents", but micromanagers (or "hovermanagers) are just as toxic.

No. Reciprocal loyalty is dead.

[tlambert]

No. Reciprocal loyalty is dead.

If you work in SV, you can likely walk away from a tech job you can't stand and have another tech job inside a week. Some people can do it the same day.

If you work in Omaha Nebraska, you can walk away from a tech job you can't stand and have another job inside a week. At Pizza Hut.

There's a huge benefit to the worker to being able to switch loyalties quickly in an industry which is notoriously disloyal to their workers; some people's notification comes in the form of them coming back from a trip and finding that their badge no longer opens the door.

There are also economic factors. First, it's very east to relocate from San Francisco to Omaha, because it's an economic downslope. It's very hard to migrate from Omaha to ... well, anywhere ... because it's an economic upslope. The equity in your house or condo will convert out nicely, going one direction, and will end very poorly going in the other.

Finally, there are the social aspects; I'm not just talking about nightlife, or the bar scene, or sexuality issues, I'm talking about having a group of friends and acquaintances with whom you can maintain face to face contact, who are able to help you out in a job search, which simply doesn't exist, if you're looking for a tech job, but don't live in a tech Mecca. It's just not going to happen. So when your company is disloyal to you (read: let go, RIF'ed, laid off, temporarily cut back, or any of the other euphemisms), there's no reciprocity.

Gone are the days you could move to Southern Utah, go to work for Browning Arms, and write IBM 360 assembly code happily until you hit retirement age, and then collect your pension for the remainder of your life, in happy retirement. Even IBM has moved to a cash-balance pension plan, instead of a fully funded pension plan. Jobs for life are a thing of the past. And relocation, when it happens, is generally a long term thing. IF jobs don't last as long as the relocation does, and there are no alternatives: no thank you.