I am a Rose undrgrad and am now working through a Masters at another University after working in industry for a few years. More than anything Rose students are in such high demand that companies continue to pull out all the stops to hire them. Each year Rose graduates approximately 400 students while attracting over 300 companies seeking their services. Moreover, since the early 90's Rose has achieved a 100% success rate of getting its graduates jobs or into graduate school.
As an anecdote when I was a senior there I had 40+ interviews and 8 offers across the country for full-time employment.
Lastly, Rose is excellent at preparing students for engineering in the real-world.
Offshore development is both good and bad. The toughest part is not being able to sit face-to-face for development discussions. The second hardest part is overcoming language and cultural barriers. The best part is that you can get some highly productive developers for a very low cost. Here are some tips for making it work:
- Hold a weekly conference call with your local and offshore developers to discuss progress. - Stay in phone contact daily with one or more of the developers offshore. - Use cheap PC video to add a dimension of being there when possible. - Make sure you have a solid configuration management and testing plan. Your offshore developers should be able to access your bug tracking and requirements databases just as your local developers do. Plus they must have equal access to your source control systems. - Iterative development and constant integration are key. This finds problems sooner which is key with offshore developers. - Make sure you pound home over and over the reason for the project. Offshore developers are fabulous at taking a well defined spec, coding it up, and checking it in. However, do not expect them to understand your customer (some will but my experience is that these are few - mostly because of the business culture differences). - That actually leads to a huge key: Define your requirements as much as possible. Even more so give them detailed design documents.
Offshore developers can be great, but you must work very hard to integrate them into your team and even harder at continually managing the project.
Remember, if they get stuck at 10am their time you can't answer them until 12 or so hours later your time and they can't start work off of your answer for another 12 hours. So you just lost a day.
Check out Remote View. It's a tool designed for really large satellite images, but can be used for a any standard type of image. This tool is optimized for HUGE images upwards of 1GB apiece. I've had a lot of luck with it.
Slashdot Mirror
I am a Rose undrgrad and am now working through a Masters at another University after working in industry for a few years. More than anything Rose students are in such high demand that companies continue to pull out all the stops to hire them. Each year Rose graduates approximately 400 students while attracting over 300 companies seeking their services. Moreover, since the early 90's Rose has achieved a 100% success rate of getting its graduates jobs or into graduate school.
As an anecdote when I was a senior there I had 40+ interviews and 8 offers across the country for full-time employment.
Lastly, Rose is excellent at preparing students for engineering in the real-world.
Offshore development is both good and bad. The toughest part is not being able to sit face-to-face for development discussions. The second hardest part is overcoming language and cultural barriers. The best part is that you can get some highly productive developers for a very low cost. Here are some tips for making it work:
- Hold a weekly conference call with your local and offshore developers to discuss progress.
- Stay in phone contact daily with one or more of the developers offshore.
- Use cheap PC video to add a dimension of being there when possible.
- Make sure you have a solid configuration management and testing plan. Your offshore developers should be able to access your bug tracking and requirements databases just as your local developers do. Plus they must have equal access to your source control systems.
- Iterative development and constant integration are key. This finds problems sooner which is key with offshore developers.
- Make sure you pound home over and over the reason for the project. Offshore developers are fabulous at taking a well defined spec, coding it up, and checking it in. However, do not expect them to understand your customer (some will but my experience is that these are few - mostly because of the business culture differences).
- That actually leads to a huge key: Define your requirements as much as possible. Even more so give them detailed design documents.
Offshore developers can be great, but you must work very hard to integrate them into your team and even harder at continually managing the project.
Remember, if they get stuck at 10am their time you can't answer them until 12 or so hours later your time and they can't start work off of your answer for another 12 hours. So you just lost a day.
Good Luck,
Travis Sparks
Check out Remote View. It's a tool designed for really large satellite images, but can be used for a any standard type of image. This tool is optimized for HUGE images upwards of 1GB apiece. I've had a lot of luck with it.