http://www.cis.org/sites/cis.org/files/articles/2005/back130...
H1B presents some friction in switching jobs, but to call it "difficult", especially in current market conditions, is vastly overselling it.
Although the regulations do not provide a grace period for unemployment between H-1B employers, USCIS generally approves petitions to change from one employer to the next and considers you to have maintained status if the gap is 30 days or less. CAVEAT: your (new) employer is the one that has to request the change, so if your new employer isn't organized to do this, or doesn't want to, you're in the country illegally and won't get paid.
So there's a "the administration hates congress" grace period of 30 days. After that, you actually have to leave the country and cannot start work somewhere else.
If companies started paying 2x-3x current rates they would start attracting very senior people who would spend the time necessary to retrain for the positions paying a lot more.
Also, at 2x-3x the rates, some business models would cease to be viable, freeing up the developers working on those businesses to be available for hire by the companies rating in the dough.
We really haven't begun to scratch the surface of trying to fix this problem by being more competitive with salary.
There's a list that US Immigration and Customs Enforcement provides http://en.wikipedia.org/wiki/STEM_fields#STEM-eligible_degre... and it covers "physics, actuarial science, chemistry, biology, mathematics, applied mathematics, statistics, computer science, computational science, psychology, biochemistry, robotics, computer engineering, electrical engineering, electronics, mechanical engineering, industrial engineering, information science, civil engineering, aerospace engineering, chemical engineering, astrophysics, astronomy, optics, nanotechnology, nuclear physics, mathematical biology, operations research, neurobiology, biomechanics, bioinformatics, acoustical engineering, geographic information systems, atmospheric sciences, educational/instructional technology, software engineering, and educational research".
If you wanted the research to sound dramatic, you could then require the S part of STEM to include all of http://en.wikipedia.org/wiki/Branches_of_science and quickly jump to a conclusion that just because somebody with a sociology or meteorology major had trouble finding good work, domestic tech companies should be barred from bringing in more STEM majors on H1-B.
If tech companies were less focused on H1-Bs in particular, and were simply advocating for more high skill workers to be given green cards, I'd have an easier time taking them at their word. But they're not. They only want people admitted under terms that strip them of negotiating power, and there's no publicly defensible reason for that.
I mean, the optics are just terrible. In the long run, I don't see how this doesn't come back to bite the companies involved.
For employment-based green cards you generally have to get PERM labor certification (where the sponsoring employer literally advertises your job and has to show that there aren't American citizens/green card holders who can do it). That takes a while on its own (weeks, generally months).
Then depending on your education/experience, you get a date which corresponds to your position in an immigrant visa queue. The more education/experience you have the higher the queue you can sit in, and it's done by birth country (not citizenship). There are separate queues for China, India, Mexico, Philippines, and "everywhere else." If you have a graduate degree, significant job experience directly related to the US position, or some skill the lawyers can pass off as highly rare/sought after, you might end up in the EB-1/EB-2 queues which are quite short (if you entered the queue today you'd already be at the front). In which case the processing time might only be a few weeks/months.
Or you could end up in the EB-3 queue (bachelor's or equivalent experience a.k.a. many software engineers). Right now people who entered the queue 2 years ago are at the front if they're not from China/India/Mexico/Philippines (http://travel.state.gov/content/visas/english/law-and-policy...), 4 years ago for China, and 11 years ago for India.
Once you get to the front of that queue, you need to "adjust status" which means a physical exam, fingerprinting, and other busy work none of which appear to be based on country of origin. You could end up here for a few months or over a year, it's hard to know until you find out what USCIS service center is processing your case and can look up historical data. Until you get to the end of this you're technically still bound to your employer though there are some loopholes. Adjustment of status can take sufficiently long that the government passed a law in 2000 allowing green card petitions in this state to be fully portable across employers after 180 days.
Most likely this. When you have a horizontally sharded MySQL database that spans multiple datacenters - managing replication, failover and scaling out is not something you would expect most developers to be able to handle.
Let alone fine-tuning various kernel parameters, in depth monitoring and other performance tunings.
EDIT: Sure most experienced developers would have a high level and abstract idea about various things that may be outta whack - but it takes some one with expertise in the field to go beyond guesses.
Most of the software we use hasn't existed long enough for real specialization. Hell, there are still people who were alive before software existed.
If you ask me, the real problem was whatever legal technicalities allowed vendors to create certification programs for "experts" using their own software.
Managing databases is an operational overhead. You want to minimize expenditure on it. Developers create IP. You want to maximize investment into that.
A software developer cannot be asked to manage a linux database; I mean she can, but that is not what she is good at. Conversely, an IT person cannot be asked to architect the backed of a payment gateway system. Of course there is some overlap (devops is what comes to mind). I'm guessing that most of FB/MS employees are probably developers, so when they mention IT workers in the same breath as shortage at FB/MS, they are exposing their ignorance.
Furthermore, the paper itself seems to be published as a "report" on the page of a dubious organizations. Come on journalists, please do some actual journalism! Ask more people than those who confirm what your story wants to show. Find and determine the truth of the story; that is what you are paid for!
edit: as I suspected, most of the funding for this "institute" comes from labor unions. http://en.wikipedia.org/wiki/Economic_Policy_Institute#Fundi...