Slashdot Mirror
Extreme Telecommuting
wiredog writes: "The Washington Post has an article about a company in Chantilly Virginia, most of whose programmers telecommute from Novosibirsk, Russia." Anyone out there in a similarly distant job?
← Back to Stories (view on slashdot.org)
The only reason this company is doing it is because they can pay the Russians the equivalent of minimum wage. ($1000/month /160 hours = $6.25/hour if they only work 40 hours/week!). There's nothign admirable about this company.
... because their competitors would have them arrested.
It's the American Way.
--
E_NOSIG
I telecommute - I could be dealing with a customer in Belgium, in Denver, CO or to the company down the street from my house (in Buffalo, NY) - who cares as far as I'm concerned? I'm sitting in my office @ home and I could be dealing with a client on Pluto, doesn't change much for me..
;-)
See, that's the whole point, telecommuting - you can work from anywhere. Who approves these submissions and why haven't they been shot?
I went to a guest architecture lecture (my wife's in grad school) recently where the (US-bound) speaker had collaborated with an architect in Finland for a particular contest. He attributed much of their success in winning the project to that partnership; they could work almost twice as much within the tight deadline over the other competitors, trading the work off as daylight reached the respective timezones.
My company has recently been working on a project in France which has had some of our workers colocated there. While it can be frustrating if you need answers (and they've already gone home) to have to wait until they wake up again, but OTOH when timelines were tight trading the development work back and forth more than made up for the overhead of communication.
IIRC, No Magic Inc. offers (or at least used to offer) Lithuanian Java/C++ programmers for hire. [And not only do you get the alternate-timezone benefit, but they were cheap, too...something like $25/hour (this was 2 years ago...I dunno what their pricing is like now).
Lomeiko acknowledged a problem with vacations. Under Russian law each employee is entitled to 24 days of paid holiday, but Plesk can't afford the disruption that would bring, so the company tries to "limit" vacations to 10 days. The work ethic here is pretty intense.
I'm not one to crow about exploitation, but come on: they're paying Russian wages, can't they accept Russian vacations? It's not like 24 days is that much anyway, for most of the world.
sulli
RTFJ.
I mean, the position and authority sounded great. But who'd want to manage a group of people halfway across the globe? Even if there were no language barrier to overcome, I'd be "managing" a group of programmers whose clock was off of mine by nearly twelve hours. We'd do almost all our interaction by e-mail, asynchronously.
I know from having worked only in production that unless you can meet face-to-face with your immediate supervisor on a regular basis, it's difficult if not impossible to develop any cohesion as a team. I could have told those guys what to do, and I'm sure they'd have done it, but I'd never have been able to get a sense of who they were and what they were truly capable of. I'd be managing a big black box.
Sending programming labor overseas is no new concept, and it has obvious financial advantages. But practically speaking, I'd much rather have a highly-paid programmer next door to me than an inexpensive one several thousand miles away.
> There is something wrong when a "U.S. company" can actively discriminate against Americans in its hiring practices (how many of those jobs were offered to U.S. citizens?) while circumventing OSHA, FLSA, and other labor regulations.
Here's the fatal flaw in your argument, pointed up by the simple question, "how many of those jobs were offered to U.S. citizens?" In response, how many of those jobs were offered to British, or German, or Japanese citizens? The answer is "none", and for exactly the same reason. They aren't discriminating against Americans, they're discriminating against expensive programmers. Yes, it sucks that they can take a job offshore and get it done for less money, but that's not a new practice by any means, and it's a short-term problem anyway. Your solution has an abvious flaw as well. If the U.S. government forces U.S. companies to use U.S. talent only, they're going to have to charge more for the finished product. That means that they can't compete as well with U.S. companies who use offshore talent (which your solution will fix), but it also means they can't compete as well with Russian companies who use Russian programmers. It's easy to say that that's not a problem, since the U.S. software is better, but that's just pro-U.S. bias, and besides, what if U.S. companies want to sell their software to the rest of the world?
> How would you like to go to a job interview and be told "you have to work 55 hours per week for $12,000 per year or we'll give this job to some guy in Kiev"?
Again, this argument doesn't make any sense, on two levels. Firstly, to compare apples to apples (we'll use year 2000-value apples), you'd have to say, "you have to work 55 hours per week for $134,000 a year in purchasing power, or we'll give this job to some guy in Kiev" which is the equivalent earning power. Conversely, as companies compete in the world market, these nests of underpaid resources will rise to levels more in line with the U.S. and other countries. For now, there are lots of programmers willing to work for peanuts in Russia and India, but the talent pool is going to get tapped eventually to the point where salaries will have to rise, as companies battle for the talent in these locations. For now, there is a wild discrepancy between the developed world and the developing world, and because of that the U.S. job market is going to suffer. While it seems to make sense on the surface, your solution is historically referred to as "economic isolationism", and our country's history shows that it simply does not work in the long term. See the automotive industry for a pointed example, or the garment industry, wherein government protections drove prices so far out of line with reality that, instead of forcing U.S. companies to hire US-ians, it forced many of the companies to move to other countries entirely, which, of course, did not help the U.S. workers who now had no company from which to demand a job. The only way to solve such an imbalance is to adjust prices, and again, historically prices don't fall on the whole. What will end up happening is that prices for good programmers outside the U.S. will rise as local demand exceeds local supply.
In short, while it's a very feel-good gesture, government protection of U.S. jobs will not be worth the stunting of the U.S. programming industry that such sanctions will engender.
Virg