Well, it can work out but if the project is in a time crunch, good luck. Are you simply contracting the development project out to a offshore partner? Or are you building an offshore team that will work for you in a longer term?
I think infrastructure is always the biggest issue when dealing with team away from the headquarter. Not in terms of language issue but simply time difference, computer networks issues (VPN, etc.), and human-to-human interaction issues. Not to mention project management of trying to making sure everyone is in sync. in terms of requirement.
BTW, I think requirement is probably the key here. I think it will almost be impossible to hammer down the requirement for a particular development work if not all the players are in the same physical location. Including the Subject matter expert, technologist, architect, business users, etc.
IMHO, there will be a lot of hidden costs involved in working with off shore teams. Especially for new development work.
the paper stated that if a startup follows the common ground of implemeting their system in a popular language such as C, C++, or Java then the startup is no better than the 'average' startup that uses the same technology is funny and wrong.
its not about whether use LISP or Java or whatever. But the idea and the way it is implemented counts. And yes, if the application being used can't be maintained because the technology of choice is not very common then that would work against the technology selection itself.
Linux community should be fairly happy about this move from IBM. This can help Linux to become a stronger contenter as the platform of the choice for developing enterprise wide web systems.
Slashdot Mirror
Well, it can work out but if the project is in a time crunch, good luck. Are you simply contracting the development project out to a offshore partner? Or are you building an offshore team that will work for you in a longer term?
I think infrastructure is always the biggest issue when dealing with team away from the headquarter. Not in terms of language issue but simply time difference, computer networks issues (VPN, etc.), and human-to-human interaction issues. Not to mention project management of trying to making sure everyone is in sync. in terms of requirement.
BTW, I think requirement is probably the key here. I think it will almost be impossible to hammer down the requirement for a particular development work if not all the players are in the same physical location. Including the Subject matter expert, technologist, architect, business users, etc.
IMHO, there will be a lot of hidden costs involved in working with off shore teams. Especially for new development work.
Good luck!
-Joe
the paper stated that if a startup follows the common ground of implemeting their system in a popular language such as C, C++, or Java then the startup is no better than the 'average' startup that uses the same technology is funny and wrong.
its not about whether use LISP or Java or whatever. But the idea and the way it is implemented counts. And yes, if the application being used can't be maintained because the technology of choice is not very common then that would work against the technology selection itself.
Linux community should be fairly happy about this move from IBM. This can help Linux to become a stronger contenter as the platform of the choice for developing enterprise wide web systems.