Off to the Microsoft PDC. For anyone who might actually find my BLOG and know what the PDC is you might realize its a little early - the PDC starts on the October 19. Well you are correct, I will be playing golf in Palm Springs, CA with by brothers (early in the week) and some old Microsoft buddies (later in the week). That way I will be well rested for the next project we are going to tackle work.
This project has been designated as one where will use Satyam's services. This should prove a unique challenge to the development cycle, since as I understand their business model, they like to take parts (if not most) of the project offshore. I think there are two types of projects; those which you can afford to send offshore and those you can not. The projects that make good candidates for offshore work, in my opinion, are ones which are well defined and where you don't mind loosing the intellectual property you gain by doing the devleopment yourself. Since the only reason we are re-writing this system is because it is written using an unsupported technology, this seems like a pretty good case to let this go offshore. Unfortunately, for reasons before my ownership, it appears that we are going to use Satyam in a more T&E role.
Which gets me thinking a little more...is just knowing how the system is constructed considered intelectual property? What I mean is, once the system is delivered is it done? Certainly not. So if you did not write the system, how on do you plan on maintaining it? I mean certainly anyone can read the code, but is the code maintainable? Are you able to understand the intent of the person who wrote the system, so that as you update the system you aren't making things worse? What about the "not grown here" mentality you run into? It would be interesting to talk to folks who have moved projects offshore on how they solved these problems.
Fore!
11:01:40 PM 
|
|
