I have hands-on experience leading remote development work. I have to say that it is definitely not a walk in the park. 30%-%40 of my time was dedicated to communication.... back and forth between all the offices involved. Its tough work and is only successful when you have the buy in and effort from everyone. i was wokring 16 hour days just to make sure things ran smoothly.... can't do that kind of effort for too long. THings worked out ok in the end.
I have also seen the flip side, where the product/system developed outside the US completely sucked. I don't lay the blame entirely on the company that did the work. Anyone with half a brain could have identified and corrected the issues before the project came to a standstill, but the folks back here in America didn't have the inclination to do it. You snooze, you lose.
You forget that a lot of the H1B workers cam over when times were great and companies couldn't fill positions fast enough.
Nowadays, no one is hiring H1Bs (unless they have a skill they cannot find elsewhere) and companies are hiring US workers.
Just because there are layoffs now does not mean that you should layoff H1Bs in favor of US citizend. You lay off the people who suck or who don;t have the skill
I was architect for a project with a team of 25 folks. 15 in Hyderabad, India and 10 in Boston. We used StarTeam as the source repository. I have to say it kicks ass!!!
Starteam has got a built in bug tracking system, provides extended support for build labels, branching etc. They provide two clients (1) Windows client (2) Web client (HTML, Javascript etc.). So basically, the server can be configured to listen on port xxxx or can be accessed by a web server which will run the web client.
The downside to it is that it has piss-poor diff-merge tools. But we used Araxis (which really really kicks ass) for merging files.
This setup and some basic procedures let us do continuous builds without too much of a headache.
Slashdot Mirror
I have hands-on experience leading remote development work. I have to say that it is definitely not a walk in the park. 30%-%40 of my time was dedicated to communication .... back and forth between all the offices involved. Its tough work and is only successful when you have the buy in and effort from everyone. i was wokring 16 hour days just to make sure things ran smoothly .... can't do that kind of effort for too long. THings worked out ok in the end.
I have also seen the flip side, where the product/system developed outside the US completely sucked. I don't lay the blame entirely on the company that did the work. Anyone with half a brain could have identified and corrected the issues before the project came to a standstill, but the folks back here in America didn't have the inclination to do it. You snooze, you lose.
You forget that a lot of the H1B workers cam over when times were great and companies couldn't fill positions fast enough.
Nowadays, no one is hiring H1Bs (unless they have a skill they cannot find elsewhere) and companies are hiring US workers.
Just because there are layoffs now does not mean that you should layoff H1Bs in favor of US citizend. You lay off the people who suck or who don;t have the skill
I was architect for a project with a team of 25 folks. 15 in Hyderabad, India and 10 in Boston. We used StarTeam as the source repository. I have to say it kicks ass!!!
Starteam has got a built in bug tracking system, provides extended support for build labels, branching etc. They provide two clients (1) Windows client (2) Web client (HTML, Javascript etc.). So basically, the server can be configured to listen on port xxxx or can be accessed by a web server which will run the web client.
The downside to it is that it has piss-poor diff-merge tools. But we used Araxis (which really really kicks ass) for merging files.
This setup and some basic procedures let us do continuous builds without too much of a headache.